Kconfig 36 KB

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