Kconfig 23 KB

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