Kconfig 32 KB

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