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
220 This driver adds support to talk with the ChromeOS EC from userspace.
222 If you have a supported Chromebook, choose Y or M here.
223 The module will be called cros_ec_dev.
226 tristate "Cirrus Logic Madera codecs"
232 select PINCTRL_MADERA
234 Support for the Cirrus Logic Madera platform audio codecs
236 config MFD_MADERA_I2C
237 tristate "Cirrus Logic Madera codecs with I2C"
238 depends on MFD_MADERA
242 Support for the Cirrus Logic Madera platform audio SoC
243 core functionality controlled via I2C.
245 config MFD_MADERA_SPI
246 tristate "Cirrus Logic Madera codecs with SPI"
247 depends on MFD_MADERA
248 depends on SPI_MASTER
251 Support for the Cirrus Logic Madera platform audio SoC
252 core functionality controlled via SPI.
255 bool "Cirrus Logic CS47L35"
256 select PINCTRL_CS47L35
257 depends on MFD_MADERA
259 Support for Cirrus Logic CS47L35 Smart Codec
262 bool "Cirrus Logic CS47L85"
263 select PINCTRL_CS47L85
264 depends on MFD_MADERA
266 Support for Cirrus Logic CS47L85 Smart Codec
269 bool "Cirrus Logic CS47L90/91"
270 select PINCTRL_CS47L90
271 depends on MFD_MADERA
273 Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
277 depends on GPIOLIB && ARM
280 This driver supports the ASIC3 multifunction chip found on many
281 PDAs (mainly iPAQ and HTC based ones)
284 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
287 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
288 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
289 usually found on PXA processors-based platforms. This includes
290 the I2C driver and the core APIs _only_, you have to select
291 individual components like LCD backlight, voltage regulators,
292 LEDs and battery-charger under the corresponding menus.
298 config MFD_DA9052_SPI
299 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
303 depends on SPI_MASTER=y
305 Support for the Dialog Semiconductor DA9052 PMIC
306 when controlled using SPI. This driver provides common support
307 for accessing the device, additional drivers must be enabled in
308 order to use the functionality of the device.
310 config MFD_DA9052_I2C
311 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
317 Support for the Dialog Semiconductor DA9052 PMIC
318 when controlled using I2C. This driver provides common support
319 for accessing the device, additional drivers must be enabled in
320 order to use the functionality of the device.
323 bool "Dialog Semiconductor DA9055 PMIC Support"
329 Say yes here for support of Dialog Semiconductor DA9055. This is
330 a Power Management IC. This driver provides common support for
331 accessing the device as well as the I2C interface to the chip itself.
332 Additional drivers must be enabled in order to use the functionality
335 This driver can be built as a module. If built as a module it will be
339 tristate "Dialog Semiconductor DA9062/61 PMIC Support"
345 Say yes here for support for the Dialog Semiconductor DA9061 and
347 This includes the I2C driver and core APIs.
348 Additional drivers must be enabled in order to use the functionality
352 tristate "Dialog Semiconductor DA9063 PMIC Support"
358 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
359 This includes the I2C driver and core APIs.
360 Additional drivers must be enabled in order to use the functionality
364 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
370 This adds support for the DA9150 integrated charger and fuel-gauge
371 chip. This driver provides common support for accessing the device.
372 Additional drivers must be enabled in order to use the specific
373 features of the device.
376 tristate "Diolan DLN2 support"
380 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
381 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
382 etc. must be enabled in order to use the functionality of
385 config MFD_EXYNOS_LPASS
386 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
387 depends on ARCH_EXYNOS || COMPILE_TEST
391 Select this option to enable support for Samsung Exynos Low Power
396 depends on (SPI_MASTER || I2C)
400 Enable support for the Freescale MC13783 and MC13892 PMICs.
401 This driver provides common support for accessing the device,
402 additional drivers must be enabled in order to use the
403 functionality of the device.
405 config MFD_MC13XXX_SPI
406 tristate "Freescale MC13783 and MC13892 SPI interface"
407 depends on SPI_MASTER
411 Select this if your MC13xxx is connected via an SPI bus.
413 config MFD_MC13XXX_I2C
414 tristate "Freescale MC13892 I2C interface"
419 Select this if your MC13xxx is connected via an I2C bus.
422 tristate "Freescale i.MX23/i.MX28 LRADC"
423 depends on ARCH_MXS || COMPILE_TEST
427 Say yes here to build support for the Low Resolution
428 Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
429 processors. This driver provides common support for accessing the
430 device, additional drivers must be enabled in order to use the
431 functionality of the device:
432 mxs-lradc-adc for ADC readings
433 mxs-lradc-ts for touchscreen support
435 This driver can also be built as a module. If so, the module will be
438 config MFD_MX25_TSADC
439 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
441 depends on (SOC_IMX25 && OF) || COMPILE_TEST
443 Enable support for the integrated Touchscreen and ADC unit of the
444 i.MX25 processors. They consist of a conversion queue for general
445 purpose ADC and a queue for Touchscreens.
447 config MFD_HI6421_PMIC
448 tristate "HiSilicon Hi6421 PMU/Codec IC"
453 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
454 functions, such as regulators, RTC, codec, Coulomb counter, etc.
455 This driver includes core APIs _only_. You have to select
456 individul components like voltage regulators under corresponding
457 menus in order to enable them.
458 We communicate with the Hi6421 via memory-mapped I/O.
460 config MFD_HI655X_PMIC
461 tristate "HiSilicon Hi655X series PMU/Codec IC"
462 depends on ARCH_HISI || COMPILE_TEST
468 Select this option to enable Hisilicon hi655x series pmic driver.
471 tristate "HTC PASIC3 LED/DS1WM chip support"
474 This core driver provides register access for the LED/DS1WM
475 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
476 HTC Magician devices, respectively. Actual functionality is
477 handled by the leds-pasic3 and ds1wm drivers.
480 bool "HTC I2C PLD chip support"
481 depends on I2C=y && GPIOLIB
483 If you say yes here you get support for the supposed CPLD
484 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
485 This device provides input and output GPIOs through an I2C
486 interface to one or more sub-chips.
488 config MFD_INTEL_QUARK_I2C_GPIO
489 tristate "Intel Quark MFD I2C GPIO"
492 depends on COMMON_CLK
495 This MFD provides support for I2C and GPIO that exist only
496 in a single PCI device. It splits the 2 IO devices to
497 their respective IO driver.
498 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
501 tristate "Intel ICH LPC"
505 The LPC bridge function of the Intel ICH provides support for
506 many functional units. This driver provides needed support for
507 other drivers to control these functions, currently GPIO and
511 tristate "Intel SCH LPC"
515 LPC bridge function of the Intel SCH provides support for
516 System Management Bus and General Purpose I/O.
518 config INTEL_SOC_PMIC
519 bool "Support for Crystal Cove PMIC"
520 depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
521 depends on X86 || COMPILE_TEST
525 select I2C_DESIGNWARE_PLATFORM
527 Select this option to enable support for Crystal Cove PMIC
528 on some Intel SoC systems. The PMIC provides ADC, GPIO,
529 thermal, charger and related power management functions
532 This option is a bool as it provides an ACPI OpRegion which must be
533 available before any devices using it are probed. This option also
534 causes the designware-i2c driver to be builtin for the same reason.
536 config INTEL_SOC_PMIC_BXTWC
537 tristate "Support for Intel Broxton Whiskey Cove PMIC"
538 depends on INTEL_PMC_IPC
542 Select this option to enable support for Whiskey Cove PMIC
543 on Intel Broxton systems. The PMIC provides ADC, GPIO,
544 thermal, charger and related power management functions
547 config INTEL_SOC_PMIC_CHTWC
548 bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
549 depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
550 depends on X86 || COMPILE_TEST
554 select I2C_DESIGNWARE_PLATFORM
556 Select this option to enable support for the Intel Cherry Trail
557 Whiskey Cove PMIC found on some Intel Cherry Trail systems.
559 This option is a bool as it provides an ACPI OpRegion which must be
560 available before any devices using it are probed. This option also
561 causes the designware-i2c driver to be builtin for the same reason.
563 config INTEL_SOC_PMIC_CHTDC_TI
564 tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
573 Select this option for supporting Dollar Cove (TI version) PMIC
574 device that is found on some Intel Cherry Trail systems.
576 config MFD_INTEL_LPSS
581 config MFD_INTEL_LPSS_ACPI
582 tristate "Intel Low Power Subsystem support in ACPI mode"
583 select MFD_INTEL_LPSS
584 depends on X86 && ACPI
586 This driver supports Intel Low Power Subsystem (LPSS) devices such as
587 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
590 config MFD_INTEL_LPSS_PCI
591 tristate "Intel Low Power Subsystem support in PCI mode"
592 select MFD_INTEL_LPSS
593 depends on X86 && PCI
595 This driver supports Intel Low Power Subsystem (LPSS) devices such as
596 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
599 config MFD_INTEL_MSIC
601 depends on INTEL_SCU_IPC
604 Select this option to enable access to Intel MSIC (Avatele
605 Passage) chip. This chip embeds audio, battery, GPIO, etc.
606 devices used in Intel Medfield platforms.
608 config MFD_IPAQ_MICRO
609 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
610 depends on SA1100_H3100 || SA1100_H3600
613 Select this to get support for the Microcontroller found in
614 the Compaq iPAQ handheld computers. This is an Atmel
615 AT90LS8535 microcontroller flashed with a special iPAQ
616 firmware using the custom protocol implemented in this driver.
618 config MFD_JANZ_CMODIO
619 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
623 This is the core driver for the Janz CMOD-IO PCI MODULbus
624 carrier board. This device is a PCI to MODULbus bridge which may
625 host many different types of MODULbus daughterboards, including
626 CAN and GPIO controllers.
628 config MFD_JZ4740_ADC
629 bool "Janz JZ4740 ADC core"
631 select GENERIC_IRQ_CHIP
632 depends on MACH_JZ4740
634 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
635 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
638 tristate "Kontron module PLD device"
641 This is the core driver for the PLD (Programmable Logic Device) found
642 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
643 device may provide functions like watchdog, GPIO, UART and I2C bus.
645 The following modules are supported:
652 * COMe-bPC2 (ETXexpress-PC)
653 * COMe-bSC# (ETXexpress-SC T#)
659 * COMe-cDC2 (microETXexpress-DC)
662 * COMe-cPC2 (microETXexpress-PC)
667 * COMe-mTT10 (nanoETXexpress-TT)
670 This driver can also be built as a module. If so, the module
671 will be called kempld-core.
674 tristate "Marvell 88PM800"
680 This supports for Marvell 88PM800 Power Management IC.
681 This includes the I2C driver and the core APIs _only_, you have to
682 select individual components like voltage regulators, RTC and
683 battery-charger under the corresponding menus.
686 tristate "Marvell 88PM805"
692 This supports for Marvell 88PM805 Power Management IC. This includes
693 the I2C driver and the core APIs _only_, you have to select individual
694 components like codec device, headset/Mic device under the
698 bool "Marvell 88PM8606/88PM8607"
703 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
704 This includes the I2C driver and the core APIs _only_, you have to
705 select individual components like voltage regulators, RTC and
706 battery-charger under the corresponding menus.
709 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
716 Say yes here to add support for Maxim Semiconductor MAX14577 and
717 MAX77836 Micro-USB ICs with battery charger.
718 This driver provides common support for accessing the device;
719 additional drivers must be enabled in order to use the functionality
723 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
725 depends on OF || COMPILE_TEST
731 Say yes here to add support for Maxim Semiconductor MAX77620 and
732 MAX20024 which are Power Management IC with General purpose pins,
733 RTC, regulators, clock generator, watchdog etc. This driver
734 provides common support for accessing the device; additional drivers
735 must be enabled in order to use the functionality of the device.
738 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
740 depends on OF || COMPILE_TEST
746 Say yes here to add support for Maxim Semiconductor MAX77686 and
747 MAX77802 which are Power Management IC with an RTC on chip.
748 This driver provides common support for accessing the device;
749 additional drivers must be enabled in order to use the functionality
753 tristate "Maxim Semiconductor MAX77693 PMIC Support"
759 Say yes here to add support for Maxim Semiconductor MAX77693.
760 This is a companion Power Management IC with Flash, Haptic, Charger,
761 and MUIC(Micro USB Interface Controller) controls on chip.
762 This driver provides common support for accessing the device;
763 additional drivers must be enabled in order to use the functionality
767 bool "Maxim Semiconductor MAX77843 PMIC Support"
773 Say yes here to add support for Maxim Semiconductor MAX77843.
774 This is companion Power Management IC with LEDs, Haptic, Charger,
775 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
776 This driver provides common support for accessing the device;
777 additional drivers must be enabled in order to use the functionality
781 tristate "Maxim Semiconductor MAX8907 PMIC Support"
787 Say yes here to add support for Maxim Semiconductor MAX8907. This is
788 a Power Management IC. This driver provides common support for
789 accessing the device; additional drivers must be enabled in order
790 to use the functionality of the device.
793 bool "Maxim Semiconductor MAX8925 PMIC Support"
797 Say yes here to add support for Maxim Semiconductor MAX8925. This is
798 a Power Management IC. This driver provides common support for
799 accessing the device, additional drivers must be enabled in order
800 to use the functionality of the device.
803 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
808 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
809 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
810 MUIC controls on chip.
811 This driver provides common support for accessing the device;
812 additional drivers must be enabled in order to use the functionality
816 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
821 Say yes here to add support for Maxim Semiconductor MAX8998 and
822 National Semiconductor LP3974. This is a Power Management IC.
823 This driver provides common support for accessing the device,
824 additional drivers must be enabled in order to use the functionality
828 tristate "MediaTek MT6397 PMIC Support"
832 Say yes here to add support for MediaTek MT6397 PMIC. This is
833 a Power Management IC. This driver provides common support for
834 accessing the device; additional drivers must be enabled in order
835 to use the functionality of the device.
838 tristate "MEN 14F021P00 Board Management Controller Support"
842 Say yes here to add support for the MEN 14F021P00 BMC
843 which is a Board Management Controller connected to the I2C bus.
844 The device supports multiple sub-devices like LED, HWMON and WDT.
845 This driver provides common support for accessing the devices;
846 additional drivers must be enabled in order to use the
847 functionality of the BMC device.
849 This driver can also be built as a module. If so the module
850 will be called menf21bmc.
853 bool "Motorola EZXPCAP Support"
854 depends on SPI_MASTER
856 This enables the PCAP ASIC present on EZX Phones. This is
857 needed for MMC, TouchScreen, Sound, USB, etc..
860 tristate "Support for Motorola CPCAP"
862 depends on OF || COMPILE_TEST
866 Say yes here if you want to include driver for CPCAP.
867 It is used on many Motorola phones and tablets as a PMIC.
868 At least Motorola Droid 4 is known to use CPCAP.
870 config MFD_VIPERBOARD
871 tristate "Nano River Technologies Viperboard"
876 Say yes here if you want support for Nano River Technologies
878 There are mfd cell drivers available for i2c master, adc and
879 both gpios found on the board. The spi part does not yet
881 You need to select the mfd cell drivers separately.
882 The drivers do not support all features the board exposes.
885 tristate "Nokia Retu and Tahvo multi-function device"
890 Retu and Tahvo are a multi-function devices found on Nokia
891 Internet Tablets (770, N800 and N810).
894 tristate "NXP PCF50633"
898 Say yes here if you have NXP PCF50633 chip on your board.
899 This core driver provides register access and IRQ handling
900 facilities, and registers devices for the various functions
901 so that function-specific drivers can bind to them.
904 tristate "NXP PCF50633 ADC"
905 depends on MFD_PCF50633
907 Say yes here if you want to include support for ADC in the
911 tristate "NXP PCF50633 GPIO"
912 depends on MFD_PCF50633
914 Say yes here if you want to include support GPIO for pins on
918 tristate "Philips UCB1400 Core driver"
922 This enables support for the Philips UCB1400 core functions.
923 The UCB1400 is an AC97 audio codec.
925 To compile this driver as a module, choose M here: the
926 module will be called ucb1400_core.
929 tristate "Qualcomm PM8xxx PMIC chips driver"
930 depends on (ARM || HEXAGON || COMPILE_TEST)
935 If you say yes to this option, support will be included for the
936 built-in PM8xxx PMIC chips.
938 This is required if your board has a PM8xxx and uses its features,
939 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
941 Say M here if you want to include support for PM8xxx chips as a
942 module. This will build a module called "pm8xxx-core".
945 tristate "Qualcomm Resource Power Manager (RPM)"
946 depends on ARCH_QCOM && OF
948 If you say yes to this option, support will be included for the
949 Resource Power Manager system found in the Qualcomm 8660, 8960 and
952 This is required to access many regulators, clocks and bus
953 frequencies controlled by the RPM on these devices.
955 Say M here if you want to include support for the Qualcomm RPM as a
956 module. This will build a module called "qcom_rpm".
959 tristate "Qualcomm SPMI PMICs"
960 depends on ARCH_QCOM || COMPILE_TEST
965 This enables support for the Qualcomm SPMI PMICs.
966 These PMICs are currently used with the Snapdragon 800 series of
967 SoCs. Note, that this will only be useful paired with descriptions
968 of the independent functions as children nodes in the device tree.
970 Say M here if you want to include support for the SPMI PMIC
971 series as a module. The module will be called "qcom-spmi-pmic".
974 tristate "RDC R-321x southbridge"
978 Say yes here if you want to have support for the RDC R-321x SoC
979 southbridge which provides access to GPIOs and Watchdog using the
980 southbridge PCI device configuration space.
983 tristate "Richtek RT5033 Power Management IC"
989 This driver provides for the Richtek RT5033 Power Management IC,
990 which includes the I2C driver and the Core APIs. This driver provides
991 common support for accessing the device. The device supports multiple
992 sub-devices like charger, fuel gauge, flash LED, current source,
996 bool "Ricoh RC5T583 Power Management system device"
1001 Select this option to get support for the RICOH583 Power
1002 Management system device.
1003 This driver provides common support for accessing the device
1004 through i2c interface. The device supports multiple sub-devices
1005 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1006 Additional drivers must be enabled in order to use the
1007 different functionality of the device.
1010 tristate "Rockchip RK805/RK808/RK818 Power Management Chip"
1011 depends on I2C && OF
1016 If you say yes here you get support for the RK805, RK808 and RK818
1017 Power Management chips.
1018 This driver provides common support for accessing the device
1019 through I2C interface. The device supports multiple sub-devices
1020 including interrupts, RTC, LDO & DCDC regulators, and onkey.
1023 tristate "Ricoh RN5T567/618 PMIC"
1029 Say yes here to add support for the Ricoh RN5T567,
1030 RN5T618, RC5T619 PMIC.
1031 This driver provides common support for accessing the device,
1032 additional drivers must be enabled in order to use the
1033 functionality of the device.
1036 tristate "SAMSUNG Electronics PMIC Series Support"
1042 Support for the Samsung Electronics PMIC devices coming
1043 usually along with Samsung Exynos SoC chipset.
1044 This driver provides common support for accessing the device,
1045 additional drivers must be enabled in order to use the functionality
1048 To compile this driver as a module, choose M here: the
1049 module will be called sec-core.
1050 Have in mind that important core drivers (like regulators) depend
1051 on this driver so building this as a module might require proper
1052 initial ramdisk or might not boot up as well in certain scenarios.
1054 config MFD_SI476X_CORE
1055 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1060 This is the core driver for the SI476x series of AM/FM
1061 radio. This MFD driver connects the radio-si476x V4L2 module
1062 and the si476x audio codec.
1064 To compile this driver as a module, choose M here: the
1065 module will be called si476x-core.
1068 tristate "Silicon Motion SM501"
1070 This is the core driver for the Silicon Motion SM501 multimedia
1071 companion chip. This device is a multifunction device which may
1072 provide numerous interfaces including USB host controller, USB gadget,
1073 asynchronous serial ports, audio functions, and a dual display video
1074 interface. The device may be connected by PCI or local bus with
1075 varying functions enabled.
1077 config MFD_SM501_GPIO
1078 bool "Export GPIO via GPIO layer"
1079 depends on MFD_SM501 && GPIOLIB
1081 This option uses the gpio library layer to export the 64 GPIO
1082 lines on the SM501. The platform data is used to supply the
1083 base number for the first GPIO line to register.
1086 tristate "Skyworks Solutions SKY81452"
1091 This is the core driver for the Skyworks SKY81452 backlight and
1092 voltage regulator device.
1094 This driver can also be built as a module. If so, the module
1095 will be called sky81452.
1098 bool "SMSC ECE1099 series chips"
1103 If you say yes here you get support for the
1104 ece1099 chips from SMSC.
1106 To compile this driver as a module, choose M here: the
1107 module will be called smsc.
1109 config MFD_SC27XX_PMIC
1110 tristate "Spreadtrum SC27xx PMICs"
1111 depends on ARCH_SPRD || COMPILE_TEST
1112 depends on SPI_MASTER
1117 This enables support for the Spreadtrum SC27xx PMICs with SPI
1118 interface. The SC27xx series PMICs integrate power management,
1119 audio codec, battery management and user interface support
1120 function (such as RTC, Typec, indicator and so on) in a single chip.
1122 This driver provides common support for accessing the SC27xx PMICs,
1123 and it also adds the irq_chip parts for handling the PMIC chip events.
1126 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1127 default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1129 Say yes here if you have the ABX500 Mixed Signal IC family
1130 chips. This core driver expose register access functions.
1131 Functionality specific drivers using these functions can
1132 remain unchanged when IC changes. Binding of the functions to
1133 actual register access is done by the IC core driver.
1136 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1137 depends on I2C=y && ABX500_CORE
1139 default y if ARCH_U300
1141 Select this to enable the AB3100 Mixed Signal IC core
1142 functionality. This connects to a AB3100 on the I2C bus
1143 and expose a number of symbols needed for dependent devices
1144 to read and write registers and subscribe to events from
1145 this multi-functional IC. This is needed to use other features
1146 of the AB3100 such as battery-backed RTC, charging control,
1147 LEDs, vibrator, system power and temperature, power management
1151 tristate "ST-Ericsson AB3100 OTP functions"
1152 depends on AB3100_CORE
1153 default y if AB3100_CORE
1155 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1156 programmable memory) support. This exposes a sysfs file to read
1160 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1161 depends on ABX500_CORE && MFD_DB8500_PRCMU
1166 Select this option to enable access to AB8500 power management
1167 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1168 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1169 the irq_chip parts for handling the Mixed Signal chip events.
1170 This chip embeds various other multimedia funtionalities as well.
1173 bool "Enable debug info via debugfs"
1174 depends on AB8500_GPADC && DEBUG_FS
1175 default y if DEBUG_FS
1177 Select this option if you want debug information using the debug
1178 filesystem, debugfs.
1181 bool "ST-Ericsson AB8500 GPADC driver"
1182 depends on AB8500_CORE && REGULATOR_AB8500
1185 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1187 config MFD_DB8500_PRCMU
1188 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1189 depends on UX500_SOC_DB8500
1192 Select this option to enable support for the DB8500 Power Reset
1193 and Control Management Unit. This is basically an autonomous
1194 system controller running an XP70 microprocessor, which is accessed
1195 through a register map.
1198 bool "STMicroelectronics STMPE"
1199 depends on (I2C=y || SPI_MASTER=y)
1203 Support for the STMPE family of I/O Expanders from
1206 Currently supported devices are:
1208 STMPE811: GPIO, Touchscreen
1209 STMPE1601: GPIO, Keypad
1210 STMPE1801: GPIO, Keypad
1211 STMPE2401: GPIO, Keypad
1212 STMPE2403: GPIO, Keypad
1214 This driver provides common support for accessing the device,
1215 additional drivers must be enabled in order to use the functionality
1216 of the device. Currently available sub drivers are:
1219 Keypad: stmpe-keypad
1220 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 && I2C=y
1425 select I2C_DESIGNWARE_PLATFORM
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 "VIA VX855/VX875 integrated south bridge"
1685 Say yes here to enable support for various functions of the
1686 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1687 and/or vx855_gpio drivers for this to do anything useful.
1695 config MFD_ARIZONA_I2C
1696 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1701 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1702 audio SoC core functionality controlled via I2C.
1704 config MFD_ARIZONA_SPI
1705 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1708 depends on SPI_MASTER
1710 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1711 audio SoC core functionality controlled via SPI.
1714 bool "Cirrus Logic CS47L24 and WM1831"
1715 depends on MFD_ARIZONA
1717 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1720 bool "Wolfson Microelectronics WM5102"
1721 depends on MFD_ARIZONA
1723 Support for Wolfson Microelectronics WM5102 low power audio SoC
1726 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1727 depends on MFD_ARIZONA
1729 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1733 bool "Wolfson Microelectronics WM8997"
1734 depends on MFD_ARIZONA
1736 Support for Wolfson Microelectronics WM8997 low power audio SoC
1739 bool "Wolfson Microelectronics WM8998"
1740 depends on MFD_ARIZONA
1742 Support for Wolfson Microelectronics WM8998 low power audio SoC
1745 bool "Wolfson Microelectronics WM8400"
1750 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1751 CODEC. This driver provides common support for accessing
1752 the device, additional drivers must be enabled in order to use
1753 the functionality of the device.
1758 config MFD_WM831X_I2C
1759 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1766 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1767 when controlled using I2C. This driver provides common support
1768 for accessing the device, additional drivers must be enabled in
1769 order to use the functionality of the device.
1771 config MFD_WM831X_SPI
1772 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1777 depends on SPI_MASTER
1779 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1780 when controlled using SPI. This driver provides common support
1781 for accessing the device, additional drivers must be enabled in
1782 order to use the functionality of the device.
1787 config MFD_WM8350_I2C
1788 bool "Wolfson Microelectronics WM8350 with I2C"
1793 The WM8350 is an integrated audio and power management
1794 subsystem with watchdog and RTC functionality for embedded
1795 systems. This option enables core support for the WM8350 with
1796 I2C as the control interface. Additional options must be
1797 selected to enable support for the functionality of the chip.
1800 tristate "Wolfson Microelectronics WM8994"
1806 The WM8994 is a highly integrated hi-fi CODEC designed for
1807 smartphone applications. As well as audio functionality it
1808 has on board GPIO and regulator functionality which is
1809 supported via the relevant subsystems. This driver provides
1810 core support for the WM8994, in order to use the actual
1811 functionaltiy of the device other drivers must be enabled.
1814 tristate "Wolfson Microelectronics WM97xx"
1817 select AC97_BUS_COMPAT
1818 depends on AC97_BUS_NEW
1820 The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1821 designed for smartphone applications. As well as audio functionality
1822 it has on board GPIO and a touchscreen functionality which is
1823 supported via the relevant subsystems. This driver provides core
1824 support for the WM97xx, in order to use the actual functionaltiy of
1825 the device other drivers must be enabled.
1828 tristate "Support for ST Microelectronics STw481x"
1829 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1833 Select this option to enable the STw481x chip driver used
1834 in various ST Microelectronics and ST-Ericsson embedded
1837 config MFD_ROHM_BD718XX
1838 tristate "ROHM BD71837 Power Management IC"
1845 Select this option to get support for the ROHM BD71837
1846 Power Management ICs. BD71837 is designed to power processors like
1847 NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
1848 and emergency shut down as well as 32,768KHz clock output.
1850 config MFD_STM32_LPTIMER
1851 tristate "Support for STM32 Low-Power Timer"
1852 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1857 Select this option to enable STM32 Low-Power Timer driver
1858 used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1859 resources are also dealt with here.
1861 To compile this driver as a module, choose M here: the
1862 module will be called stm32-lptimer.
1864 config MFD_STM32_TIMERS
1865 tristate "Support for STM32 Timers"
1866 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1871 Select this option to enable STM32 timers driver used
1872 for PWM and IIO Timer. This driver allow to share the
1873 registers between the others drivers.
1875 menu "Multimedia Capabilities Port drivers"
1876 depends on ARCH_SA1100
1883 tristate "Support SA11x0 MCP interface"
1884 depends on ARCH_SA1100
1889 tristate "Support for UCB1200 / UCB1300"
1890 depends on MCP_SA11X0
1893 config MCP_UCB1200_TS
1894 tristate "Touchscreen interface support"
1895 depends on MCP_UCB1200 && INPUT
1899 config MFD_VEXPRESS_SYSREG
1900 bool "Versatile Express System Registers"
1901 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1904 select GPIO_GENERIC_PLATFORM
1908 System Registers are the platform configuration block
1909 on the ARM Ltd. Versatile Express board.
1912 tristate "RAVE SP MCU core driver"
1913 depends on SERIAL_DEV_BUS
1916 Select this to get support for the Supervisory Processor
1917 device found on several devices in RAVE line of hardware.