Kconfig 32 KB

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