Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. menuconfig MFD_SUPPORT
  5. bool "Multifunction device drivers"
  6. depends on HAS_IOMEM
  7. default y
  8. help
  9. Multifunction devices embed several functions (e.g. GPIOs,
  10. touchscreens, keyboards, current regulators, power management chips,
  11. etc...) in one single integrated circuit. They usually talk to the
  12. main CPU through one or more IRQ lines and low speed data busses (SPI,
  13. I2C, etc..). They appear as one single device to the main system
  14. through the data bus and the MFD framework allows for sub devices
  15. (a.k.a. functions) to appear as discrete platform devices.
  16. MFDs are typically found on embedded platforms.
  17. This option alone does not add any kernel code.
  18. if MFD_SUPPORT
  19. config MFD_CORE
  20. tristate
  21. default n
  22. config MFD_88PM860X
  23. bool "Support Marvell 88PM8606/88PM8607"
  24. depends on I2C=y && GENERIC_HARDIRQS
  25. select MFD_CORE
  26. help
  27. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  28. This includes the I2C driver and the core APIs _only_, you have to
  29. select individual components like voltage regulators, RTC and
  30. battery-charger under the corresponding menus.
  31. config MFD_SM501
  32. tristate "Support for Silicon Motion SM501"
  33. ---help---
  34. This is the core driver for the Silicon Motion SM501 multimedia
  35. companion chip. This device is a multifunction device which may
  36. provide numerous interfaces including USB host controller, USB gadget,
  37. asynchronous serial ports, audio functions, and a dual display video
  38. interface. The device may be connected by PCI or local bus with
  39. varying functions enabled.
  40. config MFD_SM501_GPIO
  41. bool "Export GPIO via GPIO layer"
  42. depends on MFD_SM501 && GPIOLIB
  43. ---help---
  44. This option uses the gpio library layer to export the 64 GPIO
  45. lines on the SM501. The platform data is used to supply the
  46. base number for the first GPIO line to register.
  47. config MFD_ASIC3
  48. bool "Support for Compaq ASIC3"
  49. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  50. select MFD_CORE
  51. ---help---
  52. This driver supports the ASIC3 multifunction chip found on many
  53. PDAs (mainly iPAQ and HTC based ones)
  54. config MFD_DAVINCI_VOICECODEC
  55. tristate
  56. select MFD_CORE
  57. config MFD_DM355EVM_MSP
  58. bool "DaVinci DM355 EVM microcontroller"
  59. depends on I2C=y && MACH_DAVINCI_DM355_EVM
  60. help
  61. This driver supports the MSP430 microcontroller used on these
  62. boards. MSP430 firmware manages resets and power sequencing,
  63. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  64. config MFD_TI_SSP
  65. tristate "TI Sequencer Serial Port support"
  66. depends on ARCH_DAVINCI_TNETV107X
  67. select MFD_CORE
  68. ---help---
  69. Say Y here if you want support for the Sequencer Serial Port
  70. in a Texas Instruments TNETV107X SoC.
  71. To compile this driver as a module, choose M here: the
  72. module will be called ti-ssp.
  73. config HTC_EGPIO
  74. bool "HTC EGPIO support"
  75. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  76. help
  77. This driver supports the CPLD egpio chip present on
  78. several HTC phones. It provides basic support for input
  79. pins, output pins, and irqs.
  80. config HTC_PASIC3
  81. tristate "HTC PASIC3 LED/DS1WM chip support"
  82. select MFD_CORE
  83. help
  84. This core driver provides register access for the LED/DS1WM
  85. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  86. HTC Magician devices, respectively. Actual functionality is
  87. handled by the leds-pasic3 and ds1wm drivers.
  88. config HTC_I2CPLD
  89. bool "HTC I2C PLD chip support"
  90. depends on I2C=y && GPIOLIB
  91. help
  92. If you say yes here you get support for the supposed CPLD
  93. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  94. This device provides input and output GPIOs through an I2C
  95. interface to one or more sub-chips.
  96. config UCB1400_CORE
  97. tristate "Philips UCB1400 Core driver"
  98. depends on AC97_BUS
  99. depends on GPIOLIB
  100. help
  101. This enables support for the Philips UCB1400 core functions.
  102. The UCB1400 is an AC97 audio codec.
  103. To compile this driver as a module, choose M here: the
  104. module will be called ucb1400_core.
  105. config TPS6105X
  106. tristate "TPS61050/61052 Boost Converters"
  107. depends on I2C
  108. select REGULATOR
  109. select REGULATOR_FIXED_VOLTAGE
  110. help
  111. This option enables a driver for the TP61050/TPS61052
  112. high-power "white LED driver". This boost converter is
  113. sometimes used for other things than white LEDs, and
  114. also contains a GPIO pin.
  115. config TPS65010
  116. tristate "TPS6501x Power Management chips"
  117. depends on I2C && GPIOLIB
  118. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  119. help
  120. If you say yes here you get support for the TPS6501x series of
  121. Power Management chips. These include voltage regulators,
  122. lithium ion/polymer battery charging, and other features that
  123. are often used in portable devices like cell phones and cameras.
  124. This driver can also be built as a module. If so, the module
  125. will be called tps65010.
  126. config TPS6507X
  127. tristate "TPS6507x Power Management / Touch Screen chips"
  128. select MFD_CORE
  129. depends on I2C
  130. help
  131. If you say yes here you get support for the TPS6507x series of
  132. Power Management / Touch Screen chips. These include voltage
  133. regulators, lithium ion/polymer battery charging, touch screen
  134. and other features that are often used in portable devices.
  135. This driver can also be built as a module. If so, the module
  136. will be called tps6507x.
  137. config MENELAUS
  138. bool "Texas Instruments TWL92330/Menelaus PM chip"
  139. depends on I2C=y && ARCH_OMAP2
  140. help
  141. If you say yes here you get support for the Texas Instruments
  142. TWL92330/Menelaus Power Management chip. This include voltage
  143. regulators, Dual slot memory card transceivers, real-time clock
  144. and other features that are often used in portable devices like
  145. cell phones and PDAs.
  146. config TWL4030_CORE
  147. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  148. depends on I2C=y && GENERIC_HARDIRQS
  149. help
  150. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  151. This core driver provides register access and IRQ handling
  152. facilities, and registers devices for the various functions
  153. so that function-specific drivers can bind to them.
  154. These multi-function chips are found on many OMAP2 and OMAP3
  155. boards, providing power management, RTC, GPIO, keypad, a
  156. high speed USB OTG transceiver, an audio codec (on most
  157. versions) and many other features.
  158. config TWL4030_MADC
  159. tristate "Texas Instruments TWL4030 MADC"
  160. depends on TWL4030_CORE
  161. help
  162. This driver provides support for triton TWL4030-MADC. The
  163. driver supports both RT and SW conversion methods.
  164. This driver can be built as a module. If so it will be
  165. named twl4030-madc
  166. config TWL4030_POWER
  167. bool "Support power resources on TWL4030 family chips"
  168. depends on TWL4030_CORE && ARM
  169. help
  170. Say yes here if you want to use the power resources on the
  171. TWL4030 family chips. Most of these resources are regulators,
  172. which have a separate driver; some are control signals, such
  173. as clock request handshaking.
  174. This driver uses board-specific data to initialize the resources
  175. and load scripts controling which resources are switched off/on
  176. or reset when a sleep, wakeup or warm reset event occurs.
  177. config TWL4030_CODEC
  178. bool
  179. depends on TWL4030_CORE
  180. select MFD_CORE
  181. default n
  182. config TWL6030_PWM
  183. tristate "TWL6030 PWM (Pulse Width Modulator) Support"
  184. depends on TWL4030_CORE
  185. select HAVE_PWM
  186. default n
  187. help
  188. Say yes here if you want support for TWL6030 PWM.
  189. This is used to control charging LED brightness.
  190. config MFD_STMPE
  191. bool "Support STMicroelectronics STMPE"
  192. depends on I2C=y && GENERIC_HARDIRQS
  193. select MFD_CORE
  194. help
  195. Support for the STMPE family of I/O Expanders from
  196. STMicroelectronics.
  197. Currently supported devices are:
  198. STMPE811: GPIO, Touchscreen
  199. STMPE1601: GPIO, Keypad
  200. STMPE2401: GPIO, Keypad
  201. STMPE2403: GPIO, Keypad
  202. This driver provides common support for accessing the device,
  203. additional drivers must be enabled in order to use the functionality
  204. of the device. Currently available sub drivers are:
  205. GPIO: stmpe-gpio
  206. Keypad: stmpe-keypad
  207. Touchscreen: stmpe-ts
  208. config MFD_TC3589X
  209. bool "Support Toshiba TC35892 and variants"
  210. depends on I2C=y && GENERIC_HARDIRQS
  211. select MFD_CORE
  212. help
  213. Support for the Toshiba TC35892 and variants I/O Expander.
  214. This driver provides common support for accessing the device,
  215. additional drivers must be enabled in order to use the
  216. functionality of the device.
  217. config MFD_TMIO
  218. bool
  219. default n
  220. config MFD_T7L66XB
  221. bool "Support Toshiba T7L66XB"
  222. depends on ARM && HAVE_CLK
  223. select MFD_CORE
  224. select MFD_TMIO
  225. help
  226. Support for Toshiba Mobile IO Controller T7L66XB
  227. config MFD_TC6387XB
  228. bool "Support Toshiba TC6387XB"
  229. depends on ARM && HAVE_CLK
  230. select MFD_CORE
  231. select MFD_TMIO
  232. help
  233. Support for Toshiba Mobile IO Controller TC6387XB
  234. config MFD_TC6393XB
  235. bool "Support Toshiba TC6393XB"
  236. depends on GPIOLIB && ARM
  237. select MFD_CORE
  238. select MFD_TMIO
  239. help
  240. Support for Toshiba Mobile IO Controller TC6393XB
  241. config PMIC_DA903X
  242. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  243. depends on I2C=y
  244. help
  245. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  246. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  247. usually found on PXA processors-based platforms. This includes
  248. the I2C driver and the core APIs _only_, you have to select
  249. individual components like LCD backlight, voltage regulators,
  250. LEDs and battery-charger under the corresponding menus.
  251. config PMIC_ADP5520
  252. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  253. depends on I2C=y
  254. help
  255. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  256. Multifunction Power Management IC. This includes
  257. the I2C driver and the core APIs _only_, you have to select
  258. individual components like LCD backlight, LEDs, GPIOs and Kepad
  259. under the corresponding menus.
  260. config MFD_MAX8925
  261. bool "Maxim Semiconductor MAX8925 PMIC Support"
  262. depends on I2C=y && GENERIC_HARDIRQS
  263. select MFD_CORE
  264. help
  265. Say yes here to support for Maxim Semiconductor MAX8925. This is
  266. a Power Management IC. This driver provies common support for
  267. accessing the device, additional drivers must be enabled in order
  268. to use the functionality of the device.
  269. config MFD_MAX8997
  270. bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
  271. depends on I2C=y && GENERIC_HARDIRQS
  272. select MFD_CORE
  273. help
  274. Say yes here to support for Maxim Semiconductor MAX8998/8966.
  275. This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
  276. MUIC controls on chip.
  277. This driver provides common support for accessing the device;
  278. additional drivers must be enabled in order to use the functionality
  279. of the device.
  280. config MFD_MAX8998
  281. bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
  282. depends on I2C=y && GENERIC_HARDIRQS
  283. select MFD_CORE
  284. help
  285. Say yes here to support for Maxim Semiconductor MAX8998 and
  286. National Semiconductor LP3974. This is a Power Management IC.
  287. This driver provies common support for accessing the device,
  288. additional drivers must be enabled in order to use the functionality
  289. of the device.
  290. config MFD_WM8400
  291. tristate "Support Wolfson Microelectronics WM8400"
  292. select MFD_CORE
  293. depends on I2C
  294. help
  295. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  296. CODEC. This driver provides common support for accessing
  297. the device, additional drivers must be enabled in order to use
  298. the functionality of the device.
  299. config MFD_WM831X
  300. bool
  301. depends on GENERIC_HARDIRQS
  302. config MFD_WM831X_I2C
  303. bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
  304. select MFD_CORE
  305. select MFD_WM831X
  306. depends on I2C=y && GENERIC_HARDIRQS
  307. help
  308. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  309. when controlled using I2C. This driver provides common support
  310. for accessing the device, additional drivers must be enabled in
  311. order to use the functionality of the device.
  312. config MFD_WM831X_SPI
  313. bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
  314. select MFD_CORE
  315. select MFD_WM831X
  316. depends on SPI_MASTER && GENERIC_HARDIRQS
  317. help
  318. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  319. when controlled using SPI. This driver provides common support
  320. for accessing the device, additional drivers must be enabled in
  321. order to use the functionality of the device.
  322. config MFD_WM8350
  323. bool
  324. depends on GENERIC_HARDIRQS
  325. config MFD_WM8350_CONFIG_MODE_0
  326. bool
  327. depends on MFD_WM8350
  328. config MFD_WM8350_CONFIG_MODE_1
  329. bool
  330. depends on MFD_WM8350
  331. config MFD_WM8350_CONFIG_MODE_2
  332. bool
  333. depends on MFD_WM8350
  334. config MFD_WM8350_CONFIG_MODE_3
  335. bool
  336. depends on MFD_WM8350
  337. config MFD_WM8351_CONFIG_MODE_0
  338. bool
  339. depends on MFD_WM8350
  340. config MFD_WM8351_CONFIG_MODE_1
  341. bool
  342. depends on MFD_WM8350
  343. config MFD_WM8351_CONFIG_MODE_2
  344. bool
  345. depends on MFD_WM8350
  346. config MFD_WM8351_CONFIG_MODE_3
  347. bool
  348. depends on MFD_WM8350
  349. config MFD_WM8352_CONFIG_MODE_0
  350. bool
  351. depends on MFD_WM8350
  352. config MFD_WM8352_CONFIG_MODE_1
  353. bool
  354. depends on MFD_WM8350
  355. config MFD_WM8352_CONFIG_MODE_2
  356. bool
  357. depends on MFD_WM8350
  358. config MFD_WM8352_CONFIG_MODE_3
  359. bool
  360. depends on MFD_WM8350
  361. config MFD_WM8350_I2C
  362. bool "Support Wolfson Microelectronics WM8350 with I2C"
  363. select MFD_WM8350
  364. depends on I2C=y && GENERIC_HARDIRQS
  365. help
  366. The WM8350 is an integrated audio and power management
  367. subsystem with watchdog and RTC functionality for embedded
  368. systems. This option enables core support for the WM8350 with
  369. I2C as the control interface. Additional options must be
  370. selected to enable support for the functionality of the chip.
  371. config MFD_WM8994
  372. bool "Support Wolfson Microelectronics WM8994"
  373. select MFD_CORE
  374. depends on I2C=y && GENERIC_HARDIRQS
  375. help
  376. The WM8994 is a highly integrated hi-fi CODEC designed for
  377. smartphone applicatiosn. As well as audio functionality it
  378. has on board GPIO and regulator functionality which is
  379. supported via the relevant subsystems. This driver provides
  380. core support for the WM8994, in order to use the actual
  381. functionaltiy of the device other drivers must be enabled.
  382. config MFD_PCF50633
  383. tristate "Support for NXP PCF50633"
  384. depends on I2C
  385. help
  386. Say yes here if you have NXP PCF50633 chip on your board.
  387. This core driver provides register access and IRQ handling
  388. facilities, and registers devices for the various functions
  389. so that function-specific drivers can bind to them.
  390. config MFD_MC13783
  391. tristate
  392. config MFD_MC13XXX
  393. tristate "Support Freescale MC13783 and MC13892"
  394. depends on SPI_MASTER
  395. select MFD_CORE
  396. select MFD_MC13783
  397. help
  398. Support for the Freescale (Atlas) PMIC and audio CODECs
  399. MC13783 and MC13892.
  400. This driver provides common support for accessing the device,
  401. additional drivers must be enabled in order to use the
  402. functionality of the device.
  403. config PCF50633_ADC
  404. tristate "Support for NXP PCF50633 ADC"
  405. depends on MFD_PCF50633
  406. help
  407. Say yes here if you want to include support for ADC in the
  408. NXP PCF50633 chip.
  409. config PCF50633_GPIO
  410. tristate "Support for NXP PCF50633 GPIO"
  411. depends on MFD_PCF50633
  412. help
  413. Say yes here if you want to include support GPIO for pins on
  414. the PCF50633 chip.
  415. config ABX500_CORE
  416. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  417. default y if ARCH_U300 || ARCH_U8500
  418. help
  419. Say yes here if you have the ABX500 Mixed Signal IC family
  420. chips. This core driver expose register access functions.
  421. Functionality specific drivers using these functions can
  422. remain unchanged when IC changes. Binding of the functions to
  423. actual register access is done by the IC core driver.
  424. config AB3100_CORE
  425. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  426. depends on I2C=y && ABX500_CORE
  427. select MFD_CORE
  428. default y if ARCH_U300
  429. help
  430. Select this to enable the AB3100 Mixed Signal IC core
  431. functionality. This connects to a AB3100 on the I2C bus
  432. and expose a number of symbols needed for dependent devices
  433. to read and write registers and subscribe to events from
  434. this multi-functional IC. This is needed to use other features
  435. of the AB3100 such as battery-backed RTC, charging control,
  436. LEDs, vibrator, system power and temperature, power management
  437. and ALSA sound.
  438. config AB3100_OTP
  439. tristate "ST-Ericsson AB3100 OTP functions"
  440. depends on AB3100_CORE
  441. default y if AB3100_CORE
  442. help
  443. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  444. programmable memory) support. This exposes a sysfs file to read
  445. out OTP values.
  446. config EZX_PCAP
  447. bool "PCAP Support"
  448. depends on GENERIC_HARDIRQS && SPI_MASTER
  449. help
  450. This enables the PCAP ASIC present on EZX Phones. This is
  451. needed for MMC, TouchScreen, Sound, USB, etc..
  452. config AB8500_CORE
  453. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  454. depends on GENERIC_HARDIRQS && ABX500_CORE
  455. select MFD_CORE
  456. help
  457. Select this option to enable access to AB8500 power management
  458. chip. This connects to U8500 either on the SSP/SPI bus (deprecated
  459. since hardware version v1.0) or the I2C bus via PRCMU. It also adds
  460. the irq_chip parts for handling the Mixed Signal chip events.
  461. This chip embeds various other multimedia funtionalities as well.
  462. config AB8500_I2C_CORE
  463. bool "AB8500 register access via PRCMU I2C"
  464. depends on AB8500_CORE && UX500_SOC_DB8500
  465. default y
  466. help
  467. This enables register access to the AB8500 chip via PRCMU I2C.
  468. The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
  469. the I2C bus is connected to the Power Reset
  470. and Mangagement Unit, PRCMU.
  471. config AB8500_DEBUG
  472. bool "Enable debug info via debugfs"
  473. depends on AB8500_CORE && DEBUG_FS
  474. default y if DEBUG_FS
  475. help
  476. Select this option if you want debug information using the debug
  477. filesystem, debugfs.
  478. config AB8500_GPADC
  479. bool "AB8500 GPADC driver"
  480. depends on AB8500_CORE && REGULATOR_AB8500
  481. default y
  482. help
  483. AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
  484. config AB3550_CORE
  485. bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
  486. select MFD_CORE
  487. depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
  488. help
  489. Select this to enable the AB3550 Mixed Signal IC core
  490. functionality. This connects to a AB3550 on the I2C bus
  491. and expose a number of symbols needed for dependent devices
  492. to read and write registers and subscribe to events from
  493. this multi-functional IC. This is needed to use other features
  494. of the AB3550 such as battery-backed RTC, charging control,
  495. LEDs, vibrator, system power and temperature, power management
  496. and ALSA sound.
  497. config MFD_CS5535
  498. tristate "Support for CS5535 and CS5536 southbridge core functions"
  499. select MFD_CORE
  500. depends on PCI
  501. ---help---
  502. This is the core driver for CS5535/CS5536 MFD functions. This is
  503. necessary for using the board's GPIO and MFGPT functionality.
  504. config MFD_TIMBERDALE
  505. tristate "Support for the Timberdale FPGA"
  506. select MFD_CORE
  507. depends on PCI && GPIOLIB
  508. ---help---
  509. This is the core driver for the timberdale FPGA. This device is a
  510. multifunction device which exposes numerous platform devices.
  511. The timberdale FPGA can be found on the Intel Atom development board
  512. for in-vehicle infontainment, called Russellville.
  513. config LPC_SCH
  514. tristate "Intel SCH LPC"
  515. depends on PCI
  516. select MFD_CORE
  517. help
  518. LPC bridge function of the Intel SCH provides support for
  519. System Management Bus and General Purpose I/O.
  520. config MFD_RDC321X
  521. tristate "Support for RDC-R321x southbridge"
  522. select MFD_CORE
  523. depends on PCI
  524. help
  525. Say yes here if you want to have support for the RDC R-321x SoC
  526. southbridge which provides access to GPIOs and Watchdog using the
  527. southbridge PCI device configuration space.
  528. config MFD_JANZ_CMODIO
  529. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  530. select MFD_CORE
  531. depends on PCI
  532. help
  533. This is the core driver for the Janz CMOD-IO PCI MODULbus
  534. carrier board. This device is a PCI to MODULbus bridge which may
  535. host many different types of MODULbus daughterboards, including
  536. CAN and GPIO controllers.
  537. config MFD_JZ4740_ADC
  538. tristate "Support for the JZ4740 SoC ADC core"
  539. select MFD_CORE
  540. depends on MACH_JZ4740
  541. help
  542. Say yes here if you want support for the ADC unit in the JZ4740 SoC.
  543. This driver is necessary for jz4740-battery and jz4740-hwmon driver.
  544. config MFD_TPS6586X
  545. bool "TPS6586x Power Management chips"
  546. depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
  547. select MFD_CORE
  548. help
  549. If you say yes here you get support for the TPS6586X series of
  550. Power Management chips.
  551. This driver provides common support for accessing the device,
  552. additional drivers must be enabled in order to use the
  553. functionality of the device.
  554. This driver can also be built as a module. If so, the module
  555. will be called tps6586x.
  556. config MFD_VX855
  557. tristate "Support for VIA VX855/VX875 integrated south bridge"
  558. depends on PCI
  559. select MFD_CORE
  560. help
  561. Say yes here to enable support for various functions of the
  562. VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
  563. and/or vx855_gpio drivers for this to do anything useful.
  564. config MFD_WL1273_CORE
  565. tristate "Support for TI WL1273 FM radio."
  566. depends on I2C
  567. select MFD_CORE
  568. default n
  569. help
  570. This is the core driver for the TI WL1273 FM radio. This MFD
  571. driver connects the radio-wl1273 V4L2 module and the wl1273
  572. audio codec.
  573. config MFD_OMAP_USB_HOST
  574. bool "Support OMAP USBHS core driver"
  575. depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
  576. default y
  577. help
  578. This is the core driver for the OAMP EHCI and OHCI drivers.
  579. This MFD driver does the required setup functionalities for
  580. OMAP USB Host drivers.
  581. endif # MFD_SUPPORT
  582. menu "Multimedia Capabilities Port drivers"
  583. depends on ARCH_SA1100
  584. config MCP
  585. tristate
  586. # Interface drivers
  587. config MCP_SA11X0
  588. tristate "Support SA11x0 MCP interface"
  589. depends on ARCH_SA1100
  590. select MCP
  591. # Chip drivers
  592. config MCP_UCB1200
  593. tristate "Support for UCB1200 / UCB1300"
  594. depends on MCP
  595. config MCP_UCB1200_TS
  596. tristate "Touchscreen interface support"
  597. depends on MCP_UCB1200 && INPUT
  598. endmenu