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
50 Support for the AS3711 PMIC from AMS
53 tristate "ams AS3722 Power Management IC"
57 depends on I2C=y && OF
59 The ams AS3722 is a compact system PMU suitable for mobile phones,
60 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
61 controllers, 11 LDOs, RTC, automatic battery, temperature and
62 over current monitoring, GPIOs, ADC and a watchdog.
65 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
68 Say yes here to add support for Analog Devices AD5520 and ADP5501,
69 Multifunction Power Management IC. This includes
70 the I2C driver and the core APIs _only_, you have to select
71 individual components like LCD backlight, LEDs, GPIOs and Kepad
72 under the corresponding menus.
74 config MFD_AAT2870_CORE
75 bool "AnalogicTech AAT2870"
78 depends on GPIOLIB || COMPILE_TEST
80 If you say yes here you get support for the AAT2870.
81 This driver provides common support for accessing the device,
82 additional drivers must be enabled in order to use the
83 functionality of the device.
85 config MFD_ATMEL_FLEXCOM
86 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
90 Select this to get support for Atmel Flexcom. This is a wrapper
91 which embeds a SPI controller, a I2C controller and a USART. Only
92 one function can be used at a time. The choice is done at boot time
93 by the probe function of this MFD driver according to a device tree
96 config MFD_ATMEL_HLCDC
97 tristate "Atmel HLCDC (High-end LCD Controller)"
102 If you say yes here you get support for the HLCDC block.
103 This driver provides common support for accessing the device,
104 additional drivers must be enabled in order to use the
105 functionality of the device.
108 tristate "Broadcom BCM590xx PMUs"
113 Support for the BCM590xx PMUs from Broadcom
116 tristate "X-Powers AC100"
120 If you say Y here you get support for the X-Powers AC100 audio codec
122 This driver include only the core APIs. You have to select individual
123 components like codecs or RTC under the corresponding menus.
130 config MFD_AXP20X_I2C
131 tristate "X-Powers AXP series PMICs with I2C"
136 If you say Y here you get support for the X-Powers AXP series power
137 management ICs (PMICs) controlled with I2C.
138 This driver include only the core APIs. You have to select individual
139 components like regulators or the PEK (Power Enable Key) under the
142 config MFD_AXP20X_RSB
143 tristate "X-Powers AXP series PMICs with RSB"
147 If you say Y here you get support for the X-Powers AXP series power
148 management ICs (PMICs) controlled with RSB.
149 This driver include only the core APIs. You have to select individual
150 components like regulators or the PEK (Power Enable Key) under the
154 tristate "ChromeOS Embedded Controller"
156 select CHROME_PLATFORMS
158 depends on X86 || ARM || ARM64 || COMPILE_TEST
160 If you say Y here you get support for the ChromeOS Embedded
161 Controller (EC) providing keyboard, battery and power services.
162 You also need to enable the driver for the bus you are using. The
163 protocol for talking to the EC is defined by the bus driver.
165 config MFD_CROS_EC_I2C
166 tristate "ChromeOS Embedded Controller (I2C)"
167 depends on MFD_CROS_EC && I2C
170 If you say Y here, you get support for talking to the ChromeOS
171 EC through an I2C bus. This uses a simple byte-level protocol with
172 a checksum. Failing accesses will be retried three times to
175 config MFD_CROS_EC_SPI
176 tristate "ChromeOS Embedded Controller (SPI)"
177 depends on MFD_CROS_EC && SPI
180 If you say Y here, you get support for talking to the ChromeOS EC
181 through a SPI bus, using a byte-level protocol. Since the EC's
182 response time cannot be guaranteed, we support ignoring
183 'pre-amble' bytes before the response actually starts.
187 depends on GPIOLIB && ARM
190 This driver supports the ASIC3 multifunction chip found on many
191 PDAs (mainly iPAQ and HTC based ones)
194 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
197 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
198 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
199 usually found on PXA processors-based platforms. This includes
200 the I2C driver and the core APIs _only_, you have to select
201 individual components like LCD backlight, voltage regulators,
202 LEDs and battery-charger under the corresponding menus.
208 config MFD_DA9052_SPI
209 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
213 depends on SPI_MASTER=y
215 Support for the Dialog Semiconductor DA9052 PMIC
216 when controlled using SPI. This driver provides common support
217 for accessing the device, additional drivers must be enabled in
218 order to use the functionality of the device.
220 config MFD_DA9052_I2C
221 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
227 Support for the Dialog Semiconductor DA9052 PMIC
228 when controlled using I2C. This driver provides common support
229 for accessing the device, additional drivers must be enabled in
230 order to use the functionality of the device.
233 bool "Dialog Semiconductor DA9055 PMIC Support"
239 Say yes here for support of Dialog Semiconductor DA9055. This is
240 a Power Management IC. This driver provides common support for
241 accessing the device as well as the I2C interface to the chip itself.
242 Additional drivers must be enabled in order to use the functionality
245 This driver can be built as a module. If built as a module it will be
249 tristate "Dialog Semiconductor DA9062 PMIC Support"
255 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
256 This includes the I2C driver and core APIs.
257 Additional drivers must be enabled in order to use the functionality
261 tristate "Dialog Semiconductor DA9063 PMIC Support"
267 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
268 This includes the I2C driver and core APIs.
269 Additional drivers must be enabled in order to use the functionality
273 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
279 This adds support for the DA9150 integrated charger and fuel-gauge
280 chip. This driver provides common support for accessing the device.
281 Additional drivers must be enabled in order to use the specific
282 features of the device.
285 tristate "Diolan DLN2 support"
289 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
290 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
291 etc. must be enabled in order to use the functionality of
294 config MFD_EXYNOS_LPASS
295 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
299 Select this option to enable support for Samsung Exynos Low Power
304 depends on (SPI_MASTER || I2C)
308 Enable support for the Freescale MC13783 and MC13892 PMICs.
309 This driver provides common support for accessing the device,
310 additional drivers must be enabled in order to use the
311 functionality of the device.
313 config MFD_MC13XXX_SPI
314 tristate "Freescale MC13783 and MC13892 SPI interface"
315 depends on SPI_MASTER
319 Select this if your MC13xxx is connected via an SPI bus.
321 config MFD_MC13XXX_I2C
322 tristate "Freescale MC13892 I2C interface"
327 Select this if your MC13xxx is connected via an I2C bus.
329 config MFD_MX25_TSADC
330 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
332 depends on (SOC_IMX25 && OF) || COMPILE_TEST
334 Enable support for the integrated Touchscreen and ADC unit of the
335 i.MX25 processors. They consist of a conversion queue for general
336 purpose ADC and a queue for Touchscreens.
338 config MFD_HI6421_PMIC
339 tristate "HiSilicon Hi6421 PMU/Codec IC"
344 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
345 functions, such as regulators, RTC, codec, Coulomb counter, etc.
346 This driver includes core APIs _only_. You have to select
347 individul components like voltage regulators under corresponding
348 menus in order to enable them.
349 We communicate with the Hi6421 via memory-mapped I/O.
351 config MFD_HI655X_PMIC
352 tristate "HiSilicon Hi655X series PMU/Codec IC"
353 depends on ARCH_HISI || COMPILE_TEST
359 Select this option to enable Hisilicon hi655x series pmic driver.
362 tristate "HTC PASIC3 LED/DS1WM chip support"
365 This core driver provides register access for the LED/DS1WM
366 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
367 HTC Magician devices, respectively. Actual functionality is
368 handled by the leds-pasic3 and ds1wm drivers.
371 bool "HTC I2C PLD chip support"
372 depends on I2C=y && GPIOLIB
374 If you say yes here you get support for the supposed CPLD
375 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
376 This device provides input and output GPIOs through an I2C
377 interface to one or more sub-chips.
379 config MFD_INTEL_QUARK_I2C_GPIO
380 tristate "Intel Quark MFD I2C GPIO"
383 depends on COMMON_CLK
386 This MFD provides support for I2C and GPIO that exist only
387 in a single PCI device. It splits the 2 IO devices to
388 their respective IO driver.
389 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
392 tristate "Intel ICH LPC"
396 The LPC bridge function of the Intel ICH provides support for
397 many functional units. This driver provides needed support for
398 other drivers to control these functions, currently GPIO and
402 tristate "Intel SCH LPC"
406 LPC bridge function of the Intel SCH provides support for
407 System Management Bus and General Purpose I/O.
409 config INTEL_SOC_PMIC
410 bool "Support for Intel Atom SoC PMIC"
417 Select this option to enable support for the PMIC device
418 on some Intel SoC systems. The PMIC provides ADC, GPIO,
419 thermal, charger and related power management functions
422 config MFD_INTEL_LPSS
427 config MFD_INTEL_LPSS_ACPI
428 tristate "Intel Low Power Subsystem support in ACPI mode"
429 select MFD_INTEL_LPSS
430 depends on X86 && ACPI
432 This driver supports Intel Low Power Subsystem (LPSS) devices such as
433 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
436 config MFD_INTEL_LPSS_PCI
437 tristate "Intel Low Power Subsystem support in PCI mode"
438 select MFD_INTEL_LPSS
439 depends on X86 && PCI
441 This driver supports Intel Low Power Subsystem (LPSS) devices such as
442 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
445 config MFD_INTEL_MSIC
447 depends on INTEL_SCU_IPC
450 Select this option to enable access to Intel MSIC (Avatele
451 Passage) chip. This chip embeds audio, battery, GPIO, etc.
452 devices used in Intel Medfield platforms.
454 config MFD_IPAQ_MICRO
455 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
456 depends on SA1100_H3100 || SA1100_H3600
459 Select this to get support for the Microcontroller found in
460 the Compaq iPAQ handheld computers. This is an Atmel
461 AT90LS8535 microcontroller flashed with a special iPAQ
462 firmware using the custom protocol implemented in this driver.
464 config MFD_JANZ_CMODIO
465 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
469 This is the core driver for the Janz CMOD-IO PCI MODULbus
470 carrier board. This device is a PCI to MODULbus bridge which may
471 host many different types of MODULbus daughterboards, including
472 CAN and GPIO controllers.
474 config MFD_JZ4740_ADC
475 bool "Janz JZ4740 ADC core"
477 select GENERIC_IRQ_CHIP
478 depends on MACH_JZ4740
480 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
481 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
484 tristate "Kontron module PLD device"
487 This is the core driver for the PLD (Programmable Logic Device) found
488 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
489 device may provide functions like watchdog, GPIO, UART and I2C bus.
491 The following modules are supported:
495 * COMe-bPC2 (ETXexpress-PC)
496 * COMe-bSC# (ETXexpress-SC T#)
501 * COMe-cDC2 (microETXexpress-DC)
503 * COMe-cPC2 (microETXexpress-PC)
508 * COMe-mTT10 (nanoETXexpress-TT)
511 This driver can also be built as a module. If so, the module
512 will be called kempld-core.
515 tristate "Marvell 88PM800"
521 This supports for Marvell 88PM800 Power Management IC.
522 This includes the I2C driver and the core APIs _only_, you have to
523 select individual components like voltage regulators, RTC and
524 battery-charger under the corresponding menus.
527 tristate "Marvell 88PM805"
533 This supports for Marvell 88PM805 Power Management IC. This includes
534 the I2C driver and the core APIs _only_, you have to select individual
535 components like codec device, headset/Mic device under the
539 bool "Marvell 88PM8606/88PM8607"
544 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
545 This includes the I2C driver and the core APIs _only_, you have to
546 select individual components like voltage regulators, RTC and
547 battery-charger under the corresponding menus.
550 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
557 Say yes here to add support for Maxim Semiconductor MAX14577 and
558 MAX77836 Micro-USB ICs with battery charger.
559 This driver provides common support for accessing the device;
560 additional drivers must be enabled in order to use the functionality
564 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
572 Say yes here to add support for Maxim Semiconductor MAX77620 and
573 MAX20024 which are Power Management IC with General purpose pins,
574 RTC, regulators, clock generator, watchdog etc. This driver
575 provides common support for accessing the device; additional drivers
576 must be enabled in order to use the functionality of the device.
579 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
587 Say yes here to add support for Maxim Semiconductor MAX77686 and
588 MAX77802 which are Power Management IC with an RTC on chip.
589 This driver provides common support for accessing the device;
590 additional drivers must be enabled in order to use the functionality
594 tristate "Maxim Semiconductor MAX77693 PMIC Support"
600 Say yes here to add support for Maxim Semiconductor MAX77693.
601 This is a companion Power Management IC with Flash, Haptic, Charger,
602 and MUIC(Micro USB Interface Controller) controls on chip.
603 This driver provides common support for accessing the device;
604 additional drivers must be enabled in order to use the functionality
608 bool "Maxim Semiconductor MAX77843 PMIC Support"
614 Say yes here to add support for Maxim Semiconductor MAX77843.
615 This is companion Power Management IC with LEDs, Haptic, Charger,
616 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
617 This driver provides common support for accessing the device;
618 additional drivers must be enabled in order to use the functionality
622 tristate "Maxim Semiconductor MAX8907 PMIC Support"
628 Say yes here to add support for Maxim Semiconductor MAX8907. This is
629 a Power Management IC. This driver provides common support for
630 accessing the device; additional drivers must be enabled in order
631 to use the functionality of the device.
634 bool "Maxim Semiconductor MAX8925 PMIC Support"
638 Say yes here to add support for Maxim Semiconductor MAX8925. This is
639 a Power Management IC. This driver provides common support for
640 accessing the device, additional drivers must be enabled in order
641 to use the functionality of the device.
644 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
649 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
650 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
651 MUIC controls on chip.
652 This driver provides common support for accessing the device;
653 additional drivers must be enabled in order to use the functionality
657 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
662 Say yes here to add support for Maxim Semiconductor MAX8998 and
663 National Semiconductor LP3974. This is a Power Management IC.
664 This driver provides common support for accessing the device,
665 additional drivers must be enabled in order to use the functionality
669 tristate "MediaTek MT6397 PMIC Support"
673 Say yes here to add support for MediaTek MT6397 PMIC. This is
674 a Power Management IC. This driver provides common support for
675 accessing the device; additional drivers must be enabled in order
676 to use the functionality of the device.
679 tristate "MEN 14F021P00 Board Management Controller Support"
683 Say yes here to add support for the MEN 14F021P00 BMC
684 which is a Board Management Controller connected to the I2C bus.
685 The device supports multiple sub-devices like LED, HWMON and WDT.
686 This driver provides common support for accessing the devices;
687 additional drivers must be enabled in order to use the
688 functionality of the BMC device.
690 This driver can also be built as a module. If so the module
691 will be called menf21bmc.
694 bool "Motorola EZXPCAP Support"
695 depends on SPI_MASTER
697 This enables the PCAP ASIC present on EZX Phones. This is
698 needed for MMC, TouchScreen, Sound, USB, etc..
700 config MFD_VIPERBOARD
701 tristate "Nano River Technologies Viperboard"
706 Say yes here if you want support for Nano River Technologies
708 There are mfd cell drivers available for i2c master, adc and
709 both gpios found on the board. The spi part does not yet
711 You need to select the mfd cell drivers separately.
712 The drivers do not support all features the board exposes.
715 tristate "Nokia Retu and Tahvo multi-function device"
720 Retu and Tahvo are a multi-function devices found on Nokia
721 Internet Tablets (770, N800 and N810).
724 tristate "NXP PCF50633"
728 Say yes here if you have NXP PCF50633 chip on your board.
729 This core driver provides register access and IRQ handling
730 facilities, and registers devices for the various functions
731 so that function-specific drivers can bind to them.
734 tristate "NXP PCF50633 ADC"
735 depends on MFD_PCF50633
737 Say yes here if you want to include support for ADC in the
741 tristate "NXP PCF50633 GPIO"
742 depends on MFD_PCF50633
744 Say yes here if you want to include support GPIO for pins on
748 tristate "Philips UCB1400 Core driver"
752 This enables support for the Philips UCB1400 core functions.
753 The UCB1400 is an AC97 audio codec.
755 To compile this driver as a module, choose M here: the
756 module will be called ucb1400_core.
761 config MFD_PM8921_CORE
762 tristate "Qualcomm PM8921 PMIC chip"
763 depends on (ARM || HEXAGON)
769 If you say yes to this option, support will be included for the
770 built-in PM8921 PMIC chip.
772 This is required if your board has a PM8921 and uses its features,
773 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
775 Say M here if you want to include support for PM8921 chip as a module.
776 This will build a module called "pm8921-core".
779 tristate "Qualcomm Resource Power Manager (RPM)"
780 depends on ARCH_QCOM && OF
782 If you say yes to this option, support will be included for the
783 Resource Power Manager system found in the Qualcomm 8660, 8960 and
786 This is required to access many regulators, clocks and bus
787 frequencies controlled by the RPM on these devices.
789 Say M here if you want to include support for the Qualcomm RPM as a
790 module. This will build a module called "qcom_rpm".
793 tristate "Qualcomm SPMI PMICs"
794 depends on ARCH_QCOM || COMPILE_TEST
799 This enables support for the Qualcomm SPMI PMICs.
800 These PMICs are currently used with the Snapdragon 800 series of
801 SoCs. Note, that this will only be useful paired with descriptions
802 of the independent functions as children nodes in the device tree.
804 Say M here if you want to include support for the SPMI PMIC
805 series as a module. The module will be called "qcom-spmi-pmic".
808 tristate "RDC R-321x southbridge"
812 Say yes here if you want to have support for the RDC R-321x SoC
813 southbridge which provides access to GPIOs and Watchdog using the
814 southbridge PCI device configuration space.
817 tristate "Realtek PCI-E card reader"
821 This supports for Realtek PCI-Express card reader including rts5209,
822 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
823 Realtek card reader supports access to many types of memory cards,
824 such as Memory Stick, Memory Stick Pro, Secure Digital and
828 tristate "Richtek RT5033 Power Management IC"
834 This driver provides for the Richtek RT5033 Power Management IC,
835 which includes the I2C driver and the Core APIs. This driver provides
836 common support for accessing the device. The device supports multiple
837 sub-devices like charger, fuel gauge, flash LED, current source,
841 tristate "Realtek USB card reader"
845 Select this option to get support for Realtek USB 2.0 card readers
846 including RTS5129, RTS5139, RTS5179 and RTS5170.
847 Realtek card reader supports access to many types of memory cards,
848 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
851 bool "Ricoh RC5T583 Power Management system device"
856 Select this option to get support for the RICOH583 Power
857 Management system device.
858 This driver provides common support for accessing the device
859 through i2c interface. The device supports multiple sub-devices
860 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
861 Additional drivers must be enabled in order to use the
862 different functionality of the device.
865 tristate "Rockchip RK808/RK818 Power Management Chip"
871 If you say yes here you get support for the RK808 and RK818
872 Power Management chips.
873 This driver provides common support for accessing the device
874 through I2C interface. The device supports multiple sub-devices
875 including interrupts, RTC, LDO & DCDC regulators, and onkey.
878 tristate "Ricoh RN5T567/618 PMIC"
884 Say yes here to add support for the Ricoh RN5T567 or R5T618 PMIC.
885 This driver provides common support for accessing the device,
886 additional drivers must be enabled in order to use the
887 functionality of the device.
890 bool "SAMSUNG Electronics PMIC Series Support"
896 Support for the Samsung Electronics MFD series.
897 This driver provides common support for accessing the device,
898 additional drivers must be enabled in order to use the functionality
901 config MFD_SI476X_CORE
902 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
907 This is the core driver for the SI476x series of AM/FM
908 radio. This MFD driver connects the radio-si476x V4L2 module
909 and the si476x audio codec.
911 To compile this driver as a module, choose M here: the
912 module will be called si476x-core.
915 tristate "Silicon Motion SM501"
917 This is the core driver for the Silicon Motion SM501 multimedia
918 companion chip. This device is a multifunction device which may
919 provide numerous interfaces including USB host controller, USB gadget,
920 asynchronous serial ports, audio functions, and a dual display video
921 interface. The device may be connected by PCI or local bus with
922 varying functions enabled.
924 config MFD_SM501_GPIO
925 bool "Export GPIO via GPIO layer"
926 depends on MFD_SM501 && GPIOLIB
928 This option uses the gpio library layer to export the 64 GPIO
929 lines on the SM501. The platform data is used to supply the
930 base number for the first GPIO line to register.
933 tristate "Skyworks Solutions SKY81452"
938 This is the core driver for the Skyworks SKY81452 backlight and
939 voltage regulator device.
941 This driver can also be built as a module. If so, the module
942 will be called sky81452.
945 bool "SMSC ECE1099 series chips"
950 If you say yes here you get support for the
951 ece1099 chips from SMSC.
953 To compile this driver as a module, choose M here: the
954 module will be called smsc.
957 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
958 default y if ARCH_U300 || ARCH_U8500
960 Say yes here if you have the ABX500 Mixed Signal IC family
961 chips. This core driver expose register access functions.
962 Functionality specific drivers using these functions can
963 remain unchanged when IC changes. Binding of the functions to
964 actual register access is done by the IC core driver.
967 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
968 depends on I2C=y && ABX500_CORE
970 default y if ARCH_U300
972 Select this to enable the AB3100 Mixed Signal IC core
973 functionality. This connects to a AB3100 on the I2C bus
974 and expose a number of symbols needed for dependent devices
975 to read and write registers and subscribe to events from
976 this multi-functional IC. This is needed to use other features
977 of the AB3100 such as battery-backed RTC, charging control,
978 LEDs, vibrator, system power and temperature, power management
982 tristate "ST-Ericsson AB3100 OTP functions"
983 depends on AB3100_CORE
984 default y if AB3100_CORE
986 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
987 programmable memory) support. This exposes a sysfs file to read
991 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
992 depends on ABX500_CORE && MFD_DB8500_PRCMU
997 Select this option to enable access to AB8500 power management
998 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
999 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1000 the irq_chip parts for handling the Mixed Signal chip events.
1001 This chip embeds various other multimedia funtionalities as well.
1004 bool "Enable debug info via debugfs"
1005 depends on AB8500_GPADC && DEBUG_FS
1006 default y if DEBUG_FS
1008 Select this option if you want debug information using the debug
1009 filesystem, debugfs.
1012 bool "ST-Ericsson AB8500 GPADC driver"
1013 depends on AB8500_CORE && REGULATOR_AB8500
1016 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1018 config MFD_DB8500_PRCMU
1019 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1020 depends on UX500_SOC_DB8500
1023 Select this option to enable support for the DB8500 Power Reset
1024 and Control Management Unit. This is basically an autonomous
1025 system controller running an XP70 microprocessor, which is accessed
1026 through a register map.
1029 bool "STMicroelectronics STMPE"
1030 depends on (I2C=y || SPI_MASTER=y)
1034 Support for the STMPE family of I/O Expanders from
1037 Currently supported devices are:
1039 STMPE811: GPIO, Touchscreen
1040 STMPE1601: GPIO, Keypad
1041 STMPE1801: GPIO, Keypad
1042 STMPE2401: GPIO, Keypad
1043 STMPE2403: GPIO, Keypad
1045 This driver provides common support for accessing the device,
1046 additional drivers must be enabled in order to use the functionality
1047 of the device. Currently available sub drivers are:
1050 Keypad: stmpe-keypad
1051 Touchscreen: stmpe-ts
1053 menu "STMicroelectronics STMPE Interface Drivers"
1054 depends on MFD_STMPE
1057 bool "STMicroelectronics STMPE I2C Interface"
1061 This is used to enable I2C interface of STMPE
1064 bool "STMicroelectronics STMPE SPI Interface"
1065 depends on SPI_MASTER
1067 This is used to enable SPI interface of STMPE
1071 bool "STMicroelectronics STA2X11"
1076 config MFD_SUN6I_PRCM
1077 bool "Allwinner A31 PRCM controller"
1078 depends on ARCH_SUNXI
1081 Support for the PRCM (Power/Reset/Clock Management) unit available
1085 bool "System Controller Register R/W Based on Regmap"
1088 Select this option to enable accessing system control registers
1091 config MFD_DAVINCI_VOICECODEC
1096 config MFD_TI_AM335X_TSCADC
1097 tristate "TI ADC / Touch Screen chip support"
1102 If you say yes here you get support for Texas Instruments series
1103 of Touch Screen /ADC chips.
1104 To compile this driver as a module, choose M here: the
1105 module will be called ti_am335x_tscadc.
1107 config MFD_DM355EVM_MSP
1108 bool "TI DaVinci DM355 EVM microcontroller"
1109 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1111 This driver supports the MSP430 microcontroller used on these
1112 boards. MSP430 firmware manages resets and power sequencing,
1113 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1116 tristate "TI/National Semiconductor LP3943 MFD Driver"
1121 Support for the TI/National Semiconductor LP3943.
1122 This driver consists of GPIO and PWM drivers.
1123 With these functionalities, it can be used for LED string control or
1124 general usage such like a GPIO controller and a PWM controller.
1127 bool "TI LP8788 Power Management Unit Driver"
1133 TI LP8788 PMU supports regulators, battery charger, RTC,
1134 ADC, backlight driver and current sinks.
1136 config MFD_OMAP_USB_HOST
1137 bool "TI OMAP USBHS core and TLL driver"
1138 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1141 This is the core driver for the OAMP EHCI and OHCI drivers.
1142 This MFD driver does the required setup functionalities for
1143 OMAP USB Host drivers.
1146 bool "TI Palmas series chips"
1152 If you say yes here you get support for the Palmas
1153 series of PMIC chips from Texas Instruments.
1156 tristate "TI TPS61050/61052 Boost Converters"
1161 select REGULATOR_FIXED_VOLTAGE
1163 This option enables a driver for the TP61050/TPS61052
1164 high-power "white LED driver". This boost converter is
1165 sometimes used for other things than white LEDs, and
1166 also contains a GPIO pin.
1169 tristate "TI TPS6501x Power Management chips"
1170 depends on I2C && GPIOLIB
1171 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1173 If you say yes here you get support for the TPS6501x series of
1174 Power Management chips. These include voltage regulators,
1175 lithium ion/polymer battery charging, and other features that
1176 are often used in portable devices like cell phones and cameras.
1178 This driver can also be built as a module. If so, the module
1179 will be called tps65010.
1182 tristate "TI TPS6507x Power Management / Touch Screen chips"
1186 If you say yes here you get support for the TPS6507x series of
1187 Power Management / Touch Screen chips. These include voltage
1188 regulators, lithium ion/polymer battery charging, touch screen
1189 and other features that are often used in portable devices.
1190 This driver can also be built as a module. If so, the module
1191 will be called tps6507x.
1194 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1200 If you say yes here you get support for the TPS65086 series of
1201 Power Management chips.
1202 This driver provides common support for accessing the device,
1203 additional drivers must be enabled in order to use the
1204 functionality of the device.
1206 config TPS65911_COMPARATOR
1210 bool "TI TPS65090 Power Management chips"
1216 If you say yes here you get support for the TPS65090 series of
1217 Power Management chips.
1218 This driver provides common support for accessing the device,
1219 additional drivers must be enabled in order to use the
1220 functionality of the device.
1223 tristate "TI TPS65217 Power Management / White LED chips"
1229 If you say yes here you get support for the TPS65217 series of
1230 Power Management / White LED chips.
1231 These include voltage regulators, lithium ion/polymer battery
1232 charger, wled and other features that are often used in portable
1235 This driver can also be built as a module. If so, the module
1236 will be called tps65217.
1238 config MFD_TI_LP873X
1239 tristate "TI LP873X Power Management IC"
1244 If you say yes here then you get support for the LP873X series of
1245 Power Management Integrated Circuits (PMIC).
1246 These include voltage regulators, thermal protection, configurable
1247 General Purpose Outputs (GPO) that are used in portable devices.
1249 This driver can also be built as a module. If so, the module
1250 will be called lp873x.
1253 tristate "TI TPS65218 Power Management chips"
1259 If you say yes here you get support for the TPS65218 series of
1260 Power Management chips.
1261 These include voltage regulators, gpio and other features
1262 that are often used in portable devices. Only regulator
1263 component is currently supported.
1265 This driver can also be built as a module. If so, the module
1266 will be called tps65218.
1269 bool "TI TPS6586x Power Management chips"
1274 If you say yes here you get support for the TPS6586X series of
1275 Power Management chips.
1276 This driver provides common support for accessing the device,
1277 additional drivers must be enabled in order to use the
1278 functionality of the device.
1280 This driver can also be built as a module. If so, the module
1281 will be called tps6586x.
1284 bool "TI TPS65910 Power Management chip"
1286 depends on GPIOLIB || COMPILE_TEST
1292 if you say yes here you get support for the TPS65910 series of
1293 Power Management chips.
1301 config MFD_TPS65912_I2C
1302 tristate "TI TPS65912 Power Management chip with I2C"
1307 If you say yes here you get support for the TPS65912 series of
1308 PM chips with I2C interface.
1310 config MFD_TPS65912_SPI
1311 tristate "TI TPS65912 Power Management chip with SPI"
1314 depends on SPI_MASTER
1316 If you say yes here you get support for the TPS65912 series of
1317 PM chips with SPI interface.
1320 bool "TI TPS80031/TPS80032 Power Management chips"
1326 If you say yes here you get support for the Texas Instruments
1327 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1328 Path and Battery Charger. The device provides five configurable
1329 step-down converters, 11 general purpose LDOs, USB OTG Module,
1330 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1331 Power Path from USB, 32K clock generator.
1334 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1339 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1340 This core driver provides register access and IRQ handling
1341 facilities, and registers devices for the various functions
1342 so that function-specific drivers can bind to them.
1344 These multi-function chips are found on many OMAP2 and OMAP3
1345 boards, providing power management, RTC, GPIO, keypad, a
1346 high speed USB OTG transceiver, an audio codec (on most
1347 versions) and many other features.
1349 config TWL4030_POWER
1350 bool "TI TWL4030 power resources"
1351 depends on TWL4030_CORE && ARM
1353 Say yes here if you want to use the power resources on the
1354 TWL4030 family chips. Most of these resources are regulators,
1355 which have a separate driver; some are control signals, such
1356 as clock request handshaking.
1358 This driver uses board-specific data to initialize the resources
1359 and load scripts controlling which resources are switched off/on
1360 or reset when a sleep, wakeup or warm reset event occurs.
1362 config MFD_TWL4030_AUDIO
1363 bool "TI TWL4030 Audio"
1364 depends on TWL4030_CORE
1369 bool "TI TWL6040 audio codec"
1376 Say yes here if you want support for Texas Instruments TWL6040 audio
1378 This driver provides common support for accessing the device,
1379 additional drivers must be enabled in order to use the
1380 functionality of the device (audio, vibra).
1383 bool "TI TWL92330/Menelaus PM chip"
1384 depends on I2C=y && ARCH_OMAP2
1386 If you say yes here you get support for the Texas Instruments
1387 TWL92330/Menelaus Power Management chip. This include voltage
1388 regulators, Dual slot memory card transceivers, real-time clock
1389 and other features that are often used in portable devices like
1390 cell phones and PDAs.
1392 config MFD_WL1273_CORE
1393 tristate "TI WL1273 FM radio"
1398 This is the core driver for the TI WL1273 FM radio. This MFD
1399 driver connects the radio-wl1273 V4L2 module and the wl1273
1403 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1408 Say yes here to enable support for National Semiconductor / TI
1409 LM3533 Lighting Power chips.
1411 This driver provides common support for accessing the device;
1412 additional drivers must be enabled in order to use the LED,
1413 backlight or ambient-light-sensor functionality of the device.
1415 config MFD_TIMBERDALE
1416 tristate "Timberdale FPGA"
1418 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1420 This is the core driver for the timberdale FPGA. This device is a
1421 multifunction device which exposes numerous platform devices.
1423 The timberdale FPGA can be found on the Intel Atom development board
1424 for in-vehicle infontainment, called Russellville.
1427 bool "Toshiba TC35892 and variants"
1432 Support for the Toshiba TC35892 and variants I/O Expander.
1434 This driver provides common support for accessing the device,
1435 additional drivers must be enabled in order to use the
1436 functionality of the device.
1443 bool "Toshiba T7L66XB"
1444 depends on ARM && HAVE_CLK
1448 Support for Toshiba Mobile IO Controller T7L66XB
1451 bool "Toshiba TC6387XB"
1452 depends on ARM && HAVE_CLK
1456 Support for Toshiba Mobile IO Controller TC6387XB
1459 bool "Toshiba TC6393XB"
1460 depends on ARM && HAVE_CLK
1465 Support for Toshiba Mobile IO Controller TC6393XB
1468 tristate "VIA VX855/VX875 integrated south bridge"
1472 Say yes here to enable support for various functions of the
1473 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1474 and/or vx855_gpio drivers for this to do anything useful.
1482 config MFD_ARIZONA_I2C
1483 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1488 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1489 audio SoC core functionality controlled via I2C.
1491 config MFD_ARIZONA_SPI
1492 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1495 depends on SPI_MASTER
1497 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1498 audio SoC core functionality controlled via SPI.
1501 bool "Cirrus Logic CS47L24 and WM1831"
1502 depends on MFD_ARIZONA
1504 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1507 bool "Wolfson Microelectronics WM5102"
1508 depends on MFD_ARIZONA
1510 Support for Wolfson Microelectronics WM5102 low power audio SoC
1513 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1514 depends on MFD_ARIZONA
1516 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1520 bool "Wolfson Microelectronics WM8997"
1521 depends on MFD_ARIZONA
1523 Support for Wolfson Microelectronics WM8997 low power audio SoC
1526 bool "Wolfson Microelectronics WM8998"
1527 depends on MFD_ARIZONA
1529 Support for Wolfson Microelectronics WM8998 low power audio SoC
1532 bool "Wolfson Microelectronics WM8400"
1537 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1538 CODEC. This driver provides common support for accessing
1539 the device, additional drivers must be enabled in order to use
1540 the functionality of the device.
1545 config MFD_WM831X_I2C
1546 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1553 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1554 when controlled using I2C. This driver provides common support
1555 for accessing the device, additional drivers must be enabled in
1556 order to use the functionality of the device.
1558 config MFD_WM831X_SPI
1559 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1564 depends on SPI_MASTER
1566 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1567 when controlled using SPI. This driver provides common support
1568 for accessing the device, additional drivers must be enabled in
1569 order to use the functionality of the device.
1574 config MFD_WM8350_I2C
1575 bool "Wolfson Microelectronics WM8350 with I2C"
1580 The WM8350 is an integrated audio and power management
1581 subsystem with watchdog and RTC functionality for embedded
1582 systems. This option enables core support for the WM8350 with
1583 I2C as the control interface. Additional options must be
1584 selected to enable support for the functionality of the chip.
1587 tristate "Wolfson Microelectronics WM8994"
1593 The WM8994 is a highly integrated hi-fi CODEC designed for
1594 smartphone applications. As well as audio functionality it
1595 has on board GPIO and regulator functionality which is
1596 supported via the relevant subsystems. This driver provides
1597 core support for the WM8994, in order to use the actual
1598 functionaltiy of the device other drivers must be enabled.
1601 tristate "Support for ST Microelectronics STw481x"
1602 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1606 Select this option to enable the STw481x chip driver used
1607 in various ST Microelectronics and ST-Ericsson embedded
1610 menu "Multimedia Capabilities Port drivers"
1611 depends on ARCH_SA1100
1618 tristate "Support SA11x0 MCP interface"
1619 depends on ARCH_SA1100
1624 tristate "Support for UCB1200 / UCB1300"
1625 depends on MCP_SA11X0
1628 config MCP_UCB1200_TS
1629 tristate "Touchscreen interface support"
1630 depends on MCP_UCB1200 && INPUT
1634 config MFD_VEXPRESS_SYSREG
1635 bool "Versatile Express System Registers"
1636 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1639 select GPIO_GENERIC_PLATFORM
1643 System Registers are the platform configuration block
1644 on the ARM Ltd. Versatile Express board.