Kconfig 22 KB

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