Kconfig 36 KB

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