Kconfig 26 KB

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