Kconfig 24 KB

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