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 CS47L35"
266 select PINCTRL_CS47L35
267 depends on MFD_MADERA
269 Support for Cirrus Logic CS47L35 Smart Codec
272 bool "Cirrus Logic CS47L85"
273 select PINCTRL_CS47L85
274 depends on MFD_MADERA
276 Support for Cirrus Logic CS47L85 Smart Codec
279 bool "Cirrus Logic CS47L90/91"
280 select PINCTRL_CS47L90
281 depends on MFD_MADERA
283 Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
287 depends on GPIOLIB && ARM
290 This driver supports the ASIC3 multifunction chip found on many
291 PDAs (mainly iPAQ and HTC based ones)
294 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
297 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
298 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
299 usually found on PXA processors-based platforms. This includes
300 the I2C driver and the core APIs _only_, you have to select
301 individual components like LCD backlight, voltage regulators,
302 LEDs and battery-charger under the corresponding menus.
308 config MFD_DA9052_SPI
309 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
313 depends on SPI_MASTER=y
315 Support for the Dialog Semiconductor DA9052 PMIC
316 when controlled using SPI. This driver provides common support
317 for accessing the device, additional drivers must be enabled in
318 order to use the functionality of the device.
320 config MFD_DA9052_I2C
321 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
327 Support for the Dialog Semiconductor DA9052 PMIC
328 when controlled using I2C. This driver provides common support
329 for accessing the device, additional drivers must be enabled in
330 order to use the functionality of the device.
333 bool "Dialog Semiconductor DA9055 PMIC Support"
339 Say yes here for support of Dialog Semiconductor DA9055. This is
340 a Power Management IC. This driver provides common support for
341 accessing the device as well as the I2C interface to the chip itself.
342 Additional drivers must be enabled in order to use the functionality
345 This driver can be built as a module. If built as a module it will be
349 tristate "Dialog Semiconductor DA9062/61 PMIC Support"
355 Say yes here for support for the Dialog Semiconductor DA9061 and
357 This includes the I2C driver and core APIs.
358 Additional drivers must be enabled in order to use the functionality
362 tristate "Dialog Semiconductor DA9063 PMIC Support"
368 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
369 This includes the I2C driver and core APIs.
370 Additional drivers must be enabled in order to use the functionality
374 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
380 This adds support for the DA9150 integrated charger and fuel-gauge
381 chip. This driver provides common support for accessing the device.
382 Additional drivers must be enabled in order to use the specific
383 features of the device.
386 tristate "Diolan DLN2 support"
390 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
391 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
392 etc. must be enabled in order to use the functionality of
395 config MFD_EXYNOS_LPASS
396 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
397 depends on ARCH_EXYNOS || COMPILE_TEST
401 Select this option to enable support for Samsung Exynos Low Power
406 depends on (SPI_MASTER || I2C)
410 Enable support for the Freescale MC13783 and MC13892 PMICs.
411 This driver provides common support for accessing the device,
412 additional drivers must be enabled in order to use the
413 functionality of the device.
415 config MFD_MC13XXX_SPI
416 tristate "Freescale MC13783 and MC13892 SPI interface"
417 depends on SPI_MASTER
421 Select this if your MC13xxx is connected via an SPI bus.
423 config MFD_MC13XXX_I2C
424 tristate "Freescale MC13892 I2C interface"
429 Select this if your MC13xxx is connected via an I2C bus.
432 tristate "Freescale i.MX23/i.MX28 LRADC"
433 depends on ARCH_MXS || COMPILE_TEST
437 Say yes here to build support for the Low Resolution
438 Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
439 processors. This driver provides common support for accessing the
440 device, additional drivers must be enabled in order to use the
441 functionality of the device:
442 mxs-lradc-adc for ADC readings
443 mxs-lradc-ts for touchscreen support
445 This driver can also be built as a module. If so, the module will be
448 config MFD_MX25_TSADC
449 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
451 depends on (SOC_IMX25 && OF) || COMPILE_TEST
453 Enable support for the integrated Touchscreen and ADC unit of the
454 i.MX25 processors. They consist of a conversion queue for general
455 purpose ADC and a queue for Touchscreens.
457 config MFD_HI6421_PMIC
458 tristate "HiSilicon Hi6421 PMU/Codec IC"
463 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
464 functions, such as regulators, RTC, codec, Coulomb counter, etc.
465 This driver includes core APIs _only_. You have to select
466 individul components like voltage regulators under corresponding
467 menus in order to enable them.
468 We communicate with the Hi6421 via memory-mapped I/O.
470 config MFD_HI655X_PMIC
471 tristate "HiSilicon Hi655X series PMU/Codec IC"
472 depends on ARCH_HISI || COMPILE_TEST
478 Select this option to enable Hisilicon hi655x series pmic driver.
481 tristate "HTC PASIC3 LED/DS1WM chip support"
484 This core driver provides register access for the LED/DS1WM
485 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
486 HTC Magician devices, respectively. Actual functionality is
487 handled by the leds-pasic3 and ds1wm drivers.
490 bool "HTC I2C PLD chip support"
491 depends on I2C=y && GPIOLIB
493 If you say yes here you get support for the supposed CPLD
494 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
495 This device provides input and output GPIOs through an I2C
496 interface to one or more sub-chips.
498 config MFD_INTEL_QUARK_I2C_GPIO
499 tristate "Intel Quark MFD I2C GPIO"
502 depends on COMMON_CLK
505 This MFD provides support for I2C and GPIO that exist only
506 in a single PCI device. It splits the 2 IO devices to
507 their respective IO driver.
508 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
511 tristate "Intel ICH LPC"
515 The LPC bridge function of the Intel ICH provides support for
516 many functional units. This driver provides needed support for
517 other drivers to control these functions, currently GPIO and
521 tristate "Intel SCH LPC"
525 LPC bridge function of the Intel SCH provides support for
526 System Management Bus and General Purpose I/O.
528 config INTEL_SOC_PMIC
529 bool "Support for Crystal Cove PMIC"
530 depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
531 depends on X86 || COMPILE_TEST
532 depends on I2C_DESIGNWARE_PLATFORM=y
537 Select this option to enable support for Crystal Cove PMIC
538 on some Intel SoC systems. The PMIC provides ADC, GPIO,
539 thermal, charger and related power management functions
542 This option is a bool as it provides an ACPI OpRegion which must be
543 available before any devices using it are probed. This option also
544 causes the designware-i2c driver to be builtin for the same reason.
546 config INTEL_SOC_PMIC_BXTWC
547 tristate "Support for Intel Broxton Whiskey Cove PMIC"
548 depends on INTEL_PMC_IPC
552 Select this option to enable support for Whiskey Cove PMIC
553 on Intel Broxton systems. The PMIC provides ADC, GPIO,
554 thermal, charger and related power management functions
557 config INTEL_SOC_PMIC_CHTWC
558 bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
559 depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
560 depends on X86 || COMPILE_TEST
561 depends on I2C_DESIGNWARE_PLATFORM=y
566 Select this option to enable support for the Intel Cherry Trail
567 Whiskey Cove PMIC found on some Intel Cherry Trail systems.
569 This option is a bool as it provides an ACPI OpRegion which must be
570 available before any devices using it are probed. This option also
571 causes the designware-i2c driver to be builtin for the same reason.
573 config INTEL_SOC_PMIC_CHTDC_TI
574 tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
583 Select this option for supporting Dollar Cove (TI version) PMIC
584 device that is found on some Intel Cherry Trail systems.
586 config MFD_INTEL_LPSS
591 config MFD_INTEL_LPSS_ACPI
592 tristate "Intel Low Power Subsystem support in ACPI mode"
593 select MFD_INTEL_LPSS
594 depends on X86 && ACPI
596 This driver supports Intel Low Power Subsystem (LPSS) devices such as
597 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
600 config MFD_INTEL_LPSS_PCI
601 tristate "Intel Low Power Subsystem support in PCI mode"
602 select MFD_INTEL_LPSS
603 depends on X86 && PCI
605 This driver supports Intel Low Power Subsystem (LPSS) devices such as
606 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
609 config MFD_INTEL_MSIC
611 depends on INTEL_SCU_IPC
614 Select this option to enable access to Intel MSIC (Avatele
615 Passage) chip. This chip embeds audio, battery, GPIO, etc.
616 devices used in Intel Medfield platforms.
618 config MFD_IPAQ_MICRO
619 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
620 depends on SA1100_H3100 || SA1100_H3600
623 Select this to get support for the Microcontroller found in
624 the Compaq iPAQ handheld computers. This is an Atmel
625 AT90LS8535 microcontroller flashed with a special iPAQ
626 firmware using the custom protocol implemented in this driver.
628 config MFD_JANZ_CMODIO
629 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
633 This is the core driver for the Janz CMOD-IO PCI MODULbus
634 carrier board. This device is a PCI to MODULbus bridge which may
635 host many different types of MODULbus daughterboards, including
636 CAN and GPIO controllers.
638 config MFD_JZ4740_ADC
639 bool "Janz JZ4740 ADC core"
641 select GENERIC_IRQ_CHIP
642 depends on MACH_JZ4740
644 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
645 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
648 tristate "Kontron module PLD device"
651 This is the core driver for the PLD (Programmable Logic Device) found
652 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
653 device may provide functions like watchdog, GPIO, UART and I2C bus.
655 The following modules are supported:
662 * COMe-bPC2 (ETXexpress-PC)
663 * COMe-bSC# (ETXexpress-SC T#)
669 * COMe-cDC2 (microETXexpress-DC)
672 * COMe-cPC2 (microETXexpress-PC)
677 * COMe-mTT10 (nanoETXexpress-TT)
680 This driver can also be built as a module. If so, the module
681 will be called kempld-core.
684 tristate "Marvell 88PM800"
690 This supports for Marvell 88PM800 Power Management IC.
691 This includes the I2C driver and the core APIs _only_, you have to
692 select individual components like voltage regulators, RTC and
693 battery-charger under the corresponding menus.
696 tristate "Marvell 88PM805"
702 This supports for Marvell 88PM805 Power Management IC. This includes
703 the I2C driver and the core APIs _only_, you have to select individual
704 components like codec device, headset/Mic device under the
708 bool "Marvell 88PM8606/88PM8607"
713 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
714 This includes the I2C driver and the core APIs _only_, you have to
715 select individual components like voltage regulators, RTC and
716 battery-charger under the corresponding menus.
719 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
726 Say yes here to add support for Maxim Semiconductor MAX14577 and
727 MAX77836 Micro-USB ICs with battery charger.
728 This driver provides common support for accessing the device;
729 additional drivers must be enabled in order to use the functionality
733 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
735 depends on OF || COMPILE_TEST
741 Say yes here to add support for Maxim Semiconductor MAX77620 and
742 MAX20024 which are Power Management IC with General purpose pins,
743 RTC, regulators, clock generator, watchdog etc. This driver
744 provides common support for accessing the device; additional drivers
745 must be enabled in order to use the functionality of the device.
748 tristate "Maxim MAX77650/77651 PMIC Support"
750 depends on OF || COMPILE_TEST
754 Say Y here to add support for Maxim Semiconductor MAX77650 and
755 MAX77651 Power Management ICs. This is the core multifunction
756 driver for interacting with the device. The module name is
757 'max77650'. Additional drivers can be enabled in order to use
758 the following functionalities of the device: GPIO, regulator,
762 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
764 depends on OF || COMPILE_TEST
770 Say yes here to add support for Maxim Semiconductor MAX77686 and
771 MAX77802 which are Power Management IC with an RTC on chip.
772 This driver provides common support for accessing the device;
773 additional drivers must be enabled in order to use the functionality
777 tristate "Maxim Semiconductor MAX77693 PMIC Support"
783 Say yes here to add support for Maxim Semiconductor MAX77693.
784 This is a companion Power Management IC with Flash, Haptic, Charger,
785 and MUIC(Micro USB Interface Controller) controls on chip.
786 This driver provides common support for accessing the device;
787 additional drivers must be enabled in order to use the functionality
791 bool "Maxim Semiconductor MAX77843 PMIC Support"
797 Say yes here to add support for Maxim Semiconductor MAX77843.
798 This is companion Power Management IC with LEDs, Haptic, Charger,
799 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
800 This driver provides common support for accessing the device;
801 additional drivers must be enabled in order to use the functionality
805 tristate "Maxim Semiconductor MAX8907 PMIC Support"
811 Say yes here to add support for Maxim Semiconductor MAX8907. This is
812 a Power Management IC. This driver provides common support for
813 accessing the device; additional drivers must be enabled in order
814 to use the functionality of the device.
817 bool "Maxim Semiconductor MAX8925 PMIC Support"
821 Say yes here to add support for Maxim Semiconductor MAX8925. This is
822 a Power Management IC. This driver provides common support for
823 accessing the device, additional drivers must be enabled in order
824 to use the functionality of the device.
827 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
832 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
833 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
834 MUIC controls on chip.
835 This driver provides common support for accessing the device;
836 additional drivers must be enabled in order to use the functionality
840 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
845 Say yes here to add support for Maxim Semiconductor MAX8998 and
846 National Semiconductor LP3974. This is a Power Management IC.
847 This driver provides common support for accessing the device,
848 additional drivers must be enabled in order to use the functionality
852 tristate "MediaTek MT6397 PMIC Support"
856 Say yes here to add support for MediaTek MT6397 PMIC. This is
857 a Power Management IC. This driver provides common support for
858 accessing the device; additional drivers must be enabled in order
859 to use the functionality of the device.
862 tristate "MEN 14F021P00 Board Management Controller Support"
866 Say yes here to add support for the MEN 14F021P00 BMC
867 which is a Board Management Controller connected to the I2C bus.
868 The device supports multiple sub-devices like LED, HWMON and WDT.
869 This driver provides common support for accessing the devices;
870 additional drivers must be enabled in order to use the
871 functionality of the BMC device.
873 This driver can also be built as a module. If so the module
874 will be called menf21bmc.
877 bool "Motorola EZXPCAP Support"
878 depends on SPI_MASTER
880 This enables the PCAP ASIC present on EZX Phones. This is
881 needed for MMC, TouchScreen, Sound, USB, etc..
884 tristate "Support for Motorola CPCAP"
886 depends on OF || COMPILE_TEST
890 Say yes here if you want to include driver for CPCAP.
891 It is used on many Motorola phones and tablets as a PMIC.
892 At least Motorola Droid 4 is known to use CPCAP.
894 config MFD_VIPERBOARD
895 tristate "Nano River Technologies Viperboard"
900 Say yes here if you want support for Nano River Technologies
902 There are mfd cell drivers available for i2c master, adc and
903 both gpios found on the board. The spi part does not yet
905 You need to select the mfd cell drivers separately.
906 The drivers do not support all features the board exposes.
909 tristate "Nokia Retu and Tahvo multi-function device"
914 Retu and Tahvo are a multi-function devices found on Nokia
915 Internet Tablets (770, N800 and N810).
918 tristate "NXP PCF50633"
922 Say yes here if you have NXP PCF50633 chip on your board.
923 This core driver provides register access and IRQ handling
924 facilities, and registers devices for the various functions
925 so that function-specific drivers can bind to them.
928 tristate "NXP PCF50633 ADC"
929 depends on MFD_PCF50633
931 Say yes here if you want to include support for ADC in the
935 tristate "NXP PCF50633 GPIO"
936 depends on MFD_PCF50633
938 Say yes here if you want to include support GPIO for pins on
942 tristate "Philips UCB1400 Core driver"
946 This enables support for the Philips UCB1400 core functions.
947 The UCB1400 is an AC97 audio codec.
949 To compile this driver as a module, choose M here: the
950 module will be called ucb1400_core.
953 tristate "Qualcomm PM8xxx PMIC chips driver"
954 depends on (ARM || HEXAGON || COMPILE_TEST)
955 select IRQ_DOMAIN_HIERARCHY
959 If you say yes to this option, support will be included for the
960 built-in PM8xxx PMIC chips.
962 This is required if your board has a PM8xxx and uses its features,
963 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
965 Say M here if you want to include support for PM8xxx chips as a
966 module. This will build a module called "pm8xxx-core".
969 tristate "Qualcomm Resource Power Manager (RPM)"
970 depends on ARCH_QCOM && OF
972 If you say yes to this option, support will be included for the
973 Resource Power Manager system found in the Qualcomm 8660, 8960 and
976 This is required to access many regulators, clocks and bus
977 frequencies controlled by the RPM on these devices.
979 Say M here if you want to include support for the Qualcomm RPM as a
980 module. This will build a module called "qcom_rpm".
983 tristate "Qualcomm SPMI PMICs"
984 depends on ARCH_QCOM || COMPILE_TEST
989 This enables support for the Qualcomm SPMI PMICs.
990 These PMICs are currently used with the Snapdragon 800 series of
991 SoCs. Note, that this will only be useful paired with descriptions
992 of the independent functions as children nodes in the device tree.
994 Say M here if you want to include support for the SPMI PMIC
995 series as a module. The module will be called "qcom-spmi-pmic".
998 tristate "RDC R-321x southbridge"
1002 Say yes here if you want to have support for the RDC R-321x SoC
1003 southbridge which provides access to GPIOs and Watchdog using the
1004 southbridge PCI device configuration space.
1007 tristate "Richtek RT5033 Power Management IC"
1013 This driver provides for the Richtek RT5033 Power Management IC,
1014 which includes the I2C driver and the Core APIs. This driver provides
1015 common support for accessing the device. The device supports multiple
1016 sub-devices like charger, fuel gauge, flash LED, current source,
1020 bool "Ricoh RC5T583 Power Management system device"
1025 Select this option to get support for the RICOH583 Power
1026 Management system device.
1027 This driver provides common support for accessing the device
1028 through i2c interface. The device supports multiple sub-devices
1029 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1030 Additional drivers must be enabled in order to use the
1031 different functionality of the device.
1034 tristate "Rockchip RK805/RK808/RK818 Power Management Chip"
1035 depends on I2C && OF
1040 If you say yes here you get support for the RK805, RK808 and RK818
1041 Power Management chips.
1042 This driver provides common support for accessing the device
1043 through I2C interface. The device supports multiple sub-devices
1044 including interrupts, RTC, LDO & DCDC regulators, and onkey.
1047 tristate "Ricoh RN5T567/618 PMIC"
1053 Say yes here to add support for the Ricoh RN5T567,
1054 RN5T618, RC5T619 PMIC.
1055 This driver provides common support for accessing the device,
1056 additional drivers must be enabled in order to use the
1057 functionality of the device.
1060 tristate "SAMSUNG Electronics PMIC Series Support"
1066 Support for the Samsung Electronics PMIC devices coming
1067 usually along with Samsung Exynos SoC chipset.
1068 This driver provides common support for accessing the device,
1069 additional drivers must be enabled in order to use the functionality
1072 To compile this driver as a module, choose M here: the
1073 module will be called sec-core.
1074 Have in mind that important core drivers (like regulators) depend
1075 on this driver so building this as a module might require proper
1076 initial ramdisk or might not boot up as well in certain scenarios.
1078 config MFD_SI476X_CORE
1079 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1084 This is the core driver for the SI476x series of AM/FM
1085 radio. This MFD driver connects the radio-si476x V4L2 module
1086 and the si476x audio codec.
1088 To compile this driver as a module, choose M here: the
1089 module will be called si476x-core.
1092 tristate "Silicon Motion SM501"
1094 select DMA_DECLARE_COHERENT
1096 This is the core driver for the Silicon Motion SM501 multimedia
1097 companion chip. This device is a multifunction device which may
1098 provide numerous interfaces including USB host controller, USB gadget,
1099 asynchronous serial ports, audio functions, and a dual display video
1100 interface. The device may be connected by PCI or local bus with
1101 varying functions enabled.
1103 config MFD_SM501_GPIO
1104 bool "Export GPIO via GPIO layer"
1105 depends on MFD_SM501 && GPIOLIB
1107 This option uses the gpio library layer to export the 64 GPIO
1108 lines on the SM501. The platform data is used to supply the
1109 base number for the first GPIO line to register.
1112 tristate "Skyworks Solutions SKY81452"
1117 This is the core driver for the Skyworks SKY81452 backlight and
1118 voltage regulator device.
1120 This driver can also be built as a module. If so, the module
1121 will be called sky81452.
1124 bool "SMSC ECE1099 series chips"
1129 If you say yes here you get support for the
1130 ece1099 chips from SMSC.
1132 To compile this driver as a module, choose M here: the
1133 module will be called smsc.
1135 config MFD_SC27XX_PMIC
1136 tristate "Spreadtrum SC27xx PMICs"
1137 depends on ARCH_SPRD || COMPILE_TEST
1138 depends on SPI_MASTER
1143 This enables support for the Spreadtrum SC27xx PMICs with SPI
1144 interface. The SC27xx series PMICs integrate power management,
1145 audio codec, battery management and user interface support
1146 function (such as RTC, Typec, indicator and so on) in a single chip.
1148 This driver provides common support for accessing the SC27xx PMICs,
1149 and it also adds the irq_chip parts for handling the PMIC chip events.
1152 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1153 default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1155 Say yes here if you have the ABX500 Mixed Signal IC family
1156 chips. This core driver expose register access functions.
1157 Functionality specific drivers using these functions can
1158 remain unchanged when IC changes. Binding of the functions to
1159 actual register access is done by the IC core driver.
1162 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1163 depends on I2C=y && ABX500_CORE
1165 default y if ARCH_U300
1167 Select this to enable the AB3100 Mixed Signal IC core
1168 functionality. This connects to a AB3100 on the I2C bus
1169 and expose a number of symbols needed for dependent devices
1170 to read and write registers and subscribe to events from
1171 this multi-functional IC. This is needed to use other features
1172 of the AB3100 such as battery-backed RTC, charging control,
1173 LEDs, vibrator, system power and temperature, power management
1177 tristate "ST-Ericsson AB3100 OTP functions"
1178 depends on AB3100_CORE
1179 default y if AB3100_CORE
1181 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1182 programmable memory) support. This exposes a sysfs file to read
1186 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1187 depends on ABX500_CORE && MFD_DB8500_PRCMU
1192 Select this option to enable access to AB8500 power management
1193 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1194 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1195 the irq_chip parts for handling the Mixed Signal chip events.
1196 This chip embeds various other multimedia funtionalities as well.
1199 bool "Enable debug info via debugfs"
1200 depends on AB8500_GPADC && DEBUG_FS
1201 default y if DEBUG_FS
1203 Select this option if you want debug information using the debug
1204 filesystem, debugfs.
1207 bool "ST-Ericsson AB8500 GPADC driver"
1208 depends on AB8500_CORE && REGULATOR_AB8500
1211 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1213 config MFD_DB8500_PRCMU
1214 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1215 depends on UX500_SOC_DB8500
1218 Select this option to enable support for the DB8500 Power Reset
1219 and Control Management Unit. This is basically an autonomous
1220 system controller running an XP70 microprocessor, which is accessed
1221 through a register map.
1224 bool "STMicroelectronics STMPE"
1225 depends on (I2C=y || SPI_MASTER=y)
1229 Support for the STMPE family of I/O Expanders from
1232 Currently supported devices are:
1234 STMPE811: GPIO, Touchscreen, ADC
1235 STMPE1601: GPIO, Keypad
1236 STMPE1801: GPIO, Keypad
1237 STMPE2401: GPIO, Keypad
1238 STMPE2403: GPIO, Keypad
1240 This driver provides common support for accessing the device,
1241 additional drivers must be enabled in order to use the functionality
1242 of the device. Currently available sub drivers are:
1245 Keypad: stmpe-keypad
1246 Touchscreen: stmpe-ts
1249 menu "STMicroelectronics STMPE Interface Drivers"
1250 depends on MFD_STMPE
1253 bool "STMicroelectronics STMPE I2C Interface"
1257 This is used to enable I2C interface of STMPE
1260 bool "STMicroelectronics STMPE SPI Interface"
1261 depends on SPI_MASTER
1263 This is used to enable SPI interface of STMPE
1267 bool "STMicroelectronics STA2X11"
1272 config MFD_SUN6I_PRCM
1273 bool "Allwinner A31 PRCM controller"
1274 depends on ARCH_SUNXI || COMPILE_TEST
1277 Support for the PRCM (Power/Reset/Clock Management) unit available
1281 bool "System Controller Register R/W Based on Regmap"
1284 Select this option to enable accessing system control registers
1287 config MFD_DAVINCI_VOICECODEC
1292 config MFD_TI_AM335X_TSCADC
1293 tristate "TI ADC / Touch Screen chip support"
1298 If you say yes here you get support for Texas Instruments series
1299 of Touch Screen /ADC chips.
1300 To compile this driver as a module, choose M here: the
1301 module will be called ti_am335x_tscadc.
1303 config MFD_DM355EVM_MSP
1304 bool "TI DaVinci DM355 EVM microcontroller"
1305 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1307 This driver supports the MSP430 microcontroller used on these
1308 boards. MSP430 firmware manages resets and power sequencing,
1309 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1312 tristate "TI/National Semiconductor LP3943 MFD Driver"
1317 Support for the TI/National Semiconductor LP3943.
1318 This driver consists of GPIO and PWM drivers.
1319 With these functionalities, it can be used for LED string control or
1320 general usage such like a GPIO controller and a PWM controller.
1323 bool "TI LP8788 Power Management Unit Driver"
1329 TI LP8788 PMU supports regulators, battery charger, RTC,
1330 ADC, backlight driver and current sinks.
1333 tristate "TI Lighting Management Unit driver"
1338 Say yes here to enable support for TI LMU chips.
1339 TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and
1340 LM36274. It consists of backlight, LED and regulator driver.
1341 It provides consistent device controls for lighting functions.
1343 config MFD_OMAP_USB_HOST
1344 bool "TI OMAP USBHS core and TLL driver"
1345 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1348 This is the core driver for the OAMP EHCI and OHCI drivers.
1349 This MFD driver does the required setup functionalities for
1350 OMAP USB Host drivers.
1353 bool "TI Palmas series chips"
1359 If you say yes here you get support for the Palmas
1360 series of PMIC chips from Texas Instruments.
1363 tristate "TI TPS61050/61052 Boost Converters"
1368 select REGULATOR_FIXED_VOLTAGE
1370 This option enables a driver for the TP61050/TPS61052
1371 high-power "white LED driver". This boost converter is
1372 sometimes used for other things than white LEDs, and
1373 also contains a GPIO pin.
1376 tristate "TI TPS6501x Power Management chips"
1377 depends on I2C && GPIOLIB
1378 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1380 If you say yes here you get support for the TPS6501x series of
1381 Power Management chips. These include voltage regulators,
1382 lithium ion/polymer battery charging, and other features that
1383 are often used in portable devices like cell phones and cameras.
1385 This driver can also be built as a module. If so, the module
1386 will be called tps65010.
1389 tristate "TI TPS6507x Power Management / Touch Screen chips"
1393 If you say yes here you get support for the TPS6507x series of
1394 Power Management / Touch Screen chips. These include voltage
1395 regulators, lithium ion/polymer battery charging, touch screen
1396 and other features that are often used in portable devices.
1397 This driver can also be built as a module. If so, the module
1398 will be called tps6507x.
1401 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1408 If you say yes here you get support for the TPS65086 series of
1409 Power Management chips.
1410 This driver provides common support for accessing the device,
1411 additional drivers must be enabled in order to use the
1412 functionality of the device.
1414 config TPS65911_COMPARATOR
1418 bool "TI TPS65090 Power Management chips"
1424 If you say yes here you get support for the TPS65090 series of
1425 Power Management chips.
1426 This driver provides common support for accessing the device,
1427 additional drivers must be enabled in order to use the
1428 functionality of the device.
1431 tristate "TI TPS65217 Power Management / White LED chips"
1432 depends on I2C && OF
1437 If you say yes here you get support for the TPS65217 series of
1438 Power Management / White LED chips.
1439 These include voltage regulators, lithium ion/polymer battery
1440 charger, wled and other features that are often used in portable
1443 This driver can also be built as a module. If so, the module
1444 will be called tps65217.
1447 bool "TI TPS68470 Power Management / LED chips"
1448 depends on ACPI && PCI && I2C=y
1449 depends on I2C_DESIGNWARE_PLATFORM=y
1453 If you say yes here you get support for the TPS68470 series of
1454 Power Management / LED chips.
1456 These include voltage regulators, LEDs and other features
1457 that are often used in portable devices.
1459 This option is a bool as it provides an ACPI operation
1460 region, which must be available before any of the devices
1461 using this are probed. This option also configures the
1462 designware-i2c driver to be built-in, for the same reason.
1464 config MFD_TI_LP873X
1465 tristate "TI LP873X Power Management IC"
1470 If you say yes here then you get support for the LP873X series of
1471 Power Management Integrated Circuits (PMIC).
1472 These include voltage regulators, thermal protection, configurable
1473 General Purpose Outputs (GPO) that are used in portable devices.
1475 This driver can also be built as a module. If so, the module
1476 will be called lp873x.
1478 config MFD_TI_LP87565
1479 tristate "TI LP87565 Power Management IC"
1480 depends on I2C && OF
1484 If you say yes here then you get support for the LP87565 series of
1485 Power Management Integrated Circuits (PMIC).
1486 These include voltage regulators, thermal protection, configurable
1487 General Purpose Outputs (GPO) that are used in portable devices.
1489 This driver can also be built as a module. If so, the module
1490 will be called lp87565.
1493 tristate "TI TPS65218 Power Management chips"
1494 depends on I2C && OF
1499 If you say yes here you get support for the TPS65218 series of
1500 Power Management chips.
1501 These include voltage regulators, gpio and other features
1502 that are often used in portable devices.
1504 This driver can also be built as a module. If so, the module
1505 will be called tps65218.
1508 bool "TI TPS6586x Power Management chips"
1513 If you say yes here you get support for the TPS6586X series of
1514 Power Management chips.
1515 This driver provides common support for accessing the device,
1516 additional drivers must be enabled in order to use the
1517 functionality of the device.
1519 This driver can also be built as a module. If so, the module
1520 will be called tps6586x.
1523 bool "TI TPS65910 Power Management chip"
1525 depends on GPIOLIB || COMPILE_TEST
1531 if you say yes here you get support for the TPS65910 series of
1532 Power Management chips.
1540 config MFD_TPS65912_I2C
1541 tristate "TI TPS65912 Power Management chip with I2C"
1546 If you say yes here you get support for the TPS65912 series of
1547 PM chips with I2C interface.
1549 config MFD_TPS65912_SPI
1550 tristate "TI TPS65912 Power Management chip with SPI"
1553 depends on SPI_MASTER
1555 If you say yes here you get support for the TPS65912 series of
1556 PM chips with SPI interface.
1559 bool "TI TPS80031/TPS80032 Power Management chips"
1565 If you say yes here you get support for the Texas Instruments
1566 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1567 Path and Battery Charger. The device provides five configurable
1568 step-down converters, 11 general purpose LDOs, USB OTG Module,
1569 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1570 Power Path from USB, 32K clock generator.
1573 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1578 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1579 This core driver provides register access and IRQ handling
1580 facilities, and registers devices for the various functions
1581 so that function-specific drivers can bind to them.
1583 These multi-function chips are found on many OMAP2 and OMAP3
1584 boards, providing power management, RTC, GPIO, keypad, a
1585 high speed USB OTG transceiver, an audio codec (on most
1586 versions) and many other features.
1588 config TWL4030_POWER
1589 bool "TI TWL4030 power resources"
1590 depends on TWL4030_CORE && ARM
1592 Say yes here if you want to use the power resources on the
1593 TWL4030 family chips. Most of these resources are regulators,
1594 which have a separate driver; some are control signals, such
1595 as clock request handshaking.
1597 This driver uses board-specific data to initialize the resources
1598 and load scripts controlling which resources are switched off/on
1599 or reset when a sleep, wakeup or warm reset event occurs.
1601 config MFD_TWL4030_AUDIO
1602 bool "TI TWL4030 Audio"
1603 depends on TWL4030_CORE
1608 bool "TI TWL6040 audio codec"
1615 Say yes here if you want support for Texas Instruments TWL6040 audio
1617 This driver provides common support for accessing the device,
1618 additional drivers must be enabled in order to use the
1619 functionality of the device (audio, vibra).
1622 bool "TI TWL92330/Menelaus PM chip"
1623 depends on I2C=y && ARCH_OMAP2
1625 If you say yes here you get support for the Texas Instruments
1626 TWL92330/Menelaus Power Management chip. This include voltage
1627 regulators, Dual slot memory card transceivers, real-time clock
1628 and other features that are often used in portable devices like
1629 cell phones and PDAs.
1631 config MFD_WL1273_CORE
1632 tristate "TI WL1273 FM radio"
1637 This is the core driver for the TI WL1273 FM radio. This MFD
1638 driver connects the radio-wl1273 V4L2 module and the wl1273
1642 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1647 Say yes here to enable support for National Semiconductor / TI
1648 LM3533 Lighting Power chips.
1650 This driver provides common support for accessing the device;
1651 additional drivers must be enabled in order to use the LED,
1652 backlight or ambient-light-sensor functionality of the device.
1654 config MFD_TIMBERDALE
1655 tristate "Timberdale FPGA"
1657 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1659 This is the core driver for the timberdale FPGA. This device is a
1660 multifunction device which exposes numerous platform devices.
1662 The timberdale FPGA can be found on the Intel Atom development board
1663 for in-vehicle infontainment, called Russellville.
1666 bool "Toshiba TC35892 and variants"
1671 Support for the Toshiba TC35892 and variants I/O Expander.
1673 This driver provides common support for accessing the device,
1674 additional drivers must be enabled in order to use the
1675 functionality of the device.
1682 bool "Toshiba T7L66XB"
1683 depends on ARM && HAVE_CLK
1687 Support for Toshiba Mobile IO Controller T7L66XB
1690 bool "Toshiba TC6387XB"
1691 depends on ARM && HAVE_CLK
1695 Support for Toshiba Mobile IO Controller TC6387XB
1698 bool "Toshiba TC6393XB"
1699 depends on ARM && HAVE_CLK
1703 select DMA_DECLARE_COHERENT
1705 Support for Toshiba Mobile IO Controller TC6393XB
1708 tristate "TQ-Systems IO controller TQMX86"
1711 Say yes here to enable support for various functions of the
1712 TQ-Systems IO controller and watchdog device, found on their
1713 ComExpress CPU modules.
1716 tristate "VIA VX855/VX875 integrated south bridge"
1720 Say yes here to enable support for various functions of the
1721 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1722 and/or vx855_gpio drivers for this to do anything useful.
1724 config MFD_LOCHNAGAR
1725 bool "Cirrus Logic Lochnagar Audio Development Board"
1728 depends on I2C=y && OF
1730 Support for Cirrus Logic Lochnagar audio development board.
1738 config MFD_ARIZONA_I2C
1739 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1744 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1745 audio SoC core functionality controlled via I2C.
1747 config MFD_ARIZONA_SPI
1748 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1751 depends on SPI_MASTER
1753 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1754 audio SoC core functionality controlled via SPI.
1757 bool "Cirrus Logic CS47L24 and WM1831"
1758 depends on MFD_ARIZONA
1760 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1763 bool "Wolfson Microelectronics WM5102"
1764 depends on MFD_ARIZONA
1766 Support for Wolfson Microelectronics WM5102 low power audio SoC
1769 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1770 depends on MFD_ARIZONA
1772 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1776 bool "Wolfson Microelectronics WM8997"
1777 depends on MFD_ARIZONA
1779 Support for Wolfson Microelectronics WM8997 low power audio SoC
1782 bool "Wolfson Microelectronics WM8998"
1783 depends on MFD_ARIZONA
1785 Support for Wolfson Microelectronics WM8998 low power audio SoC
1788 bool "Wolfson Microelectronics WM8400"
1793 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1794 CODEC. This driver provides common support for accessing
1795 the device, additional drivers must be enabled in order to use
1796 the functionality of the device.
1801 config MFD_WM831X_I2C
1802 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1809 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1810 when controlled using I2C. This driver provides common support
1811 for accessing the device, additional drivers must be enabled in
1812 order to use the functionality of the device.
1814 config MFD_WM831X_SPI
1815 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1820 depends on SPI_MASTER
1822 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1823 when controlled using SPI. This driver provides common support
1824 for accessing the device, additional drivers must be enabled in
1825 order to use the functionality of the device.
1830 config MFD_WM8350_I2C
1831 bool "Wolfson Microelectronics WM8350 with I2C"
1836 The WM8350 is an integrated audio and power management
1837 subsystem with watchdog and RTC functionality for embedded
1838 systems. This option enables core support for the WM8350 with
1839 I2C as the control interface. Additional options must be
1840 selected to enable support for the functionality of the chip.
1843 tristate "Wolfson Microelectronics WM8994"
1849 The WM8994 is a highly integrated hi-fi CODEC designed for
1850 smartphone applications. As well as audio functionality it
1851 has on board GPIO and regulator functionality which is
1852 supported via the relevant subsystems. This driver provides
1853 core support for the WM8994, in order to use the actual
1854 functionaltiy of the device other drivers must be enabled.
1857 tristate "Wolfson Microelectronics WM97xx"
1860 select AC97_BUS_COMPAT
1861 depends on AC97_BUS_NEW
1863 The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1864 designed for smartphone applications. As well as audio functionality
1865 it has on board GPIO and a touchscreen functionality which is
1866 supported via the relevant subsystems. This driver provides core
1867 support for the WM97xx, in order to use the actual functionaltiy of
1868 the device other drivers must be enabled.
1871 tristate "Support for ST Microelectronics STw481x"
1872 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1876 Select this option to enable the STw481x chip driver used
1877 in various ST Microelectronics and ST-Ericsson embedded
1880 config MFD_ROHM_BD718XX
1881 tristate "ROHM BD71837 Power Management IC"
1888 Select this option to get support for the ROHM BD71837
1889 Power Management ICs. BD71837 is designed to power processors like
1890 NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
1891 and emergency shut down as well as 32,768KHz clock output.
1893 config MFD_STM32_LPTIMER
1894 tristate "Support for STM32 Low-Power Timer"
1895 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1900 Select this option to enable STM32 Low-Power Timer driver
1901 used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1902 resources are also dealt with here.
1904 To compile this driver as a module, choose M here: the
1905 module will be called stm32-lptimer.
1907 config MFD_STM32_TIMERS
1908 tristate "Support for STM32 Timers"
1909 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1914 Select this option to enable STM32 timers driver used
1915 for PWM and IIO Timer. This driver allow to share the
1916 registers between the others drivers.
1919 tristate "Support for STPMIC1 PMIC"
1920 depends on (I2C=y && OF)
1925 Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on
1926 key, watchdog and regulator functionalities which are supported via
1927 the relevant subsystems. This driver provides core support for the
1928 STPMIC1. In order to use the actual functionaltiy of the device other
1929 drivers must be enabled.
1931 To compile this driver as a module, choose M here: the
1932 module will be called stpmic1.
1935 tristate "Support for STMicroelectronics Multi-Function eXpander (STMFX)"
1937 depends on OF || COMPILE_TEST
1941 Support for the STMicroelectronics Multi-Function eXpander.
1943 This driver provides common support for accessing the device,
1944 additional drivers must be enabled in order to use the functionality
1947 menu "Multimedia Capabilities Port drivers"
1948 depends on ARCH_SA1100
1955 tristate "Support SA11x0 MCP interface"
1956 depends on ARCH_SA1100
1961 tristate "Support for UCB1200 / UCB1300"
1962 depends on MCP_SA11X0
1965 config MCP_UCB1200_TS
1966 tristate "Touchscreen interface support"
1967 depends on MCP_UCB1200 && INPUT
1971 config MFD_VEXPRESS_SYSREG
1972 bool "Versatile Express System Registers"
1973 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1976 select GPIO_GENERIC_PLATFORM
1980 System Registers are the platform configuration block
1981 on the ARM Ltd. Versatile Express board.
1984 tristate "RAVE SP MCU core driver"
1985 depends on SERIAL_DEV_BUS
1988 Select this to get support for the Supervisory Processor
1989 device found on several devices in RAVE line of hardware.