Kconfig 21 KB

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