Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477
  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 TPS6507X
  103. tristate "TPS6507x Power Management / Touch Screen chips"
  104. select MFD_CORE
  105. depends on I2C
  106. help
  107. If you say yes here you get support for the TPS6507x series of
  108. Power Management / Touch Screen chips. These include voltage
  109. regulators, lithium ion/polymer battery charging, touch screen
  110. and other features that are often used in portable devices.
  111. This driver can also be built as a module. If so, the module
  112. will be called tps6507x.
  113. config MENELAUS
  114. bool "Texas Instruments TWL92330/Menelaus PM chip"
  115. depends on I2C=y && ARCH_OMAP2
  116. help
  117. If you say yes here you get support for the Texas Instruments
  118. TWL92330/Menelaus Power Management chip. This include voltage
  119. regulators, Dual slot memory card transceivers, real-time clock
  120. and other features that are often used in portable devices like
  121. cell phones and PDAs.
  122. config TWL4030_CORE
  123. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  124. depends on I2C=y && GENERIC_HARDIRQS
  125. help
  126. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  127. This core driver provides register access and IRQ handling
  128. facilities, and registers devices for the various functions
  129. so that function-specific drivers can bind to them.
  130. These multi-function chips are found on many OMAP2 and OMAP3
  131. boards, providing power management, RTC, GPIO, keypad, a
  132. high speed USB OTG transceiver, an audio codec (on most
  133. versions) and many other features.
  134. config TWL4030_POWER
  135. bool "Support power resources on TWL4030 family chips"
  136. depends on TWL4030_CORE && ARM
  137. help
  138. Say yes here if you want to use the power resources on the
  139. TWL4030 family chips. Most of these resources are regulators,
  140. which have a separate driver; some are control signals, such
  141. as clock request handshaking.
  142. This driver uses board-specific data to initialize the resources
  143. and load scripts controling which resources are switched off/on
  144. or reset when a sleep, wakeup or warm reset event occurs.
  145. config TWL4030_CODEC
  146. bool
  147. depends on TWL4030_CORE
  148. select MFD_CORE
  149. default n
  150. config MFD_TC35892
  151. bool "Support Toshiba TC35892"
  152. depends on I2C=y && GENERIC_HARDIRQS
  153. select MFD_CORE
  154. help
  155. Support for the Toshiba TC35892 I/O Expander.
  156. This driver provides common support for accessing the device,
  157. additional drivers must be enabled in order to use the
  158. functionality of the device.
  159. config MFD_TMIO
  160. bool
  161. default n
  162. config TMIO_MMC_DMA
  163. bool
  164. select DMA_ENGINE
  165. select DMADEVICES
  166. config MFD_T7L66XB
  167. bool "Support Toshiba T7L66XB"
  168. depends on ARM && HAVE_CLK
  169. select MFD_CORE
  170. select MFD_TMIO
  171. help
  172. Support for Toshiba Mobile IO Controller T7L66XB
  173. config MFD_TC6387XB
  174. bool "Support Toshiba TC6387XB"
  175. depends on ARM && HAVE_CLK
  176. select MFD_CORE
  177. select MFD_TMIO
  178. help
  179. Support for Toshiba Mobile IO Controller TC6387XB
  180. config MFD_TC6393XB
  181. bool "Support Toshiba TC6393XB"
  182. depends on GPIOLIB && ARM
  183. select MFD_CORE
  184. select MFD_TMIO
  185. help
  186. Support for Toshiba Mobile IO Controller TC6393XB
  187. config PMIC_DA903X
  188. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  189. depends on I2C=y
  190. help
  191. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  192. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  193. usually found on PXA processors-based platforms. This includes
  194. the I2C driver and the core APIs _only_, you have to select
  195. individual components like LCD backlight, voltage regulators,
  196. LEDs and battery-charger under the corresponding menus.
  197. config PMIC_ADP5520
  198. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  199. depends on I2C=y
  200. help
  201. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  202. Multifunction Power Management IC. This includes
  203. the I2C driver and the core APIs _only_, you have to select
  204. individual components like LCD backlight, LEDs, GPIOs and Kepad
  205. under the corresponding menus.
  206. config MFD_MAX8925
  207. bool "Maxim Semiconductor MAX8925 PMIC Support"
  208. depends on I2C=y && GENERIC_HARDIRQS
  209. select MFD_CORE
  210. help
  211. Say yes here to support for Maxim Semiconductor MAX8925. This is
  212. a Power Management IC. This driver provies common support for
  213. accessing the device, additional drivers must be enabled in order
  214. to use the functionality of the device.
  215. config MFD_WM8400
  216. tristate "Support Wolfson Microelectronics WM8400"
  217. select MFD_CORE
  218. depends on I2C
  219. help
  220. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  221. CODEC. This driver provides common support for accessing
  222. the device, additional drivers must be enabled in order to use
  223. the functionality of the device.
  224. config MFD_WM831X
  225. bool "Support Wolfson Microelectronics WM831x/2x PMICs"
  226. select MFD_CORE
  227. depends on I2C=y && GENERIC_HARDIRQS
  228. help
  229. Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
  230. This driver provides common support for accessing the device,
  231. additional drivers must be enabled in order to use the
  232. functionality of the device.
  233. config MFD_WM8350
  234. bool
  235. depends on GENERIC_HARDIRQS
  236. config MFD_WM8350_CONFIG_MODE_0
  237. bool
  238. depends on MFD_WM8350
  239. config MFD_WM8350_CONFIG_MODE_1
  240. bool
  241. depends on MFD_WM8350
  242. config MFD_WM8350_CONFIG_MODE_2
  243. bool
  244. depends on MFD_WM8350
  245. config MFD_WM8350_CONFIG_MODE_3
  246. bool
  247. depends on MFD_WM8350
  248. config MFD_WM8351_CONFIG_MODE_0
  249. bool
  250. depends on MFD_WM8350
  251. config MFD_WM8351_CONFIG_MODE_1
  252. bool
  253. depends on MFD_WM8350
  254. config MFD_WM8351_CONFIG_MODE_2
  255. bool
  256. depends on MFD_WM8350
  257. config MFD_WM8351_CONFIG_MODE_3
  258. bool
  259. depends on MFD_WM8350
  260. config MFD_WM8352_CONFIG_MODE_0
  261. bool
  262. depends on MFD_WM8350
  263. config MFD_WM8352_CONFIG_MODE_1
  264. bool
  265. depends on MFD_WM8350
  266. config MFD_WM8352_CONFIG_MODE_2
  267. bool
  268. depends on MFD_WM8350
  269. config MFD_WM8352_CONFIG_MODE_3
  270. bool
  271. depends on MFD_WM8350
  272. config MFD_WM8350_I2C
  273. bool "Support Wolfson Microelectronics WM8350 with I2C"
  274. select MFD_WM8350
  275. depends on I2C=y && GENERIC_HARDIRQS
  276. help
  277. The WM8350 is an integrated audio and power management
  278. subsystem with watchdog and RTC functionality for embedded
  279. systems. This option enables core support for the WM8350 with
  280. I2C as the control interface. Additional options must be
  281. selected to enable support for the functionality of the chip.
  282. config MFD_WM8994
  283. bool "Support Wolfson Microelectronics WM8994"
  284. select MFD_CORE
  285. depends on I2C=y && GENERIC_HARDIRQS
  286. help
  287. The WM8994 is a highly integrated hi-fi CODEC designed for
  288. smartphone applicatiosn. As well as audio functionality it
  289. has on board GPIO and regulator functionality which is
  290. supported via the relevant subsystems. This driver provides
  291. core support for the WM8994, in order to use the actual
  292. functionaltiy of the device other drivers must be enabled.
  293. config MFD_PCF50633
  294. tristate "Support for NXP PCF50633"
  295. depends on I2C
  296. help
  297. Say yes here if you have NXP PCF50633 chip on your board.
  298. This core driver provides register access and IRQ handling
  299. facilities, and registers devices for the various functions
  300. so that function-specific drivers can bind to them.
  301. config MFD_MC13783
  302. tristate "Support Freescale MC13783"
  303. depends on SPI_MASTER
  304. select MFD_CORE
  305. help
  306. Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
  307. This driver provides common support for accessing the device,
  308. additional drivers must be enabled in order to use the
  309. functionality of the device.
  310. config PCF50633_ADC
  311. tristate "Support for NXP PCF50633 ADC"
  312. depends on MFD_PCF50633
  313. help
  314. Say yes here if you want to include support for ADC in the
  315. NXP PCF50633 chip.
  316. config PCF50633_GPIO
  317. tristate "Support for NXP PCF50633 GPIO"
  318. depends on MFD_PCF50633
  319. help
  320. Say yes here if you want to include support GPIO for pins on
  321. the PCF50633 chip.
  322. config AB3100_CORE
  323. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  324. depends on I2C=y
  325. default y if ARCH_U300
  326. help
  327. Select this to enable the AB3100 Mixed Signal IC core
  328. functionality. This connects to a AB3100 on the I2C bus
  329. and expose a number of symbols needed for dependent devices
  330. to read and write registers and subscribe to events from
  331. this multi-functional IC. This is needed to use other features
  332. of the AB3100 such as battery-backed RTC, charging control,
  333. LEDs, vibrator, system power and temperature, power management
  334. and ALSA sound.
  335. config AB3100_OTP
  336. tristate "ST-Ericsson AB3100 OTP functions"
  337. depends on AB3100_CORE
  338. default y if AB3100_CORE
  339. help
  340. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  341. programmable memory) support. This exposes a sysfs file to read
  342. out OTP values.
  343. config EZX_PCAP
  344. bool "PCAP Support"
  345. depends on GENERIC_HARDIRQS && SPI_MASTER
  346. help
  347. This enables the PCAP ASIC present on EZX Phones. This is
  348. needed for MMC, TouchScreen, Sound, USB, etc..
  349. config AB4500_CORE
  350. tristate "ST-Ericsson's AB4500 Mixed Signal Power management chip"
  351. depends on SPI
  352. help
  353. Select this option to enable access to AB4500 power management
  354. chip. This connects to U8500 on the SSP/SPI bus and exports
  355. read/write functions for the devices to get access to this chip.
  356. This chip embeds various other multimedia funtionalities as well.
  357. config MFD_TIMBERDALE
  358. tristate "Support for the Timberdale FPGA"
  359. select MFD_CORE
  360. depends on PCI && GPIOLIB
  361. ---help---
  362. This is the core driver for the timberdale FPGA. This device is a
  363. multifunction device which exposes numerous platform devices.
  364. The timberdale FPGA can be found on the Intel Atom development board
  365. for in-vehicle infontainment, called Russellville.
  366. config LPC_SCH
  367. tristate "Intel SCH LPC"
  368. depends on PCI
  369. select MFD_CORE
  370. help
  371. LPC bridge function of the Intel SCH provides support for
  372. System Management Bus and General Purpose I/O.
  373. config MFD_RDC321X
  374. tristate "Support for RDC-R321x southbridge"
  375. select MFD_CORE
  376. depends on PCI
  377. help
  378. Say yes here if you want to have support for the RDC R-321x SoC
  379. southbridge which provides access to GPIOs and Watchdog using the
  380. southbridge PCI device configuration space.
  381. config MFD_JANZ_CMODIO
  382. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  383. select MFD_CORE
  384. depends on PCI
  385. help
  386. This is the core driver for the Janz CMOD-IO PCI MODULbus
  387. carrier board. This device is a PCI to MODULbus bridge which may
  388. host many different types of MODULbus daughterboards, including
  389. CAN and GPIO controllers.
  390. endmenu
  391. menu "Multimedia Capabilities Port drivers"
  392. depends on ARCH_SA1100
  393. config MCP
  394. tristate
  395. # Interface drivers
  396. config MCP_SA11X0
  397. tristate "Support SA11x0 MCP interface"
  398. depends on ARCH_SA1100
  399. select MCP
  400. # Chip drivers
  401. config MCP_UCB1200
  402. tristate "Support for UCB1200 / UCB1300"
  403. depends on MCP
  404. config MCP_UCB1200_TS
  405. tristate "Touchscreen interface support"
  406. depends on MCP_UCB1200 && INPUT
  407. endmenu