Kconfig 33 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108
  1. #
  2. # Multifunction miscellaneous devices
  3. #
  4. if HAS_IOMEM
  5. menu "Multifunction device drivers"
  6. config MFD_CORE
  7. tristate
  8. select IRQ_DOMAIN
  9. default n
  10. config MFD_88PM860X
  11. bool "Support Marvell 88PM8606/88PM8607"
  12. depends on I2C=y && GENERIC_HARDIRQS
  13. select REGMAP_I2C
  14. select MFD_CORE
  15. help
  16. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  17. This includes the I2C driver and the core APIs _only_, you have to
  18. select individual components like voltage regulators, RTC and
  19. battery-charger under the corresponding menus.
  20. config MFD_88PM800
  21. tristate "Support Marvell 88PM800"
  22. depends on I2C=y && GENERIC_HARDIRQS
  23. select REGMAP_I2C
  24. select REGMAP_IRQ
  25. select MFD_CORE
  26. help
  27. This supports for Marvell 88PM800 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_88PM805
  32. tristate "Support Marvell 88PM805"
  33. depends on I2C=y && GENERIC_HARDIRQS
  34. select REGMAP_I2C
  35. select REGMAP_IRQ
  36. select MFD_CORE
  37. help
  38. This supports for Marvell 88PM805 Power Management IC. This includes
  39. the I2C driver and the core APIs _only_, you have to select individual
  40. components like codec device, headset/Mic device under the
  41. corresponding menus.
  42. config MFD_SM501
  43. tristate "Support for Silicon Motion SM501"
  44. ---help---
  45. This is the core driver for the Silicon Motion SM501 multimedia
  46. companion chip. This device is a multifunction device which may
  47. provide numerous interfaces including USB host controller, USB gadget,
  48. asynchronous serial ports, audio functions, and a dual display video
  49. interface. The device may be connected by PCI or local bus with
  50. varying functions enabled.
  51. config MFD_SM501_GPIO
  52. bool "Export GPIO via GPIO layer"
  53. depends on MFD_SM501 && GPIOLIB
  54. ---help---
  55. This option uses the gpio library layer to export the 64 GPIO
  56. lines on the SM501. The platform data is used to supply the
  57. base number for the first GPIO line to register.
  58. config MFD_RTSX_PCI
  59. tristate "Support for Realtek PCI-E card reader"
  60. depends on PCI
  61. select MFD_CORE
  62. help
  63. This supports for Realtek PCI-Express card reader including rts5209,
  64. rts5229, rtl8411, etc. Realtek card reader supports access to many
  65. types of memory cards, such as Memory Stick, Memory Stick Pro,
  66. Secure Digital and MultiMediaCard.
  67. config MFD_ASIC3
  68. bool "Support for Compaq ASIC3"
  69. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  70. select MFD_CORE
  71. ---help---
  72. This driver supports the ASIC3 multifunction chip found on many
  73. PDAs (mainly iPAQ and HTC based ones)
  74. config MFD_DAVINCI_VOICECODEC
  75. tristate
  76. select MFD_CORE
  77. config MFD_DM355EVM_MSP
  78. bool "DaVinci DM355 EVM microcontroller"
  79. depends on I2C=y && MACH_DAVINCI_DM355_EVM
  80. help
  81. This driver supports the MSP430 microcontroller used on these
  82. boards. MSP430 firmware manages resets and power sequencing,
  83. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  84. config MFD_TI_SSP
  85. tristate "TI Sequencer Serial Port support"
  86. depends on ARCH_DAVINCI_TNETV107X
  87. select MFD_CORE
  88. ---help---
  89. Say Y here if you want support for the Sequencer Serial Port
  90. in a Texas Instruments TNETV107X SoC.
  91. To compile this driver as a module, choose M here: the
  92. module will be called ti-ssp.
  93. config MFD_TI_AM335X_TSCADC
  94. tristate "TI ADC / Touch Screen chip support"
  95. select MFD_CORE
  96. select REGMAP
  97. select REGMAP_MMIO
  98. help
  99. If you say yes here you get support for Texas Instruments series
  100. of Touch Screen /ADC chips.
  101. To compile this driver as a module, choose M here: the
  102. module will be called ti_am335x_tscadc.
  103. config HTC_EGPIO
  104. bool "HTC EGPIO support"
  105. depends on GENERIC_HARDIRQS && GPIOLIB && ARM
  106. help
  107. This driver supports the CPLD egpio chip present on
  108. several HTC phones. It provides basic support for input
  109. pins, output pins, and irqs.
  110. config HTC_PASIC3
  111. tristate "HTC PASIC3 LED/DS1WM chip support"
  112. select MFD_CORE
  113. help
  114. This core driver provides register access for the LED/DS1WM
  115. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  116. HTC Magician devices, respectively. Actual functionality is
  117. handled by the leds-pasic3 and ds1wm drivers.
  118. config HTC_I2CPLD
  119. bool "HTC I2C PLD chip support"
  120. depends on I2C=y && GPIOLIB
  121. help
  122. If you say yes here you get support for the supposed CPLD
  123. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  124. This device provides input and output GPIOs through an I2C
  125. interface to one or more sub-chips.
  126. config UCB1400_CORE
  127. tristate "Philips UCB1400 Core driver"
  128. depends on AC97_BUS
  129. depends on GPIOLIB
  130. help
  131. This enables support for the Philips UCB1400 core functions.
  132. The UCB1400 is an AC97 audio codec.
  133. To compile this driver as a module, choose M here: the
  134. module will be called ucb1400_core.
  135. config MFD_LM3533
  136. tristate "LM3533 Lighting Power chip"
  137. depends on I2C
  138. select MFD_CORE
  139. select REGMAP_I2C
  140. help
  141. Say yes here to enable support for National Semiconductor / TI
  142. LM3533 Lighting Power chips.
  143. This driver provides common support for accessing the device;
  144. additional drivers must be enabled in order to use the LED,
  145. backlight or ambient-light-sensor functionality of the device.
  146. config TPS6105X
  147. tristate "TPS61050/61052 Boost Converters"
  148. depends on I2C
  149. select REGULATOR
  150. select MFD_CORE
  151. select REGULATOR_FIXED_VOLTAGE
  152. help
  153. This option enables a driver for the TP61050/TPS61052
  154. high-power "white LED driver". This boost converter is
  155. sometimes used for other things than white LEDs, and
  156. also contains a GPIO pin.
  157. config TPS65010
  158. tristate "TPS6501x Power Management chips"
  159. depends on I2C && GPIOLIB
  160. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  161. help
  162. If you say yes here you get support for the TPS6501x series of
  163. Power Management chips. These include voltage regulators,
  164. lithium ion/polymer battery charging, and other features that
  165. are often used in portable devices like cell phones and cameras.
  166. This driver can also be built as a module. If so, the module
  167. will be called tps65010.
  168. config TPS6507X
  169. tristate "TPS6507x Power Management / Touch Screen chips"
  170. select MFD_CORE
  171. depends on I2C
  172. help
  173. If you say yes here you get support for the TPS6507x series of
  174. Power Management / Touch Screen chips. These include voltage
  175. regulators, lithium ion/polymer battery charging, touch screen
  176. and other features that are often used in portable devices.
  177. This driver can also be built as a module. If so, the module
  178. will be called tps6507x.
  179. config MFD_TPS65217
  180. tristate "TPS65217 Power Management / White LED chips"
  181. depends on I2C
  182. select MFD_CORE
  183. select REGMAP_I2C
  184. help
  185. If you say yes here you get support for the TPS65217 series of
  186. Power Management / White LED chips.
  187. These include voltage regulators, lithium ion/polymer battery
  188. charger, wled and other features that are often used in portable
  189. devices.
  190. This driver can also be built as a module. If so, the module
  191. will be called tps65217.
  192. config MFD_TPS6586X
  193. bool "TPS6586x Power Management chips"
  194. depends on I2C=y && GENERIC_HARDIRQS
  195. select MFD_CORE
  196. select REGMAP_I2C
  197. depends on REGULATOR
  198. help
  199. If you say yes here you get support for the TPS6586X series of
  200. Power Management chips.
  201. This driver provides common support for accessing the device,
  202. additional drivers must be enabled in order to use the
  203. functionality of the device.
  204. This driver can also be built as a module. If so, the module
  205. will be called tps6586x.
  206. config MFD_TPS65910
  207. bool "TPS65910 Power Management chip"
  208. depends on I2C=y && GPIOLIB
  209. select MFD_CORE
  210. select REGMAP_I2C
  211. select IRQ_DOMAIN
  212. help
  213. if you say yes here you get support for the TPS65910 series of
  214. Power Management chips.
  215. config MFD_TPS65912
  216. bool
  217. depends on GPIOLIB
  218. config MFD_TPS65912_I2C
  219. bool "TPS65912 Power Management chip with I2C"
  220. select MFD_CORE
  221. select MFD_TPS65912
  222. depends on I2C=y && GPIOLIB
  223. help
  224. If you say yes here you get support for the TPS65912 series of
  225. PM chips with I2C interface.
  226. config MFD_TPS65912_SPI
  227. bool "TPS65912 Power Management chip with SPI"
  228. select MFD_CORE
  229. select MFD_TPS65912
  230. depends on SPI_MASTER && GPIOLIB
  231. help
  232. If you say yes here you get support for the TPS65912 series of
  233. PM chips with SPI interface.
  234. config MENELAUS
  235. bool "Texas Instruments TWL92330/Menelaus PM chip"
  236. depends on I2C=y && ARCH_OMAP2
  237. help
  238. If you say yes here you get support for the Texas Instruments
  239. TWL92330/Menelaus Power Management chip. This include voltage
  240. regulators, Dual slot memory card transceivers, real-time clock
  241. and other features that are often used in portable devices like
  242. cell phones and PDAs.
  243. config TWL4030_CORE
  244. bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  245. depends on I2C=y && GENERIC_HARDIRQS
  246. select IRQ_DOMAIN
  247. help
  248. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  249. This core driver provides register access and IRQ handling
  250. facilities, and registers devices for the various functions
  251. so that function-specific drivers can bind to them.
  252. These multi-function chips are found on many OMAP2 and OMAP3
  253. boards, providing power management, RTC, GPIO, keypad, a
  254. high speed USB OTG transceiver, an audio codec (on most
  255. versions) and many other features.
  256. config TWL4030_MADC
  257. tristate "Texas Instruments TWL4030 MADC"
  258. depends on TWL4030_CORE
  259. help
  260. This driver provides support for triton TWL4030-MADC. The
  261. driver supports both RT and SW conversion methods.
  262. This driver can be built as a module. If so it will be
  263. named twl4030-madc
  264. config TWL4030_POWER
  265. bool "Support power resources on TWL4030 family chips"
  266. depends on TWL4030_CORE && ARM
  267. help
  268. Say yes here if you want to use the power resources on the
  269. TWL4030 family chips. Most of these resources are regulators,
  270. which have a separate driver; some are control signals, such
  271. as clock request handshaking.
  272. This driver uses board-specific data to initialize the resources
  273. and load scripts controlling which resources are switched off/on
  274. or reset when a sleep, wakeup or warm reset event occurs.
  275. config MFD_TWL4030_AUDIO
  276. bool
  277. depends on TWL4030_CORE
  278. select MFD_CORE
  279. default n
  280. config TWL6040_CORE
  281. bool "Support for TWL6040 audio codec"
  282. depends on I2C=y
  283. select MFD_CORE
  284. select REGMAP_I2C
  285. select REGMAP_IRQ
  286. default n
  287. help
  288. Say yes here if you want support for Texas Instruments TWL6040 audio
  289. codec.
  290. This driver provides common support for accessing the device,
  291. additional drivers must be enabled in order to use the
  292. functionality of the device (audio, vibra).
  293. config MFD_STMPE
  294. bool "Support STMicroelectronics STMPE"
  295. depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
  296. select MFD_CORE
  297. help
  298. Support for the STMPE family of I/O Expanders from
  299. STMicroelectronics.
  300. Currently supported devices are:
  301. STMPE811: GPIO, Touchscreen
  302. STMPE1601: GPIO, Keypad
  303. STMPE2401: GPIO, Keypad
  304. STMPE2403: GPIO, Keypad
  305. This driver provides common support for accessing the device,
  306. additional drivers must be enabled in order to use the functionality
  307. of the device. Currently available sub drivers are:
  308. GPIO: stmpe-gpio
  309. Keypad: stmpe-keypad
  310. Touchscreen: stmpe-ts
  311. menu "STMPE Interface Drivers"
  312. depends on MFD_STMPE
  313. config STMPE_I2C
  314. bool "STMPE I2C Inteface"
  315. depends on I2C=y
  316. default y
  317. help
  318. This is used to enable I2C interface of STMPE
  319. config STMPE_SPI
  320. bool "STMPE SPI Inteface"
  321. depends on SPI_MASTER
  322. help
  323. This is used to enable SPI interface of STMPE
  324. endmenu
  325. config MFD_TC3589X
  326. bool "Support Toshiba TC35892 and variants"
  327. depends on I2C=y && GENERIC_HARDIRQS
  328. select MFD_CORE
  329. help
  330. Support for the Toshiba TC35892 and variants I/O Expander.
  331. This driver provides common support for accessing the device,
  332. additional drivers must be enabled in order to use the
  333. functionality of the device.
  334. config MFD_TMIO
  335. bool
  336. default n
  337. config MFD_T7L66XB
  338. bool "Support Toshiba T7L66XB"
  339. depends on ARM && HAVE_CLK
  340. select MFD_CORE
  341. select MFD_TMIO
  342. help
  343. Support for Toshiba Mobile IO Controller T7L66XB
  344. config MFD_SMSC
  345. bool "Support for the SMSC ECE1099 series chips"
  346. depends on I2C=y
  347. select MFD_CORE
  348. select REGMAP_I2C
  349. help
  350. If you say yes here you get support for the
  351. ece1099 chips from SMSC.
  352. To compile this driver as a module, choose M here: the
  353. module will be called smsc.
  354. config MFD_TC6387XB
  355. bool "Support Toshiba TC6387XB"
  356. depends on ARM && HAVE_CLK
  357. select MFD_CORE
  358. select MFD_TMIO
  359. help
  360. Support for Toshiba Mobile IO Controller TC6387XB
  361. config MFD_TC6393XB
  362. bool "Support Toshiba TC6393XB"
  363. depends on ARM && HAVE_CLK
  364. select GPIOLIB
  365. select MFD_CORE
  366. select MFD_TMIO
  367. help
  368. Support for Toshiba Mobile IO Controller TC6393XB
  369. config PMIC_DA903X
  370. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  371. depends on I2C=y
  372. help
  373. Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
  374. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  375. usually found on PXA processors-based platforms. This includes
  376. the I2C driver and the core APIs _only_, you have to select
  377. individual components like LCD backlight, voltage regulators,
  378. LEDs and battery-charger under the corresponding menus.
  379. config PMIC_DA9052
  380. bool
  381. select MFD_CORE
  382. config MFD_DA9052_SPI
  383. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
  384. select REGMAP_SPI
  385. select REGMAP_IRQ
  386. select PMIC_DA9052
  387. depends on SPI_MASTER=y
  388. help
  389. Support for the Dialog Semiconductor DA9052 PMIC
  390. when controlled using SPI. This driver provides common support
  391. for accessing the device, additional drivers must be enabled in
  392. order to use the functionality of the device.
  393. config MFD_DA9052_I2C
  394. bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
  395. select REGMAP_I2C
  396. select REGMAP_IRQ
  397. select PMIC_DA9052
  398. depends on I2C=y
  399. help
  400. Support for the Dialog Semiconductor DA9052 PMIC
  401. when controlled using I2C. This driver provides common support
  402. for accessing the device, additional drivers must be enabled in
  403. order to use the functionality of the device.
  404. config MFD_DA9055
  405. bool "Dialog Semiconductor DA9055 PMIC Support"
  406. select REGMAP_I2C
  407. select REGMAP_IRQ
  408. select PMIC_DA9055
  409. select MFD_CORE
  410. depends on I2C=y
  411. help
  412. Say yes here for support of Dialog Semiconductor DA9055. This is
  413. a Power Management IC. This driver provides common support for
  414. accessing the device as well as the I2C interface to the chip itself.
  415. Additional drivers must be enabled in order to use the functionality
  416. of the device.
  417. This driver can be built as a module. If built as a module it will be
  418. called "da9055"
  419. config PMIC_ADP5520
  420. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  421. depends on I2C=y
  422. help
  423. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  424. Multifunction Power Management IC. This includes
  425. the I2C driver and the core APIs _only_, you have to select
  426. individual components like LCD backlight, LEDs, GPIOs and Kepad
  427. under the corresponding menus.
  428. config MFD_LP8788
  429. bool "Texas Instruments LP8788 Power Management Unit Driver"
  430. depends on I2C=y
  431. select MFD_CORE
  432. select REGMAP_I2C
  433. select IRQ_DOMAIN
  434. help
  435. TI LP8788 PMU supports regulators, battery charger, RTC,
  436. ADC, backlight driver and current sinks.
  437. config MFD_MAX77686
  438. bool "Maxim Semiconductor MAX77686 PMIC Support"
  439. depends on I2C=y && GENERIC_HARDIRQS
  440. select MFD_CORE
  441. select REGMAP_I2C
  442. select IRQ_DOMAIN
  443. help
  444. Say yes here to support for Maxim Semiconductor MAX77686.
  445. This is a Power Management IC with RTC on chip.
  446. This driver provides common support for accessing the device;
  447. additional drivers must be enabled in order to use the functionality
  448. of the device.
  449. config MFD_MAX77693
  450. bool "Maxim Semiconductor MAX77693 PMIC Support"
  451. depends on I2C=y && GENERIC_HARDIRQS
  452. select MFD_CORE
  453. select REGMAP_I2C
  454. help
  455. Say yes here to support for Maxim Semiconductor MAX77693.
  456. This is a companion Power Management IC with Flash, Haptic, Charger,
  457. and MUIC(Micro USB Interface Controller) controls on chip.
  458. This driver provides common support for accessing the device;
  459. additional drivers must be enabled in order to use the functionality
  460. of the device.
  461. config MFD_MAX8907
  462. tristate "Maxim Semiconductor MAX8907 PMIC Support"
  463. select MFD_CORE
  464. depends on I2C=y && GENERIC_HARDIRQS
  465. select REGMAP_I2C
  466. select REGMAP_IRQ
  467. help
  468. Say yes here to support for Maxim Semiconductor MAX8907. This is
  469. a Power Management IC. This driver provides common support for
  470. accessing the device; additional drivers must be enabled in order
  471. to use the functionality of the device.
  472. config MFD_MAX8925
  473. bool "Maxim Semiconductor MAX8925 PMIC Support"
  474. depends on I2C=y && GENERIC_HARDIRQS
  475. select MFD_CORE
  476. help
  477. Say yes here to support for Maxim Semiconductor MAX8925. This is
  478. a Power Management IC. This driver provides common support for
  479. accessing the device, additional drivers must be enabled in order
  480. to use the functionality of the device.
  481. config MFD_MAX8997
  482. bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
  483. depends on I2C=y && GENERIC_HARDIRQS
  484. select MFD_CORE
  485. select IRQ_DOMAIN
  486. help
  487. Say yes here to support for Maxim Semiconductor MAX8997/8966.
  488. This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
  489. MUIC controls on chip.
  490. This driver provides common support for accessing the device;
  491. additional drivers must be enabled in order to use the functionality
  492. of the device.
  493. config MFD_MAX8998
  494. bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
  495. depends on I2C=y && GENERIC_HARDIRQS
  496. select MFD_CORE
  497. help
  498. Say yes here to support for Maxim Semiconductor MAX8998 and
  499. National Semiconductor LP3974. This is a Power Management IC.
  500. This driver provides common support for accessing the device,
  501. additional drivers must be enabled in order to use the functionality
  502. of the device.
  503. config MFD_SEC_CORE
  504. bool "SAMSUNG Electronics PMIC Series Support"
  505. depends on I2C=y && GENERIC_HARDIRQS
  506. select MFD_CORE
  507. select REGMAP_I2C
  508. select REGMAP_IRQ
  509. help
  510. Support for the Samsung Electronics MFD series.
  511. This driver provides common support for accessing the device,
  512. additional drivers must be enabled in order to use the functionality
  513. of the device
  514. config MFD_ARIZONA
  515. select REGMAP
  516. select REGMAP_IRQ
  517. select MFD_CORE
  518. bool
  519. config MFD_ARIZONA_I2C
  520. tristate "Support Wolfson Microelectronics Arizona platform with I2C"
  521. select MFD_ARIZONA
  522. select MFD_CORE
  523. select REGMAP_I2C
  524. depends on I2C
  525. help
  526. Support for the Wolfson Microelectronics Arizona platform audio SoC
  527. core functionality controlled via I2C.
  528. config MFD_ARIZONA_SPI
  529. tristate "Support Wolfson Microelectronics Arizona platform with SPI"
  530. select MFD_ARIZONA
  531. select MFD_CORE
  532. select REGMAP_SPI
  533. depends on SPI_MASTER
  534. help
  535. Support for the Wolfson Microelectronics Arizona platform audio SoC
  536. core functionality controlled via I2C.
  537. config MFD_WM5102
  538. bool "Support Wolfson Microelectronics WM5102"
  539. depends on MFD_ARIZONA
  540. help
  541. Support for Wolfson Microelectronics WM5102 low power audio SoC
  542. config MFD_WM5110
  543. bool "Support Wolfson Microelectronics WM5110"
  544. depends on MFD_ARIZONA
  545. help
  546. Support for Wolfson Microelectronics WM5110 low power audio SoC
  547. config MFD_WM8400
  548. bool "Support Wolfson Microelectronics WM8400"
  549. select MFD_CORE
  550. depends on I2C=y
  551. select REGMAP_I2C
  552. help
  553. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  554. CODEC. This driver provides common support for accessing
  555. the device, additional drivers must be enabled in order to use
  556. the functionality of the device.
  557. config MFD_WM831X
  558. bool
  559. depends on GENERIC_HARDIRQS
  560. config MFD_WM831X_I2C
  561. bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
  562. select MFD_CORE
  563. select MFD_WM831X
  564. select REGMAP_I2C
  565. select IRQ_DOMAIN
  566. depends on I2C=y && GENERIC_HARDIRQS
  567. help
  568. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  569. when controlled using I2C. This driver provides common support
  570. for accessing the device, additional drivers must be enabled in
  571. order to use the functionality of the device.
  572. config MFD_WM831X_SPI
  573. bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
  574. select MFD_CORE
  575. select MFD_WM831X
  576. select REGMAP_SPI
  577. select IRQ_DOMAIN
  578. depends on SPI_MASTER && GENERIC_HARDIRQS
  579. help
  580. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  581. when controlled using SPI. This driver provides common support
  582. for accessing the device, additional drivers must be enabled in
  583. order to use the functionality of the device.
  584. config MFD_WM8350
  585. bool
  586. depends on GENERIC_HARDIRQS
  587. config MFD_WM8350_CONFIG_MODE_0
  588. bool
  589. depends on MFD_WM8350
  590. config MFD_WM8350_CONFIG_MODE_1
  591. bool
  592. depends on MFD_WM8350
  593. config MFD_WM8350_CONFIG_MODE_2
  594. bool
  595. depends on MFD_WM8350
  596. config MFD_WM8350_CONFIG_MODE_3
  597. bool
  598. depends on MFD_WM8350
  599. config MFD_WM8351_CONFIG_MODE_0
  600. bool
  601. depends on MFD_WM8350
  602. config MFD_WM8351_CONFIG_MODE_1
  603. bool
  604. depends on MFD_WM8350
  605. config MFD_WM8351_CONFIG_MODE_2
  606. bool
  607. depends on MFD_WM8350
  608. config MFD_WM8351_CONFIG_MODE_3
  609. bool
  610. depends on MFD_WM8350
  611. config MFD_WM8352_CONFIG_MODE_0
  612. bool
  613. depends on MFD_WM8350
  614. config MFD_WM8352_CONFIG_MODE_1
  615. bool
  616. depends on MFD_WM8350
  617. config MFD_WM8352_CONFIG_MODE_2
  618. bool
  619. depends on MFD_WM8350
  620. config MFD_WM8352_CONFIG_MODE_3
  621. bool
  622. depends on MFD_WM8350
  623. config MFD_WM8350_I2C
  624. bool "Support Wolfson Microelectronics WM8350 with I2C"
  625. select MFD_WM8350
  626. depends on I2C=y && GENERIC_HARDIRQS
  627. help
  628. The WM8350 is an integrated audio and power management
  629. subsystem with watchdog and RTC functionality for embedded
  630. systems. This option enables core support for the WM8350 with
  631. I2C as the control interface. Additional options must be
  632. selected to enable support for the functionality of the chip.
  633. config MFD_WM8994
  634. bool "Support Wolfson Microelectronics WM8994"
  635. select MFD_CORE
  636. select REGMAP_I2C
  637. select REGMAP_IRQ
  638. depends on I2C=y && GENERIC_HARDIRQS
  639. help
  640. The WM8994 is a highly integrated hi-fi CODEC designed for
  641. smartphone applicatiosn. As well as audio functionality it
  642. has on board GPIO and regulator functionality which is
  643. supported via the relevant subsystems. This driver provides
  644. core support for the WM8994, in order to use the actual
  645. functionaltiy of the device other drivers must be enabled.
  646. config MFD_PCF50633
  647. tristate "Support for NXP PCF50633"
  648. depends on I2C
  649. select REGMAP_I2C
  650. help
  651. Say yes here if you have NXP PCF50633 chip on your board.
  652. This core driver provides register access and IRQ handling
  653. facilities, and registers devices for the various functions
  654. so that function-specific drivers can bind to them.
  655. config PCF50633_ADC
  656. tristate "Support for NXP PCF50633 ADC"
  657. depends on MFD_PCF50633
  658. help
  659. Say yes here if you want to include support for ADC in the
  660. NXP PCF50633 chip.
  661. config PCF50633_GPIO
  662. tristate "Support for NXP PCF50633 GPIO"
  663. depends on MFD_PCF50633
  664. help
  665. Say yes here if you want to include support GPIO for pins on
  666. the PCF50633 chip.
  667. config MFD_MC13783
  668. tristate
  669. config MFD_MC13XXX
  670. tristate
  671. depends on SPI_MASTER || I2C
  672. select MFD_CORE
  673. select MFD_MC13783
  674. help
  675. Enable support for the Freescale MC13783 and MC13892 PMICs.
  676. This driver provides common support for accessing the device,
  677. additional drivers must be enabled in order to use the
  678. functionality of the device.
  679. config MFD_MC13XXX_SPI
  680. tristate "Freescale MC13783 and MC13892 SPI interface"
  681. depends on SPI_MASTER
  682. select REGMAP_SPI
  683. select MFD_MC13XXX
  684. help
  685. Select this if your MC13xxx is connected via an SPI bus.
  686. config MFD_MC13XXX_I2C
  687. tristate "Freescale MC13892 I2C interface"
  688. depends on I2C
  689. select REGMAP_I2C
  690. select MFD_MC13XXX
  691. help
  692. Select this if your MC13xxx is connected via an I2C bus.
  693. config ABX500_CORE
  694. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  695. default y if ARCH_U300 || ARCH_U8500
  696. help
  697. Say yes here if you have the ABX500 Mixed Signal IC family
  698. chips. This core driver expose register access functions.
  699. Functionality specific drivers using these functions can
  700. remain unchanged when IC changes. Binding of the functions to
  701. actual register access is done by the IC core driver.
  702. config AB3100_CORE
  703. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  704. depends on I2C=y && ABX500_CORE
  705. select MFD_CORE
  706. default y if ARCH_U300
  707. help
  708. Select this to enable the AB3100 Mixed Signal IC core
  709. functionality. This connects to a AB3100 on the I2C bus
  710. and expose a number of symbols needed for dependent devices
  711. to read and write registers and subscribe to events from
  712. this multi-functional IC. This is needed to use other features
  713. of the AB3100 such as battery-backed RTC, charging control,
  714. LEDs, vibrator, system power and temperature, power management
  715. and ALSA sound.
  716. config AB3100_OTP
  717. tristate "ST-Ericsson AB3100 OTP functions"
  718. depends on AB3100_CORE
  719. default y if AB3100_CORE
  720. help
  721. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  722. programmable memory) support. This exposes a sysfs file to read
  723. out OTP values.
  724. config EZX_PCAP
  725. bool "PCAP Support"
  726. depends on GENERIC_HARDIRQS && SPI_MASTER
  727. help
  728. This enables the PCAP ASIC present on EZX Phones. This is
  729. needed for MMC, TouchScreen, Sound, USB, etc..
  730. config AB8500_CORE
  731. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  732. depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
  733. select MFD_CORE
  734. select IRQ_DOMAIN
  735. help
  736. Select this option to enable access to AB8500 power management
  737. chip. This connects to U8500 either on the SSP/SPI bus (deprecated
  738. since hardware version v1.0) or the I2C bus via PRCMU. It also adds
  739. the irq_chip parts for handling the Mixed Signal chip events.
  740. This chip embeds various other multimedia funtionalities as well.
  741. config AB8500_DEBUG
  742. bool "Enable debug info via debugfs"
  743. depends on AB8500_CORE && DEBUG_FS
  744. default y if DEBUG_FS
  745. help
  746. Select this option if you want debug information using the debug
  747. filesystem, debugfs.
  748. config AB8500_GPADC
  749. bool "AB8500 GPADC driver"
  750. depends on AB8500_CORE && REGULATOR_AB8500
  751. default y
  752. help
  753. AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
  754. config MFD_DB8500_PRCMU
  755. bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
  756. depends on UX500_SOC_DB8500
  757. select MFD_CORE
  758. help
  759. Select this option to enable support for the DB8500 Power Reset
  760. and Control Management Unit. This is basically an autonomous
  761. system controller running an XP70 microprocessor, which is accessed
  762. through a register map.
  763. config MFD_CS5535
  764. tristate "Support for CS5535 and CS5536 southbridge core functions"
  765. select MFD_CORE
  766. depends on PCI && X86
  767. ---help---
  768. This is the core driver for CS5535/CS5536 MFD functions. This is
  769. necessary for using the board's GPIO and MFGPT functionality.
  770. config MFD_TIMBERDALE
  771. tristate "Support for the Timberdale FPGA"
  772. select MFD_CORE
  773. depends on PCI && GPIOLIB
  774. ---help---
  775. This is the core driver for the timberdale FPGA. This device is a
  776. multifunction device which exposes numerous platform devices.
  777. The timberdale FPGA can be found on the Intel Atom development board
  778. for in-vehicle infontainment, called Russellville.
  779. config LPC_SCH
  780. tristate "Intel SCH LPC"
  781. depends on PCI
  782. select MFD_CORE
  783. help
  784. LPC bridge function of the Intel SCH provides support for
  785. System Management Bus and General Purpose I/O.
  786. config LPC_ICH
  787. tristate "Intel ICH LPC"
  788. depends on PCI
  789. select MFD_CORE
  790. help
  791. The LPC bridge function of the Intel ICH provides support for
  792. many functional units. This driver provides needed support for
  793. other drivers to control these functions, currently GPIO and
  794. watchdog.
  795. config MFD_RDC321X
  796. tristate "Support for RDC-R321x southbridge"
  797. select MFD_CORE
  798. depends on PCI
  799. help
  800. Say yes here if you want to have support for the RDC R-321x SoC
  801. southbridge which provides access to GPIOs and Watchdog using the
  802. southbridge PCI device configuration space.
  803. config MFD_JANZ_CMODIO
  804. tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
  805. select MFD_CORE
  806. depends on PCI
  807. help
  808. This is the core driver for the Janz CMOD-IO PCI MODULbus
  809. carrier board. This device is a PCI to MODULbus bridge which may
  810. host many different types of MODULbus daughterboards, including
  811. CAN and GPIO controllers.
  812. config MFD_JZ4740_ADC
  813. bool "Support for the JZ4740 SoC ADC core"
  814. select MFD_CORE
  815. select GENERIC_IRQ_CHIP
  816. depends on MACH_JZ4740
  817. help
  818. Say yes here if you want support for the ADC unit in the JZ4740 SoC.
  819. This driver is necessary for jz4740-battery and jz4740-hwmon driver.
  820. config MFD_VX855
  821. tristate "Support for VIA VX855/VX875 integrated south bridge"
  822. depends on PCI
  823. select MFD_CORE
  824. help
  825. Say yes here to enable support for various functions of the
  826. VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
  827. and/or vx855_gpio drivers for this to do anything useful.
  828. config MFD_WL1273_CORE
  829. tristate "Support for TI WL1273 FM radio."
  830. depends on I2C
  831. select MFD_CORE
  832. default n
  833. help
  834. This is the core driver for the TI WL1273 FM radio. This MFD
  835. driver connects the radio-wl1273 V4L2 module and the wl1273
  836. audio codec.
  837. config MFD_OMAP_USB_HOST
  838. bool "Support OMAP USBHS core and TLL driver"
  839. depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
  840. default y
  841. help
  842. This is the core driver for the OAMP EHCI and OHCI drivers.
  843. This MFD driver does the required setup functionalities for
  844. OMAP USB Host drivers.
  845. config MFD_PM8XXX
  846. tristate
  847. config MFD_PM8921_CORE
  848. tristate "Qualcomm PM8921 PMIC chip"
  849. depends on MSM_SSBI
  850. select MFD_CORE
  851. select MFD_PM8XXX
  852. help
  853. If you say yes to this option, support will be included for the
  854. built-in PM8921 PMIC chip.
  855. This is required if your board has a PM8921 and uses its features,
  856. such as: MPPs, GPIOs, regulators, interrupts, and PWM.
  857. Say M here if you want to include support for PM8921 chip as a module.
  858. This will build a module called "pm8921-core".
  859. config MFD_PM8XXX_IRQ
  860. bool "Support for Qualcomm PM8xxx IRQ features"
  861. depends on MFD_PM8XXX
  862. default y if MFD_PM8XXX
  863. help
  864. This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
  865. This is required to use certain other PM 8xxx features, such as GPIO
  866. and MPP.
  867. config TPS65911_COMPARATOR
  868. tristate
  869. config MFD_TPS65090
  870. bool "TPS65090 Power Management chips"
  871. depends on I2C=y && GENERIC_HARDIRQS
  872. select MFD_CORE
  873. select REGMAP_I2C
  874. help
  875. If you say yes here you get support for the TPS65090 series of
  876. Power Management chips.
  877. This driver provides common support for accessing the device,
  878. additional drivers must be enabled in order to use the
  879. functionality of the device.
  880. config MFD_AAT2870_CORE
  881. bool "Support for the AnalogicTech AAT2870"
  882. select MFD_CORE
  883. depends on I2C=y && GPIOLIB
  884. help
  885. If you say yes here you get support for the AAT2870.
  886. This driver provides common support for accessing the device,
  887. additional drivers must be enabled in order to use the
  888. functionality of the device.
  889. config MFD_INTEL_MSIC
  890. bool "Support for Intel MSIC"
  891. depends on INTEL_SCU_IPC
  892. select MFD_CORE
  893. help
  894. Select this option to enable access to Intel MSIC (Avatele
  895. Passage) chip. This chip embeds audio, battery, GPIO, etc.
  896. devices used in Intel Medfield platforms.
  897. config MFD_RC5T583
  898. bool "Ricoh RC5T583 Power Management system device"
  899. depends on I2C=y && GENERIC_HARDIRQS
  900. select MFD_CORE
  901. select REGMAP_I2C
  902. help
  903. Select this option to get support for the RICOH583 Power
  904. Management system device.
  905. This driver provides common support for accessing the device
  906. through i2c interface. The device supports multiple sub-devices
  907. like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
  908. Additional drivers must be enabled in order to use the
  909. different functionality of the device.
  910. config MFD_STA2X11
  911. bool "STA2X11 multi function device support"
  912. depends on STA2X11
  913. select MFD_CORE
  914. select REGMAP_MMIO
  915. config MFD_SYSCON
  916. bool "System Controller Register R/W Based on Regmap"
  917. depends on OF
  918. select REGMAP_MMIO
  919. help
  920. Select this option to enable accessing system control registers
  921. via regmap.
  922. config MFD_PALMAS
  923. bool "Support for the TI Palmas series chips"
  924. select MFD_CORE
  925. select REGMAP_I2C
  926. select REGMAP_IRQ
  927. depends on I2C=y
  928. help
  929. If you say yes here you get support for the Palmas
  930. series of PMIC chips from Texas Instruments.
  931. config MFD_VIPERBOARD
  932. tristate "Support for Nano River Technologies Viperboard"
  933. select MFD_CORE
  934. depends on USB
  935. default n
  936. help
  937. Say yes here if you want support for Nano River Technologies
  938. Viperboard.
  939. There are mfd cell drivers available for i2c master, adc and
  940. both gpios found on the board. The spi part does not yet
  941. have a driver.
  942. You need to select the mfd cell drivers separately.
  943. The drivers do not support all features the board exposes.
  944. endmenu
  945. endif
  946. menu "Multimedia Capabilities Port drivers"
  947. depends on ARCH_SA1100
  948. config MCP
  949. tristate
  950. # Interface drivers
  951. config MCP_SA11X0
  952. tristate "Support SA11x0 MCP interface"
  953. depends on ARCH_SA1100
  954. select MCP
  955. # Chip drivers
  956. config MCP_UCB1200
  957. bool "Support for UCB1200 / UCB1300"
  958. depends on MCP_SA11X0
  959. select MCP
  960. config MCP_UCB1200_TS
  961. tristate "Touchscreen interface support"
  962. depends on MCP_UCB1200 && INPUT
  963. endmenu