Kconfig 21 KB

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