/drivers/mfd/Kconfig

http://github.com/mirrors/linux · #! · 1621 lines · 1433 code · 188 blank · 0 comment · 0 complexity · 381fd414db97a3cae21e25e031908b57 MD5 · raw file

  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_32 || (X86 && COMPILE_TEST))
  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_ALTERA_A10SR
  18. bool "Altera Arria10 DevKit System Resource chip"
  19. depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
  20. select REGMAP_SPI
  21. select MFD_CORE
  22. help
  23. Support for the Altera Arria10 DevKit MAX5 System Resource chip
  24. using the SPI interface. This driver provides common support for
  25. accessing the external gpio extender (LEDs & buttons) and
  26. power supply alarms (hwmon).
  27. config MFD_ACT8945A
  28. tristate "Active-semi ACT8945A"
  29. select MFD_CORE
  30. select REGMAP_I2C
  31. depends on I2C && OF
  32. help
  33. Support for the ACT8945A PMIC from Active-semi. This device
  34. features three step-down DC/DC converters and four low-dropout
  35. linear regulators, along with a complete ActivePath battery
  36. charger.
  37. config MFD_AS3711
  38. bool "AMS AS3711"
  39. select MFD_CORE
  40. select REGMAP_I2C
  41. select REGMAP_IRQ
  42. depends on I2C=y
  43. help
  44. Support for the AS3711 PMIC from AMS
  45. config MFD_AS3722
  46. bool "ams AS3722 Power Management IC"
  47. select MFD_CORE
  48. select REGMAP_I2C
  49. select REGMAP_IRQ
  50. depends on I2C=y && OF
  51. help
  52. The ams AS3722 is a compact system PMU suitable for mobile phones,
  53. tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
  54. controllers, 11 LDOs, RTC, automatic battery, temperature and
  55. over current monitoring, GPIOs, ADC and a watchdog.
  56. config PMIC_ADP5520
  57. bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  58. depends on I2C=y
  59. help
  60. Say yes here to add support for Analog Devices AD5520 and ADP5501,
  61. Multifunction Power Management IC. This includes
  62. the I2C driver and the core APIs _only_, you have to select
  63. individual components like LCD backlight, LEDs, GPIOs and Kepad
  64. under the corresponding menus.
  65. config MFD_AAT2870_CORE
  66. bool "AnalogicTech AAT2870"
  67. select MFD_CORE
  68. depends on I2C=y
  69. depends on GPIOLIB || COMPILE_TEST
  70. help
  71. If you say yes here you get support for the AAT2870.
  72. This driver provides common support for accessing the device,
  73. additional drivers must be enabled in order to use the
  74. functionality of the device.
  75. config MFD_ATMEL_FLEXCOM
  76. tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
  77. select MFD_CORE
  78. depends on OF
  79. help
  80. Select this to get support for Atmel Flexcom. This is a wrapper
  81. which embeds a SPI controller, a I2C controller and a USART. Only
  82. one function can be used at a time. The choice is done at boot time
  83. by the probe function of this MFD driver according to a device tree
  84. property.
  85. config MFD_ATMEL_HLCDC
  86. tristate "Atmel HLCDC (High-end LCD Controller)"
  87. select MFD_CORE
  88. select REGMAP_MMIO
  89. depends on OF
  90. help
  91. If you say yes here you get support for the HLCDC block.
  92. This driver provides common support for accessing the device,
  93. additional drivers must be enabled in order to use the
  94. functionality of the device.
  95. config MFD_BCM590XX
  96. tristate "Broadcom BCM590xx PMUs"
  97. select MFD_CORE
  98. select REGMAP_I2C
  99. depends on I2C
  100. help
  101. Support for the BCM590xx PMUs from Broadcom
  102. config MFD_AXP20X
  103. tristate
  104. select MFD_CORE
  105. select REGMAP_IRQ
  106. config MFD_AXP20X_I2C
  107. tristate "X-Powers AXP series PMICs with I2C"
  108. select MFD_AXP20X
  109. select REGMAP_I2C
  110. depends on I2C
  111. help
  112. If you say Y here you get support for the X-Powers AXP series power
  113. management ICs (PMICs) controlled with I2C.
  114. This driver include only the core APIs. You have to select individual
  115. components like regulators or the PEK (Power Enable Key) under the
  116. corresponding menus.
  117. config MFD_AXP20X_RSB
  118. tristate "X-Powers AXP series PMICs with RSB"
  119. select MFD_AXP20X
  120. depends on SUNXI_RSB
  121. help
  122. If you say Y here you get support for the X-Powers AXP series power
  123. management ICs (PMICs) controlled with RSB.
  124. This driver include only the core APIs. You have to select individual
  125. components like regulators or the PEK (Power Enable Key) under the
  126. corresponding menus.
  127. config MFD_CROS_EC
  128. tristate "ChromeOS Embedded Controller"
  129. select MFD_CORE
  130. select CHROME_PLATFORMS
  131. select CROS_EC_PROTO
  132. depends on X86 || ARM || ARM64 || COMPILE_TEST
  133. help
  134. If you say Y here you get support for the ChromeOS Embedded
  135. Controller (EC) providing keyboard, battery and power services.
  136. You also need to enable the driver for the bus you are using. The
  137. protocol for talking to the EC is defined by the bus driver.
  138. config MFD_CROS_EC_I2C
  139. tristate "ChromeOS Embedded Controller (I2C)"
  140. depends on MFD_CROS_EC && I2C
  141. help
  142. If you say Y here, you get support for talking to the ChromeOS
  143. EC through an I2C bus. This uses a simple byte-level protocol with
  144. a checksum. Failing accesses will be retried three times to
  145. improve reliability.
  146. config MFD_CROS_EC_SPI
  147. tristate "ChromeOS Embedded Controller (SPI)"
  148. depends on MFD_CROS_EC && SPI
  149. ---help---
  150. If you say Y here, you get support for talking to the ChromeOS EC
  151. through a SPI bus, using a byte-level protocol. Since the EC's
  152. response time cannot be guaranteed, we support ignoring
  153. 'pre-amble' bytes before the response actually starts.
  154. config MFD_ASIC3
  155. bool "Compaq ASIC3"
  156. depends on GPIOLIB && ARM
  157. select MFD_CORE
  158. ---help---
  159. This driver supports the ASIC3 multifunction chip found on many
  160. PDAs (mainly iPAQ and HTC based ones)
  161. config PMIC_DA903X
  162. bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
  163. depends on I2C=y
  164. help
  165. Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
  166. ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
  167. usually found on PXA processors-based platforms. This includes
  168. the I2C driver and the core APIs _only_, you have to select
  169. individual components like LCD backlight, voltage regulators,
  170. LEDs and battery-charger under the corresponding menus.
  171. config PMIC_DA9052
  172. bool
  173. select MFD_CORE
  174. config MFD_DA9052_SPI
  175. bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
  176. select REGMAP_SPI
  177. select REGMAP_IRQ
  178. select PMIC_DA9052
  179. depends on SPI_MASTER=y
  180. help
  181. Support for the Dialog Semiconductor DA9052 PMIC
  182. when controlled using SPI. This driver provides common support
  183. for accessing the device, additional drivers must be enabled in
  184. order to use the functionality of the device.
  185. config MFD_DA9052_I2C
  186. bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
  187. select REGMAP_I2C
  188. select REGMAP_IRQ
  189. select PMIC_DA9052
  190. depends on I2C=y
  191. help
  192. Support for the Dialog Semiconductor DA9052 PMIC
  193. when controlled using I2C. This driver provides common support
  194. for accessing the device, additional drivers must be enabled in
  195. order to use the functionality of the device.
  196. config MFD_DA9055
  197. bool "Dialog Semiconductor DA9055 PMIC Support"
  198. select REGMAP_I2C
  199. select REGMAP_IRQ
  200. select MFD_CORE
  201. depends on I2C=y
  202. help
  203. Say yes here for support of Dialog Semiconductor DA9055. This is
  204. a Power Management IC. This driver provides common support for
  205. accessing the device as well as the I2C interface to the chip itself.
  206. Additional drivers must be enabled in order to use the functionality
  207. of the device.
  208. This driver can be built as a module. If built as a module it will be
  209. called "da9055"
  210. config MFD_DA9062
  211. tristate "Dialog Semiconductor DA9062 PMIC Support"
  212. select MFD_CORE
  213. select REGMAP_I2C
  214. select REGMAP_IRQ
  215. depends on I2C
  216. help
  217. Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
  218. This includes the I2C driver and core APIs.
  219. Additional drivers must be enabled in order to use the functionality
  220. of the device.
  221. config MFD_DA9063
  222. tristate "Dialog Semiconductor DA9063 PMIC Support"
  223. select MFD_CORE
  224. select REGMAP_I2C
  225. select REGMAP_IRQ
  226. depends on I2C
  227. help
  228. Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
  229. This includes the I2C driver and core APIs.
  230. Additional drivers must be enabled in order to use the functionality
  231. of the device.
  232. config MFD_DA9150
  233. tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
  234. depends on I2C
  235. select MFD_CORE
  236. select REGMAP_I2C
  237. select REGMAP_IRQ
  238. help
  239. This adds support for the DA9150 integrated charger and fuel-gauge
  240. chip. This driver provides common support for accessing the device.
  241. Additional drivers must be enabled in order to use the specific
  242. features of the device.
  243. config MFD_DLN2
  244. tristate "Diolan DLN2 support"
  245. select MFD_CORE
  246. depends on USB
  247. help
  248. This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
  249. DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
  250. etc. must be enabled in order to use the functionality of
  251. the device.
  252. config MFD_MC13XXX
  253. tristate
  254. depends on (SPI_MASTER || I2C)
  255. select MFD_CORE
  256. select REGMAP_IRQ
  257. help
  258. Enable support for the Freescale MC13783 and MC13892 PMICs.
  259. This driver provides common support for accessing the device,
  260. additional drivers must be enabled in order to use the
  261. functionality of the device.
  262. config MFD_MC13XXX_SPI
  263. tristate "Freescale MC13783 and MC13892 SPI interface"
  264. depends on SPI_MASTER
  265. select REGMAP_SPI
  266. select MFD_MC13XXX
  267. help
  268. Select this if your MC13xxx is connected via an SPI bus.
  269. config MFD_MC13XXX_I2C
  270. tristate "Freescale MC13892 I2C interface"
  271. depends on I2C
  272. select REGMAP_I2C
  273. select MFD_MC13XXX
  274. help
  275. Select this if your MC13xxx is connected via an I2C bus.
  276. config MFD_MX25_TSADC
  277. tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
  278. select REGMAP_MMIO
  279. depends on (SOC_IMX25 && OF) || COMPILE_TEST
  280. help
  281. Enable support for the integrated Touchscreen and ADC unit of the
  282. i.MX25 processors. They consist of a conversion queue for general
  283. purpose ADC and a queue for Touchscreens.
  284. config MFD_HI6421_PMIC
  285. tristate "HiSilicon Hi6421 PMU/Codec IC"
  286. depends on OF
  287. select MFD_CORE
  288. select REGMAP_MMIO
  289. help
  290. Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
  291. functions, such as regulators, RTC, codec, Coulomb counter, etc.
  292. This driver includes core APIs _only_. You have to select
  293. individul components like voltage regulators under corresponding
  294. menus in order to enable them.
  295. We communicate with the Hi6421 via memory-mapped I/O.
  296. config MFD_HI655X_PMIC
  297. tristate "HiSilicon Hi655X series PMU/Codec IC"
  298. depends on ARCH_HISI || COMPILE_TEST
  299. depends on OF
  300. select MFD_CORE
  301. select REGMAP_MMIO
  302. select REGMAP_IRQ
  303. help
  304. Select this option to enable Hisilicon hi655x series pmic driver.
  305. config HTC_EGPIO
  306. bool "HTC EGPIO support"
  307. depends on GPIOLIB && ARM
  308. help
  309. This driver supports the CPLD egpio chip present on
  310. several HTC phones. It provides basic support for input
  311. pins, output pins, and irqs.
  312. config HTC_PASIC3
  313. tristate "HTC PASIC3 LED/DS1WM chip support"
  314. select MFD_CORE
  315. help
  316. This core driver provides register access for the LED/DS1WM
  317. chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
  318. HTC Magician devices, respectively. Actual functionality is
  319. handled by the leds-pasic3 and ds1wm drivers.
  320. config HTC_I2CPLD
  321. bool "HTC I2C PLD chip support"
  322. depends on I2C=y && GPIOLIB
  323. help
  324. If you say yes here you get support for the supposed CPLD
  325. found on omap850 HTC devices like the HTC Wizard and HTC Herald.
  326. This device provides input and output GPIOs through an I2C
  327. interface to one or more sub-chips.
  328. config MFD_INTEL_QUARK_I2C_GPIO
  329. tristate "Intel Quark MFD I2C GPIO"
  330. depends on PCI
  331. depends on X86
  332. depends on COMMON_CLK
  333. select MFD_CORE
  334. help
  335. This MFD provides support for I2C and GPIO that exist only
  336. in a single PCI device. It splits the 2 IO devices to
  337. their respective IO driver.
  338. The GPIO exports a total amount of 8 interrupt-capable GPIOs.
  339. config LPC_ICH
  340. tristate "Intel ICH LPC"
  341. depends on PCI
  342. select MFD_CORE
  343. help
  344. The LPC bridge function of the Intel ICH provides support for
  345. many functional units. This driver provides needed support for
  346. other drivers to control these functions, currently GPIO and
  347. watchdog.
  348. config LPC_SCH
  349. tristate "Intel SCH LPC"
  350. depends on PCI
  351. select MFD_CORE
  352. help
  353. LPC bridge function of the Intel SCH provides support for
  354. System Management Bus and General Purpose I/O.
  355. config INTEL_SOC_PMIC
  356. bool "Support for Intel Atom SoC PMIC"
  357. depends on GPIOLIB
  358. depends on I2C=y
  359. select MFD_CORE
  360. select REGMAP_I2C
  361. select REGMAP_IRQ
  362. help
  363. Select this option to enable support for the PMIC device
  364. on some Intel SoC systems. The PMIC provides ADC, GPIO,
  365. thermal, charger and related power management functions
  366. on these systems.
  367. config MFD_INTEL_LPSS
  368. tristate
  369. select COMMON_CLK
  370. select MFD_CORE
  371. config MFD_INTEL_LPSS_ACPI
  372. tristate "Intel Low Power Subsystem support in ACPI mode"
  373. select MFD_INTEL_LPSS
  374. depends on X86 && ACPI
  375. help
  376. This driver supports Intel Low Power Subsystem (LPSS) devices such as
  377. I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
  378. PCH) in ACPI mode.
  379. config MFD_INTEL_LPSS_PCI
  380. tristate "Intel Low Power Subsystem support in PCI mode"
  381. select MFD_INTEL_LPSS
  382. depends on X86 && PCI
  383. help
  384. This driver supports Intel Low Power Subsystem (LPSS) devices such as
  385. I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
  386. PCH) in PCI mode.
  387. config MFD_INTEL_MSIC
  388. bool "Intel MSIC"
  389. depends on INTEL_SCU_IPC
  390. select MFD_CORE
  391. help
  392. Select this option to enable access to Intel MSIC (Avatele
  393. Passage) chip. This chip embeds audio, battery, GPIO, etc.
  394. devices used in Intel Medfield platforms.
  395. config MFD_IPAQ_MICRO
  396. bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
  397. depends on SA1100_H3100 || SA1100_H3600
  398. select MFD_CORE
  399. help
  400. Select this to get support for the Microcontroller found in
  401. the Compaq iPAQ handheld computers. This is an Atmel
  402. AT90LS8535 microcontroller flashed with a special iPAQ
  403. firmware using the custom protocol implemented in this driver.
  404. config MFD_JANZ_CMODIO
  405. tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
  406. select MFD_CORE
  407. depends on PCI
  408. help
  409. This is the core driver for the Janz CMOD-IO PCI MODULbus
  410. carrier board. This device is a PCI to MODULbus bridge which may
  411. host many different types of MODULbus daughterboards, including
  412. CAN and GPIO controllers.
  413. config MFD_JZ4740_ADC
  414. bool "Janz JZ4740 ADC core"
  415. select MFD_CORE
  416. select GENERIC_IRQ_CHIP
  417. depends on MACH_JZ4740
  418. help
  419. Say yes here if you want support for the ADC unit in the JZ4740 SoC.
  420. This driver is necessary for jz4740-battery and jz4740-hwmon driver.
  421. config MFD_KEMPLD
  422. tristate "Kontron module PLD device"
  423. select MFD_CORE
  424. help
  425. This is the core driver for the PLD (Programmable Logic Device) found
  426. on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
  427. device may provide functions like watchdog, GPIO, UART and I2C bus.
  428. The following modules are supported:
  429. * COMe-bBL6
  430. * COMe-bHL6
  431. * COMe-bIP#
  432. * COMe-bPC2 (ETXexpress-PC)
  433. * COMe-bSC# (ETXexpress-SC T#)
  434. * COMe-cBL6
  435. * COMe-cBT6
  436. * COMe-cBW6
  437. * COMe-cCT6
  438. * COMe-cDC2 (microETXexpress-DC)
  439. * COMe-cHL6
  440. * COMe-cPC2 (microETXexpress-PC)
  441. * COMe-cSL6
  442. * COMe-mAL10
  443. * COMe-mBT10
  444. * COMe-mCT10
  445. * COMe-mTT10 (nanoETXexpress-TT)
  446. * ETX-OH
  447. This driver can also be built as a module. If so, the module
  448. will be called kempld-core.
  449. config MFD_88PM800
  450. tristate "Marvell 88PM800"
  451. depends on I2C
  452. select REGMAP_I2C
  453. select REGMAP_IRQ
  454. select MFD_CORE
  455. help
  456. This supports for Marvell 88PM800 Power Management IC.
  457. This includes the I2C driver and the core APIs _only_, you have to
  458. select individual components like voltage regulators, RTC and
  459. battery-charger under the corresponding menus.
  460. config MFD_88PM805
  461. tristate "Marvell 88PM805"
  462. depends on I2C
  463. select REGMAP_I2C
  464. select REGMAP_IRQ
  465. select MFD_CORE
  466. help
  467. This supports for Marvell 88PM805 Power Management IC. This includes
  468. the I2C driver and the core APIs _only_, you have to select individual
  469. components like codec device, headset/Mic device under the
  470. corresponding menus.
  471. config MFD_88PM860X
  472. bool "Marvell 88PM8606/88PM8607"
  473. depends on I2C=y
  474. select REGMAP_I2C
  475. select MFD_CORE
  476. help
  477. This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  478. This includes the I2C driver and the core APIs _only_, you have to
  479. select individual components like voltage regulators, RTC and
  480. battery-charger under the corresponding menus.
  481. config MFD_MAX14577
  482. tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
  483. depends on I2C
  484. select MFD_CORE
  485. select REGMAP_I2C
  486. select REGMAP_IRQ
  487. select IRQ_DOMAIN
  488. help
  489. Say yes here to add support for Maxim Semiconductor MAX14577 and
  490. MAX77836 Micro-USB ICs with battery charger.
  491. This driver provides common support for accessing the device;
  492. additional drivers must be enabled in order to use the functionality
  493. of the device.
  494. config MFD_MAX77620
  495. bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
  496. depends on I2C=y
  497. depends on OF
  498. select MFD_CORE
  499. select REGMAP_I2C
  500. select REGMAP_IRQ
  501. select IRQ_DOMAIN
  502. help
  503. Say yes here to add support for Maxim Semiconductor MAX77620 and
  504. MAX20024 which are Power Management IC with General purpose pins,
  505. RTC, regulators, clock generator, watchdog etc. This driver
  506. provides common support for accessing the device; additional drivers
  507. must be enabled in order to use the functionality of the device.
  508. config MFD_MAX77686
  509. tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
  510. depends on I2C
  511. depends on OF
  512. select MFD_CORE
  513. select REGMAP_I2C
  514. select REGMAP_IRQ
  515. select IRQ_DOMAIN
  516. help
  517. Say yes here to add support for Maxim Semiconductor MAX77686 and
  518. MAX77802 which are Power Management IC with an RTC on chip.
  519. This driver provides common support for accessing the device;
  520. additional drivers must be enabled in order to use the functionality
  521. of the device.
  522. config MFD_MAX77693
  523. tristate "Maxim Semiconductor MAX77693 PMIC Support"
  524. depends on I2C
  525. select MFD_CORE
  526. select REGMAP_I2C
  527. select REGMAP_IRQ
  528. help
  529. Say yes here to add support for Maxim Semiconductor MAX77693.
  530. This is a companion Power Management IC with Flash, Haptic, Charger,
  531. and MUIC(Micro USB Interface Controller) controls on chip.
  532. This driver provides common support for accessing the device;
  533. additional drivers must be enabled in order to use the functionality
  534. of the device.
  535. config MFD_MAX77843
  536. bool "Maxim Semiconductor MAX77843 PMIC Support"
  537. depends on I2C=y
  538. select MFD_CORE
  539. select REGMAP_I2C
  540. select REGMAP_IRQ
  541. help
  542. Say yes here to add support for Maxim Semiconductor MAX77843.
  543. This is companion Power Management IC with LEDs, Haptic, Charger,
  544. Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
  545. This driver provides common support for accessing the device;
  546. additional drivers must be enabled in order to use the functionality
  547. of the device.
  548. config MFD_MAX8907
  549. tristate "Maxim Semiconductor MAX8907 PMIC Support"
  550. select MFD_CORE
  551. depends on I2C
  552. select REGMAP_I2C
  553. select REGMAP_IRQ
  554. help
  555. Say yes here to add support for Maxim Semiconductor MAX8907. This is
  556. a Power Management IC. This driver provides common support for
  557. accessing the device; additional drivers must be enabled in order
  558. to use the functionality of the device.
  559. config MFD_MAX8925
  560. bool "Maxim Semiconductor MAX8925 PMIC Support"
  561. depends on I2C=y
  562. select MFD_CORE
  563. help
  564. Say yes here to add support for Maxim Semiconductor MAX8925. This is
  565. a Power Management IC. This driver provides common support for
  566. accessing the device, additional drivers must be enabled in order
  567. to use the functionality of the device.
  568. config MFD_MAX8997
  569. bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
  570. depends on I2C=y
  571. select MFD_CORE
  572. select IRQ_DOMAIN
  573. help
  574. Say yes here to add support for Maxim Semiconductor MAX8997/8966.
  575. This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
  576. MUIC controls on chip.
  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.
  580. config MFD_MAX8998
  581. bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
  582. depends on I2C=y
  583. select MFD_CORE
  584. select IRQ_DOMAIN
  585. help
  586. Say yes here to add support for Maxim Semiconductor MAX8998 and
  587. National Semiconductor LP3974. This is a Power Management IC.
  588. This driver provides common support for accessing the device,
  589. additional drivers must be enabled in order to use the functionality
  590. of the device.
  591. config MFD_MT6397
  592. tristate "MediaTek MT6397 PMIC Support"
  593. select MFD_CORE
  594. select IRQ_DOMAIN
  595. help
  596. Say yes here to add support for MediaTek MT6397 PMIC. This is
  597. a Power Management IC. This driver provides common support for
  598. accessing the device; additional drivers must be enabled in order
  599. to use the functionality of the device.
  600. config MFD_MENF21BMC
  601. tristate "MEN 14F021P00 Board Management Controller Support"
  602. depends on I2C
  603. select MFD_CORE
  604. help
  605. Say yes here to add support for the MEN 14F021P00 BMC
  606. which is a Board Management Controller connected to the I2C bus.
  607. The device supports multiple sub-devices like LED, HWMON and WDT.
  608. This driver provides common support for accessing the devices;
  609. additional drivers must be enabled in order to use the
  610. functionality of the BMC device.
  611. This driver can also be built as a module. If so the module
  612. will be called menf21bmc.
  613. config EZX_PCAP
  614. bool "Motorola EZXPCAP Support"
  615. depends on SPI_MASTER
  616. help
  617. This enables the PCAP ASIC present on EZX Phones. This is
  618. needed for MMC, TouchScreen, Sound, USB, etc..
  619. config MFD_VIPERBOARD
  620. tristate "Nano River Technologies Viperboard"
  621. select MFD_CORE
  622. depends on USB
  623. default n
  624. help
  625. Say yes here if you want support for Nano River Technologies
  626. Viperboard.
  627. There are mfd cell drivers available for i2c master, adc and
  628. both gpios found on the board. The spi part does not yet
  629. have a driver.
  630. You need to select the mfd cell drivers separately.
  631. The drivers do not support all features the board exposes.
  632. config MFD_RETU
  633. tristate "Nokia Retu and Tahvo multi-function device"
  634. select MFD_CORE
  635. depends on I2C
  636. select REGMAP_IRQ
  637. help
  638. Retu and Tahvo are a multi-function devices found on Nokia
  639. Internet Tablets (770, N800 and N810).
  640. config MFD_PCF50633
  641. tristate "NXP PCF50633"
  642. depends on I2C
  643. select REGMAP_I2C
  644. help
  645. Say yes here if you have NXP PCF50633 chip on your board.
  646. This core driver provides register access and IRQ handling
  647. facilities, and registers devices for the various functions
  648. so that function-specific drivers can bind to them.
  649. config PCF50633_ADC
  650. tristate "NXP PCF50633 ADC"
  651. depends on MFD_PCF50633
  652. help
  653. Say yes here if you want to include support for ADC in the
  654. NXP PCF50633 chip.
  655. config PCF50633_GPIO
  656. tristate "NXP PCF50633 GPIO"
  657. depends on MFD_PCF50633
  658. help
  659. Say yes here if you want to include support GPIO for pins on
  660. the PCF50633 chip.
  661. config UCB1400_CORE
  662. tristate "Philips UCB1400 Core driver"
  663. depends on AC97_BUS
  664. depends on GPIOLIB
  665. help
  666. This enables support for the Philips UCB1400 core functions.
  667. The UCB1400 is an AC97 audio codec.
  668. To compile this driver as a module, choose M here: the
  669. module will be called ucb1400_core.
  670. config MFD_PM8XXX
  671. tristate
  672. config MFD_PM8921_CORE
  673. tristate "Qualcomm PM8921 PMIC chip"
  674. depends on (ARM || HEXAGON)
  675. select IRQ_DOMAIN
  676. select MFD_CORE
  677. select MFD_PM8XXX
  678. select REGMAP
  679. help
  680. If you say yes to this option, support will be included for the
  681. built-in PM8921 PMIC chip.
  682. This is required if your board has a PM8921 and uses its features,
  683. such as: MPPs, GPIOs, regulators, interrupts, and PWM.
  684. Say M here if you want to include support for PM8921 chip as a module.
  685. This will build a module called "pm8921-core".
  686. config MFD_QCOM_RPM
  687. tristate "Qualcomm Resource Power Manager (RPM)"
  688. depends on ARCH_QCOM && OF
  689. help
  690. If you say yes to this option, support will be included for the
  691. Resource Power Manager system found in the Qualcomm 8660, 8960 and
  692. 8064 based devices.
  693. This is required to access many regulators, clocks and bus
  694. frequencies controlled by the RPM on these devices.
  695. Say M here if you want to include support for the Qualcomm RPM as a
  696. module. This will build a module called "qcom_rpm".
  697. config MFD_SPMI_PMIC
  698. tristate "Qualcomm SPMI PMICs"
  699. depends on ARCH_QCOM || COMPILE_TEST
  700. depends on OF
  701. depends on SPMI
  702. select REGMAP_SPMI
  703. help
  704. This enables support for the Qualcomm SPMI PMICs.
  705. These PMICs are currently used with the Snapdragon 800 series of
  706. SoCs. Note, that this will only be useful paired with descriptions
  707. of the independent functions as children nodes in the device tree.
  708. Say M here if you want to include support for the SPMI PMIC
  709. series as a module. The module will be called "qcom-spmi-pmic".
  710. config MFD_RDC321X
  711. tristate "RDC R-321x southbridge"
  712. select MFD_CORE
  713. depends on PCI
  714. help
  715. Say yes here if you want to have support for the RDC R-321x SoC
  716. southbridge which provides access to GPIOs and Watchdog using the
  717. southbridge PCI device configuration space.
  718. config MFD_RTSX_PCI
  719. tristate "Realtek PCI-E card reader"
  720. depends on PCI
  721. select MFD_CORE
  722. help
  723. This supports for Realtek PCI-Express card reader including rts5209,
  724. rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
  725. Realtek card reader supports access to many types of memory cards,
  726. such as Memory Stick, Memory Stick Pro, Secure Digital and
  727. MultiMediaCard.
  728. config MFD_RT5033
  729. tristate "Richtek RT5033 Power Management IC"
  730. depends on I2C
  731. select MFD_CORE
  732. select REGMAP_I2C
  733. select REGMAP_IRQ
  734. help
  735. This driver provides for the Richtek RT5033 Power Management IC,
  736. which includes the I2C driver and the Core APIs. This driver provides
  737. common support for accessing the device. The device supports multiple
  738. sub-devices like charger, fuel gauge, flash LED, current source,
  739. LDO and Buck.
  740. config MFD_RTSX_USB
  741. tristate "Realtek USB card reader"
  742. depends on USB
  743. select MFD_CORE
  744. help
  745. Select this option to get support for Realtek USB 2.0 card readers
  746. including RTS5129, RTS5139, RTS5179 and RTS5170.
  747. Realtek card reader supports access to many types of memory cards,
  748. such as Memory Stick Pro, Secure Digital and MultiMediaCard.
  749. config MFD_RC5T583
  750. bool "Ricoh RC5T583 Power Management system device"
  751. depends on I2C=y
  752. select MFD_CORE
  753. select REGMAP_I2C
  754. help
  755. Select this option to get support for the RICOH583 Power
  756. Management system device.
  757. This driver provides common support for accessing the device
  758. through i2c interface. The device supports multiple sub-devices
  759. like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
  760. Additional drivers must be enabled in order to use the
  761. different functionality of the device.
  762. config MFD_RK808
  763. tristate "Rockchip RK808 Power Management chip"
  764. depends on I2C && OF
  765. select MFD_CORE
  766. select REGMAP_I2C
  767. select REGMAP_IRQ
  768. help
  769. If you say yes here you get support for the RK808
  770. Power Management chips.
  771. This driver provides common support for accessing the device
  772. through I2C interface. The device supports multiple sub-devices
  773. including interrupts, RTC, LDO & DCDC regulators, and onkey.
  774. config MFD_RN5T618
  775. tristate "Ricoh RN5T567/618 PMIC"
  776. depends on I2C
  777. depends on OF
  778. select MFD_CORE
  779. select REGMAP_I2C
  780. help
  781. Say yes here to add support for the Ricoh RN5T567 or R5T618 PMIC.
  782. This driver provides common support for accessing the device,
  783. additional drivers must be enabled in order to use the
  784. functionality of the device.
  785. config MFD_SEC_CORE
  786. bool "SAMSUNG Electronics PMIC Series Support"
  787. depends on I2C=y
  788. select MFD_CORE
  789. select REGMAP_I2C
  790. select REGMAP_IRQ
  791. help
  792. Support for the Samsung Electronics MFD series.
  793. This driver provides common support for accessing the device,
  794. additional drivers must be enabled in order to use the functionality
  795. of the device
  796. config MFD_SI476X_CORE
  797. tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
  798. depends on I2C
  799. select MFD_CORE
  800. select REGMAP_I2C
  801. help
  802. This is the core driver for the SI476x series of AM/FM
  803. radio. This MFD driver connects the radio-si476x V4L2 module
  804. and the si476x audio codec.
  805. To compile this driver as a module, choose M here: the
  806. module will be called si476x-core.
  807. config MFD_SM501
  808. tristate "Silicon Motion SM501"
  809. ---help---
  810. This is the core driver for the Silicon Motion SM501 multimedia
  811. companion chip. This device is a multifunction device which may
  812. provide numerous interfaces including USB host controller, USB gadget,
  813. asynchronous serial ports, audio functions, and a dual display video
  814. interface. The device may be connected by PCI or local bus with
  815. varying functions enabled.
  816. config MFD_SM501_GPIO
  817. bool "Export GPIO via GPIO layer"
  818. depends on MFD_SM501 && GPIOLIB
  819. ---help---
  820. This option uses the gpio library layer to export the 64 GPIO
  821. lines on the SM501. The platform data is used to supply the
  822. base number for the first GPIO line to register.
  823. config MFD_SKY81452
  824. tristate "Skyworks Solutions SKY81452"
  825. select MFD_CORE
  826. select REGMAP_I2C
  827. depends on I2C
  828. help
  829. This is the core driver for the Skyworks SKY81452 backlight and
  830. voltage regulator device.
  831. This driver can also be built as a module. If so, the module
  832. will be called sky81452.
  833. config MFD_SMSC
  834. bool "SMSC ECE1099 series chips"
  835. depends on I2C=y
  836. select MFD_CORE
  837. select REGMAP_I2C
  838. help
  839. If you say yes here you get support for the
  840. ece1099 chips from SMSC.
  841. To compile this driver as a module, choose M here: the
  842. module will be called smsc.
  843. config ABX500_CORE
  844. bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
  845. default y if ARCH_U300 || ARCH_U8500
  846. help
  847. Say yes here if you have the ABX500 Mixed Signal IC family
  848. chips. This core driver expose register access functions.
  849. Functionality specific drivers using these functions can
  850. remain unchanged when IC changes. Binding of the functions to
  851. actual register access is done by the IC core driver.
  852. config AB3100_CORE
  853. bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
  854. depends on I2C=y && ABX500_CORE
  855. select MFD_CORE
  856. default y if ARCH_U300
  857. help
  858. Select this to enable the AB3100 Mixed Signal IC core
  859. functionality. This connects to a AB3100 on the I2C bus
  860. and expose a number of symbols needed for dependent devices
  861. to read and write registers and subscribe to events from
  862. this multi-functional IC. This is needed to use other features
  863. of the AB3100 such as battery-backed RTC, charging control,
  864. LEDs, vibrator, system power and temperature, power management
  865. and ALSA sound.
  866. config AB3100_OTP
  867. tristate "ST-Ericsson AB3100 OTP functions"
  868. depends on AB3100_CORE
  869. default y if AB3100_CORE
  870. help
  871. Select this to enable the AB3100 Mixed Signal IC OTP (one-time
  872. programmable memory) support. This exposes a sysfs file to read
  873. out OTP values.
  874. config AB8500_CORE
  875. bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
  876. depends on ABX500_CORE && MFD_DB8500_PRCMU
  877. select POWER_SUPPLY
  878. select MFD_CORE
  879. select IRQ_DOMAIN
  880. help
  881. Select this option to enable access to AB8500 power management
  882. chip. This connects to U8500 either on the SSP/SPI bus (deprecated
  883. since hardware version v1.0) or the I2C bus via PRCMU. It also adds
  884. the irq_chip parts for handling the Mixed Signal chip events.
  885. This chip embeds various other multimedia funtionalities as well.
  886. config AB8500_DEBUG
  887. bool "Enable debug info via debugfs"
  888. depends on AB8500_GPADC && DEBUG_FS
  889. default y if DEBUG_FS
  890. help
  891. Select this option if you want debug information using the debug
  892. filesystem, debugfs.
  893. config AB8500_GPADC
  894. bool "ST-Ericsson AB8500 GPADC driver"
  895. depends on AB8500_CORE && REGULATOR_AB8500
  896. default y
  897. help
  898. AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
  899. config MFD_DB8500_PRCMU
  900. bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
  901. depends on UX500_SOC_DB8500
  902. select MFD_CORE
  903. help
  904. Select this option to enable support for the DB8500 Power Reset
  905. and Control Management Unit. This is basically an autonomous
  906. system controller running an XP70 microprocessor, which is accessed
  907. through a register map.
  908. config MFD_STMPE
  909. bool "STMicroelectronics STMPE"
  910. depends on (I2C=y || SPI_MASTER=y)
  911. depends on OF
  912. select MFD_CORE
  913. help
  914. Support for the STMPE family of I/O Expanders from
  915. STMicroelectronics.
  916. Currently supported devices are:
  917. STMPE811: GPIO, Touchscreen
  918. STMPE1601: GPIO, Keypad
  919. STMPE1801: GPIO, Keypad
  920. STMPE2401: GPIO, Keypad
  921. STMPE2403: GPIO, Keypad
  922. This driver provides common support for accessing the device,
  923. additional drivers must be enabled in order to use the functionality
  924. of the device. Currently available sub drivers are:
  925. GPIO: stmpe-gpio
  926. Keypad: stmpe-keypad
  927. Touchscreen: stmpe-ts
  928. menu "STMicroelectronics STMPE Interface Drivers"
  929. depends on MFD_STMPE
  930. config STMPE_I2C
  931. bool "STMicroelectronics STMPE I2C Interface"
  932. depends on I2C=y
  933. default y
  934. help
  935. This is used to enable I2C interface of STMPE
  936. config STMPE_SPI
  937. bool "STMicroelectronics STMPE SPI Interface"
  938. depends on SPI_MASTER
  939. help
  940. This is used to enable SPI interface of STMPE
  941. endmenu
  942. config MFD_STA2X11
  943. bool "STMicroelectronics STA2X11"
  944. depends on STA2X11
  945. select MFD_CORE
  946. select REGMAP_MMIO
  947. config MFD_SUN6I_PRCM
  948. bool "Allwinner A31 PRCM controller"
  949. depends on ARCH_SUNXI
  950. select MFD_CORE
  951. help
  952. Support for the PRCM (Power/Reset/Clock Management) unit available
  953. in A31 SoC.
  954. config MFD_SYSCON
  955. bool "System Controller Register R/W Based on Regmap"
  956. select REGMAP_MMIO
  957. help
  958. Select this option to enable accessing system control registers
  959. via regmap.
  960. config MFD_DAVINCI_VOICECODEC
  961. tristate
  962. select MFD_CORE
  963. select REGMAP_MMIO
  964. config MFD_TI_AM335X_TSCADC
  965. tristate "TI ADC / Touch Screen chip support"
  966. select MFD_CORE
  967. select REGMAP
  968. select REGMAP_MMIO
  969. help
  970. If you say yes here you get support for Texas Instruments series
  971. of Touch Screen /ADC chips.
  972. To compile this driver as a module, choose M here: the
  973. module will be called ti_am335x_tscadc.
  974. config MFD_DM355EVM_MSP
  975. bool "TI DaVinci DM355 EVM microcontroller"
  976. depends on I2C=y && MACH_DAVINCI_DM355_EVM
  977. help
  978. This driver supports the MSP430 microcontroller used on these
  979. boards. MSP430 firmware manages resets and power sequencing,
  980. inputs from buttons and the IR remote, LEDs, an RTC, and more.
  981. config MFD_LP3943
  982. tristate "TI/National Semiconductor LP3943 MFD Driver"
  983. depends on I2C
  984. select MFD_CORE
  985. select REGMAP_I2C
  986. help
  987. Support for the TI/National Semiconductor LP3943.
  988. This driver consists of GPIO and PWM drivers.
  989. With these functionalities, it can be used for LED string control or
  990. general usage such like a GPIO controller and a PWM controller.
  991. config MFD_LP8788
  992. bool "TI LP8788 Power Management Unit Driver"
  993. depends on I2C=y
  994. select MFD_CORE
  995. select REGMAP_I2C
  996. select IRQ_DOMAIN
  997. help
  998. TI LP8788 PMU supports regulators, battery charger, RTC,
  999. ADC, backlight driver and current sinks.
  1000. config MFD_OMAP_USB_HOST
  1001. bool "TI OMAP USBHS core and TLL driver"
  1002. depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
  1003. default y
  1004. help
  1005. This is the core driver for the OAMP EHCI and OHCI drivers.
  1006. This MFD driver does the required setup functionalities for
  1007. OMAP USB Host drivers.
  1008. config MFD_PALMAS
  1009. bool "TI Palmas series chips"
  1010. select MFD_CORE
  1011. select REGMAP_I2C
  1012. select REGMAP_IRQ
  1013. depends on I2C=y
  1014. help
  1015. If you say yes here you get support for the Palmas
  1016. series of PMIC chips from Texas Instruments.
  1017. config TPS6105X
  1018. tristate "TI TPS61050/61052 Boost Converters"
  1019. depends on I2C
  1020. select REGMAP_I2C
  1021. select REGULATOR
  1022. select MFD_CORE
  1023. select REGULATOR_FIXED_VOLTAGE
  1024. help
  1025. This option enables a driver for the TP61050/TPS61052
  1026. high-power "white LED driver". This boost converter is
  1027. sometimes used for other things than white LEDs, and
  1028. also contains a GPIO pin.
  1029. config TPS65010
  1030. tristate "TI TPS6501x Power Management chips"
  1031. depends on I2C && GPIOLIB
  1032. default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
  1033. help
  1034. If you say yes here you get support for the TPS6501x series of
  1035. Power Management chips. These include voltage regulators,
  1036. lithium ion/polymer battery charging, and other features that
  1037. are often used in portable devices like cell phones and cameras.
  1038. This driver can also be built as a module. If so, the module
  1039. will be called tps65010.
  1040. config TPS6507X
  1041. tristate "TI TPS6507x Power Management / Touch Screen chips"
  1042. select MFD_CORE
  1043. depends on I2C
  1044. help
  1045. If you say yes here you get support for the TPS6507x series of
  1046. Power Management / Touch Screen chips. These include voltage
  1047. regulators, lithium ion/polymer battery charging, touch screen
  1048. and other features that are often used in portable devices.
  1049. This driver can also be built as a module. If so, the module
  1050. will be called tps6507x.
  1051. config MFD_TPS65086
  1052. tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
  1053. select REGMAP
  1054. select REGMAP_IRQ
  1055. select REGMAP_I2C
  1056. depends on I2C
  1057. help
  1058. If you say yes here you get support for the TPS65086 series of
  1059. Power Management chips.
  1060. This driver provides common support for accessing the device,
  1061. additional drivers must be enabled in order to use the
  1062. functionality of the device.
  1063. config TPS65911_COMPARATOR
  1064. tristate
  1065. config MFD_TPS65090
  1066. bool "TI TPS65090 Power Management chips"
  1067. depends on I2C=y
  1068. select MFD_CORE
  1069. select REGMAP_I2C
  1070. select REGMAP_IRQ
  1071. help
  1072. If you say yes here you get support for the TPS65090 series of
  1073. Power Management chips.
  1074. This driver provides common support for accessing the device,
  1075. additional drivers must be enabled in order to use the
  1076. functionality of the device.
  1077. config MFD_TPS65217
  1078. tristate "TI TPS65217 Power Management / White LED chips"
  1079. depends on I2C
  1080. select MFD_CORE
  1081. select REGMAP_I2C
  1082. help
  1083. If you say yes here you get support for the TPS65217 series of
  1084. Power Management / White LED chips.
  1085. These include voltage regulators, lithium ion/polymer battery
  1086. charger, wled and other features that are often used in portable
  1087. devices.
  1088. This driver can also be built as a module. If so, the module
  1089. will be called tps65217.
  1090. config MFD_TPS65218
  1091. tristate "TI TPS65218 Power Management chips"
  1092. depends on I2C
  1093. select MFD_CORE
  1094. select REGMAP_I2C
  1095. select REGMAP_IRQ
  1096. help
  1097. If you say yes here you get support for the TPS65218 series of
  1098. Power Management chips.
  1099. These include voltage regulators, gpio and other features
  1100. that are often used in portable devices. Only regulator
  1101. component is currently supported.
  1102. This driver can also be built as a module. If so, the module
  1103. will be called tps65218.
  1104. config MFD_TPS6586X
  1105. bool "TI TPS6586x Power Management chips"
  1106. depends on I2C=y
  1107. select MFD_CORE
  1108. select REGMAP_I2C
  1109. help
  1110. If you say yes here you get support for the TPS6586X series of
  1111. Power Management chips.
  1112. This driver provides common support for accessing the device,
  1113. additional drivers must be enabled in order to use the
  1114. functionality of the device.
  1115. This driver can also be built as a module. If so, the module
  1116. will be called tps6586x.
  1117. config MFD_TPS65910
  1118. bool "TI TPS65910 Power Management chip"
  1119. depends on I2C=y
  1120. depends on GPIOLIB || COMPILE_TEST
  1121. select MFD_CORE
  1122. select REGMAP_I2C
  1123. select REGMAP_IRQ
  1124. select IRQ_DOMAIN
  1125. help
  1126. if you say yes here you get support for the TPS65910 series of
  1127. Power Management chips.
  1128. config MFD_TPS65912
  1129. tristate
  1130. select MFD_CORE
  1131. select REGMAP
  1132. select REGMAP_IRQ
  1133. config MFD_TPS65912_I2C
  1134. tristate "TI TPS65912 Power Management chip with I2C"
  1135. select MFD_TPS65912
  1136. select REGMAP_I2C
  1137. depends on I2C
  1138. help
  1139. If you say yes here you get support for the TPS65912 series of
  1140. PM chips with I2C interface.
  1141. config MFD_TPS65912_SPI
  1142. tristate "TI TPS65912 Power Management chip with SPI"
  1143. select MFD_TPS65912
  1144. select REGMAP_SPI
  1145. depends on SPI_MASTER
  1146. help
  1147. If you say yes here you get support for the TPS65912 series of
  1148. PM chips with SPI interface.
  1149. config MFD_TPS80031
  1150. bool "TI TPS80031/TPS80032 Power Management chips"
  1151. depends on I2C=y
  1152. select MFD_CORE
  1153. select REGMAP_I2C
  1154. select REGMAP_IRQ
  1155. help
  1156. If you say yes here you get support for the Texas Instruments
  1157. TPS80031/ TPS80032 Fully Integrated Power Management with Power
  1158. Path and Battery Charger. The device provides five configurable
  1159. step-down converters, 11 general purpose LDOs, USB OTG Module,
  1160. ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
  1161. Power Path from USB, 32K clock generator.
  1162. config TWL4030_CORE
  1163. bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
  1164. depends on I2C=y
  1165. select IRQ_DOMAIN
  1166. select REGMAP_I2C
  1167. help
  1168. Say yes here if you have TWL4030 / TWL6030 family chip on your board.
  1169. This core driver provides register access and IRQ handling
  1170. facilities, and registers devices for the various functions
  1171. so that function-specific drivers can bind to them.
  1172. These multi-function chips are found on many OMAP2 and OMAP3
  1173. boards, providing power management, RTC, GPIO, keypad, a
  1174. high speed USB OTG transceiver, an audio codec (on most
  1175. versions) and many other features.
  1176. config TWL4030_POWER
  1177. bool "TI TWL4030 power resources"
  1178. depends on TWL4030_CORE && ARM
  1179. help
  1180. Say yes here if you want to use the power resources on the
  1181. TWL4030 family chips. Most of these resources are regulators,
  1182. which have a separate driver; some are control signals, such
  1183. as clock request handshaking.
  1184. This driver uses board-specific data to initialize the resources
  1185. and load scripts controlling which resources are switched off/on
  1186. or reset when a sleep, wakeup or warm reset event occurs.
  1187. config MFD_TWL4030_AUDIO
  1188. bool "TI TWL4030 Audio"
  1189. depends on TWL4030_CORE
  1190. select MFD_CORE
  1191. default n
  1192. config TWL6040_CORE
  1193. bool "TI TWL6040 audio codec"
  1194. depends on I2C=y
  1195. select MFD_CORE
  1196. select REGMAP_I2C
  1197. select REGMAP_IRQ
  1198. default n
  1199. help
  1200. Say yes here if you want support for Texas Instruments TWL6040 audio
  1201. codec.
  1202. This driver provides common support for accessing the device,
  1203. additional drivers must be enabled in order to use the
  1204. functionality of the device (audio, vibra).
  1205. config MENELAUS
  1206. bool "TI TWL92330/Menelaus PM chip"
  1207. depends on I2C=y && ARCH_OMAP2
  1208. help
  1209. If you say yes here you get support for the Texas Instruments
  1210. TWL92330/Menelaus Power Management chip. This include voltage
  1211. regulators, Dual slot memory card transceivers, real-time clock
  1212. and other features that are often used in portable devices like
  1213. cell phones and PDAs.
  1214. config MFD_WL1273_CORE
  1215. tristate "TI WL1273 FM radio"
  1216. depends on I2C
  1217. select MFD_CORE
  1218. default n
  1219. help
  1220. This is the core driver for the TI WL1273 FM radio. This MFD
  1221. driver connects the radio-wl1273 V4L2 module and the wl1273
  1222. audio codec.
  1223. config MFD_LM3533
  1224. tristate "TI/National Semiconductor LM3533 Lighting Power chip"
  1225. depends on I2C
  1226. select MFD_CORE
  1227. select REGMAP_I2C
  1228. help
  1229. Say yes here to enable support for National Semiconductor / TI
  1230. LM3533 Lighting Power chips.
  1231. This driver provides common support for accessing the device;
  1232. additional drivers must be enabled in order to use the LED,
  1233. backlight or ambient-light-sensor functionality of the device.
  1234. config MFD_TIMBERDALE
  1235. tristate "Timberdale FPGA"
  1236. select MFD_CORE
  1237. depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
  1238. ---help---
  1239. This is the core driver for the timberdale FPGA. This device is a
  1240. multifunction device which exposes numerous platform devices.
  1241. The timberdale FPGA can be found on the Intel Atom development board
  1242. for in-vehicle infontainment, called Russellville.
  1243. config MFD_TC3589X
  1244. bool "Toshiba TC35892 and variants"
  1245. depends on I2C=y
  1246. depends on OF
  1247. select MFD_CORE
  1248. help
  1249. Support for the Toshiba TC35892 and variants I/O Expander.
  1250. This driver provides common support for accessing the device,
  1251. additional drivers must be enabled in order to use the
  1252. functionality of the device.
  1253. config MFD_TMIO
  1254. bool
  1255. default n
  1256. config MFD_T7L66XB
  1257. bool "Toshiba T7L66XB"
  1258. depends on ARM && HAVE_CLK
  1259. select MFD_CORE
  1260. select MFD_TMIO
  1261. help
  1262. Support for Toshiba Mobile IO Controller T7L66XB
  1263. config MFD_TC6387XB
  1264. bool "Toshiba TC6387XB"
  1265. depends on ARM && HAVE_CLK
  1266. select MFD_CORE
  1267. select MFD_TMIO
  1268. help
  1269. Support for Toshiba Mobile IO Controller TC6387XB
  1270. config MFD_TC6393XB
  1271. bool "Toshiba TC6393XB"
  1272. depends on ARM && HAVE_CLK
  1273. select GPIOLIB
  1274. select MFD_CORE
  1275. select MFD_TMIO
  1276. help
  1277. Support for Toshiba Mobile IO Controller TC6393XB
  1278. config MFD_VX855
  1279. tristate "VIA VX855/VX875 integrated south bridge"
  1280. depends on PCI
  1281. select MFD_CORE
  1282. help
  1283. Say yes here to enable support for various functions of the
  1284. VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
  1285. and/or vx855_gpio drivers for this to do anything useful.
  1286. config MFD_ARIZONA
  1287. select REGMAP
  1288. select REGMAP_IRQ
  1289. select MFD_CORE
  1290. bool
  1291. config MFD_ARIZONA_I2C
  1292. tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
  1293. select MFD_ARIZONA
  1294. select REGMAP_I2C
  1295. depends on I2C
  1296. help
  1297. Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
  1298. audio SoC core functionality controlled via I2C.
  1299. config MFD_ARIZONA_SPI
  1300. tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
  1301. select MFD_ARIZONA
  1302. select REGMAP_SPI
  1303. depends on SPI_MASTER
  1304. help
  1305. Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
  1306. audio SoC core functionality controlled via SPI.
  1307. config MFD_CS47L24
  1308. bool "Cirrus Logic CS47L24 and WM1831"
  1309. depends on MFD_ARIZONA
  1310. help
  1311. Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
  1312. config MFD_WM5102
  1313. bool "Wolfson Microelectronics WM5102"
  1314. depends on MFD_ARIZONA
  1315. help
  1316. Support for Wolfson Microelectronics WM5102 low power audio SoC
  1317. config MFD_WM5110
  1318. bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
  1319. depends on MFD_ARIZONA
  1320. help
  1321. Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
  1322. low power audio SoC
  1323. config MFD_WM8997
  1324. bool "Wolfson Microelectronics WM8997"
  1325. depends on MFD_ARIZONA
  1326. help
  1327. Support for Wolfson Microelectronics WM8997 low power audio SoC
  1328. config MFD_WM8998
  1329. bool "Wolfson Microelectronics WM8998"
  1330. depends on MFD_ARIZONA
  1331. help
  1332. Support for Wolfson Microelectronics WM8998 low power audio SoC
  1333. config MFD_WM8400
  1334. bool "Wolfson Microelectronics WM8400"
  1335. select MFD_CORE
  1336. depends on I2C=y
  1337. select REGMAP_I2C
  1338. help
  1339. Support for the Wolfson Microelecronics WM8400 PMIC and audio
  1340. CODEC. This driver provides common support for accessing
  1341. the device, additional drivers must be enabled in order to use
  1342. the functionality of the device.
  1343. config MFD_WM831X
  1344. bool
  1345. config MFD_WM831X_I2C
  1346. bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
  1347. select MFD_CORE
  1348. select MFD_WM831X
  1349. select REGMAP_I2C
  1350. select IRQ_DOMAIN
  1351. depends on I2C=y
  1352. help
  1353. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  1354. when controlled using I2C. This driver provides common support
  1355. for accessing the device, additional drivers must be enabled in
  1356. order to use the functionality of the device.
  1357. config MFD_WM831X_SPI
  1358. bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
  1359. select MFD_CORE
  1360. select MFD_WM831X
  1361. select REGMAP_SPI
  1362. select IRQ_DOMAIN
  1363. depends on SPI_MASTER
  1364. help
  1365. Support for the Wolfson Microelecronics WM831x and WM832x PMICs
  1366. when controlled using SPI. This driver provides common support
  1367. for accessing the device, additional drivers must be enabled in
  1368. order to use the functionality of the device.
  1369. config MFD_WM8350
  1370. bool
  1371. config MFD_WM8350_I2C
  1372. bool "Wolfson Microelectronics WM8350 with I2C"
  1373. select MFD_WM8350
  1374. depends on I2C=y
  1375. help
  1376. The WM8350 is an integrated audio and power management
  1377. subsystem with watchdog and RTC functionality for embedded
  1378. systems. This option enables core support for the WM8350 with
  1379. I2C as the control interface. Additional options must be
  1380. selected to enable support for the functionality of the chip.
  1381. config MFD_WM8994
  1382. tristate "Wolfson Microelectronics WM8994"
  1383. select MFD_CORE
  1384. select REGMAP_I2C
  1385. select REGMAP_IRQ
  1386. depends on I2C
  1387. help
  1388. The WM8994 is a highly integrated hi-fi CODEC designed for
  1389. smartphone applications. As well as audio functionality it
  1390. has on board GPIO and regulator functionality which is
  1391. supported via the relevant subsystems. This driver provides
  1392. core support for the WM8994, in order to use the actual
  1393. functionaltiy of the device other drivers must be enabled.
  1394. config MFD_STW481X
  1395. tristate "Support for ST Microelectronics STw481x"
  1396. depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
  1397. select REGMAP_I2C
  1398. select MFD_CORE
  1399. help
  1400. Select this option to enable the STw481x chip driver used
  1401. in various ST Microelectronics and ST-Ericsson embedded
  1402. Nomadik series.
  1403. menu "Multimedia Capabilities Port drivers"
  1404. depends on ARCH_SA1100
  1405. config MCP
  1406. tristate
  1407. # Interface drivers
  1408. config MCP_SA11X0
  1409. tristate "Support SA11x0 MCP interface"
  1410. depends on ARCH_SA1100
  1411. select MCP
  1412. # Chip drivers
  1413. config MCP_UCB1200
  1414. tristate "Support for UCB1200 / UCB1300"
  1415. depends on MCP_SA11X0
  1416. select MCP
  1417. config MCP_UCB1200_TS
  1418. tristate "Touchscreen interface support"
  1419. depends on MCP_UCB1200 && INPUT
  1420. endmenu
  1421. config MFD_VEXPRESS_SYSREG
  1422. bool "Versatile Express System Registers"
  1423. depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
  1424. default y
  1425. select CLKSRC_MMIO
  1426. select GPIO_GENERIC_PLATFORM
  1427. select MFD_CORE
  1428. select MFD_SYSCON
  1429. help
  1430. System Registers are the platform configuration block
  1431. on the ARM Ltd. Versatile Express board.
  1432. endmenu
  1433. endif