Kconfig 35 KB

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