2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
21 config MFD_ALTERA_A10SR
22 bool "Altera Arria10 DevKit System Resource chip"
23 depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
27 Support for the Altera Arria10 DevKit MAX5 System Resource chip
28 using the SPI interface. This driver provides common support for
29 accessing the external gpio extender (LEDs & buttons) and
30 power supply alarms (hwmon).
33 tristate "Active-semi ACT8945A"
38 Support for the ACT8945A PMIC from Active-semi. This device
39 features three step-down DC/DC converters and four low-dropout
40 linear regulators, along with a complete ActivePath battery
43 config MFD_SUN4I_GPADC
44 tristate "Allwinner sunxi platforms' GPADC MFD driver"
48 depends on ARCH_SUNXI || COMPILE_TEST
49 depends on !TOUCHSCREEN_SUN4I
51 Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC.
52 This driver will only map the hardware interrupt and registers, you
53 have to select individual drivers based on this MFD to be able to use
54 the ADC or the thermal sensor. This will try to probe the ADC driver
55 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
57 To compile this driver as a module, choose M here: the module will be
67 Support for the AS3711 PMIC from AMS
70 tristate "ams AS3722 Power Management IC"
74 depends on I2C=y && OF
76 The ams AS3722 is a compact system PMU suitable for mobile phones,
77 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
78 controllers, 11 LDOs, RTC, automatic battery, temperature and
79 over current monitoring, GPIOs, ADC and a watchdog.
82 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
85 Say yes here to add support for Analog Devices AD5520 and ADP5501,
86 Multifunction Power Management IC. This includes
87 the I2C driver and the core APIs _only_, you have to select
88 individual components like LCD backlight, LEDs, GPIOs and Kepad
89 under the corresponding menus.
91 config MFD_AAT2870_CORE
92 bool "AnalogicTech AAT2870"
95 depends on GPIOLIB || COMPILE_TEST
97 If you say yes here you get support for the AAT2870.
98 This driver provides common support for accessing the device,
99 additional drivers must be enabled in order to use the
100 functionality of the device.
102 config MFD_AT91_USART
103 tristate "AT91 USART Driver"
105 depends on ARCH_AT91 || COMPILE_TEST
107 Select this to get support for AT91 USART IP. This is a wrapper
108 over at91-usart-serial driver and usart-spi-driver. Only one function
109 can be used at a time. The choice is done at boot time by the probe
110 function of this MFD driver according to a device tree property.
112 config MFD_ATMEL_FLEXCOM
113 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
117 Select this to get support for Atmel Flexcom. This is a wrapper
118 which embeds a SPI controller, a I2C controller and a USART. Only
119 one function can be used at a time. The choice is done at boot time
120 by the probe function of this MFD driver according to a device tree
123 config MFD_ATMEL_HLCDC
124 tristate "Atmel HLCDC (High-end LCD Controller)"
129 If you say yes here you get support for the HLCDC block.
130 This driver provides common support for accessing the device,
131 additional drivers must be enabled in order to use the
132 functionality of the device.
139 tristate "Broadcom BCM590xx PMUs"
144 Support for the BCM590xx PMUs from Broadcom
147 tristate "ROHM BD9571MWV PMIC"
153 Support for the ROHM BD9571MWV PMIC, which contains single
154 voltage regulator, voltage sampling units, GPIO block and
157 This driver can also be built as a module. If so, the module
158 will be called bd9571mwv.
161 tristate "X-Powers AC100"
165 If you say Y here you get support for the X-Powers AC100 audio codec
167 This driver include only the core APIs. You have to select individual
168 components like codecs or RTC under the corresponding menus.
175 config MFD_AXP20X_I2C
176 tristate "X-Powers AXP series PMICs with I2C"
181 If you say Y here you get support for the X-Powers AXP series power
182 management ICs (PMICs) controlled with I2C.
183 This driver include only the core APIs. You have to select individual
184 components like regulators or the PEK (Power Enable Key) under the
187 Note on x86 this provides an ACPI OpRegion, so this must be 'y'
188 (builtin) and not a module, as the OpRegion must be available as
189 soon as possible. For the same reason the I2C bus driver options
190 I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
192 config MFD_AXP20X_RSB
193 tristate "X-Powers AXP series PMICs with RSB"
197 If you say Y here you get support for the X-Powers AXP series power
198 management ICs (PMICs) controlled with RSB.
199 This driver include only the core APIs. You have to select individual
200 components like regulators or the PEK (Power Enable Key) under the
204 tristate "ChromeOS Embedded Controller"
206 select CHROME_PLATFORMS
208 depends on X86 || ARM || ARM64 || COMPILE_TEST
210 If you say Y here you get support for the ChromeOS Embedded
211 Controller (EC) providing keyboard, battery and power services.
212 You also need to enable the driver for the bus you are using. The
213 protocol for talking to the EC is defined by the bus driver.
215 config MFD_CROS_EC_CHARDEV
216 tristate "Chrome OS Embedded Controller userspace device interface"
217 depends on MFD_CROS_EC
219 This driver adds support to talk with the ChromeOS EC from userspace.
221 If you have a supported Chromebook, choose Y or M here.
222 The module will be called cros_ec_dev.
225 tristate "Cirrus Logic Madera codecs"
231 select PINCTRL_MADERA
233 Support for the Cirrus Logic Madera platform audio codecs
235 config MFD_MADERA_I2C
236 tristate "Cirrus Logic Madera codecs with I2C"
237 depends on MFD_MADERA
241 Support for the Cirrus Logic Madera platform audio SoC
242 core functionality controlled via I2C.
244 config MFD_MADERA_SPI
245 tristate "Cirrus Logic Madera codecs with SPI"
246 depends on MFD_MADERA
247 depends on SPI_MASTER
250 Support for the Cirrus Logic Madera platform audio SoC
251 core functionality controlled via SPI.
254 bool "Cirrus Logic CS47L35"
255 select PINCTRL_CS47L35
256 depends on MFD_MADERA
258 Support for Cirrus Logic CS47L35 Smart Codec
261 bool "Cirrus Logic CS47L85"
262 select PINCTRL_CS47L85
263 depends on MFD_MADERA
265 Support for Cirrus Logic CS47L85 Smart Codec
268 bool "Cirrus Logic CS47L90/91"
269 select PINCTRL_CS47L90
270 depends on MFD_MADERA
272 Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
276 depends on GPIOLIB && ARM
279 This driver supports the ASIC3 multifunction chip found on many
280 PDAs (mainly iPAQ and HTC based ones)
283 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
286 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
287 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
288 usually found on PXA processors-based platforms. This includes
289 the I2C driver and the core APIs _only_, you have to select
290 individual components like LCD backlight, voltage regulators,
291 LEDs and battery-charger under the corresponding menus.
297 config MFD_DA9052_SPI
298 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
302 depends on SPI_MASTER=y
304 Support for the Dialog Semiconductor DA9052 PMIC
305 when controlled using SPI. This driver provides common support
306 for accessing the device, additional drivers must be enabled in
307 order to use the functionality of the device.
309 config MFD_DA9052_I2C
310 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
316 Support for the Dialog Semiconductor DA9052 PMIC
317 when controlled using I2C. This driver provides common support
318 for accessing the device, additional drivers must be enabled in
319 order to use the functionality of the device.
322 bool "Dialog Semiconductor DA9055 PMIC Support"
328 Say yes here for support of Dialog Semiconductor DA9055. This is
329 a Power Management IC. This driver provides common support for
330 accessing the device as well as the I2C interface to the chip itself.
331 Additional drivers must be enabled in order to use the functionality
334 This driver can be built as a module. If built as a module it will be
338 tristate "Dialog Semiconductor DA9062/61 PMIC Support"
344 Say yes here for support for the Dialog Semiconductor DA9061 and
346 This includes the I2C driver and core APIs.
347 Additional drivers must be enabled in order to use the functionality
351 tristate "Dialog Semiconductor DA9063 PMIC Support"
357 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
358 This includes the I2C driver and core APIs.
359 Additional drivers must be enabled in order to use the functionality
363 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
369 This adds support for the DA9150 integrated charger and fuel-gauge
370 chip. This driver provides common support for accessing the device.
371 Additional drivers must be enabled in order to use the specific
372 features of the device.
375 tristate "Diolan DLN2 support"
379 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
380 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
381 etc. must be enabled in order to use the functionality of
384 config MFD_EXYNOS_LPASS
385 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
386 depends on ARCH_EXYNOS || COMPILE_TEST
390 Select this option to enable support for Samsung Exynos Low Power
395 depends on (SPI_MASTER || I2C)
399 Enable support for the Freescale MC13783 and MC13892 PMICs.
400 This driver provides common support for accessing the device,
401 additional drivers must be enabled in order to use the
402 functionality of the device.
404 config MFD_MC13XXX_SPI
405 tristate "Freescale MC13783 and MC13892 SPI interface"
406 depends on SPI_MASTER
410 Select this if your MC13xxx is connected via an SPI bus.
412 config MFD_MC13XXX_I2C
413 tristate "Freescale MC13892 I2C interface"
418 Select this if your MC13xxx is connected via an I2C bus.
421 tristate "Freescale i.MX23/i.MX28 LRADC"
422 depends on ARCH_MXS || COMPILE_TEST
426 Say yes here to build support for the Low Resolution
427 Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
428 processors. This driver provides common support for accessing the
429 device, additional drivers must be enabled in order to use the
430 functionality of the device:
431 mxs-lradc-adc for ADC readings
432 mxs-lradc-ts for touchscreen support
434 This driver can also be built as a module. If so, the module will be
437 config MFD_MX25_TSADC
438 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
440 depends on (SOC_IMX25 && OF) || COMPILE_TEST
442 Enable support for the integrated Touchscreen and ADC unit of the
443 i.MX25 processors. They consist of a conversion queue for general
444 purpose ADC and a queue for Touchscreens.
446 config MFD_HI6421_PMIC
447 tristate "HiSilicon Hi6421 PMU/Codec IC"
452 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
453 functions, such as regulators, RTC, codec, Coulomb counter, etc.
454 This driver includes core APIs _only_. You have to select
455 individul components like voltage regulators under corresponding
456 menus in order to enable them.
457 We communicate with the Hi6421 via memory-mapped I/O.
459 config MFD_HI655X_PMIC
460 tristate "HiSilicon Hi655X series PMU/Codec IC"
461 depends on ARCH_HISI || COMPILE_TEST
467 Select this option to enable Hisilicon hi655x series pmic driver.
470 tristate "HTC PASIC3 LED/DS1WM chip support"
473 This core driver provides register access for the LED/DS1WM
474 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
475 HTC Magician devices, respectively. Actual functionality is
476 handled by the leds-pasic3 and ds1wm drivers.
479 bool "HTC I2C PLD chip support"
480 depends on I2C=y && GPIOLIB
482 If you say yes here you get support for the supposed CPLD
483 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
484 This device provides input and output GPIOs through an I2C
485 interface to one or more sub-chips.
487 config MFD_INTEL_QUARK_I2C_GPIO
488 tristate "Intel Quark MFD I2C GPIO"
491 depends on COMMON_CLK
494 This MFD provides support for I2C and GPIO that exist only
495 in a single PCI device. It splits the 2 IO devices to
496 their respective IO driver.
497 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
500 tristate "Intel ICH LPC"
504 The LPC bridge function of the Intel ICH provides support for
505 many functional units. This driver provides needed support for
506 other drivers to control these functions, currently GPIO and
510 tristate "Intel SCH LPC"
514 LPC bridge function of the Intel SCH provides support for
515 System Management Bus and General Purpose I/O.
517 config INTEL_SOC_PMIC
518 bool "Support for Crystal Cove PMIC"
519 depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
520 depends on X86 || COMPILE_TEST
521 depends on I2C_DESIGNWARE_PLATFORM=y
526 Select this option to enable support for Crystal Cove PMIC
527 on some Intel SoC systems. The PMIC provides ADC, GPIO,
528 thermal, charger and related power management functions
531 This option is a bool as it provides an ACPI OpRegion which must be
532 available before any devices using it are probed. This option also
533 causes the designware-i2c driver to be builtin for the same reason.
535 config INTEL_SOC_PMIC_BXTWC
536 tristate "Support for Intel Broxton Whiskey Cove PMIC"
537 depends on INTEL_PMC_IPC
541 Select this option to enable support for Whiskey Cove PMIC
542 on Intel Broxton systems. The PMIC provides ADC, GPIO,
543 thermal, charger and related power management functions
546 config INTEL_SOC_PMIC_CHTWC
547 bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
548 depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
549 depends on X86 || COMPILE_TEST
550 depends on I2C_DESIGNWARE_PLATFORM=y
555 Select this option to enable support for the Intel Cherry Trail
556 Whiskey Cove PMIC found on some Intel Cherry Trail systems.
558 This option is a bool as it provides an ACPI OpRegion which must be
559 available before any devices using it are probed. This option also
560 causes the designware-i2c driver to be builtin for the same reason.
562 config INTEL_SOC_PMIC_CHTDC_TI
563 tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
572 Select this option for supporting Dollar Cove (TI version) PMIC
573 device that is found on some Intel Cherry Trail systems.
575 config MFD_INTEL_LPSS
580 config MFD_INTEL_LPSS_ACPI
581 tristate "Intel Low Power Subsystem support in ACPI mode"
582 select MFD_INTEL_LPSS
583 depends on X86 && ACPI
585 This driver supports Intel Low Power Subsystem (LPSS) devices such as
586 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
589 config MFD_INTEL_LPSS_PCI
590 tristate "Intel Low Power Subsystem support in PCI mode"
591 select MFD_INTEL_LPSS
592 depends on X86 && PCI
594 This driver supports Intel Low Power Subsystem (LPSS) devices such as
595 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
598 config MFD_INTEL_MSIC
600 depends on INTEL_SCU_IPC
603 Select this option to enable access to Intel MSIC (Avatele
604 Passage) chip. This chip embeds audio, battery, GPIO, etc.
605 devices used in Intel Medfield platforms.
607 config MFD_IPAQ_MICRO
608 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
609 depends on SA1100_H3100 || SA1100_H3600
612 Select this to get support for the Microcontroller found in
613 the Compaq iPAQ handheld computers. This is an Atmel
614 AT90LS8535 microcontroller flashed with a special iPAQ
615 firmware using the custom protocol implemented in this driver.
617 config MFD_JANZ_CMODIO
618 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
622 This is the core driver for the Janz CMOD-IO PCI MODULbus
623 carrier board. This device is a PCI to MODULbus bridge which may
624 host many different types of MODULbus daughterboards, including
625 CAN and GPIO controllers.
627 config MFD_JZ4740_ADC
628 bool "Janz JZ4740 ADC core"
630 select GENERIC_IRQ_CHIP
631 depends on MACH_JZ4740
633 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
634 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
637 tristate "Kontron module PLD device"
640 This is the core driver for the PLD (Programmable Logic Device) found
641 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
642 device may provide functions like watchdog, GPIO, UART and I2C bus.
644 The following modules are supported:
651 * COMe-bPC2 (ETXexpress-PC)
652 * COMe-bSC# (ETXexpress-SC T#)
658 * COMe-cDC2 (microETXexpress-DC)
661 * COMe-cPC2 (microETXexpress-PC)
666 * COMe-mTT10 (nanoETXexpress-TT)
669 This driver can also be built as a module. If so, the module
670 will be called kempld-core.
673 tristate "Marvell 88PM800"
679 This supports for Marvell 88PM800 Power Management IC.
680 This includes the I2C driver and the core APIs _only_, you have to
681 select individual components like voltage regulators, RTC and
682 battery-charger under the corresponding menus.
685 tristate "Marvell 88PM805"
691 This supports for Marvell 88PM805 Power Management IC. This includes
692 the I2C driver and the core APIs _only_, you have to select individual
693 components like codec device, headset/Mic device under the
697 bool "Marvell 88PM8606/88PM8607"
702 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
703 This includes the I2C driver and the core APIs _only_, you have to
704 select individual components like voltage regulators, RTC and
705 battery-charger under the corresponding menus.
708 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
715 Say yes here to add support for Maxim Semiconductor MAX14577 and
716 MAX77836 Micro-USB ICs with battery charger.
717 This driver provides common support for accessing the device;
718 additional drivers must be enabled in order to use the functionality
722 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
724 depends on OF || COMPILE_TEST
730 Say yes here to add support for Maxim Semiconductor MAX77620 and
731 MAX20024 which are Power Management IC with General purpose pins,
732 RTC, regulators, clock generator, watchdog etc. This driver
733 provides common support for accessing the device; additional drivers
734 must be enabled in order to use the functionality of the device.
737 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
739 depends on OF || COMPILE_TEST
745 Say yes here to add support for Maxim Semiconductor MAX77686 and
746 MAX77802 which are Power Management IC with an RTC on chip.
747 This driver provides common support for accessing the device;
748 additional drivers must be enabled in order to use the functionality
752 tristate "Maxim Semiconductor MAX77693 PMIC Support"
758 Say yes here to add support for Maxim Semiconductor MAX77693.
759 This is a companion Power Management IC with Flash, Haptic, Charger,
760 and MUIC(Micro USB Interface Controller) controls on chip.
761 This driver provides common support for accessing the device;
762 additional drivers must be enabled in order to use the functionality
766 bool "Maxim Semiconductor MAX77843 PMIC Support"
772 Say yes here to add support for Maxim Semiconductor MAX77843.
773 This is companion Power Management IC with LEDs, Haptic, Charger,
774 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
775 This driver provides common support for accessing the device;
776 additional drivers must be enabled in order to use the functionality
780 tristate "Maxim Semiconductor MAX8907 PMIC Support"
786 Say yes here to add support for Maxim Semiconductor MAX8907. This is
787 a Power Management IC. This driver provides common support for
788 accessing the device; additional drivers must be enabled in order
789 to use the functionality of the device.
792 bool "Maxim Semiconductor MAX8925 PMIC Support"
796 Say yes here to add support for Maxim Semiconductor MAX8925. This is
797 a Power Management IC. This driver provides common support for
798 accessing the device, additional drivers must be enabled in order
799 to use the functionality of the device.
802 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
807 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
808 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
809 MUIC controls on chip.
810 This driver provides common support for accessing the device;
811 additional drivers must be enabled in order to use the functionality
815 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
820 Say yes here to add support for Maxim Semiconductor MAX8998 and
821 National Semiconductor LP3974. This is a Power Management IC.
822 This driver provides common support for accessing the device,
823 additional drivers must be enabled in order to use the functionality
827 tristate "MediaTek MT6397 PMIC Support"
831 Say yes here to add support for MediaTek MT6397 PMIC. This is
832 a Power Management IC. This driver provides common support for
833 accessing the device; additional drivers must be enabled in order
834 to use the functionality of the device.
837 tristate "MEN 14F021P00 Board Management Controller Support"
841 Say yes here to add support for the MEN 14F021P00 BMC
842 which is a Board Management Controller connected to the I2C bus.
843 The device supports multiple sub-devices like LED, HWMON and WDT.
844 This driver provides common support for accessing the devices;
845 additional drivers must be enabled in order to use the
846 functionality of the BMC device.
848 This driver can also be built as a module. If so the module
849 will be called menf21bmc.
852 bool "Motorola EZXPCAP Support"
853 depends on SPI_MASTER
855 This enables the PCAP ASIC present on EZX Phones. This is
856 needed for MMC, TouchScreen, Sound, USB, etc..
859 tristate "Support for Motorola CPCAP"
861 depends on OF || COMPILE_TEST
865 Say yes here if you want to include driver for CPCAP.
866 It is used on many Motorola phones and tablets as a PMIC.
867 At least Motorola Droid 4 is known to use CPCAP.
869 config MFD_VIPERBOARD
870 tristate "Nano River Technologies Viperboard"
875 Say yes here if you want support for Nano River Technologies
877 There are mfd cell drivers available for i2c master, adc and
878 both gpios found on the board. The spi part does not yet
880 You need to select the mfd cell drivers separately.
881 The drivers do not support all features the board exposes.
884 tristate "Nokia Retu and Tahvo multi-function device"
889 Retu and Tahvo are a multi-function devices found on Nokia
890 Internet Tablets (770, N800 and N810).
893 tristate "NXP PCF50633"
897 Say yes here if you have NXP PCF50633 chip on your board.
898 This core driver provides register access and IRQ handling
899 facilities, and registers devices for the various functions
900 so that function-specific drivers can bind to them.
903 tristate "NXP PCF50633 ADC"
904 depends on MFD_PCF50633
906 Say yes here if you want to include support for ADC in the
910 tristate "NXP PCF50633 GPIO"
911 depends on MFD_PCF50633
913 Say yes here if you want to include support GPIO for pins on
917 tristate "Philips UCB1400 Core driver"
921 This enables support for the Philips UCB1400 core functions.
922 The UCB1400 is an AC97 audio codec.
924 To compile this driver as a module, choose M here: the
925 module will be called ucb1400_core.
928 tristate "Qualcomm PM8xxx PMIC chips driver"
929 depends on (ARM || HEXAGON || COMPILE_TEST)
930 select IRQ_DOMAIN_HIERARCHY
934 If you say yes to this option, support will be included for the
935 built-in PM8xxx PMIC chips.
937 This is required if your board has a PM8xxx and uses its features,
938 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
940 Say M here if you want to include support for PM8xxx chips as a
941 module. This will build a module called "pm8xxx-core".
944 tristate "Qualcomm Resource Power Manager (RPM)"
945 depends on ARCH_QCOM && OF
947 If you say yes to this option, support will be included for the
948 Resource Power Manager system found in the Qualcomm 8660, 8960 and
951 This is required to access many regulators, clocks and bus
952 frequencies controlled by the RPM on these devices.
954 Say M here if you want to include support for the Qualcomm RPM as a
955 module. This will build a module called "qcom_rpm".
958 tristate "Qualcomm SPMI PMICs"
959 depends on ARCH_QCOM || COMPILE_TEST
964 This enables support for the Qualcomm SPMI PMICs.
965 These PMICs are currently used with the Snapdragon 800 series of
966 SoCs. Note, that this will only be useful paired with descriptions
967 of the independent functions as children nodes in the device tree.
969 Say M here if you want to include support for the SPMI PMIC
970 series as a module. The module will be called "qcom-spmi-pmic".
973 tristate "RDC R-321x southbridge"
977 Say yes here if you want to have support for the RDC R-321x SoC
978 southbridge which provides access to GPIOs and Watchdog using the
979 southbridge PCI device configuration space.
982 tristate "Richtek RT5033 Power Management IC"
988 This driver provides for the Richtek RT5033 Power Management IC,
989 which includes the I2C driver and the Core APIs. This driver provides
990 common support for accessing the device. The device supports multiple
991 sub-devices like charger, fuel gauge, flash LED, current source,
995 bool "Ricoh RC5T583 Power Management system device"
1000 Select this option to get support for the RICOH583 Power
1001 Management system device.
1002 This driver provides common support for accessing the device
1003 through i2c interface. The device supports multiple sub-devices
1004 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1005 Additional drivers must be enabled in order to use the
1006 different functionality of the device.
1009 tristate "Rockchip RK805/RK808/RK818 Power Management Chip"
1010 depends on I2C && OF
1015 If you say yes here you get support for the RK805, RK808 and RK818
1016 Power Management chips.
1017 This driver provides common support for accessing the device
1018 through I2C interface. The device supports multiple sub-devices
1019 including interrupts, RTC, LDO & DCDC regulators, and onkey.
1022 tristate "Ricoh RN5T567/618 PMIC"
1028 Say yes here to add support for the Ricoh RN5T567,
1029 RN5T618, RC5T619 PMIC.
1030 This driver provides common support for accessing the device,
1031 additional drivers must be enabled in order to use the
1032 functionality of the device.
1035 tristate "SAMSUNG Electronics PMIC Series Support"
1041 Support for the Samsung Electronics PMIC devices coming
1042 usually along with Samsung Exynos SoC chipset.
1043 This driver provides common support for accessing the device,
1044 additional drivers must be enabled in order to use the functionality
1047 To compile this driver as a module, choose M here: the
1048 module will be called sec-core.
1049 Have in mind that important core drivers (like regulators) depend
1050 on this driver so building this as a module might require proper
1051 initial ramdisk or might not boot up as well in certain scenarios.
1053 config MFD_SI476X_CORE
1054 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1059 This is the core driver for the SI476x series of AM/FM
1060 radio. This MFD driver connects the radio-si476x V4L2 module
1061 and the si476x audio codec.
1063 To compile this driver as a module, choose M here: the
1064 module will be called si476x-core.
1067 tristate "Silicon Motion SM501"
1069 This is the core driver for the Silicon Motion SM501 multimedia
1070 companion chip. This device is a multifunction device which may
1071 provide numerous interfaces including USB host controller, USB gadget,
1072 asynchronous serial ports, audio functions, and a dual display video
1073 interface. The device may be connected by PCI or local bus with
1074 varying functions enabled.
1076 config MFD_SM501_GPIO
1077 bool "Export GPIO via GPIO layer"
1078 depends on MFD_SM501 && GPIOLIB
1080 This option uses the gpio library layer to export the 64 GPIO
1081 lines on the SM501. The platform data is used to supply the
1082 base number for the first GPIO line to register.
1085 tristate "Skyworks Solutions SKY81452"
1090 This is the core driver for the Skyworks SKY81452 backlight and
1091 voltage regulator device.
1093 This driver can also be built as a module. If so, the module
1094 will be called sky81452.
1097 bool "SMSC ECE1099 series chips"
1102 If you say yes here you get support for the
1103 ece1099 chips from SMSC.
1105 To compile this driver as a module, choose M here: the
1106 module will be called smsc.
1108 config MFD_SC27XX_PMIC
1109 tristate "Spreadtrum SC27xx PMICs"
1110 depends on ARCH_SPRD || COMPILE_TEST
1111 depends on SPI_MASTER
1116 This enables support for the Spreadtrum SC27xx PMICs with SPI
1117 interface. The SC27xx series PMICs integrate power management,
1118 audio codec, battery management and user interface support
1119 function (such as RTC, Typec, indicator and so on) in a single chip.
1121 This driver provides common support for accessing the SC27xx PMICs,
1122 and it also adds the irq_chip parts for handling the PMIC chip events.
1125 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1126 default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1128 Say yes here if you have the ABX500 Mixed Signal IC family
1129 chips. This core driver expose register access functions.
1130 Functionality specific drivers using these functions can
1131 remain unchanged when IC changes. Binding of the functions to
1132 actual register access is done by the IC core driver.
1135 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1136 depends on I2C=y && ABX500_CORE
1138 default y if ARCH_U300
1140 Select this to enable the AB3100 Mixed Signal IC core
1141 functionality. This connects to a AB3100 on the I2C bus
1142 and expose a number of symbols needed for dependent devices
1143 to read and write registers and subscribe to events from
1144 this multi-functional IC. This is needed to use other features
1145 of the AB3100 such as battery-backed RTC, charging control,
1146 LEDs, vibrator, system power and temperature, power management
1150 tristate "ST-Ericsson AB3100 OTP functions"
1151 depends on AB3100_CORE
1152 default y if AB3100_CORE
1154 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1155 programmable memory) support. This exposes a sysfs file to read
1159 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1160 depends on ABX500_CORE && MFD_DB8500_PRCMU
1165 Select this option to enable access to AB8500 power management
1166 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1167 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1168 the irq_chip parts for handling the Mixed Signal chip events.
1169 This chip embeds various other multimedia funtionalities as well.
1172 bool "Enable debug info via debugfs"
1173 depends on AB8500_GPADC && DEBUG_FS
1174 default y if DEBUG_FS
1176 Select this option if you want debug information using the debug
1177 filesystem, debugfs.
1180 bool "ST-Ericsson AB8500 GPADC driver"
1181 depends on AB8500_CORE && REGULATOR_AB8500
1184 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1186 config MFD_DB8500_PRCMU
1187 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1188 depends on UX500_SOC_DB8500
1191 Select this option to enable support for the DB8500 Power Reset
1192 and Control Management Unit. This is basically an autonomous
1193 system controller running an XP70 microprocessor, which is accessed
1194 through a register map.
1197 bool "STMicroelectronics STMPE"
1198 depends on (I2C=y || SPI_MASTER=y)
1202 Support for the STMPE family of I/O Expanders from
1205 Currently supported devices are:
1207 STMPE811: GPIO, Touchscreen, ADC
1208 STMPE1601: GPIO, Keypad
1209 STMPE1801: GPIO, Keypad
1210 STMPE2401: GPIO, Keypad
1211 STMPE2403: GPIO, Keypad
1213 This driver provides common support for accessing the device,
1214 additional drivers must be enabled in order to use the functionality
1215 of the device. Currently available sub drivers are:
1218 Keypad: stmpe-keypad
1219 Touchscreen: stmpe-ts
1222 menu "STMicroelectronics STMPE Interface Drivers"
1223 depends on MFD_STMPE
1226 bool "STMicroelectronics STMPE I2C Interface"
1230 This is used to enable I2C interface of STMPE
1233 bool "STMicroelectronics STMPE SPI Interface"
1234 depends on SPI_MASTER
1236 This is used to enable SPI interface of STMPE
1240 bool "STMicroelectronics STA2X11"
1245 config MFD_SUN6I_PRCM
1246 bool "Allwinner A31 PRCM controller"
1247 depends on ARCH_SUNXI
1250 Support for the PRCM (Power/Reset/Clock Management) unit available
1254 bool "System Controller Register R/W Based on Regmap"
1257 Select this option to enable accessing system control registers
1260 config MFD_DAVINCI_VOICECODEC
1265 config MFD_TI_AM335X_TSCADC
1266 tristate "TI ADC / Touch Screen chip support"
1271 If you say yes here you get support for Texas Instruments series
1272 of Touch Screen /ADC chips.
1273 To compile this driver as a module, choose M here: the
1274 module will be called ti_am335x_tscadc.
1276 config MFD_DM355EVM_MSP
1277 bool "TI DaVinci DM355 EVM microcontroller"
1278 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1280 This driver supports the MSP430 microcontroller used on these
1281 boards. MSP430 firmware manages resets and power sequencing,
1282 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1285 tristate "TI/National Semiconductor LP3943 MFD Driver"
1290 Support for the TI/National Semiconductor LP3943.
1291 This driver consists of GPIO and PWM drivers.
1292 With these functionalities, it can be used for LED string control or
1293 general usage such like a GPIO controller and a PWM controller.
1296 bool "TI LP8788 Power Management Unit Driver"
1302 TI LP8788 PMU supports regulators, battery charger, RTC,
1303 ADC, backlight driver and current sinks.
1306 tristate "TI Lighting Management Unit driver"
1311 Say yes here to enable support for TI LMU chips.
1313 TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
1314 It consists of backlight, LED and regulator driver.
1315 It provides consistent device controls for lighting functions.
1317 config MFD_OMAP_USB_HOST
1318 bool "TI OMAP USBHS core and TLL driver"
1319 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1322 This is the core driver for the OAMP EHCI and OHCI drivers.
1323 This MFD driver does the required setup functionalities for
1324 OMAP USB Host drivers.
1327 bool "TI Palmas series chips"
1333 If you say yes here you get support for the Palmas
1334 series of PMIC chips from Texas Instruments.
1337 tristate "TI TPS61050/61052 Boost Converters"
1342 select REGULATOR_FIXED_VOLTAGE
1344 This option enables a driver for the TP61050/TPS61052
1345 high-power "white LED driver". This boost converter is
1346 sometimes used for other things than white LEDs, and
1347 also contains a GPIO pin.
1350 tristate "TI TPS6501x Power Management chips"
1351 depends on I2C && GPIOLIB
1352 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1354 If you say yes here you get support for the TPS6501x series of
1355 Power Management chips. These include voltage regulators,
1356 lithium ion/polymer battery charging, and other features that
1357 are often used in portable devices like cell phones and cameras.
1359 This driver can also be built as a module. If so, the module
1360 will be called tps65010.
1363 tristate "TI TPS6507x Power Management / Touch Screen chips"
1367 If you say yes here you get support for the TPS6507x series of
1368 Power Management / Touch Screen chips. These include voltage
1369 regulators, lithium ion/polymer battery charging, touch screen
1370 and other features that are often used in portable devices.
1371 This driver can also be built as a module. If so, the module
1372 will be called tps6507x.
1375 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1382 If you say yes here you get support for the TPS65086 series of
1383 Power Management chips.
1384 This driver provides common support for accessing the device,
1385 additional drivers must be enabled in order to use the
1386 functionality of the device.
1388 config TPS65911_COMPARATOR
1392 bool "TI TPS65090 Power Management chips"
1398 If you say yes here you get support for the TPS65090 series of
1399 Power Management chips.
1400 This driver provides common support for accessing the device,
1401 additional drivers must be enabled in order to use the
1402 functionality of the device.
1405 tristate "TI TPS65217 Power Management / White LED chips"
1406 depends on I2C && OF
1411 If you say yes here you get support for the TPS65217 series of
1412 Power Management / White LED chips.
1413 These include voltage regulators, lithium ion/polymer battery
1414 charger, wled and other features that are often used in portable
1417 This driver can also be built as a module. If so, the module
1418 will be called tps65217.
1421 bool "TI TPS68470 Power Management / LED chips"
1422 depends on ACPI && PCI && I2C=y
1423 depends on I2C_DESIGNWARE_PLATFORM=y
1427 If you say yes here you get support for the TPS68470 series of
1428 Power Management / LED chips.
1430 These include voltage regulators, LEDs and other features
1431 that are often used in portable devices.
1433 This option is a bool as it provides an ACPI operation
1434 region, which must be available before any of the devices
1435 using this are probed. This option also configures the
1436 designware-i2c driver to be built-in, for the same reason.
1438 config MFD_TI_LP873X
1439 tristate "TI LP873X Power Management IC"
1444 If you say yes here then you get support for the LP873X series of
1445 Power Management Integrated Circuits (PMIC).
1446 These include voltage regulators, thermal protection, configurable
1447 General Purpose Outputs (GPO) that are used in portable devices.
1449 This driver can also be built as a module. If so, the module
1450 will be called lp873x.
1452 config MFD_TI_LP87565
1453 tristate "TI LP87565 Power Management IC"
1454 depends on I2C && OF
1458 If you say yes here then you get support for the LP87565 series of
1459 Power Management Integrated Circuits (PMIC).
1460 These include voltage regulators, thermal protection, configurable
1461 General Purpose Outputs (GPO) that are used in portable devices.
1463 This driver can also be built as a module. If so, the module
1464 will be called lp87565.
1467 tristate "TI TPS65218 Power Management chips"
1468 depends on I2C && OF
1473 If you say yes here you get support for the TPS65218 series of
1474 Power Management chips.
1475 These include voltage regulators, gpio and other features
1476 that are often used in portable devices.
1478 This driver can also be built as a module. If so, the module
1479 will be called tps65218.
1482 bool "TI TPS6586x Power Management chips"
1487 If you say yes here you get support for the TPS6586X series of
1488 Power Management chips.
1489 This driver provides common support for accessing the device,
1490 additional drivers must be enabled in order to use the
1491 functionality of the device.
1493 This driver can also be built as a module. If so, the module
1494 will be called tps6586x.
1497 bool "TI TPS65910 Power Management chip"
1499 depends on GPIOLIB || COMPILE_TEST
1505 if you say yes here you get support for the TPS65910 series of
1506 Power Management chips.
1514 config MFD_TPS65912_I2C
1515 tristate "TI TPS65912 Power Management chip with I2C"
1520 If you say yes here you get support for the TPS65912 series of
1521 PM chips with I2C interface.
1523 config MFD_TPS65912_SPI
1524 tristate "TI TPS65912 Power Management chip with SPI"
1527 depends on SPI_MASTER
1529 If you say yes here you get support for the TPS65912 series of
1530 PM chips with SPI interface.
1533 bool "TI TPS80031/TPS80032 Power Management chips"
1539 If you say yes here you get support for the Texas Instruments
1540 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1541 Path and Battery Charger. The device provides five configurable
1542 step-down converters, 11 general purpose LDOs, USB OTG Module,
1543 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1544 Power Path from USB, 32K clock generator.
1547 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1552 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1553 This core driver provides register access and IRQ handling
1554 facilities, and registers devices for the various functions
1555 so that function-specific drivers can bind to them.
1557 These multi-function chips are found on many OMAP2 and OMAP3
1558 boards, providing power management, RTC, GPIO, keypad, a
1559 high speed USB OTG transceiver, an audio codec (on most
1560 versions) and many other features.
1562 config TWL4030_POWER
1563 bool "TI TWL4030 power resources"
1564 depends on TWL4030_CORE && ARM
1566 Say yes here if you want to use the power resources on the
1567 TWL4030 family chips. Most of these resources are regulators,
1568 which have a separate driver; some are control signals, such
1569 as clock request handshaking.
1571 This driver uses board-specific data to initialize the resources
1572 and load scripts controlling which resources are switched off/on
1573 or reset when a sleep, wakeup or warm reset event occurs.
1575 config MFD_TWL4030_AUDIO
1576 bool "TI TWL4030 Audio"
1577 depends on TWL4030_CORE
1582 bool "TI TWL6040 audio codec"
1589 Say yes here if you want support for Texas Instruments TWL6040 audio
1591 This driver provides common support for accessing the device,
1592 additional drivers must be enabled in order to use the
1593 functionality of the device (audio, vibra).
1596 bool "TI TWL92330/Menelaus PM chip"
1597 depends on I2C=y && ARCH_OMAP2
1599 If you say yes here you get support for the Texas Instruments
1600 TWL92330/Menelaus Power Management chip. This include voltage
1601 regulators, Dual slot memory card transceivers, real-time clock
1602 and other features that are often used in portable devices like
1603 cell phones and PDAs.
1605 config MFD_WL1273_CORE
1606 tristate "TI WL1273 FM radio"
1611 This is the core driver for the TI WL1273 FM radio. This MFD
1612 driver connects the radio-wl1273 V4L2 module and the wl1273
1616 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1621 Say yes here to enable support for National Semiconductor / TI
1622 LM3533 Lighting Power chips.
1624 This driver provides common support for accessing the device;
1625 additional drivers must be enabled in order to use the LED,
1626 backlight or ambient-light-sensor functionality of the device.
1628 config MFD_TIMBERDALE
1629 tristate "Timberdale FPGA"
1631 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1633 This is the core driver for the timberdale FPGA. This device is a
1634 multifunction device which exposes numerous platform devices.
1636 The timberdale FPGA can be found on the Intel Atom development board
1637 for in-vehicle infontainment, called Russellville.
1640 bool "Toshiba TC35892 and variants"
1645 Support for the Toshiba TC35892 and variants I/O Expander.
1647 This driver provides common support for accessing the device,
1648 additional drivers must be enabled in order to use the
1649 functionality of the device.
1656 bool "Toshiba T7L66XB"
1657 depends on ARM && HAVE_CLK
1661 Support for Toshiba Mobile IO Controller T7L66XB
1664 bool "Toshiba TC6387XB"
1665 depends on ARM && HAVE_CLK
1669 Support for Toshiba Mobile IO Controller TC6387XB
1672 bool "Toshiba TC6393XB"
1673 depends on ARM && HAVE_CLK
1678 Support for Toshiba Mobile IO Controller TC6393XB
1681 tristate "TQ-Systems IO controller TQMX86"
1684 Say yes here to enable support for various functions of the
1685 TQ-Systems IO controller and watchdog device, found on their
1686 ComExpress CPU modules.
1689 tristate "VIA VX855/VX875 integrated south bridge"
1693 Say yes here to enable support for various functions of the
1694 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1695 and/or vx855_gpio drivers for this to do anything useful.
1697 config MFD_LOCHNAGAR
1698 bool "Cirrus Logic Lochnagar Audio Development Board"
1701 depends on I2C=y && OF
1703 Support for Cirrus Logic Lochnagar audio development board.
1711 config MFD_ARIZONA_I2C
1712 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1717 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1718 audio SoC core functionality controlled via I2C.
1720 config MFD_ARIZONA_SPI
1721 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1724 depends on SPI_MASTER
1726 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1727 audio SoC core functionality controlled via SPI.
1730 bool "Cirrus Logic CS47L24 and WM1831"
1731 depends on MFD_ARIZONA
1733 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1736 bool "Wolfson Microelectronics WM5102"
1737 depends on MFD_ARIZONA
1739 Support for Wolfson Microelectronics WM5102 low power audio SoC
1742 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1743 depends on MFD_ARIZONA
1745 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1749 bool "Wolfson Microelectronics WM8997"
1750 depends on MFD_ARIZONA
1752 Support for Wolfson Microelectronics WM8997 low power audio SoC
1755 bool "Wolfson Microelectronics WM8998"
1756 depends on MFD_ARIZONA
1758 Support for Wolfson Microelectronics WM8998 low power audio SoC
1761 bool "Wolfson Microelectronics WM8400"
1766 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1767 CODEC. This driver provides common support for accessing
1768 the device, additional drivers must be enabled in order to use
1769 the functionality of the device.
1774 config MFD_WM831X_I2C
1775 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1782 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1783 when controlled using I2C. This driver provides common support
1784 for accessing the device, additional drivers must be enabled in
1785 order to use the functionality of the device.
1787 config MFD_WM831X_SPI
1788 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1793 depends on SPI_MASTER
1795 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1796 when controlled using SPI. This driver provides common support
1797 for accessing the device, additional drivers must be enabled in
1798 order to use the functionality of the device.
1803 config MFD_WM8350_I2C
1804 bool "Wolfson Microelectronics WM8350 with I2C"
1809 The WM8350 is an integrated audio and power management
1810 subsystem with watchdog and RTC functionality for embedded
1811 systems. This option enables core support for the WM8350 with
1812 I2C as the control interface. Additional options must be
1813 selected to enable support for the functionality of the chip.
1816 tristate "Wolfson Microelectronics WM8994"
1822 The WM8994 is a highly integrated hi-fi CODEC designed for
1823 smartphone applications. As well as audio functionality it
1824 has on board GPIO and regulator functionality which is
1825 supported via the relevant subsystems. This driver provides
1826 core support for the WM8994, in order to use the actual
1827 functionaltiy of the device other drivers must be enabled.
1830 tristate "Wolfson Microelectronics WM97xx"
1833 select AC97_BUS_COMPAT
1834 depends on AC97_BUS_NEW
1836 The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1837 designed for smartphone applications. As well as audio functionality
1838 it has on board GPIO and a touchscreen functionality which is
1839 supported via the relevant subsystems. This driver provides core
1840 support for the WM97xx, in order to use the actual functionaltiy of
1841 the device other drivers must be enabled.
1844 tristate "Support for ST Microelectronics STw481x"
1845 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1849 Select this option to enable the STw481x chip driver used
1850 in various ST Microelectronics and ST-Ericsson embedded
1853 config MFD_ROHM_BD718XX
1854 tristate "ROHM BD71837 Power Management IC"
1861 Select this option to get support for the ROHM BD71837
1862 Power Management ICs. BD71837 is designed to power processors like
1863 NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
1864 and emergency shut down as well as 32,768KHz clock output.
1866 config MFD_STM32_LPTIMER
1867 tristate "Support for STM32 Low-Power Timer"
1868 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1873 Select this option to enable STM32 Low-Power Timer driver
1874 used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1875 resources are also dealt with here.
1877 To compile this driver as a module, choose M here: the
1878 module will be called stm32-lptimer.
1880 config MFD_STM32_TIMERS
1881 tristate "Support for STM32 Timers"
1882 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1887 Select this option to enable STM32 timers driver used
1888 for PWM and IIO Timer. This driver allow to share the
1889 registers between the others drivers.
1892 tristate "Support for STPMIC1 PMIC"
1893 depends on (I2C=y && OF)
1898 Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on
1899 key, watchdog and regulator functionalities which are supported via
1900 the relevant subsystems. This driver provides core support for the
1901 STPMIC1. In order to use the actual functionaltiy of the device other
1902 drivers must be enabled.
1904 To compile this driver as a module, choose M here: the
1905 module will be called stpmic1.
1907 menu "Multimedia Capabilities Port drivers"
1908 depends on ARCH_SA1100
1915 tristate "Support SA11x0 MCP interface"
1916 depends on ARCH_SA1100
1921 tristate "Support for UCB1200 / UCB1300"
1922 depends on MCP_SA11X0
1925 config MCP_UCB1200_TS
1926 tristate "Touchscreen interface support"
1927 depends on MCP_UCB1200 && INPUT
1931 config MFD_VEXPRESS_SYSREG
1932 bool "Versatile Express System Registers"
1933 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1936 select GPIO_GENERIC_PLATFORM
1940 System Registers are the platform configuration block
1941 on the ARM Ltd. Versatile Express board.
1944 tristate "RAVE SP MCU core driver"
1945 depends on SERIAL_DEV_BUS
1948 Select this to get support for the Supervisory Processor
1949 device found on several devices in RAVE line of hardware.