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_ATMEL_FLEXCOM
103 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
107 Select this to get support for Atmel Flexcom. This is a wrapper
108 which embeds a SPI controller, a I2C controller and a USART. Only
109 one function can be used at a time. The choice is done at boot time
110 by the probe function of this MFD driver according to a device tree
113 config MFD_ATMEL_HLCDC
114 tristate "Atmel HLCDC (High-end LCD Controller)"
119 If you say yes here you get support for the HLCDC block.
120 This driver provides common support for accessing the device,
121 additional drivers must be enabled in order to use the
122 functionality of the device.
129 tristate "Broadcom BCM590xx PMUs"
134 Support for the BCM590xx PMUs from Broadcom
137 tristate "ROHM BD9571MWV PMIC"
143 Support for the ROHM BD9571MWV PMIC, which contains single
144 voltage regulator, voltage sampling units, GPIO block and
147 This driver can also be built as a module. If so, the module
148 will be called bd9571mwv.
151 tristate "X-Powers AC100"
155 If you say Y here you get support for the X-Powers AC100 audio codec
157 This driver include only the core APIs. You have to select individual
158 components like codecs or RTC under the corresponding menus.
165 config MFD_AXP20X_I2C
166 tristate "X-Powers AXP series PMICs with I2C"
171 If you say Y here you get support for the X-Powers AXP series power
172 management ICs (PMICs) controlled with I2C.
173 This driver include only the core APIs. You have to select individual
174 components like regulators or the PEK (Power Enable Key) under the
177 Note on x86 this provides an ACPI OpRegion, so this must be 'y'
178 (builtin) and not a module, as the OpRegion must be available as
179 soon as possible. For the same reason the I2C bus driver options
180 I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
182 config MFD_AXP20X_RSB
183 tristate "X-Powers AXP series PMICs with RSB"
187 If you say Y here you get support for the X-Powers AXP series power
188 management ICs (PMICs) controlled with RSB.
189 This driver include only the core APIs. You have to select individual
190 components like regulators or the PEK (Power Enable Key) under the
194 tristate "ChromeOS Embedded Controller"
196 select CHROME_PLATFORMS
198 depends on X86 || ARM || ARM64 || COMPILE_TEST
200 If you say Y here you get support for the ChromeOS Embedded
201 Controller (EC) providing keyboard, battery and power services.
202 You also need to enable the driver for the bus you are using. The
203 protocol for talking to the EC is defined by the bus driver.
205 config MFD_CROS_EC_CHARDEV
206 tristate "Chrome OS Embedded Controller userspace device interface"
207 depends on MFD_CROS_EC
210 This driver adds support to talk with the ChromeOS EC from userspace.
212 If you have a supported Chromebook, choose Y or M here.
213 The module will be called cros_ec_dev.
216 tristate "Cirrus Logic Madera codecs"
222 select PINCTRL_MADERA
224 Support for the Cirrus Logic Madera platform audio codecs
226 config MFD_MADERA_I2C
227 tristate "Cirrus Logic Madera codecs with I2C"
228 depends on MFD_MADERA
232 Support for the Cirrus Logic Madera platform audio SoC
233 core functionality controlled via I2C.
235 config MFD_MADERA_SPI
236 tristate "Cirrus Logic Madera codecs with SPI"
237 depends on MFD_MADERA
238 depends on SPI_MASTER
241 Support for the Cirrus Logic Madera platform audio SoC
242 core functionality controlled via SPI.
245 bool "Cirrus Logic CS47L35"
246 select PINCTRL_CS47L35
247 depends on MFD_MADERA
249 Support for Cirrus Logic CS47L35 Smart Codec
252 bool "Cirrus Logic CS47L85"
253 select PINCTRL_CS47L85
254 depends on MFD_MADERA
256 Support for Cirrus Logic CS47L85 Smart Codec
259 bool "Cirrus Logic CS47L90/91"
260 select PINCTRL_CS47L90
261 depends on MFD_MADERA
263 Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
267 depends on GPIOLIB && ARM
270 This driver supports the ASIC3 multifunction chip found on many
271 PDAs (mainly iPAQ and HTC based ones)
274 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
277 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
278 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
279 usually found on PXA processors-based platforms. This includes
280 the I2C driver and the core APIs _only_, you have to select
281 individual components like LCD backlight, voltage regulators,
282 LEDs and battery-charger under the corresponding menus.
288 config MFD_DA9052_SPI
289 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
293 depends on SPI_MASTER=y
295 Support for the Dialog Semiconductor DA9052 PMIC
296 when controlled using SPI. This driver provides common support
297 for accessing the device, additional drivers must be enabled in
298 order to use the functionality of the device.
300 config MFD_DA9052_I2C
301 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
307 Support for the Dialog Semiconductor DA9052 PMIC
308 when controlled using I2C. This driver provides common support
309 for accessing the device, additional drivers must be enabled in
310 order to use the functionality of the device.
313 bool "Dialog Semiconductor DA9055 PMIC Support"
319 Say yes here for support of Dialog Semiconductor DA9055. This is
320 a Power Management IC. This driver provides common support for
321 accessing the device as well as the I2C interface to the chip itself.
322 Additional drivers must be enabled in order to use the functionality
325 This driver can be built as a module. If built as a module it will be
329 tristate "Dialog Semiconductor DA9062/61 PMIC Support"
335 Say yes here for support for the Dialog Semiconductor DA9061 and
337 This includes the I2C driver and core APIs.
338 Additional drivers must be enabled in order to use the functionality
342 tristate "Dialog Semiconductor DA9063 PMIC Support"
348 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
349 This includes the I2C driver and core APIs.
350 Additional drivers must be enabled in order to use the functionality
354 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
360 This adds support for the DA9150 integrated charger and fuel-gauge
361 chip. This driver provides common support for accessing the device.
362 Additional drivers must be enabled in order to use the specific
363 features of the device.
366 tristate "Diolan DLN2 support"
370 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
371 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
372 etc. must be enabled in order to use the functionality of
375 config MFD_EXYNOS_LPASS
376 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
377 depends on ARCH_EXYNOS || COMPILE_TEST
381 Select this option to enable support for Samsung Exynos Low Power
386 depends on (SPI_MASTER || I2C)
390 Enable support for the Freescale MC13783 and MC13892 PMICs.
391 This driver provides common support for accessing the device,
392 additional drivers must be enabled in order to use the
393 functionality of the device.
395 config MFD_MC13XXX_SPI
396 tristate "Freescale MC13783 and MC13892 SPI interface"
397 depends on SPI_MASTER
401 Select this if your MC13xxx is connected via an SPI bus.
403 config MFD_MC13XXX_I2C
404 tristate "Freescale MC13892 I2C interface"
409 Select this if your MC13xxx is connected via an I2C bus.
412 tristate "Freescale i.MX23/i.MX28 LRADC"
413 depends on ARCH_MXS || COMPILE_TEST
417 Say yes here to build support for the Low Resolution
418 Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
419 processors. This driver provides common support for accessing the
420 device, additional drivers must be enabled in order to use the
421 functionality of the device:
422 mxs-lradc-adc for ADC readings
423 mxs-lradc-ts for touchscreen support
425 This driver can also be built as a module. If so, the module will be
428 config MFD_MX25_TSADC
429 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
431 depends on (SOC_IMX25 && OF) || COMPILE_TEST
433 Enable support for the integrated Touchscreen and ADC unit of the
434 i.MX25 processors. They consist of a conversion queue for general
435 purpose ADC and a queue for Touchscreens.
437 config MFD_HI6421_PMIC
438 tristate "HiSilicon Hi6421 PMU/Codec IC"
443 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
444 functions, such as regulators, RTC, codec, Coulomb counter, etc.
445 This driver includes core APIs _only_. You have to select
446 individul components like voltage regulators under corresponding
447 menus in order to enable them.
448 We communicate with the Hi6421 via memory-mapped I/O.
450 config MFD_HI655X_PMIC
451 tristate "HiSilicon Hi655X series PMU/Codec IC"
452 depends on ARCH_HISI || COMPILE_TEST
458 Select this option to enable Hisilicon hi655x series pmic driver.
461 tristate "HTC PASIC3 LED/DS1WM chip support"
464 This core driver provides register access for the LED/DS1WM
465 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
466 HTC Magician devices, respectively. Actual functionality is
467 handled by the leds-pasic3 and ds1wm drivers.
470 bool "HTC I2C PLD chip support"
471 depends on I2C=y && GPIOLIB
473 If you say yes here you get support for the supposed CPLD
474 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
475 This device provides input and output GPIOs through an I2C
476 interface to one or more sub-chips.
478 config MFD_INTEL_QUARK_I2C_GPIO
479 tristate "Intel Quark MFD I2C GPIO"
482 depends on COMMON_CLK
485 This MFD provides support for I2C and GPIO that exist only
486 in a single PCI device. It splits the 2 IO devices to
487 their respective IO driver.
488 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
491 tristate "Intel ICH LPC"
495 The LPC bridge function of the Intel ICH provides support for
496 many functional units. This driver provides needed support for
497 other drivers to control these functions, currently GPIO and
501 tristate "Intel SCH LPC"
505 LPC bridge function of the Intel SCH provides support for
506 System Management Bus and General Purpose I/O.
508 config INTEL_SOC_PMIC
509 bool "Support for Crystal Cove PMIC"
510 depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
511 depends on X86 || COMPILE_TEST
512 depends on I2C_DESIGNWARE_PLATFORM=y
517 Select this option to enable support for Crystal Cove PMIC
518 on some Intel SoC systems. The PMIC provides ADC, GPIO,
519 thermal, charger and related power management functions
522 This option is a bool as it provides an ACPI OpRegion which must be
523 available before any devices using it are probed. This option also
524 causes the designware-i2c driver to be builtin for the same reason.
526 config INTEL_SOC_PMIC_BXTWC
527 tristate "Support for Intel Broxton Whiskey Cove PMIC"
528 depends on INTEL_PMC_IPC
532 Select this option to enable support for Whiskey Cove PMIC
533 on Intel Broxton systems. The PMIC provides ADC, GPIO,
534 thermal, charger and related power management functions
537 config INTEL_SOC_PMIC_CHTWC
538 bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
539 depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
540 depends on X86 || COMPILE_TEST
541 depends on I2C_DESIGNWARE_PLATFORM=y
546 Select this option to enable support for the Intel Cherry Trail
547 Whiskey Cove PMIC found on some Intel Cherry Trail systems.
549 This option is a bool as it provides an ACPI OpRegion which must be
550 available before any devices using it are probed. This option also
551 causes the designware-i2c driver to be builtin for the same reason.
553 config INTEL_SOC_PMIC_CHTDC_TI
554 tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
563 Select this option for supporting Dollar Cove (TI version) PMIC
564 device that is found on some Intel Cherry Trail systems.
566 config MFD_INTEL_LPSS
571 config MFD_INTEL_LPSS_ACPI
572 tristate "Intel Low Power Subsystem support in ACPI mode"
573 select MFD_INTEL_LPSS
574 depends on X86 && ACPI
576 This driver supports Intel Low Power Subsystem (LPSS) devices such as
577 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
580 config MFD_INTEL_LPSS_PCI
581 tristate "Intel Low Power Subsystem support in PCI mode"
582 select MFD_INTEL_LPSS
583 depends on X86 && PCI
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_MSIC
591 depends on INTEL_SCU_IPC
594 Select this option to enable access to Intel MSIC (Avatele
595 Passage) chip. This chip embeds audio, battery, GPIO, etc.
596 devices used in Intel Medfield platforms.
598 config MFD_IPAQ_MICRO
599 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
600 depends on SA1100_H3100 || SA1100_H3600
603 Select this to get support for the Microcontroller found in
604 the Compaq iPAQ handheld computers. This is an Atmel
605 AT90LS8535 microcontroller flashed with a special iPAQ
606 firmware using the custom protocol implemented in this driver.
608 config MFD_JANZ_CMODIO
609 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
613 This is the core driver for the Janz CMOD-IO PCI MODULbus
614 carrier board. This device is a PCI to MODULbus bridge which may
615 host many different types of MODULbus daughterboards, including
616 CAN and GPIO controllers.
618 config MFD_JZ4740_ADC
619 bool "Janz JZ4740 ADC core"
621 select GENERIC_IRQ_CHIP
622 depends on MACH_JZ4740
624 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
625 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
628 tristate "Kontron module PLD device"
631 This is the core driver for the PLD (Programmable Logic Device) found
632 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
633 device may provide functions like watchdog, GPIO, UART and I2C bus.
635 The following modules are supported:
642 * COMe-bPC2 (ETXexpress-PC)
643 * COMe-bSC# (ETXexpress-SC T#)
649 * COMe-cDC2 (microETXexpress-DC)
652 * COMe-cPC2 (microETXexpress-PC)
657 * COMe-mTT10 (nanoETXexpress-TT)
660 This driver can also be built as a module. If so, the module
661 will be called kempld-core.
664 tristate "Marvell 88PM800"
670 This supports for Marvell 88PM800 Power Management IC.
671 This includes the I2C driver and the core APIs _only_, you have to
672 select individual components like voltage regulators, RTC and
673 battery-charger under the corresponding menus.
676 tristate "Marvell 88PM805"
682 This supports for Marvell 88PM805 Power Management IC. This includes
683 the I2C driver and the core APIs _only_, you have to select individual
684 components like codec device, headset/Mic device under the
688 bool "Marvell 88PM8606/88PM8607"
693 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
694 This includes the I2C driver and the core APIs _only_, you have to
695 select individual components like voltage regulators, RTC and
696 battery-charger under the corresponding menus.
699 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
706 Say yes here to add support for Maxim Semiconductor MAX14577 and
707 MAX77836 Micro-USB ICs with battery charger.
708 This driver provides common support for accessing the device;
709 additional drivers must be enabled in order to use the functionality
713 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
715 depends on OF || COMPILE_TEST
721 Say yes here to add support for Maxim Semiconductor MAX77620 and
722 MAX20024 which are Power Management IC with General purpose pins,
723 RTC, regulators, clock generator, watchdog etc. This driver
724 provides common support for accessing the device; additional drivers
725 must be enabled in order to use the functionality of the device.
728 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
730 depends on OF || COMPILE_TEST
736 Say yes here to add support for Maxim Semiconductor MAX77686 and
737 MAX77802 which are Power Management IC with an RTC on chip.
738 This driver provides common support for accessing the device;
739 additional drivers must be enabled in order to use the functionality
743 tristate "Maxim Semiconductor MAX77693 PMIC Support"
749 Say yes here to add support for Maxim Semiconductor MAX77693.
750 This is a companion Power Management IC with Flash, Haptic, Charger,
751 and MUIC(Micro USB Interface Controller) controls on chip.
752 This driver provides common support for accessing the device;
753 additional drivers must be enabled in order to use the functionality
757 bool "Maxim Semiconductor MAX77843 PMIC Support"
763 Say yes here to add support for Maxim Semiconductor MAX77843.
764 This is companion Power Management IC with LEDs, Haptic, Charger,
765 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
766 This driver provides common support for accessing the device;
767 additional drivers must be enabled in order to use the functionality
771 tristate "Maxim Semiconductor MAX8907 PMIC Support"
777 Say yes here to add support for Maxim Semiconductor MAX8907. This is
778 a Power Management IC. This driver provides common support for
779 accessing the device; additional drivers must be enabled in order
780 to use the functionality of the device.
783 bool "Maxim Semiconductor MAX8925 PMIC Support"
787 Say yes here to add support for Maxim Semiconductor MAX8925. 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 MAX8997/8966 PMIC Support"
798 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
799 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
800 MUIC controls on chip.
801 This driver provides common support for accessing the device;
802 additional drivers must be enabled in order to use the functionality
806 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
811 Say yes here to add support for Maxim Semiconductor MAX8998 and
812 National Semiconductor LP3974. This is a Power Management IC.
813 This driver provides common support for accessing the device,
814 additional drivers must be enabled in order to use the functionality
818 tristate "MediaTek MT6397 PMIC Support"
822 Say yes here to add support for MediaTek MT6397 PMIC. This is
823 a Power Management IC. This driver provides common support for
824 accessing the device; additional drivers must be enabled in order
825 to use the functionality of the device.
828 tristate "MEN 14F021P00 Board Management Controller Support"
832 Say yes here to add support for the MEN 14F021P00 BMC
833 which is a Board Management Controller connected to the I2C bus.
834 The device supports multiple sub-devices like LED, HWMON and WDT.
835 This driver provides common support for accessing the devices;
836 additional drivers must be enabled in order to use the
837 functionality of the BMC device.
839 This driver can also be built as a module. If so the module
840 will be called menf21bmc.
843 bool "Motorola EZXPCAP Support"
844 depends on SPI_MASTER
846 This enables the PCAP ASIC present on EZX Phones. This is
847 needed for MMC, TouchScreen, Sound, USB, etc..
850 tristate "Support for Motorola CPCAP"
852 depends on OF || COMPILE_TEST
856 Say yes here if you want to include driver for CPCAP.
857 It is used on many Motorola phones and tablets as a PMIC.
858 At least Motorola Droid 4 is known to use CPCAP.
860 config MFD_VIPERBOARD
861 tristate "Nano River Technologies Viperboard"
866 Say yes here if you want support for Nano River Technologies
868 There are mfd cell drivers available for i2c master, adc and
869 both gpios found on the board. The spi part does not yet
871 You need to select the mfd cell drivers separately.
872 The drivers do not support all features the board exposes.
875 tristate "Nokia Retu and Tahvo multi-function device"
880 Retu and Tahvo are a multi-function devices found on Nokia
881 Internet Tablets (770, N800 and N810).
884 tristate "NXP PCF50633"
888 Say yes here if you have NXP PCF50633 chip on your board.
889 This core driver provides register access and IRQ handling
890 facilities, and registers devices for the various functions
891 so that function-specific drivers can bind to them.
894 tristate "NXP PCF50633 ADC"
895 depends on MFD_PCF50633
897 Say yes here if you want to include support for ADC in the
901 tristate "NXP PCF50633 GPIO"
902 depends on MFD_PCF50633
904 Say yes here if you want to include support GPIO for pins on
908 tristate "Philips UCB1400 Core driver"
912 This enables support for the Philips UCB1400 core functions.
913 The UCB1400 is an AC97 audio codec.
915 To compile this driver as a module, choose M here: the
916 module will be called ucb1400_core.
919 tristate "Qualcomm PM8xxx PMIC chips driver"
920 depends on (ARM || HEXAGON || COMPILE_TEST)
925 If you say yes to this option, support will be included for the
926 built-in PM8xxx PMIC chips.
928 This is required if your board has a PM8xxx and uses its features,
929 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
931 Say M here if you want to include support for PM8xxx chips as a
932 module. This will build a module called "pm8xxx-core".
935 tristate "Qualcomm Resource Power Manager (RPM)"
936 depends on ARCH_QCOM && OF
938 If you say yes to this option, support will be included for the
939 Resource Power Manager system found in the Qualcomm 8660, 8960 and
942 This is required to access many regulators, clocks and bus
943 frequencies controlled by the RPM on these devices.
945 Say M here if you want to include support for the Qualcomm RPM as a
946 module. This will build a module called "qcom_rpm".
949 tristate "Qualcomm SPMI PMICs"
950 depends on ARCH_QCOM || COMPILE_TEST
955 This enables support for the Qualcomm SPMI PMICs.
956 These PMICs are currently used with the Snapdragon 800 series of
957 SoCs. Note, that this will only be useful paired with descriptions
958 of the independent functions as children nodes in the device tree.
960 Say M here if you want to include support for the SPMI PMIC
961 series as a module. The module will be called "qcom-spmi-pmic".
964 tristate "RDC R-321x southbridge"
968 Say yes here if you want to have support for the RDC R-321x SoC
969 southbridge which provides access to GPIOs and Watchdog using the
970 southbridge PCI device configuration space.
973 tristate "Richtek RT5033 Power Management IC"
979 This driver provides for the Richtek RT5033 Power Management IC,
980 which includes the I2C driver and the Core APIs. This driver provides
981 common support for accessing the device. The device supports multiple
982 sub-devices like charger, fuel gauge, flash LED, current source,
986 bool "Ricoh RC5T583 Power Management system device"
991 Select this option to get support for the RICOH583 Power
992 Management system device.
993 This driver provides common support for accessing the device
994 through i2c interface. The device supports multiple sub-devices
995 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
996 Additional drivers must be enabled in order to use the
997 different functionality of the device.
1000 tristate "Rockchip RK805/RK808/RK818 Power Management Chip"
1001 depends on I2C && OF
1006 If you say yes here you get support for the RK805, RK808 and RK818
1007 Power Management chips.
1008 This driver provides common support for accessing the device
1009 through I2C interface. The device supports multiple sub-devices
1010 including interrupts, RTC, LDO & DCDC regulators, and onkey.
1013 tristate "Ricoh RN5T567/618 PMIC"
1019 Say yes here to add support for the Ricoh RN5T567,
1020 RN5T618, RC5T619 PMIC.
1021 This driver provides common support for accessing the device,
1022 additional drivers must be enabled in order to use the
1023 functionality of the device.
1026 bool "SAMSUNG Electronics PMIC Series Support"
1032 Support for the Samsung Electronics MFD series.
1033 This driver provides common support for accessing the device,
1034 additional drivers must be enabled in order to use the functionality
1037 config MFD_SI476X_CORE
1038 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1043 This is the core driver for the SI476x series of AM/FM
1044 radio. This MFD driver connects the radio-si476x V4L2 module
1045 and the si476x audio codec.
1047 To compile this driver as a module, choose M here: the
1048 module will be called si476x-core.
1051 tristate "Silicon Motion SM501"
1053 This is the core driver for the Silicon Motion SM501 multimedia
1054 companion chip. This device is a multifunction device which may
1055 provide numerous interfaces including USB host controller, USB gadget,
1056 asynchronous serial ports, audio functions, and a dual display video
1057 interface. The device may be connected by PCI or local bus with
1058 varying functions enabled.
1060 config MFD_SM501_GPIO
1061 bool "Export GPIO via GPIO layer"
1062 depends on MFD_SM501 && GPIOLIB
1064 This option uses the gpio library layer to export the 64 GPIO
1065 lines on the SM501. The platform data is used to supply the
1066 base number for the first GPIO line to register.
1069 tristate "Skyworks Solutions SKY81452"
1074 This is the core driver for the Skyworks SKY81452 backlight and
1075 voltage regulator device.
1077 This driver can also be built as a module. If so, the module
1078 will be called sky81452.
1081 bool "SMSC ECE1099 series chips"
1086 If you say yes here you get support for the
1087 ece1099 chips from SMSC.
1089 To compile this driver as a module, choose M here: the
1090 module will be called smsc.
1092 config MFD_SC27XX_PMIC
1093 tristate "Spreadtrum SC27xx PMICs"
1094 depends on ARCH_SPRD || COMPILE_TEST
1095 depends on SPI_MASTER
1100 This enables support for the Spreadtrum SC27xx PMICs with SPI
1101 interface. The SC27xx series PMICs integrate power management,
1102 audio codec, battery management and user interface support
1103 function (such as RTC, Typec, indicator and so on) in a single chip.
1105 This driver provides common support for accessing the SC27xx PMICs,
1106 and it also adds the irq_chip parts for handling the PMIC chip events.
1109 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1110 default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1112 Say yes here if you have the ABX500 Mixed Signal IC family
1113 chips. This core driver expose register access functions.
1114 Functionality specific drivers using these functions can
1115 remain unchanged when IC changes. Binding of the functions to
1116 actual register access is done by the IC core driver.
1119 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1120 depends on I2C=y && ABX500_CORE
1122 default y if ARCH_U300
1124 Select this to enable the AB3100 Mixed Signal IC core
1125 functionality. This connects to a AB3100 on the I2C bus
1126 and expose a number of symbols needed for dependent devices
1127 to read and write registers and subscribe to events from
1128 this multi-functional IC. This is needed to use other features
1129 of the AB3100 such as battery-backed RTC, charging control,
1130 LEDs, vibrator, system power and temperature, power management
1134 tristate "ST-Ericsson AB3100 OTP functions"
1135 depends on AB3100_CORE
1136 default y if AB3100_CORE
1138 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1139 programmable memory) support. This exposes a sysfs file to read
1143 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1144 depends on ABX500_CORE && MFD_DB8500_PRCMU
1149 Select this option to enable access to AB8500 power management
1150 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1151 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1152 the irq_chip parts for handling the Mixed Signal chip events.
1153 This chip embeds various other multimedia funtionalities as well.
1156 bool "Enable debug info via debugfs"
1157 depends on AB8500_GPADC && DEBUG_FS
1158 default y if DEBUG_FS
1160 Select this option if you want debug information using the debug
1161 filesystem, debugfs.
1164 bool "ST-Ericsson AB8500 GPADC driver"
1165 depends on AB8500_CORE && REGULATOR_AB8500
1168 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1170 config MFD_DB8500_PRCMU
1171 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1172 depends on UX500_SOC_DB8500
1175 Select this option to enable support for the DB8500 Power Reset
1176 and Control Management Unit. This is basically an autonomous
1177 system controller running an XP70 microprocessor, which is accessed
1178 through a register map.
1181 bool "STMicroelectronics STMPE"
1182 depends on (I2C=y || SPI_MASTER=y)
1186 Support for the STMPE family of I/O Expanders from
1189 Currently supported devices are:
1191 STMPE811: GPIO, Touchscreen
1192 STMPE1601: GPIO, Keypad
1193 STMPE1801: GPIO, Keypad
1194 STMPE2401: GPIO, Keypad
1195 STMPE2403: GPIO, Keypad
1197 This driver provides common support for accessing the device,
1198 additional drivers must be enabled in order to use the functionality
1199 of the device. Currently available sub drivers are:
1202 Keypad: stmpe-keypad
1203 Touchscreen: stmpe-ts
1205 menu "STMicroelectronics STMPE Interface Drivers"
1206 depends on MFD_STMPE
1209 bool "STMicroelectronics STMPE I2C Interface"
1213 This is used to enable I2C interface of STMPE
1216 bool "STMicroelectronics STMPE SPI Interface"
1217 depends on SPI_MASTER
1219 This is used to enable SPI interface of STMPE
1223 bool "STMicroelectronics STA2X11"
1228 config MFD_SUN6I_PRCM
1229 bool "Allwinner A31 PRCM controller"
1230 depends on ARCH_SUNXI
1233 Support for the PRCM (Power/Reset/Clock Management) unit available
1237 bool "System Controller Register R/W Based on Regmap"
1240 Select this option to enable accessing system control registers
1243 config MFD_DAVINCI_VOICECODEC
1248 config MFD_TI_AM335X_TSCADC
1249 tristate "TI ADC / Touch Screen chip support"
1254 If you say yes here you get support for Texas Instruments series
1255 of Touch Screen /ADC chips.
1256 To compile this driver as a module, choose M here: the
1257 module will be called ti_am335x_tscadc.
1259 config MFD_DM355EVM_MSP
1260 bool "TI DaVinci DM355 EVM microcontroller"
1261 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1263 This driver supports the MSP430 microcontroller used on these
1264 boards. MSP430 firmware manages resets and power sequencing,
1265 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1268 tristate "TI/National Semiconductor LP3943 MFD Driver"
1273 Support for the TI/National Semiconductor LP3943.
1274 This driver consists of GPIO and PWM drivers.
1275 With these functionalities, it can be used for LED string control or
1276 general usage such like a GPIO controller and a PWM controller.
1279 bool "TI LP8788 Power Management Unit Driver"
1285 TI LP8788 PMU supports regulators, battery charger, RTC,
1286 ADC, backlight driver and current sinks.
1289 tristate "TI Lighting Management Unit driver"
1294 Say yes here to enable support for TI LMU chips.
1296 TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
1297 It consists of backlight, LED and regulator driver.
1298 It provides consistent device controls for lighting functions.
1300 config MFD_OMAP_USB_HOST
1301 bool "TI OMAP USBHS core and TLL driver"
1302 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1305 This is the core driver for the OAMP EHCI and OHCI drivers.
1306 This MFD driver does the required setup functionalities for
1307 OMAP USB Host drivers.
1310 bool "TI Palmas series chips"
1316 If you say yes here you get support for the Palmas
1317 series of PMIC chips from Texas Instruments.
1320 tristate "TI TPS61050/61052 Boost Converters"
1325 select REGULATOR_FIXED_VOLTAGE
1327 This option enables a driver for the TP61050/TPS61052
1328 high-power "white LED driver". This boost converter is
1329 sometimes used for other things than white LEDs, and
1330 also contains a GPIO pin.
1333 tristate "TI TPS6501x Power Management chips"
1334 depends on I2C && GPIOLIB
1335 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1337 If you say yes here you get support for the TPS6501x series of
1338 Power Management chips. These include voltage regulators,
1339 lithium ion/polymer battery charging, and other features that
1340 are often used in portable devices like cell phones and cameras.
1342 This driver can also be built as a module. If so, the module
1343 will be called tps65010.
1346 tristate "TI TPS6507x Power Management / Touch Screen chips"
1350 If you say yes here you get support for the TPS6507x series of
1351 Power Management / Touch Screen chips. These include voltage
1352 regulators, lithium ion/polymer battery charging, touch screen
1353 and other features that are often used in portable devices.
1354 This driver can also be built as a module. If so, the module
1355 will be called tps6507x.
1358 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1365 If you say yes here you get support for the TPS65086 series of
1366 Power Management chips.
1367 This driver provides common support for accessing the device,
1368 additional drivers must be enabled in order to use the
1369 functionality of the device.
1371 config TPS65911_COMPARATOR
1375 bool "TI TPS65090 Power Management chips"
1381 If you say yes here you get support for the TPS65090 series of
1382 Power Management chips.
1383 This driver provides common support for accessing the device,
1384 additional drivers must be enabled in order to use the
1385 functionality of the device.
1388 tristate "TI TPS65217 Power Management / White LED chips"
1389 depends on I2C && OF
1394 If you say yes here you get support for the TPS65217 series of
1395 Power Management / White LED chips.
1396 These include voltage regulators, lithium ion/polymer battery
1397 charger, wled and other features that are often used in portable
1400 This driver can also be built as a module. If so, the module
1401 will be called tps65217.
1404 bool "TI TPS68470 Power Management / LED chips"
1405 depends on ACPI && I2C=y
1406 depends on I2C_DESIGNWARE_PLATFORM=y
1410 If you say yes here you get support for the TPS68470 series of
1411 Power Management / LED chips.
1413 These include voltage regulators, LEDs and other features
1414 that are often used in portable devices.
1416 This option is a bool as it provides an ACPI operation
1417 region, which must be available before any of the devices
1418 using this are probed. This option also configures the
1419 designware-i2c driver to be built-in, for the same reason.
1421 config MFD_TI_LP873X
1422 tristate "TI LP873X Power Management IC"
1427 If you say yes here then you get support for the LP873X series of
1428 Power Management Integrated Circuits (PMIC).
1429 These include voltage regulators, thermal protection, configurable
1430 General Purpose Outputs (GPO) that are used in portable devices.
1432 This driver can also be built as a module. If so, the module
1433 will be called lp873x.
1435 config MFD_TI_LP87565
1436 tristate "TI LP87565 Power Management IC"
1437 depends on I2C && OF
1441 If you say yes here then you get support for the LP87565 series of
1442 Power Management Integrated Circuits (PMIC).
1443 These include voltage regulators, thermal protection, configurable
1444 General Purpose Outputs (GPO) that are used in portable devices.
1446 This driver can also be built as a module. If so, the module
1447 will be called lp87565.
1450 tristate "TI TPS65218 Power Management chips"
1451 depends on I2C && OF
1456 If you say yes here you get support for the TPS65218 series of
1457 Power Management chips.
1458 These include voltage regulators, gpio and other features
1459 that are often used in portable devices.
1461 This driver can also be built as a module. If so, the module
1462 will be called tps65218.
1465 bool "TI TPS6586x Power Management chips"
1470 If you say yes here you get support for the TPS6586X series of
1471 Power Management chips.
1472 This driver provides common support for accessing the device,
1473 additional drivers must be enabled in order to use the
1474 functionality of the device.
1476 This driver can also be built as a module. If so, the module
1477 will be called tps6586x.
1480 bool "TI TPS65910 Power Management chip"
1482 depends on GPIOLIB || COMPILE_TEST
1488 if you say yes here you get support for the TPS65910 series of
1489 Power Management chips.
1497 config MFD_TPS65912_I2C
1498 tristate "TI TPS65912 Power Management chip with I2C"
1503 If you say yes here you get support for the TPS65912 series of
1504 PM chips with I2C interface.
1506 config MFD_TPS65912_SPI
1507 tristate "TI TPS65912 Power Management chip with SPI"
1510 depends on SPI_MASTER
1512 If you say yes here you get support for the TPS65912 series of
1513 PM chips with SPI interface.
1516 bool "TI TPS80031/TPS80032 Power Management chips"
1522 If you say yes here you get support for the Texas Instruments
1523 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1524 Path and Battery Charger. The device provides five configurable
1525 step-down converters, 11 general purpose LDOs, USB OTG Module,
1526 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1527 Power Path from USB, 32K clock generator.
1530 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1535 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1536 This core driver provides register access and IRQ handling
1537 facilities, and registers devices for the various functions
1538 so that function-specific drivers can bind to them.
1540 These multi-function chips are found on many OMAP2 and OMAP3
1541 boards, providing power management, RTC, GPIO, keypad, a
1542 high speed USB OTG transceiver, an audio codec (on most
1543 versions) and many other features.
1545 config TWL4030_POWER
1546 bool "TI TWL4030 power resources"
1547 depends on TWL4030_CORE && ARM
1549 Say yes here if you want to use the power resources on the
1550 TWL4030 family chips. Most of these resources are regulators,
1551 which have a separate driver; some are control signals, such
1552 as clock request handshaking.
1554 This driver uses board-specific data to initialize the resources
1555 and load scripts controlling which resources are switched off/on
1556 or reset when a sleep, wakeup or warm reset event occurs.
1558 config MFD_TWL4030_AUDIO
1559 bool "TI TWL4030 Audio"
1560 depends on TWL4030_CORE
1565 bool "TI TWL6040 audio codec"
1572 Say yes here if you want support for Texas Instruments TWL6040 audio
1574 This driver provides common support for accessing the device,
1575 additional drivers must be enabled in order to use the
1576 functionality of the device (audio, vibra).
1579 bool "TI TWL92330/Menelaus PM chip"
1580 depends on I2C=y && ARCH_OMAP2
1582 If you say yes here you get support for the Texas Instruments
1583 TWL92330/Menelaus Power Management chip. This include voltage
1584 regulators, Dual slot memory card transceivers, real-time clock
1585 and other features that are often used in portable devices like
1586 cell phones and PDAs.
1588 config MFD_WL1273_CORE
1589 tristate "TI WL1273 FM radio"
1594 This is the core driver for the TI WL1273 FM radio. This MFD
1595 driver connects the radio-wl1273 V4L2 module and the wl1273
1599 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1604 Say yes here to enable support for National Semiconductor / TI
1605 LM3533 Lighting Power chips.
1607 This driver provides common support for accessing the device;
1608 additional drivers must be enabled in order to use the LED,
1609 backlight or ambient-light-sensor functionality of the device.
1611 config MFD_TIMBERDALE
1612 tristate "Timberdale FPGA"
1614 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1616 This is the core driver for the timberdale FPGA. This device is a
1617 multifunction device which exposes numerous platform devices.
1619 The timberdale FPGA can be found on the Intel Atom development board
1620 for in-vehicle infontainment, called Russellville.
1623 bool "Toshiba TC35892 and variants"
1628 Support for the Toshiba TC35892 and variants I/O Expander.
1630 This driver provides common support for accessing the device,
1631 additional drivers must be enabled in order to use the
1632 functionality of the device.
1639 bool "Toshiba T7L66XB"
1640 depends on ARM && HAVE_CLK
1644 Support for Toshiba Mobile IO Controller T7L66XB
1647 bool "Toshiba TC6387XB"
1648 depends on ARM && HAVE_CLK
1652 Support for Toshiba Mobile IO Controller TC6387XB
1655 bool "Toshiba TC6393XB"
1656 depends on ARM && HAVE_CLK
1661 Support for Toshiba Mobile IO Controller TC6393XB
1664 tristate "VIA VX855/VX875 integrated south bridge"
1668 Say yes here to enable support for various functions of the
1669 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1670 and/or vx855_gpio drivers for this to do anything useful.
1678 config MFD_ARIZONA_I2C
1679 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1684 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1685 audio SoC core functionality controlled via I2C.
1687 config MFD_ARIZONA_SPI
1688 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1691 depends on SPI_MASTER
1693 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1694 audio SoC core functionality controlled via SPI.
1697 bool "Cirrus Logic CS47L24 and WM1831"
1698 depends on MFD_ARIZONA
1700 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1703 bool "Wolfson Microelectronics WM5102"
1704 depends on MFD_ARIZONA
1706 Support for Wolfson Microelectronics WM5102 low power audio SoC
1709 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1710 depends on MFD_ARIZONA
1712 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1716 bool "Wolfson Microelectronics WM8997"
1717 depends on MFD_ARIZONA
1719 Support for Wolfson Microelectronics WM8997 low power audio SoC
1722 bool "Wolfson Microelectronics WM8998"
1723 depends on MFD_ARIZONA
1725 Support for Wolfson Microelectronics WM8998 low power audio SoC
1728 bool "Wolfson Microelectronics WM8400"
1733 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1734 CODEC. This driver provides common support for accessing
1735 the device, additional drivers must be enabled in order to use
1736 the functionality of the device.
1741 config MFD_WM831X_I2C
1742 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1749 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1750 when controlled using I2C. This driver provides common support
1751 for accessing the device, additional drivers must be enabled in
1752 order to use the functionality of the device.
1754 config MFD_WM831X_SPI
1755 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1760 depends on SPI_MASTER
1762 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1763 when controlled using SPI. This driver provides common support
1764 for accessing the device, additional drivers must be enabled in
1765 order to use the functionality of the device.
1770 config MFD_WM8350_I2C
1771 bool "Wolfson Microelectronics WM8350 with I2C"
1776 The WM8350 is an integrated audio and power management
1777 subsystem with watchdog and RTC functionality for embedded
1778 systems. This option enables core support for the WM8350 with
1779 I2C as the control interface. Additional options must be
1780 selected to enable support for the functionality of the chip.
1783 tristate "Wolfson Microelectronics WM8994"
1789 The WM8994 is a highly integrated hi-fi CODEC designed for
1790 smartphone applications. As well as audio functionality it
1791 has on board GPIO and regulator functionality which is
1792 supported via the relevant subsystems. This driver provides
1793 core support for the WM8994, in order to use the actual
1794 functionaltiy of the device other drivers must be enabled.
1797 tristate "Wolfson Microelectronics WM97xx"
1800 select AC97_BUS_COMPAT
1801 depends on AC97_BUS_NEW
1803 The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1804 designed for smartphone applications. As well as audio functionality
1805 it has on board GPIO and a touchscreen functionality which is
1806 supported via the relevant subsystems. This driver provides core
1807 support for the WM97xx, in order to use the actual functionaltiy of
1808 the device other drivers must be enabled.
1811 tristate "Support for ST Microelectronics STw481x"
1812 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1816 Select this option to enable the STw481x chip driver used
1817 in various ST Microelectronics and ST-Ericsson embedded
1820 config MFD_ROHM_BD718XX
1821 tristate "ROHM BD71837 Power Management IC"
1828 Select this option to get support for the ROHM BD71837
1829 Power Management ICs. BD71837 is designed to power processors like
1830 NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
1831 and emergency shut down as well as 32,768KHz clock output.
1833 config MFD_STM32_LPTIMER
1834 tristate "Support for STM32 Low-Power Timer"
1835 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1840 Select this option to enable STM32 Low-Power Timer driver
1841 used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1842 resources are also dealt with here.
1844 To compile this driver as a module, choose M here: the
1845 module will be called stm32-lptimer.
1847 config MFD_STM32_TIMERS
1848 tristate "Support for STM32 Timers"
1849 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1854 Select this option to enable STM32 timers driver used
1855 for PWM and IIO Timer. This driver allow to share the
1856 registers between the others drivers.
1858 menu "Multimedia Capabilities Port drivers"
1859 depends on ARCH_SA1100
1866 tristate "Support SA11x0 MCP interface"
1867 depends on ARCH_SA1100
1872 tristate "Support for UCB1200 / UCB1300"
1873 depends on MCP_SA11X0
1876 config MCP_UCB1200_TS
1877 tristate "Touchscreen interface support"
1878 depends on MCP_UCB1200 && INPUT
1882 config MFD_VEXPRESS_SYSREG
1883 bool "Versatile Express System Registers"
1884 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1887 select GPIO_GENERIC_PLATFORM
1891 System Registers are the platform configuration block
1892 on the ARM Ltd. Versatile Express board.
1895 tristate "RAVE SP MCU core driver"
1896 depends on SERIAL_DEV_BUS
1899 Select this to get support for the Supervisory Processor
1900 device found on several devices in RAVE line of hardware.