Kconfig 35 KB

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