Kconfig 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. menu "Multifunction device drivers"
  5. depends on HAS_IOMEM
  6. config MFD_CORE
  7. tristate
  8. default n
  9. config MFD_88PM860X
  10. bool "Support Marvell 88PM8606/88PM8607"
  11. depends on I2C=y && GENERIC_HARDIRQS
  12. select MFD_CORE
  13. help
  14. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  15. This includes the I2C driver and the core APIs _only_, you have to
  16. select individual components like voltage regulators, RTC and
  17. battery-charger under the corresponding menus.
  18. config MFD_SM501
  19. tristate "Support for Silicon Motion SM501"
  20. ---help---
  21. This is the core driver for the Silicon Motion SM501 multimedia
  22. companion chip. This device is a multifunction device which may
  23. provide numerous interfaces including USB host controller, USB gadget,
  24. asynchronous serial ports, audio functions, and a dual display video
  25. interface. The device may be connected by PCI or local bus with
  26. varying functions enabled.
  27. config MFD_SM501_GPIO
  28. bool "Export GPIO via GPIO layer"
  29. depends on MFD_SM501 && GPIOLIB
  30. ---help---
  31. This option uses the gpio library layer to export the 64 GPIO
  32. lines on the SM501. The platform data is used to supply the
  33. base number for the first GPIO line to register.
  34. config MFD_ASIC3
  35. bool "Support for Compaq ASIC3"
  36. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  37. select MFD_CORE
  38. ---help---
  39. This driver supports the ASIC3 multifunction chip found on many
  40. PDAs (mainly iPAQ and HTC based ones)
  41. config MFD_SH_MOBILE_SDHI
  42. bool "Support for SuperH Mobile SDHI"
  43. depends on SUPERH || ARCH_SHMOBILE
  44. select MFD_CORE
  45. select TMIO_MMC_DMA
  46. ---help---
  47. This driver supports the SDHI hardware block found in many
  48. SuperH Mobile SoCs.
  49. config MFD_DAVINCI_VOICECODEC
  50. tristate
  51. select MFD_CORE
  52. config MFD_DM355EVM_MSP
  53. bool "DaVinci DM355 EVM microcontroller"
  54. depends on I2C && MACH_DAVINCI_DM355_EVM
  55. help
  56. This driver supports the MSP430 microcontroller used on these
  57. boards. MSP430 firmware manages resets and power sequencing,
  58. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  59. config HTC_EGPIO
  60. bool "HTC EGPIO support"
  61. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  62. help
  63. This driver supports the CPLD egpio chip present on
  64. several HTC phones. It provides basic support for input
  65. pins, output pins, and irqs.
  66. config HTC_PASIC3
  67. tristate "HTC PASIC3 LED/DS1WM chip support"
  68. select MFD_CORE
  69. help
  70. This core driver provides register access for the LED/DS1WM
  71. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  72. HTC Magician devices, respectively. Actual functionality is
  73. handled by the leds-pasic3 and ds1wm drivers.
  74. config HTC_I2CPLD
  75. bool "HTC I2C PLD chip support"
  76. depends on I2C=y && GPIOLIB
  77. help
  78. If you say yes here you get support for the supposed CPLD
  79. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  80. This device provides input and output GPIOs through an I2C
  81. interface to one or more sub-chips.
  82. config UCB1400_CORE
  83. tristate "Philips UCB1400 Core driver"
  84. depends on AC97_BUS
  85. depends on GPIOLIB
  86. help
  87. This enables support for the Philips UCB1400 core functions.
  88. The UCB1400 is an AC97 audio codec.
  89. To compile this driver as a module, choose M here: the
  90. module will be called ucb1400_core.
  91. config TPS65010
  92. tristate "TPS6501x Power Management chips"
  93. depends on I2C && GPIOLIB
  94. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  95. help
  96. If you say yes here you get support for the TPS6501x series of
  97. Power Management chips. These include voltage regulators,
  98. lithium ion/polymer battery charging, and other features that
  99. are often used in portable devices like cell phones and cameras.
  100. This driver can also be built as a module. If so, the module
  101. will be called tps65010.
  102. config MENELAUS
  103. bool "Texas Instruments TWL92330/Menelaus PM chip"
  104. depends on I2C=y && ARCH_OMAP2
  105. help
  106. If you say yes here you get support for the Texas Instruments
  107. TWL92330/Menelaus Power Management chip. This include voltage
  108. regulators, Dual slot memory card transceivers, real-time clock
  109. and other features that are often used in portable devices like
  110. cell phones and PDAs.
  111. config TWL4030_CORE
  112. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  113. depends on I2C=y && GENERIC_HARDIRQS
  114. help
  115. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  116. This core driver provides register access and IRQ handling
  117. facilities, and registers devices for the various functions
  118. so that function-specific drivers can bind to them.
  119. These multi-function chips are found on many OMAP2 and OMAP3
  120. boards, providing power management, RTC, GPIO, keypad, a
  121. high speed USB OTG transceiver, an audio codec (on most
  122. versions) and many other features.
  123. config TWL4030_POWER
  124. bool "Support power resources on TWL4030 family chips"
  125. depends on TWL4030_CORE && ARM
  126. help
  127. Say yes here if you want to use the power resources on the
  128. TWL4030 family chips. Most of these resources are regulators,
  129. which have a separate driver; some are control signals, such
  130. as clock request handshaking.
  131. This driver uses board-specific data to initialize the resources
  132. and load scripts controling which resources are switched off/on
  133. or reset when a sleep, wakeup or warm reset event occurs.
  134. config TWL4030_CODEC
  135. bool
  136. depends on TWL4030_CORE
  137. select MFD_CORE
  138. default n
  139. config MFD_TMIO
  140. bool
  141. default n
  142. config TMIO_MMC_DMA
  143. bool
  144. select DMA_ENGINE
  145. select DMADEVICES
  146. config MFD_T7L66XB
  147. bool "Support Toshiba T7L66XB"
  148. depends on ARM && HAVE_CLK
  149. select MFD_CORE
  150. select MFD_TMIO
  151. help
  152. Support for Toshiba Mobile IO Controller T7L66XB
  153. config MFD_TC6387XB
  154. bool "Support Toshiba TC6387XB"
  155. depends on ARM && HAVE_CLK
  156. select MFD_CORE
  157. select MFD_TMIO
  158. help
  159. Support for Toshiba Mobile IO Controller TC6387XB
  160. config MFD_TC6393XB
  161. bool "Support Toshiba TC6393XB"
  162. depends on GPIOLIB && ARM
  163. select MFD_CORE
  164. select MFD_TMIO
  165. help
  166. Support for Toshiba Mobile IO Controller TC6393XB
  167. config PMIC_DA903X
  168. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  169. depends on I2C=y
  170. help
  171. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  172. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  173. usually found on PXA processors-based platforms. This includes
  174. the I2C driver and the core APIs _only_, you have to select
  175. individual components like LCD backlight, voltage regulators,
  176. LEDs and battery-charger under the corresponding menus.
  177. config PMIC_ADP5520
  178. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  179. depends on I2C=y
  180. help
  181. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  182. Multifunction Power Management IC. This includes
  183. the I2C driver and the core APIs _only_, you have to select
  184. individual components like LCD backlight, LEDs, GPIOs and Kepad
  185. under the corresponding menus.
  186. config MFD_MAX8925
  187. bool "Maxim Semiconductor MAX8925 PMIC Support"
  188. depends on I2C=y && GENERIC_HARDIRQS
  189. select MFD_CORE
  190. help
  191. Say yes here to support for Maxim Semiconductor MAX8925. This is
  192. a Power Management IC. This driver provies common support for
  193. accessing the device, additional drivers must be enabled in order
  194. to use the functionality of the device.
  195. config MFD_WM8400
  196. tristate "Support Wolfson Microelectronics WM8400"
  197. select MFD_CORE
  198. depends on I2C
  199. help
  200. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  201. CODEC. This driver provides common support for accessing
  202. the device, additional drivers must be enabled in order to use
  203. the functionality of the device.
  204. config MFD_WM831X
  205. bool "Support Wolfson Microelectronics WM831x/2x PMICs"
  206. select MFD_CORE
  207. depends on I2C=y && GENERIC_HARDIRQS
  208. help
  209. Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
  210. This driver provides common support for accessing the device,
  211. additional drivers must be enabled in order to use the
  212. functionality of the device.
  213. config MFD_WM8350
  214. bool
  215. depends on GENERIC_HARDIRQS
  216. config MFD_WM8350_CONFIG_MODE_0
  217. bool
  218. depends on MFD_WM8350
  219. config MFD_WM8350_CONFIG_MODE_1
  220. bool
  221. depends on MFD_WM8350
  222. config MFD_WM8350_CONFIG_MODE_2
  223. bool
  224. depends on MFD_WM8350
  225. config MFD_WM8350_CONFIG_MODE_3
  226. bool
  227. depends on MFD_WM8350
  228. config MFD_WM8351_CONFIG_MODE_0
  229. bool
  230. depends on MFD_WM8350
  231. config MFD_WM8351_CONFIG_MODE_1
  232. bool
  233. depends on MFD_WM8350
  234. config MFD_WM8351_CONFIG_MODE_2
  235. bool
  236. depends on MFD_WM8350
  237. config MFD_WM8351_CONFIG_MODE_3
  238. bool
  239. depends on MFD_WM8350
  240. config MFD_WM8352_CONFIG_MODE_0
  241. bool
  242. depends on MFD_WM8350
  243. config MFD_WM8352_CONFIG_MODE_1
  244. bool
  245. depends on MFD_WM8350
  246. config MFD_WM8352_CONFIG_MODE_2
  247. bool
  248. depends on MFD_WM8350
  249. config MFD_WM8352_CONFIG_MODE_3
  250. bool
  251. depends on MFD_WM8350
  252. config MFD_WM8350_I2C
  253. bool "Support Wolfson Microelectronics WM8350 with I2C"
  254. select MFD_WM8350
  255. depends on I2C=y && GENERIC_HARDIRQS
  256. help
  257. The WM8350 is an integrated audio and power management
  258. subsystem with watchdog and RTC functionality for embedded
  259. systems. This option enables core support for the WM8350 with
  260. I2C as the control interface. Additional options must be
  261. selected to enable support for the functionality of the chip.
  262. config MFD_WM8994
  263. bool "Support Wolfson Microelectronics WM8994"
  264. select MFD_CORE
  265. depends on I2C=y && GENERIC_HARDIRQS
  266. help
  267. The WM8994 is a highly integrated hi-fi CODEC designed for
  268. smartphone applicatiosn. As well as audio functionality it
  269. has on board GPIO and regulator functionality which is
  270. supported via the relevant subsystems. This driver provides
  271. core support for the WM8994, in order to use the actual
  272. functionaltiy of the device other drivers must be enabled.
  273. config MFD_PCF50633
  274. tristate "Support for NXP PCF50633"
  275. depends on I2C
  276. help
  277. Say yes here if you have NXP PCF50633 chip on your board.
  278. This core driver provides register access and IRQ handling
  279. facilities, and registers devices for the various functions
  280. so that function-specific drivers can bind to them.
  281. config MFD_MC13783
  282. tristate "Support Freescale MC13783"
  283. depends on SPI_MASTER
  284. select MFD_CORE
  285. help
  286. Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
  287. This driver provides common support for accessing the device,
  288. additional drivers must be enabled in order to use the
  289. functionality of the device.
  290. config PCF50633_ADC
  291. tristate "Support for NXP PCF50633 ADC"
  292. depends on MFD_PCF50633
  293. help
  294. Say yes here if you want to include support for ADC in the
  295. NXP PCF50633 chip.
  296. config PCF50633_GPIO
  297. tristate "Support for NXP PCF50633 GPIO"
  298. depends on MFD_PCF50633
  299. help
  300. Say yes here if you want to include support GPIO for pins on
  301. the PCF50633 chip.
  302. config AB3100_CORE
  303. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  304. depends on I2C=y
  305. default y if ARCH_U300
  306. help
  307. Select this to enable the AB3100 Mixed Signal IC core
  308. functionality. This connects to a AB3100 on the I2C bus
  309. and expose a number of symbols needed for dependent devices
  310. to read and write registers and subscribe to events from
  311. this multi-functional IC. This is needed to use other features
  312. of the AB3100 such as battery-backed RTC, charging control,
  313. LEDs, vibrator, system power and temperature, power management
  314. and ALSA sound.
  315. config AB3100_OTP
  316. tristate "ST-Ericsson AB3100 OTP functions"
  317. depends on AB3100_CORE
  318. default y if AB3100_CORE
  319. help
  320. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  321. programmable memory) support. This exposes a sysfs file to read
  322. out OTP values.
  323. config EZX_PCAP
  324. bool "PCAP Support"
  325. depends on GENERIC_HARDIRQS && SPI_MASTER
  326. help
  327. This enables the PCAP ASIC present on EZX Phones. This is
  328. needed for MMC, TouchScreen, Sound, USB, etc..
  329. config AB4500_CORE
  330. tristate "ST-Ericsson's AB4500 Mixed Signal Power management chip"
  331. depends on SPI
  332. help
  333. Select this option to enable access to AB4500 power management
  334. chip. This connects to U8500 on the SSP/SPI bus and exports
  335. read/write functions for the devices to get access to this chip.
  336. This chip embeds various other multimedia funtionalities as well.
  337. config MFD_TIMBERDALE
  338. tristate "Support for the Timberdale FPGA"
  339. select MFD_CORE
  340. depends on PCI && GPIOLIB
  341. ---help---
  342. This is the core driver for the timberdale FPGA. This device is a
  343. multifunction device which exposes numerous platform devices.
  344. The timberdale FPGA can be found on the Intel Atom development board
  345. for in-vehicle infontainment, called Russellville.
  346. config LPC_SCH
  347. tristate "Intel SCH LPC"
  348. depends on PCI
  349. select MFD_CORE
  350. help
  351. LPC bridge function of the Intel SCH provides support for
  352. System Management Bus and General Purpose I/O.
  353. endmenu
  354. menu "Multimedia Capabilities Port drivers"
  355. depends on ARCH_SA1100
  356. config MCP
  357. tristate
  358. # Interface drivers
  359. config MCP_SA11X0
  360. tristate "Support SA11x0 MCP interface"
  361. depends on ARCH_SA1100
  362. select MCP
  363. # Chip drivers
  364. config MCP_UCB1200
  365. tristate "Support for UCB1200 / UCB1300"
  366. depends on MCP
  367. config MCP_UCB1200_TS
  368. tristate "Touchscreen interface support"
  369. depends on MCP_UCB1200 && INPUT
  370. endmenu