1 # SPDX-License-Identifier: GPL-2.0-only
3 # Multifunction miscellaneous devices
7 menu "Multifunction device drivers"
15 tristate "AMD CS5535 and CS5536 southbridge core functions"
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
19 This is the core driver for CS5535/CS5536 MFD functions. This is
20 necessary for using the board's GPIO and MFGPT functionality.
22 config MFD_ALTERA_A10SR
23 bool "Altera Arria10 DevKit System Resource chip"
24 depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
28 Support for the Altera Arria10 DevKit MAX5 System Resource chip
29 using the SPI interface. This driver provides common support for
30 accessing the external gpio extender (LEDs & buttons) and
31 power supply alarms (hwmon).
33 config MFD_ALTERA_SYSMGR
34 bool "Altera SOCFPGA System Manager"
35 depends on (ARCH_SOCFPGA || ARCH_STRATIX10) && OF
38 Select this to get System Manager support for all Altera branded
39 SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
40 using regmap_mmio accesses for ARM32 parts and SMC calls to
44 tristate "Active-semi ACT8945A"
49 Support for the ACT8945A PMIC from Active-semi. This device
50 features three step-down DC/DC converters and four low-dropout
51 linear regulators, along with a complete ActivePath battery
54 config MFD_SUN4I_GPADC
55 tristate "Allwinner sunxi platforms' GPADC MFD driver"
59 depends on ARCH_SUNXI || COMPILE_TEST
60 depends on !TOUCHSCREEN_SUN4I
62 Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC.
63 This driver will only map the hardware interrupt and registers, you
64 have to select individual drivers based on this MFD to be able to use
65 the ADC or the thermal sensor. This will try to probe the ADC driver
66 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
68 To compile this driver as a module, choose M here: the module will be
78 Support for the AS3711 PMIC from AMS
81 tristate "ams AS3722 Power Management IC"
85 depends on I2C=y && OF
87 The ams AS3722 is a compact system PMU suitable for mobile phones,
88 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
89 controllers, 11 LDOs, RTC, automatic battery, temperature and
90 over current monitoring, GPIOs, ADC and a watchdog.
93 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
96 Say yes here to add support for Analog Devices AD5520 and ADP5501,
97 Multifunction Power Management IC. This includes
98 the I2C driver and the core APIs _only_, you have to select
99 individual components like LCD backlight, LEDs, GPIOs and Kepad
100 under the corresponding menus.
102 config MFD_AAT2870_CORE
103 bool "AnalogicTech AAT2870"
106 depends on GPIOLIB || COMPILE_TEST
108 If you say yes here you get support for the AAT2870.
109 This driver provides common support for accessing the device,
110 additional drivers must be enabled in order to use the
111 functionality of the device.
113 config MFD_AT91_USART
114 tristate "AT91 USART Driver"
116 depends on ARCH_AT91 || COMPILE_TEST
118 Select this to get support for AT91 USART IP. This is a wrapper
119 over at91-usart-serial driver and usart-spi-driver. Only one function
120 can be used at a time. The choice is done at boot time by the probe
121 function of this MFD driver according to a device tree property.
123 config MFD_ATMEL_FLEXCOM
124 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
128 Select this to get support for Atmel Flexcom. This is a wrapper
129 which embeds a SPI controller, a I2C controller and a USART. Only
130 one function can be used at a time. The choice is done at boot time
131 by the probe function of this MFD driver according to a device tree
134 config MFD_ATMEL_HLCDC
135 tristate "Atmel HLCDC (High-end LCD Controller)"
140 If you say yes here you get support for the HLCDC block.
141 This driver provides common support for accessing the device,
142 additional drivers must be enabled in order to use the
143 functionality of the device.
150 tristate "Broadcom BCM590xx PMUs"
155 Support for the BCM590xx PMUs from Broadcom
158 tristate "ROHM BD9571MWV PMIC"
164 Support for the ROHM BD9571MWV PMIC, which contains single
165 voltage regulator, voltage sampling units, GPIO block and
168 This driver can also be built as a module. If so, the module
169 will be called bd9571mwv.
172 tristate "X-Powers AC100"
176 If you say Y here you get support for the X-Powers AC100 audio codec
178 This driver include only the core APIs. You have to select individual
179 components like codecs or RTC under the corresponding menus.
186 config MFD_AXP20X_I2C
187 tristate "X-Powers AXP series PMICs with I2C"
192 If you say Y here you get support for the X-Powers AXP series power
193 management ICs (PMICs) controlled with I2C.
194 This driver include only the core APIs. You have to select individual
195 components like regulators or the PEK (Power Enable Key) under the
198 Note on x86 this provides an ACPI OpRegion, so this must be 'y'
199 (builtin) and not a module, as the OpRegion must be available as
200 soon as possible. For the same reason the I2C bus driver options
201 I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
203 config MFD_AXP20X_RSB
204 tristate "X-Powers AXP series PMICs with RSB"
208 If you say Y here you get support for the X-Powers AXP series power
209 management ICs (PMICs) controlled with RSB.
210 This driver include only the core APIs. You have to select individual
211 components like regulators or the PEK (Power Enable Key) under the
215 tristate "ChromeOS Embedded Controller"
217 select CHROME_PLATFORMS
219 depends on X86 || ARM || ARM64 || COMPILE_TEST
221 If you say Y here you get support for the ChromeOS Embedded
222 Controller (EC) providing keyboard, battery and power services.
223 You also need to enable the driver for the bus you are using. The
224 protocol for talking to the EC is defined by the bus driver.
226 config MFD_CROS_EC_CHARDEV
227 tristate "Chrome OS Embedded Controller userspace device interface"
228 depends on MFD_CROS_EC
230 This driver adds support to talk with the ChromeOS EC from userspace.
232 If you have a supported Chromebook, choose Y or M here.
233 The module will be called cros_ec_dev.
236 tristate "Cirrus Logic Madera codecs"
242 select PINCTRL_MADERA
244 Support for the Cirrus Logic Madera platform audio codecs
246 config MFD_MADERA_I2C
247 tristate "Cirrus Logic Madera codecs with I2C"
248 depends on MFD_MADERA
252 Support for the Cirrus Logic Madera platform audio SoC
253 core functionality controlled via I2C.
255 config MFD_MADERA_SPI
256 tristate "Cirrus Logic Madera codecs with SPI"
257 depends on MFD_MADERA
258 depends on SPI_MASTER
261 Support for the Cirrus Logic Madera platform audio SoC
262 core functionality controlled via SPI.
265 bool "Cirrus Logic CS47L15"
266 select PINCTRL_CS47L15
267 depends on MFD_MADERA
269 Support for Cirrus Logic CS47L15 Smart Codec
272 bool "Cirrus Logic CS47L35"
273 select PINCTRL_CS47L35
274 depends on MFD_MADERA
276 Support for Cirrus Logic CS47L35 Smart Codec
279 bool "Cirrus Logic CS47L85"
280 select PINCTRL_CS47L85
281 depends on MFD_MADERA
283 Support for Cirrus Logic CS47L85 Smart Codec
286 bool "Cirrus Logic CS47L90/91"
287 select PINCTRL_CS47L90
288 depends on MFD_MADERA
290 Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
293 bool "Cirrus Logic CS47L92/93"
294 select PINCTRL_CS47L92
295 depends on MFD_MADERA
297 Support for Cirrus Logic CS42L92, CS47L92 and CS47L93 Smart Codecs
301 depends on GPIOLIB && ARM
304 This driver supports the ASIC3 multifunction chip found on many
305 PDAs (mainly iPAQ and HTC based ones)
308 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
311 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
312 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
313 usually found on PXA processors-based platforms. This includes
314 the I2C driver and the core APIs _only_, you have to select
315 individual components like LCD backlight, voltage regulators,
316 LEDs and battery-charger under the corresponding menus.
322 config MFD_DA9052_SPI
323 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
327 depends on SPI_MASTER=y
329 Support for the Dialog Semiconductor DA9052 PMIC
330 when controlled using SPI. This driver provides common support
331 for accessing the device, additional drivers must be enabled in
332 order to use the functionality of the device.
334 config MFD_DA9052_I2C
335 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
341 Support for the Dialog Semiconductor DA9052 PMIC
342 when controlled using I2C. This driver provides common support
343 for accessing the device, additional drivers must be enabled in
344 order to use the functionality of the device.
347 bool "Dialog Semiconductor DA9055 PMIC Support"
353 Say yes here for support of Dialog Semiconductor DA9055. This is
354 a Power Management IC. This driver provides common support for
355 accessing the device as well as the I2C interface to the chip itself.
356 Additional drivers must be enabled in order to use the functionality
359 This driver can be built as a module. If built as a module it will be
363 tristate "Dialog Semiconductor DA9062/61 PMIC Support"
369 Say yes here for support for the Dialog Semiconductor DA9061 and
371 This includes the I2C driver and core APIs.
372 Additional drivers must be enabled in order to use the functionality
376 tristate "Dialog Semiconductor DA9063 PMIC Support"
382 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
383 This includes the I2C driver and core APIs.
384 Additional drivers must be enabled in order to use the functionality
388 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
394 This adds support for the DA9150 integrated charger and fuel-gauge
395 chip. This driver provides common support for accessing the device.
396 Additional drivers must be enabled in order to use the specific
397 features of the device.
400 tristate "Diolan DLN2 support"
404 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
405 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
406 etc. must be enabled in order to use the functionality of
409 config MFD_EXYNOS_LPASS
410 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
411 depends on ARCH_EXYNOS || COMPILE_TEST
415 Select this option to enable support for Samsung Exynos Low Power
420 depends on (SPI_MASTER || I2C)
424 Enable support for the Freescale MC13783 and MC13892 PMICs.
425 This driver provides common support for accessing the device,
426 additional drivers must be enabled in order to use the
427 functionality of the device.
429 config MFD_MC13XXX_SPI
430 tristate "Freescale MC13783 and MC13892 SPI interface"
431 depends on SPI_MASTER
435 Select this if your MC13xxx is connected via an SPI bus.
437 config MFD_MC13XXX_I2C
438 tristate "Freescale MC13892 I2C interface"
443 Select this if your MC13xxx is connected via an I2C bus.
446 tristate "Freescale i.MX23/i.MX28 LRADC"
447 depends on ARCH_MXS || COMPILE_TEST
451 Say yes here to build support for the Low Resolution
452 Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
453 processors. This driver provides common support for accessing the
454 device, additional drivers must be enabled in order to use the
455 functionality of the device:
456 mxs-lradc-adc for ADC readings
457 mxs-lradc-ts for touchscreen support
459 This driver can also be built as a module. If so, the module will be
462 config MFD_MX25_TSADC
463 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
465 depends on (SOC_IMX25 && OF) || COMPILE_TEST
467 Enable support for the integrated Touchscreen and ADC unit of the
468 i.MX25 processors. They consist of a conversion queue for general
469 purpose ADC and a queue for Touchscreens.
471 config MFD_HI6421_PMIC
472 tristate "HiSilicon Hi6421 PMU/Codec IC"
477 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
478 functions, such as regulators, RTC, codec, Coulomb counter, etc.
479 This driver includes core APIs _only_. You have to select
480 individul components like voltage regulators under corresponding
481 menus in order to enable them.
482 We communicate with the Hi6421 via memory-mapped I/O.
484 config MFD_HI655X_PMIC
485 tristate "HiSilicon Hi655X series PMU/Codec IC"
486 depends on ARCH_HISI || COMPILE_TEST
492 Select this option to enable Hisilicon hi655x series pmic driver.
495 tristate "HTC PASIC3 LED/DS1WM chip support"
498 This core driver provides register access for the LED/DS1WM
499 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
500 HTC Magician devices, respectively. Actual functionality is
501 handled by the leds-pasic3 and ds1wm drivers.
504 bool "HTC I2C PLD chip support"
505 depends on I2C=y && GPIOLIB
507 If you say yes here you get support for the supposed CPLD
508 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
509 This device provides input and output GPIOs through an I2C
510 interface to one or more sub-chips.
512 config MFD_INTEL_QUARK_I2C_GPIO
513 tristate "Intel Quark MFD I2C GPIO"
516 depends on COMMON_CLK
519 This MFD provides support for I2C and GPIO that exist only
520 in a single PCI device. It splits the 2 IO devices to
521 their respective IO driver.
522 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
525 tristate "Intel ICH LPC"
529 The LPC bridge function of the Intel ICH provides support for
530 many functional units. This driver provides needed support for
531 other drivers to control these functions, currently GPIO and
535 tristate "Intel SCH LPC"
539 LPC bridge function of the Intel SCH provides support for
540 System Management Bus and General Purpose I/O.
542 config INTEL_SOC_PMIC
543 bool "Support for Crystal Cove PMIC"
544 depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
545 depends on X86 || COMPILE_TEST
546 depends on I2C_DESIGNWARE_PLATFORM=y
551 Select this option to enable support for Crystal Cove PMIC
552 on some Intel SoC systems. The PMIC provides ADC, GPIO,
553 thermal, charger and related power management functions
556 This option is a bool as it provides an ACPI OpRegion which must be
557 available before any devices using it are probed. This option also
558 causes the designware-i2c driver to be builtin for the same reason.
560 config INTEL_SOC_PMIC_BXTWC
561 tristate "Support for Intel Broxton Whiskey Cove PMIC"
562 depends on INTEL_PMC_IPC
566 Select this option to enable support for Whiskey Cove PMIC
567 on Intel Broxton systems. The PMIC provides ADC, GPIO,
568 thermal, charger and related power management functions
571 config INTEL_SOC_PMIC_CHTWC
572 bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
573 depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
574 depends on X86 || COMPILE_TEST
575 depends on I2C_DESIGNWARE_PLATFORM=y
580 Select this option to enable support for the Intel Cherry Trail
581 Whiskey Cove PMIC found on some Intel Cherry Trail systems.
583 This option is a bool as it provides an ACPI OpRegion which must be
584 available before any devices using it are probed. This option also
585 causes the designware-i2c driver to be builtin for the same reason.
587 config INTEL_SOC_PMIC_CHTDC_TI
588 tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
597 Select this option for supporting Dollar Cove (TI version) PMIC
598 device that is found on some Intel Cherry Trail systems.
600 config MFD_INTEL_LPSS
605 config MFD_INTEL_LPSS_ACPI
606 tristate "Intel Low Power Subsystem support in ACPI mode"
607 select MFD_INTEL_LPSS
608 depends on X86 && ACPI
610 This driver supports Intel Low Power Subsystem (LPSS) devices such as
611 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
614 config MFD_INTEL_LPSS_PCI
615 tristate "Intel Low Power Subsystem support in PCI mode"
616 select MFD_INTEL_LPSS
617 depends on X86 && PCI
619 This driver supports Intel Low Power Subsystem (LPSS) devices such as
620 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
623 config MFD_INTEL_MSIC
625 depends on INTEL_SCU_IPC
628 Select this option to enable access to Intel MSIC (Avatele
629 Passage) chip. This chip embeds audio, battery, GPIO, etc.
630 devices used in Intel Medfield platforms.
632 config MFD_IPAQ_MICRO
633 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
634 depends on SA1100_H3100 || SA1100_H3600
637 Select this to get support for the Microcontroller found in
638 the Compaq iPAQ handheld computers. This is an Atmel
639 AT90LS8535 microcontroller flashed with a special iPAQ
640 firmware using the custom protocol implemented in this driver.
642 config MFD_JANZ_CMODIO
643 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
647 This is the core driver for the Janz CMOD-IO PCI MODULbus
648 carrier board. This device is a PCI to MODULbus bridge which may
649 host many different types of MODULbus daughterboards, including
650 CAN and GPIO controllers.
653 tristate "Kontron module PLD device"
656 This is the core driver for the PLD (Programmable Logic Device) found
657 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
658 device may provide functions like watchdog, GPIO, UART and I2C bus.
660 The following modules are supported:
667 * COMe-bPC2 (ETXexpress-PC)
668 * COMe-bSC# (ETXexpress-SC T#)
674 * COMe-cDC2 (microETXexpress-DC)
677 * COMe-cPC2 (microETXexpress-PC)
682 * COMe-mTT10 (nanoETXexpress-TT)
685 This driver can also be built as a module. If so, the module
686 will be called kempld-core.
689 tristate "Marvell 88PM800"
695 This supports for Marvell 88PM800 Power Management IC.
696 This includes the I2C driver and the core APIs _only_, you have to
697 select individual components like voltage regulators, RTC and
698 battery-charger under the corresponding menus.
701 tristate "Marvell 88PM805"
707 This supports for Marvell 88PM805 Power Management IC. This includes
708 the I2C driver and the core APIs _only_, you have to select individual
709 components like codec device, headset/Mic device under the
713 bool "Marvell 88PM8606/88PM8607"
718 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
719 This includes the I2C driver and the core APIs _only_, you have to
720 select individual components like voltage regulators, RTC and
721 battery-charger under the corresponding menus.
724 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
731 Say yes here to add support for Maxim Semiconductor MAX14577 and
732 MAX77836 Micro-USB ICs with battery charger.
733 This driver provides common support for accessing the device;
734 additional drivers must be enabled in order to use the functionality
738 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
740 depends on OF || COMPILE_TEST
746 Say yes here to add support for Maxim Semiconductor MAX77620 and
747 MAX20024 which are Power Management IC with General purpose pins,
748 RTC, regulators, clock generator, watchdog etc. This driver
749 provides common support for accessing the device; additional drivers
750 must be enabled in order to use the functionality of the device.
753 tristate "Maxim MAX77650/77651 PMIC Support"
755 depends on OF || COMPILE_TEST
759 Say Y here to add support for Maxim Semiconductor MAX77650 and
760 MAX77651 Power Management ICs. This is the core multifunction
761 driver for interacting with the device. The module name is
762 'max77650'. Additional drivers can be enabled in order to use
763 the following functionalities of the device: GPIO, regulator,
767 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
769 depends on OF || COMPILE_TEST
775 Say yes here to add support for Maxim Semiconductor MAX77686 and
776 MAX77802 which are Power Management IC with an RTC on chip.
777 This driver provides common support for accessing the device;
778 additional drivers must be enabled in order to use the functionality
782 tristate "Maxim Semiconductor MAX77693 PMIC Support"
788 Say yes here to add support for Maxim Semiconductor MAX77693.
789 This is a companion Power Management IC with Flash, Haptic, Charger,
790 and MUIC(Micro USB Interface Controller) controls on chip.
791 This driver provides common support for accessing the device;
792 additional drivers must be enabled in order to use the functionality
796 bool "Maxim Semiconductor MAX77843 PMIC Support"
802 Say yes here to add support for Maxim Semiconductor MAX77843.
803 This is companion Power Management IC with LEDs, Haptic, Charger,
804 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
805 This driver provides common support for accessing the device;
806 additional drivers must be enabled in order to use the functionality
810 tristate "Maxim Semiconductor MAX8907 PMIC Support"
816 Say yes here to add support for Maxim Semiconductor MAX8907. This is
817 a Power Management IC. This driver provides common support for
818 accessing the device; additional drivers must be enabled in order
819 to use the functionality of the device.
822 bool "Maxim Semiconductor MAX8925 PMIC Support"
826 Say yes here to add support for Maxim Semiconductor MAX8925. This is
827 a Power Management IC. This driver provides common support for
828 accessing the device, additional drivers must be enabled in order
829 to use the functionality of the device.
832 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
837 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
838 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
839 MUIC controls on chip.
840 This driver provides common support for accessing the device;
841 additional drivers must be enabled in order to use the functionality
845 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
850 Say yes here to add support for Maxim Semiconductor MAX8998 and
851 National Semiconductor LP3974. This is a Power Management IC.
852 This driver provides common support for accessing the device,
853 additional drivers must be enabled in order to use the functionality
857 tristate "MediaTek MT6397 PMIC Support"
861 Say yes here to add support for MediaTek MT6397 PMIC. This is
862 a Power Management IC. This driver provides common support for
863 accessing the device; additional drivers must be enabled in order
864 to use the functionality of the device.
867 tristate "MEN 14F021P00 Board Management Controller Support"
871 Say yes here to add support for the MEN 14F021P00 BMC
872 which is a Board Management Controller connected to the I2C bus.
873 The device supports multiple sub-devices like LED, HWMON and WDT.
874 This driver provides common support for accessing the devices;
875 additional drivers must be enabled in order to use the
876 functionality of the BMC device.
878 This driver can also be built as a module. If so the module
879 will be called menf21bmc.
882 bool "Motorola EZXPCAP Support"
883 depends on SPI_MASTER
885 This enables the PCAP ASIC present on EZX Phones. This is
886 needed for MMC, TouchScreen, Sound, USB, etc..
889 tristate "Support for Motorola CPCAP"
891 depends on OF || COMPILE_TEST
895 Say yes here if you want to include driver for CPCAP.
896 It is used on many Motorola phones and tablets as a PMIC.
897 At least Motorola Droid 4 is known to use CPCAP.
899 config MFD_VIPERBOARD
900 tristate "Nano River Technologies Viperboard"
905 Say yes here if you want support for Nano River Technologies
907 There are mfd cell drivers available for i2c master, adc and
908 both gpios found on the board. The spi part does not yet
910 You need to select the mfd cell drivers separately.
911 The drivers do not support all features the board exposes.
914 tristate "Nokia Retu and Tahvo multi-function device"
919 Retu and Tahvo are a multi-function devices found on Nokia
920 Internet Tablets (770, N800 and N810).
923 tristate "NXP PCF50633"
927 Say yes here if you have NXP PCF50633 chip on your board.
928 This core driver provides register access and IRQ handling
929 facilities, and registers devices for the various functions
930 so that function-specific drivers can bind to them.
933 tristate "NXP PCF50633 ADC"
934 depends on MFD_PCF50633
936 Say yes here if you want to include support for ADC in the
940 tristate "NXP PCF50633 GPIO"
941 depends on MFD_PCF50633
943 Say yes here if you want to include support GPIO for pins on
947 tristate "Philips UCB1400 Core driver"
951 This enables support for the Philips UCB1400 core functions.
952 The UCB1400 is an AC97 audio codec.
954 To compile this driver as a module, choose M here: the
955 module will be called ucb1400_core.
958 tristate "Qualcomm PM8xxx PMIC chips driver"
959 depends on (ARM || HEXAGON || COMPILE_TEST)
960 select IRQ_DOMAIN_HIERARCHY
964 If you say yes to this option, support will be included for the
965 built-in PM8xxx PMIC chips.
967 This is required if your board has a PM8xxx and uses its features,
968 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
970 Say M here if you want to include support for PM8xxx chips as a
971 module. This will build a module called "pm8xxx-core".
974 tristate "Qualcomm Resource Power Manager (RPM)"
975 depends on ARCH_QCOM && OF
977 If you say yes to this option, support will be included for the
978 Resource Power Manager system found in the Qualcomm 8660, 8960 and
981 This is required to access many regulators, clocks and bus
982 frequencies controlled by the RPM on these devices.
984 Say M here if you want to include support for the Qualcomm RPM as a
985 module. This will build a module called "qcom_rpm".
988 tristate "Qualcomm SPMI PMICs"
989 depends on ARCH_QCOM || COMPILE_TEST
994 This enables support for the Qualcomm SPMI PMICs.
995 These PMICs are currently used with the Snapdragon 800 series of
996 SoCs. Note, that this will only be useful paired with descriptions
997 of the independent functions as children nodes in the device tree.
999 Say M here if you want to include support for the SPMI PMIC
1000 series as a module. The module will be called "qcom-spmi-pmic".
1003 tristate "RDC R-321x southbridge"
1007 Say yes here if you want to have support for the RDC R-321x SoC
1008 southbridge which provides access to GPIOs and Watchdog using the
1009 southbridge PCI device configuration space.
1012 tristate "Richtek RT5033 Power Management IC"
1018 This driver provides for the Richtek RT5033 Power Management IC,
1019 which includes the I2C driver and the Core APIs. This driver provides
1020 common support for accessing the device. The device supports multiple
1021 sub-devices like charger, fuel gauge, flash LED, current source,
1025 bool "Ricoh RC5T583 Power Management system device"
1030 Select this option to get support for the RICOH583 Power
1031 Management system device.
1032 This driver provides common support for accessing the device
1033 through i2c interface. The device supports multiple sub-devices
1034 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1035 Additional drivers must be enabled in order to use the
1036 different functionality of the device.
1039 tristate "Rockchip RK805/RK808/RK809/RK817/RK818 Power Management Chip"
1040 depends on I2C && OF
1045 If you say yes here you get support for the RK805, RK808, RK809,
1046 RK817 and RK818 Power Management chips.
1047 This driver provides common support for accessing the device
1048 through I2C interface. The device supports multiple sub-devices
1049 including interrupts, RTC, LDO & DCDC regulators, and onkey.
1052 tristate "Ricoh RN5T567/618 PMIC"
1058 Say yes here to add support for the Ricoh RN5T567,
1059 RN5T618, RC5T619 PMIC.
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.
1065 tristate "SAMSUNG Electronics PMIC Series Support"
1071 Support for the Samsung Electronics PMIC devices coming
1072 usually along with Samsung Exynos SoC chipset.
1073 This driver provides common support for accessing the device,
1074 additional drivers must be enabled in order to use the functionality
1077 To compile this driver as a module, choose M here: the
1078 module will be called sec-core.
1079 Have in mind that important core drivers (like regulators) depend
1080 on this driver so building this as a module might require proper
1081 initial ramdisk or might not boot up as well in certain scenarios.
1083 config MFD_SI476X_CORE
1084 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1089 This is the core driver for the SI476x series of AM/FM
1090 radio. This MFD driver connects the radio-si476x V4L2 module
1091 and the si476x audio codec.
1093 To compile this driver as a module, choose M here: the
1094 module will be called si476x-core.
1097 tristate "Silicon Motion SM501"
1099 select DMA_DECLARE_COHERENT
1101 This is the core driver for the Silicon Motion SM501 multimedia
1102 companion chip. This device is a multifunction device which may
1103 provide numerous interfaces including USB host controller, USB gadget,
1104 asynchronous serial ports, audio functions, and a dual display video
1105 interface. The device may be connected by PCI or local bus with
1106 varying functions enabled.
1108 config MFD_SM501_GPIO
1109 bool "Export GPIO via GPIO layer"
1110 depends on MFD_SM501 && GPIOLIB
1112 This option uses the gpio library layer to export the 64 GPIO
1113 lines on the SM501. The platform data is used to supply the
1114 base number for the first GPIO line to register.
1117 tristate "Skyworks Solutions SKY81452"
1122 This is the core driver for the Skyworks SKY81452 backlight and
1123 voltage regulator device.
1125 This driver can also be built as a module. If so, the module
1126 will be called sky81452.
1129 bool "SMSC ECE1099 series chips"
1134 If you say yes here you get support for the
1135 ece1099 chips from SMSC.
1137 To compile this driver as a module, choose M here: the
1138 module will be called smsc.
1140 config MFD_SC27XX_PMIC
1141 tristate "Spreadtrum SC27xx PMICs"
1142 depends on ARCH_SPRD || COMPILE_TEST
1143 depends on SPI_MASTER
1148 This enables support for the Spreadtrum SC27xx PMICs with SPI
1149 interface. The SC27xx series PMICs integrate power management,
1150 audio codec, battery management and user interface support
1151 function (such as RTC, Typec, indicator and so on) in a single chip.
1153 This driver provides common support for accessing the SC27xx PMICs,
1154 and it also adds the irq_chip parts for handling the PMIC chip events.
1157 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1158 default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1160 Say yes here if you have the ABX500 Mixed Signal IC family
1161 chips. This core driver expose register access functions.
1162 Functionality specific drivers using these functions can
1163 remain unchanged when IC changes. Binding of the functions to
1164 actual register access is done by the IC core driver.
1167 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1168 depends on I2C=y && ABX500_CORE
1170 default y if ARCH_U300
1172 Select this to enable the AB3100 Mixed Signal IC core
1173 functionality. This connects to a AB3100 on the I2C bus
1174 and expose a number of symbols needed for dependent devices
1175 to read and write registers and subscribe to events from
1176 this multi-functional IC. This is needed to use other features
1177 of the AB3100 such as battery-backed RTC, charging control,
1178 LEDs, vibrator, system power and temperature, power management
1182 tristate "ST-Ericsson AB3100 OTP functions"
1183 depends on AB3100_CORE
1184 default y if AB3100_CORE
1186 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1187 programmable memory) support. This exposes a sysfs file to read
1191 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1192 depends on ABX500_CORE && MFD_DB8500_PRCMU
1197 Select this option to enable access to AB8500 power management
1198 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1199 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1200 the irq_chip parts for handling the Mixed Signal chip events.
1201 This chip embeds various other multimedia funtionalities as well.
1204 bool "Enable debug info via debugfs"
1205 depends on AB8500_GPADC && DEBUG_FS
1206 default y if DEBUG_FS
1208 Select this option if you want debug information using the debug
1209 filesystem, debugfs.
1212 bool "ST-Ericsson AB8500 GPADC driver"
1213 depends on AB8500_CORE && REGULATOR_AB8500
1216 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1218 config MFD_DB8500_PRCMU
1219 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1220 depends on UX500_SOC_DB8500
1223 Select this option to enable support for the DB8500 Power Reset
1224 and Control Management Unit. This is basically an autonomous
1225 system controller running an XP70 microprocessor, which is accessed
1226 through a register map.
1229 bool "STMicroelectronics STMPE"
1230 depends on (I2C=y || SPI_MASTER=y)
1234 Support for the STMPE family of I/O Expanders from
1237 Currently supported devices are:
1239 STMPE811: GPIO, Touchscreen, ADC
1240 STMPE1601: GPIO, Keypad
1241 STMPE1801: GPIO, Keypad
1242 STMPE2401: GPIO, Keypad
1243 STMPE2403: GPIO, Keypad
1245 This driver provides common support for accessing the device,
1246 additional drivers must be enabled in order to use the functionality
1247 of the device. Currently available sub drivers are:
1250 Keypad: stmpe-keypad
1251 Touchscreen: stmpe-ts
1254 menu "STMicroelectronics STMPE Interface Drivers"
1255 depends on MFD_STMPE
1258 bool "STMicroelectronics STMPE I2C Interface"
1262 This is used to enable I2C interface of STMPE
1265 bool "STMicroelectronics STMPE SPI Interface"
1266 depends on SPI_MASTER
1268 This is used to enable SPI interface of STMPE
1272 bool "STMicroelectronics STA2X11"
1277 config MFD_SUN6I_PRCM
1278 bool "Allwinner A31 PRCM controller"
1279 depends on ARCH_SUNXI || COMPILE_TEST
1282 Support for the PRCM (Power/Reset/Clock Management) unit available
1286 bool "System Controller Register R/W Based on Regmap"
1289 Select this option to enable accessing system control registers
1292 config MFD_DAVINCI_VOICECODEC
1297 config MFD_TI_AM335X_TSCADC
1298 tristate "TI ADC / Touch Screen chip support"
1303 If you say yes here you get support for Texas Instruments series
1304 of Touch Screen /ADC chips.
1305 To compile this driver as a module, choose M here: the
1306 module will be called ti_am335x_tscadc.
1308 config MFD_DM355EVM_MSP
1309 bool "TI DaVinci DM355 EVM microcontroller"
1310 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1312 This driver supports the MSP430 microcontroller used on these
1313 boards. MSP430 firmware manages resets and power sequencing,
1314 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1317 tristate "TI/National Semiconductor LP3943 MFD Driver"
1322 Support for the TI/National Semiconductor LP3943.
1323 This driver consists of GPIO and PWM drivers.
1324 With these functionalities, it can be used for LED string control or
1325 general usage such like a GPIO controller and a PWM controller.
1328 bool "TI LP8788 Power Management Unit Driver"
1334 TI LP8788 PMU supports regulators, battery charger, RTC,
1335 ADC, backlight driver and current sinks.
1338 tristate "TI Lighting Management Unit driver"
1343 Say yes here to enable support for TI LMU chips.
1344 TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and
1345 LM36274. It consists of backlight, LED and regulator driver.
1346 It provides consistent device controls for lighting functions.
1348 config MFD_OMAP_USB_HOST
1349 bool "TI OMAP USBHS core and TLL driver"
1350 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1353 This is the core driver for the OAMP EHCI and OHCI drivers.
1354 This MFD driver does the required setup functionalities for
1355 OMAP USB Host drivers.
1358 bool "TI Palmas series chips"
1364 If you say yes here you get support for the Palmas
1365 series of PMIC chips from Texas Instruments.
1368 tristate "TI TPS61050/61052 Boost Converters"
1373 select REGULATOR_FIXED_VOLTAGE
1375 This option enables a driver for the TP61050/TPS61052
1376 high-power "white LED driver". This boost converter is
1377 sometimes used for other things than white LEDs, and
1378 also contains a GPIO pin.
1381 tristate "TI TPS6501x Power Management chips"
1382 depends on I2C && GPIOLIB
1383 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1385 If you say yes here you get support for the TPS6501x series of
1386 Power Management chips. These include voltage regulators,
1387 lithium ion/polymer battery charging, and other features that
1388 are often used in portable devices like cell phones and cameras.
1390 This driver can also be built as a module. If so, the module
1391 will be called tps65010.
1394 tristate "TI TPS6507x Power Management / Touch Screen chips"
1398 If you say yes here you get support for the TPS6507x series of
1399 Power Management / Touch Screen chips. These include voltage
1400 regulators, lithium ion/polymer battery charging, touch screen
1401 and other features that are often used in portable devices.
1402 This driver can also be built as a module. If so, the module
1403 will be called tps6507x.
1406 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1413 If you say yes here you get support for the TPS65086 series of
1414 Power Management chips.
1415 This driver provides common support for accessing the device,
1416 additional drivers must be enabled in order to use the
1417 functionality of the device.
1419 config TPS65911_COMPARATOR
1423 bool "TI TPS65090 Power Management chips"
1429 If you say yes here you get support for the TPS65090 series of
1430 Power Management chips.
1431 This driver provides common support for accessing the device,
1432 additional drivers must be enabled in order to use the
1433 functionality of the device.
1436 tristate "TI TPS65217 Power Management / White LED chips"
1437 depends on I2C && OF
1442 If you say yes here you get support for the TPS65217 series of
1443 Power Management / White LED chips.
1444 These include voltage regulators, lithium ion/polymer battery
1445 charger, wled and other features that are often used in portable
1448 This driver can also be built as a module. If so, the module
1449 will be called tps65217.
1452 bool "TI TPS68470 Power Management / LED chips"
1453 depends on ACPI && PCI && I2C=y
1454 depends on I2C_DESIGNWARE_PLATFORM=y
1458 If you say yes here you get support for the TPS68470 series of
1459 Power Management / LED chips.
1461 These include voltage regulators, LEDs and other features
1462 that are often used in portable devices.
1464 This option is a bool as it provides an ACPI operation
1465 region, which must be available before any of the devices
1466 using this are probed. This option also configures the
1467 designware-i2c driver to be built-in, for the same reason.
1469 config MFD_TI_LP873X
1470 tristate "TI LP873X Power Management IC"
1475 If you say yes here then you get support for the LP873X series of
1476 Power Management Integrated Circuits (PMIC).
1477 These include voltage regulators, thermal protection, configurable
1478 General Purpose Outputs (GPO) that are used in portable devices.
1480 This driver can also be built as a module. If so, the module
1481 will be called lp873x.
1483 config MFD_TI_LP87565
1484 tristate "TI LP87565 Power Management IC"
1485 depends on I2C && OF
1489 If you say yes here then you get support for the LP87565 series of
1490 Power Management Integrated Circuits (PMIC).
1491 These include voltage regulators, thermal protection, configurable
1492 General Purpose Outputs (GPO) that are used in portable devices.
1494 This driver can also be built as a module. If so, the module
1495 will be called lp87565.
1498 tristate "TI TPS65218 Power Management chips"
1499 depends on I2C && OF
1504 If you say yes here you get support for the TPS65218 series of
1505 Power Management chips.
1506 These include voltage regulators, gpio and other features
1507 that are often used in portable devices.
1509 This driver can also be built as a module. If so, the module
1510 will be called tps65218.
1513 bool "TI TPS6586x Power Management chips"
1518 If you say yes here you get support for the TPS6586X series of
1519 Power Management chips.
1520 This driver provides common support for accessing the device,
1521 additional drivers must be enabled in order to use the
1522 functionality of the device.
1524 This driver can also be built as a module. If so, the module
1525 will be called tps6586x.
1528 bool "TI TPS65910 Power Management chip"
1530 depends on GPIOLIB || COMPILE_TEST
1536 if you say yes here you get support for the TPS65910 series of
1537 Power Management chips.
1545 config MFD_TPS65912_I2C
1546 tristate "TI TPS65912 Power Management chip with I2C"
1551 If you say yes here you get support for the TPS65912 series of
1552 PM chips with I2C interface.
1554 config MFD_TPS65912_SPI
1555 tristate "TI TPS65912 Power Management chip with SPI"
1558 depends on SPI_MASTER
1560 If you say yes here you get support for the TPS65912 series of
1561 PM chips with SPI interface.
1564 bool "TI TPS80031/TPS80032 Power Management chips"
1570 If you say yes here you get support for the Texas Instruments
1571 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1572 Path and Battery Charger. The device provides five configurable
1573 step-down converters, 11 general purpose LDOs, USB OTG Module,
1574 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1575 Power Path from USB, 32K clock generator.
1578 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1583 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1584 This core driver provides register access and IRQ handling
1585 facilities, and registers devices for the various functions
1586 so that function-specific drivers can bind to them.
1588 These multi-function chips are found on many OMAP2 and OMAP3
1589 boards, providing power management, RTC, GPIO, keypad, a
1590 high speed USB OTG transceiver, an audio codec (on most
1591 versions) and many other features.
1593 config TWL4030_POWER
1594 bool "TI TWL4030 power resources"
1595 depends on TWL4030_CORE && ARM
1597 Say yes here if you want to use the power resources on the
1598 TWL4030 family chips. Most of these resources are regulators,
1599 which have a separate driver; some are control signals, such
1600 as clock request handshaking.
1602 This driver uses board-specific data to initialize the resources
1603 and load scripts controlling which resources are switched off/on
1604 or reset when a sleep, wakeup or warm reset event occurs.
1606 config MFD_TWL4030_AUDIO
1607 bool "TI TWL4030 Audio"
1608 depends on TWL4030_CORE
1613 bool "TI TWL6040 audio codec"
1620 Say yes here if you want support for Texas Instruments TWL6040 audio
1622 This driver provides common support for accessing the device,
1623 additional drivers must be enabled in order to use the
1624 functionality of the device (audio, vibra).
1627 bool "TI TWL92330/Menelaus PM chip"
1628 depends on I2C=y && ARCH_OMAP2
1630 If you say yes here you get support for the Texas Instruments
1631 TWL92330/Menelaus Power Management chip. This include voltage
1632 regulators, Dual slot memory card transceivers, real-time clock
1633 and other features that are often used in portable devices like
1634 cell phones and PDAs.
1636 config MFD_WL1273_CORE
1637 tristate "TI WL1273 FM radio"
1642 This is the core driver for the TI WL1273 FM radio. This MFD
1643 driver connects the radio-wl1273 V4L2 module and the wl1273
1647 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1652 Say yes here to enable support for National Semiconductor / TI
1653 LM3533 Lighting Power chips.
1655 This driver provides common support for accessing the device;
1656 additional drivers must be enabled in order to use the LED,
1657 backlight or ambient-light-sensor functionality of the device.
1659 config MFD_TIMBERDALE
1660 tristate "Timberdale FPGA"
1662 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1664 This is the core driver for the timberdale FPGA. This device is a
1665 multifunction device which exposes numerous platform devices.
1667 The timberdale FPGA can be found on the Intel Atom development board
1668 for in-vehicle infontainment, called Russellville.
1671 bool "Toshiba TC35892 and variants"
1676 Support for the Toshiba TC35892 and variants I/O Expander.
1678 This driver provides common support for accessing the device,
1679 additional drivers must be enabled in order to use the
1680 functionality of the device.
1687 bool "Toshiba T7L66XB"
1688 depends on ARM && HAVE_CLK
1692 Support for Toshiba Mobile IO Controller T7L66XB
1695 bool "Toshiba TC6387XB"
1696 depends on ARM && HAVE_CLK
1700 Support for Toshiba Mobile IO Controller TC6387XB
1703 bool "Toshiba TC6393XB"
1704 depends on ARM && HAVE_CLK
1708 select DMA_DECLARE_COHERENT
1710 Support for Toshiba Mobile IO Controller TC6393XB
1713 tristate "TQ-Systems IO controller TQMX86"
1716 Say yes here to enable support for various functions of the
1717 TQ-Systems IO controller and watchdog device, found on their
1718 ComExpress CPU modules.
1721 tristate "VIA VX855/VX875 integrated south bridge"
1725 Say yes here to enable support for various functions of the
1726 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1727 and/or vx855_gpio drivers for this to do anything useful.
1729 config MFD_LOCHNAGAR
1730 bool "Cirrus Logic Lochnagar Audio Development Board"
1733 depends on I2C=y && OF
1735 Support for Cirrus Logic Lochnagar audio development board.
1743 config MFD_ARIZONA_I2C
1744 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1749 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1750 audio SoC core functionality controlled via I2C.
1752 config MFD_ARIZONA_SPI
1753 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1756 depends on SPI_MASTER
1758 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1759 audio SoC core functionality controlled via SPI.
1762 bool "Cirrus Logic CS47L24 and WM1831"
1763 depends on MFD_ARIZONA
1765 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1768 bool "Wolfson Microelectronics WM5102"
1769 depends on MFD_ARIZONA
1771 Support for Wolfson Microelectronics WM5102 low power audio SoC
1774 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1775 depends on MFD_ARIZONA
1777 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1781 bool "Wolfson Microelectronics WM8997"
1782 depends on MFD_ARIZONA
1784 Support for Wolfson Microelectronics WM8997 low power audio SoC
1787 bool "Wolfson Microelectronics WM8998"
1788 depends on MFD_ARIZONA
1790 Support for Wolfson Microelectronics WM8998 low power audio SoC
1793 bool "Wolfson Microelectronics WM8400"
1798 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1799 CODEC. This driver provides common support for accessing
1800 the device, additional drivers must be enabled in order to use
1801 the functionality of the device.
1806 config MFD_WM831X_I2C
1807 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1814 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1815 when controlled using I2C. This driver provides common support
1816 for accessing the device, additional drivers must be enabled in
1817 order to use the functionality of the device.
1819 config MFD_WM831X_SPI
1820 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1825 depends on SPI_MASTER
1827 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1828 when controlled using SPI. This driver provides common support
1829 for accessing the device, additional drivers must be enabled in
1830 order to use the functionality of the device.
1835 config MFD_WM8350_I2C
1836 bool "Wolfson Microelectronics WM8350 with I2C"
1841 The WM8350 is an integrated audio and power management
1842 subsystem with watchdog and RTC functionality for embedded
1843 systems. This option enables core support for the WM8350 with
1844 I2C as the control interface. Additional options must be
1845 selected to enable support for the functionality of the chip.
1848 tristate "Wolfson Microelectronics WM8994"
1854 The WM8994 is a highly integrated hi-fi CODEC designed for
1855 smartphone applications. As well as audio functionality it
1856 has on board GPIO and regulator functionality which is
1857 supported via the relevant subsystems. This driver provides
1858 core support for the WM8994, in order to use the actual
1859 functionaltiy of the device other drivers must be enabled.
1862 tristate "Wolfson Microelectronics WM97xx"
1865 select AC97_BUS_COMPAT
1866 depends on AC97_BUS_NEW
1868 The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1869 designed for smartphone applications. As well as audio functionality
1870 it has on board GPIO and a touchscreen functionality which is
1871 supported via the relevant subsystems. This driver provides core
1872 support for the WM97xx, in order to use the actual functionaltiy of
1873 the device other drivers must be enabled.
1876 tristate "Support for ST Microelectronics STw481x"
1877 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1881 Select this option to enable the STw481x chip driver used
1882 in various ST Microelectronics and ST-Ericsson embedded
1885 config MFD_ROHM_BD718XX
1886 tristate "ROHM BD71837 Power Management IC"
1893 Select this option to get support for the ROHM BD71837
1894 Power Management ICs. BD71837 is designed to power processors like
1895 NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
1896 and emergency shut down as well as 32,768KHz clock output.
1898 config MFD_ROHM_BD70528
1899 tristate "ROHM BD70528 Power Management IC"
1906 Select this option to get support for the ROHM BD70528 Power
1907 Management IC. BD71837 is general purpose single-chip power
1908 management IC for battery-powered portable devices. It contains
1909 3 ultra-low current consumption buck converters, 3 LDOs and 2 LED
1910 drivers. Also included are 4 GPIOs, a real-time clock (RTC), a 32kHz
1911 crystal oscillator, high-accuracy VREF for use with an external ADC,
1912 10 bits SAR ADC for battery temperature monitor and 1S battery
1915 config MFD_STM32_LPTIMER
1916 tristate "Support for STM32 Low-Power Timer"
1917 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1922 Select this option to enable STM32 Low-Power Timer driver
1923 used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1924 resources are also dealt with here.
1926 To compile this driver as a module, choose M here: the
1927 module will be called stm32-lptimer.
1929 config MFD_STM32_TIMERS
1930 tristate "Support for STM32 Timers"
1931 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1936 Select this option to enable STM32 timers driver used
1937 for PWM and IIO Timer. This driver allow to share the
1938 registers between the others drivers.
1941 tristate "Support for STPMIC1 PMIC"
1942 depends on (I2C=y && OF)
1947 Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on
1948 key, watchdog and regulator functionalities which are supported via
1949 the relevant subsystems. This driver provides core support for the
1950 STPMIC1. In order to use the actual functionaltiy of the device other
1951 drivers must be enabled.
1953 To compile this driver as a module, choose M here: the
1954 module will be called stpmic1.
1957 tristate "Support for STMicroelectronics Multi-Function eXpander (STMFX)"
1959 depends on OF || COMPILE_TEST
1963 Support for the STMicroelectronics Multi-Function eXpander.
1965 This driver provides common support for accessing the device,
1966 additional drivers must be enabled in order to use the functionality
1969 menu "Multimedia Capabilities Port drivers"
1970 depends on ARCH_SA1100
1977 tristate "Support SA11x0 MCP interface"
1978 depends on ARCH_SA1100
1983 tristate "Support for UCB1200 / UCB1300"
1984 depends on MCP_SA11X0
1987 config MCP_UCB1200_TS
1988 tristate "Touchscreen interface support"
1989 depends on MCP_UCB1200 && INPUT
1993 config MFD_VEXPRESS_SYSREG
1994 bool "Versatile Express System Registers"
1995 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1998 select GPIO_GENERIC_PLATFORM
2002 System Registers are the platform configuration block
2003 on the ARM Ltd. Versatile Express board.
2006 tristate "RAVE SP MCU core driver"
2007 depends on SERIAL_DEV_BUS
2010 Select this to get support for the Supervisory Processor
2011 device found on several devices in RAVE line of hardware.