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 bool "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 bool "HTC EGPIO support"
363 depends on GPIOLIB && ARM
365 This driver supports the CPLD egpio chip present on
366 several HTC phones. It provides basic support for input
367 pins, output pins, and irqs.
370 tristate "HTC PASIC3 LED/DS1WM chip support"
373 This core driver provides register access for the LED/DS1WM
374 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
375 HTC Magician devices, respectively. Actual functionality is
376 handled by the leds-pasic3 and ds1wm drivers.
379 bool "HTC I2C PLD chip support"
380 depends on I2C=y && GPIOLIB
382 If you say yes here you get support for the supposed CPLD
383 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
384 This device provides input and output GPIOs through an I2C
385 interface to one or more sub-chips.
387 config MFD_INTEL_QUARK_I2C_GPIO
388 tristate "Intel Quark MFD I2C GPIO"
391 depends on COMMON_CLK
394 This MFD provides support for I2C and GPIO that exist only
395 in a single PCI device. It splits the 2 IO devices to
396 their respective IO driver.
397 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
400 tristate "Intel ICH LPC"
404 The LPC bridge function of the Intel ICH provides support for
405 many functional units. This driver provides needed support for
406 other drivers to control these functions, currently GPIO and
410 tristate "Intel SCH LPC"
414 LPC bridge function of the Intel SCH provides support for
415 System Management Bus and General Purpose I/O.
417 config INTEL_SOC_PMIC
418 bool "Support for Intel Atom SoC PMIC"
425 Select this option to enable support for the PMIC device
426 on some Intel SoC systems. The PMIC provides ADC, GPIO,
427 thermal, charger and related power management functions
430 config MFD_INTEL_LPSS
435 config MFD_INTEL_LPSS_ACPI
436 tristate "Intel Low Power Subsystem support in ACPI mode"
437 select MFD_INTEL_LPSS
438 depends on X86 && ACPI
440 This driver supports Intel Low Power Subsystem (LPSS) devices such as
441 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
444 config MFD_INTEL_LPSS_PCI
445 tristate "Intel Low Power Subsystem support in PCI mode"
446 select MFD_INTEL_LPSS
447 depends on X86 && PCI
449 This driver supports Intel Low Power Subsystem (LPSS) devices such as
450 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
453 config MFD_INTEL_MSIC
455 depends on INTEL_SCU_IPC
458 Select this option to enable access to Intel MSIC (Avatele
459 Passage) chip. This chip embeds audio, battery, GPIO, etc.
460 devices used in Intel Medfield platforms.
462 config MFD_IPAQ_MICRO
463 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
464 depends on SA1100_H3100 || SA1100_H3600
467 Select this to get support for the Microcontroller found in
468 the Compaq iPAQ handheld computers. This is an Atmel
469 AT90LS8535 microcontroller flashed with a special iPAQ
470 firmware using the custom protocol implemented in this driver.
472 config MFD_JANZ_CMODIO
473 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
477 This is the core driver for the Janz CMOD-IO PCI MODULbus
478 carrier board. This device is a PCI to MODULbus bridge which may
479 host many different types of MODULbus daughterboards, including
480 CAN and GPIO controllers.
482 config MFD_JZ4740_ADC
483 bool "Janz JZ4740 ADC core"
485 select GENERIC_IRQ_CHIP
486 depends on MACH_JZ4740
488 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
489 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
492 tristate "Kontron module PLD device"
495 This is the core driver for the PLD (Programmable Logic Device) found
496 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
497 device may provide functions like watchdog, GPIO, UART and I2C bus.
499 The following modules are supported:
503 * COMe-bPC2 (ETXexpress-PC)
504 * COMe-bSC# (ETXexpress-SC T#)
509 * COMe-cDC2 (microETXexpress-DC)
511 * COMe-cPC2 (microETXexpress-PC)
516 * COMe-mTT10 (nanoETXexpress-TT)
519 This driver can also be built as a module. If so, the module
520 will be called kempld-core.
523 tristate "Marvell 88PM800"
529 This supports for Marvell 88PM800 Power Management IC.
530 This includes the I2C driver and the core APIs _only_, you have to
531 select individual components like voltage regulators, RTC and
532 battery-charger under the corresponding menus.
535 tristate "Marvell 88PM805"
541 This supports for Marvell 88PM805 Power Management IC. This includes
542 the I2C driver and the core APIs _only_, you have to select individual
543 components like codec device, headset/Mic device under the
547 bool "Marvell 88PM8606/88PM8607"
552 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
553 This includes the I2C driver and the core APIs _only_, you have to
554 select individual components like voltage regulators, RTC and
555 battery-charger under the corresponding menus.
558 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
565 Say yes here to add support for Maxim Semiconductor MAX14577 and
566 MAX77836 Micro-USB ICs with battery charger.
567 This driver provides common support for accessing the device;
568 additional drivers must be enabled in order to use the functionality
572 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
580 Say yes here to add support for Maxim Semiconductor MAX77620 and
581 MAX20024 which are Power Management IC with General purpose pins,
582 RTC, regulators, clock generator, watchdog etc. This driver
583 provides common support for accessing the device; additional drivers
584 must be enabled in order to use the functionality of the device.
587 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
595 Say yes here to add support for Maxim Semiconductor MAX77686 and
596 MAX77802 which are Power Management IC with an RTC on chip.
597 This driver provides common support for accessing the device;
598 additional drivers must be enabled in order to use the functionality
602 tristate "Maxim Semiconductor MAX77693 PMIC Support"
608 Say yes here to add support for Maxim Semiconductor MAX77693.
609 This is a companion Power Management IC with Flash, Haptic, Charger,
610 and MUIC(Micro USB Interface Controller) controls on chip.
611 This driver provides common support for accessing the device;
612 additional drivers must be enabled in order to use the functionality
616 bool "Maxim Semiconductor MAX77843 PMIC Support"
622 Say yes here to add support for Maxim Semiconductor MAX77843.
623 This is companion Power Management IC with LEDs, Haptic, Charger,
624 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
625 This driver provides common support for accessing the device;
626 additional drivers must be enabled in order to use the functionality
630 tristate "Maxim Semiconductor MAX8907 PMIC Support"
636 Say yes here to add support for Maxim Semiconductor MAX8907. This is
637 a Power Management IC. This driver provides common support for
638 accessing the device; additional drivers must be enabled in order
639 to use the functionality of the device.
642 bool "Maxim Semiconductor MAX8925 PMIC Support"
646 Say yes here to add support for Maxim Semiconductor MAX8925. This is
647 a Power Management IC. This driver provides common support for
648 accessing the device, additional drivers must be enabled in order
649 to use the functionality of the device.
652 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
657 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
658 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
659 MUIC controls on chip.
660 This driver provides common support for accessing the device;
661 additional drivers must be enabled in order to use the functionality
665 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
670 Say yes here to add support for Maxim Semiconductor MAX8998 and
671 National Semiconductor LP3974. This is a Power Management IC.
672 This driver provides common support for accessing the device,
673 additional drivers must be enabled in order to use the functionality
677 tristate "MediaTek MT6397 PMIC Support"
681 Say yes here to add support for MediaTek MT6397 PMIC. This is
682 a Power Management IC. This driver provides common support for
683 accessing the device; additional drivers must be enabled in order
684 to use the functionality of the device.
687 tristate "MEN 14F021P00 Board Management Controller Support"
691 Say yes here to add support for the MEN 14F021P00 BMC
692 which is a Board Management Controller connected to the I2C bus.
693 The device supports multiple sub-devices like LED, HWMON and WDT.
694 This driver provides common support for accessing the devices;
695 additional drivers must be enabled in order to use the
696 functionality of the BMC device.
698 This driver can also be built as a module. If so the module
699 will be called menf21bmc.
702 bool "Motorola EZXPCAP Support"
703 depends on SPI_MASTER
705 This enables the PCAP ASIC present on EZX Phones. This is
706 needed for MMC, TouchScreen, Sound, USB, etc..
708 config MFD_VIPERBOARD
709 tristate "Nano River Technologies Viperboard"
714 Say yes here if you want support for Nano River Technologies
716 There are mfd cell drivers available for i2c master, adc and
717 both gpios found on the board. The spi part does not yet
719 You need to select the mfd cell drivers separately.
720 The drivers do not support all features the board exposes.
723 tristate "Nokia Retu and Tahvo multi-function device"
728 Retu and Tahvo are a multi-function devices found on Nokia
729 Internet Tablets (770, N800 and N810).
732 tristate "NXP PCF50633"
736 Say yes here if you have NXP PCF50633 chip on your board.
737 This core driver provides register access and IRQ handling
738 facilities, and registers devices for the various functions
739 so that function-specific drivers can bind to them.
742 tristate "NXP PCF50633 ADC"
743 depends on MFD_PCF50633
745 Say yes here if you want to include support for ADC in the
749 tristate "NXP PCF50633 GPIO"
750 depends on MFD_PCF50633
752 Say yes here if you want to include support GPIO for pins on
756 tristate "Philips UCB1400 Core driver"
760 This enables support for the Philips UCB1400 core functions.
761 The UCB1400 is an AC97 audio codec.
763 To compile this driver as a module, choose M here: the
764 module will be called ucb1400_core.
769 config MFD_PM8921_CORE
770 tristate "Qualcomm PM8921 PMIC chip"
771 depends on (ARM || HEXAGON)
777 If you say yes to this option, support will be included for the
778 built-in PM8921 PMIC chip.
780 This is required if your board has a PM8921 and uses its features,
781 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
783 Say M here if you want to include support for PM8921 chip as a module.
784 This will build a module called "pm8921-core".
787 tristate "Qualcomm Resource Power Manager (RPM)"
788 depends on ARCH_QCOM && OF
790 If you say yes to this option, support will be included for the
791 Resource Power Manager system found in the Qualcomm 8660, 8960 and
794 This is required to access many regulators, clocks and bus
795 frequencies controlled by the RPM on these devices.
797 Say M here if you want to include support for the Qualcomm RPM as a
798 module. This will build a module called "qcom_rpm".
801 tristate "Qualcomm SPMI PMICs"
802 depends on ARCH_QCOM || COMPILE_TEST
807 This enables support for the Qualcomm SPMI PMICs.
808 These PMICs are currently used with the Snapdragon 800 series of
809 SoCs. Note, that this will only be useful paired with descriptions
810 of the independent functions as children nodes in the device tree.
812 Say M here if you want to include support for the SPMI PMIC
813 series as a module. The module will be called "qcom-spmi-pmic".
816 tristate "RDC R-321x southbridge"
820 Say yes here if you want to have support for the RDC R-321x SoC
821 southbridge which provides access to GPIOs and Watchdog using the
822 southbridge PCI device configuration space.
825 tristate "Realtek PCI-E card reader"
829 This supports for Realtek PCI-Express card reader including rts5209,
830 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
831 Realtek card reader supports access to many types of memory cards,
832 such as Memory Stick, Memory Stick Pro, Secure Digital and
836 tristate "Richtek RT5033 Power Management IC"
842 This driver provides for the Richtek RT5033 Power Management IC,
843 which includes the I2C driver and the Core APIs. This driver provides
844 common support for accessing the device. The device supports multiple
845 sub-devices like charger, fuel gauge, flash LED, current source,
849 tristate "Realtek USB card reader"
853 Select this option to get support for Realtek USB 2.0 card readers
854 including RTS5129, RTS5139, RTS5179 and RTS5170.
855 Realtek card reader supports access to many types of memory cards,
856 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
859 bool "Ricoh RC5T583 Power Management system device"
864 Select this option to get support for the RICOH583 Power
865 Management system device.
866 This driver provides common support for accessing the device
867 through i2c interface. The device supports multiple sub-devices
868 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
869 Additional drivers must be enabled in order to use the
870 different functionality of the device.
873 tristate "Rockchip RK808/RK818 Power Management Chip"
879 If you say yes here you get support for the RK808 and RK818
880 Power Management chips.
881 This driver provides common support for accessing the device
882 through I2C interface. The device supports multiple sub-devices
883 including interrupts, RTC, LDO & DCDC regulators, and onkey.
886 tristate "Ricoh RN5T567/618 PMIC"
892 Say yes here to add support for the Ricoh RN5T567 or R5T618 PMIC.
893 This driver provides common support for accessing the device,
894 additional drivers must be enabled in order to use the
895 functionality of the device.
898 bool "SAMSUNG Electronics PMIC Series Support"
904 Support for the Samsung Electronics MFD series.
905 This driver provides common support for accessing the device,
906 additional drivers must be enabled in order to use the functionality
909 config MFD_SI476X_CORE
910 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
915 This is the core driver for the SI476x series of AM/FM
916 radio. This MFD driver connects the radio-si476x V4L2 module
917 and the si476x audio codec.
919 To compile this driver as a module, choose M here: the
920 module will be called si476x-core.
923 tristate "Silicon Motion SM501"
925 This is the core driver for the Silicon Motion SM501 multimedia
926 companion chip. This device is a multifunction device which may
927 provide numerous interfaces including USB host controller, USB gadget,
928 asynchronous serial ports, audio functions, and a dual display video
929 interface. The device may be connected by PCI or local bus with
930 varying functions enabled.
932 config MFD_SM501_GPIO
933 bool "Export GPIO via GPIO layer"
934 depends on MFD_SM501 && GPIOLIB
936 This option uses the gpio library layer to export the 64 GPIO
937 lines on the SM501. The platform data is used to supply the
938 base number for the first GPIO line to register.
941 tristate "Skyworks Solutions SKY81452"
946 This is the core driver for the Skyworks SKY81452 backlight and
947 voltage regulator device.
949 This driver can also be built as a module. If so, the module
950 will be called sky81452.
953 bool "SMSC ECE1099 series chips"
958 If you say yes here you get support for the
959 ece1099 chips from SMSC.
961 To compile this driver as a module, choose M here: the
962 module will be called smsc.
965 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
966 default y if ARCH_U300 || ARCH_U8500
968 Say yes here if you have the ABX500 Mixed Signal IC family
969 chips. This core driver expose register access functions.
970 Functionality specific drivers using these functions can
971 remain unchanged when IC changes. Binding of the functions to
972 actual register access is done by the IC core driver.
975 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
976 depends on I2C=y && ABX500_CORE
978 default y if ARCH_U300
980 Select this to enable the AB3100 Mixed Signal IC core
981 functionality. This connects to a AB3100 on the I2C bus
982 and expose a number of symbols needed for dependent devices
983 to read and write registers and subscribe to events from
984 this multi-functional IC. This is needed to use other features
985 of the AB3100 such as battery-backed RTC, charging control,
986 LEDs, vibrator, system power and temperature, power management
990 tristate "ST-Ericsson AB3100 OTP functions"
991 depends on AB3100_CORE
992 default y if AB3100_CORE
994 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
995 programmable memory) support. This exposes a sysfs file to read
999 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1000 depends on ABX500_CORE && MFD_DB8500_PRCMU
1005 Select this option to enable access to AB8500 power management
1006 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1007 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1008 the irq_chip parts for handling the Mixed Signal chip events.
1009 This chip embeds various other multimedia funtionalities as well.
1012 bool "Enable debug info via debugfs"
1013 depends on AB8500_GPADC && DEBUG_FS
1014 default y if DEBUG_FS
1016 Select this option if you want debug information using the debug
1017 filesystem, debugfs.
1020 bool "ST-Ericsson AB8500 GPADC driver"
1021 depends on AB8500_CORE && REGULATOR_AB8500
1024 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1026 config MFD_DB8500_PRCMU
1027 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1028 depends on UX500_SOC_DB8500
1031 Select this option to enable support for the DB8500 Power Reset
1032 and Control Management Unit. This is basically an autonomous
1033 system controller running an XP70 microprocessor, which is accessed
1034 through a register map.
1037 bool "STMicroelectronics STMPE"
1038 depends on (I2C=y || SPI_MASTER=y)
1042 Support for the STMPE family of I/O Expanders from
1045 Currently supported devices are:
1047 STMPE811: GPIO, Touchscreen
1048 STMPE1601: GPIO, Keypad
1049 STMPE1801: GPIO, Keypad
1050 STMPE2401: GPIO, Keypad
1051 STMPE2403: GPIO, Keypad
1053 This driver provides common support for accessing the device,
1054 additional drivers must be enabled in order to use the functionality
1055 of the device. Currently available sub drivers are:
1058 Keypad: stmpe-keypad
1059 Touchscreen: stmpe-ts
1061 menu "STMicroelectronics STMPE Interface Drivers"
1062 depends on MFD_STMPE
1065 bool "STMicroelectronics STMPE I2C Interface"
1069 This is used to enable I2C interface of STMPE
1072 bool "STMicroelectronics STMPE SPI Interface"
1073 depends on SPI_MASTER
1075 This is used to enable SPI interface of STMPE
1079 bool "STMicroelectronics STA2X11"
1084 config MFD_SUN6I_PRCM
1085 bool "Allwinner A31 PRCM controller"
1086 depends on ARCH_SUNXI
1089 Support for the PRCM (Power/Reset/Clock Management) unit available
1093 bool "System Controller Register R/W Based on Regmap"
1096 Select this option to enable accessing system control registers
1099 config MFD_DAVINCI_VOICECODEC
1104 config MFD_TI_AM335X_TSCADC
1105 tristate "TI ADC / Touch Screen chip support"
1110 If you say yes here you get support for Texas Instruments series
1111 of Touch Screen /ADC chips.
1112 To compile this driver as a module, choose M here: the
1113 module will be called ti_am335x_tscadc.
1115 config MFD_DM355EVM_MSP
1116 bool "TI DaVinci DM355 EVM microcontroller"
1117 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1119 This driver supports the MSP430 microcontroller used on these
1120 boards. MSP430 firmware manages resets and power sequencing,
1121 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1124 tristate "TI/National Semiconductor LP3943 MFD Driver"
1129 Support for the TI/National Semiconductor LP3943.
1130 This driver consists of GPIO and PWM drivers.
1131 With these functionalities, it can be used for LED string control or
1132 general usage such like a GPIO controller and a PWM controller.
1135 bool "TI LP8788 Power Management Unit Driver"
1141 TI LP8788 PMU supports regulators, battery charger, RTC,
1142 ADC, backlight driver and current sinks.
1144 config MFD_OMAP_USB_HOST
1145 bool "TI OMAP USBHS core and TLL driver"
1146 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1149 This is the core driver for the OAMP EHCI and OHCI drivers.
1150 This MFD driver does the required setup functionalities for
1151 OMAP USB Host drivers.
1154 bool "TI Palmas series chips"
1160 If you say yes here you get support for the Palmas
1161 series of PMIC chips from Texas Instruments.
1164 tristate "TI TPS61050/61052 Boost Converters"
1169 select REGULATOR_FIXED_VOLTAGE
1171 This option enables a driver for the TP61050/TPS61052
1172 high-power "white LED driver". This boost converter is
1173 sometimes used for other things than white LEDs, and
1174 also contains a GPIO pin.
1177 tristate "TI TPS6501x Power Management chips"
1178 depends on I2C && GPIOLIB
1179 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1181 If you say yes here you get support for the TPS6501x series of
1182 Power Management chips. These include voltage regulators,
1183 lithium ion/polymer battery charging, and other features that
1184 are often used in portable devices like cell phones and cameras.
1186 This driver can also be built as a module. If so, the module
1187 will be called tps65010.
1190 tristate "TI TPS6507x Power Management / Touch Screen chips"
1194 If you say yes here you get support for the TPS6507x series of
1195 Power Management / Touch Screen chips. These include voltage
1196 regulators, lithium ion/polymer battery charging, touch screen
1197 and other features that are often used in portable devices.
1198 This driver can also be built as a module. If so, the module
1199 will be called tps6507x.
1202 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1208 If you say yes here you get support for the TPS65086 series of
1209 Power Management chips.
1210 This driver provides common support for accessing the device,
1211 additional drivers must be enabled in order to use the
1212 functionality of the device.
1214 config TPS65911_COMPARATOR
1218 bool "TI TPS65090 Power Management chips"
1224 If you say yes here you get support for the TPS65090 series of
1225 Power Management chips.
1226 This driver provides common support for accessing the device,
1227 additional drivers must be enabled in order to use the
1228 functionality of the device.
1231 tristate "TI TPS65217 Power Management / White LED chips"
1236 If you say yes here you get support for the TPS65217 series of
1237 Power Management / White LED chips.
1238 These include voltage regulators, lithium ion/polymer battery
1239 charger, wled and other features that are often used in portable
1242 This driver can also be built as a module. If so, the module
1243 will be called tps65217.
1245 config MFD_TI_LP873X
1246 tristate "TI LP873X Power Management IC"
1251 If you say yes here then you get support for the LP873X series of
1252 Power Management Integrated Circuits (PMIC).
1253 These include voltage regulators, thermal protection, configurable
1254 General Purpose Outputs (GPO) that are used in portable devices.
1256 This driver can also be built as a module. If so, the module
1257 will be called lp873x.
1260 tristate "TI TPS65218 Power Management chips"
1266 If you say yes here you get support for the TPS65218 series of
1267 Power Management chips.
1268 These include voltage regulators, gpio and other features
1269 that are often used in portable devices. Only regulator
1270 component is currently supported.
1272 This driver can also be built as a module. If so, the module
1273 will be called tps65218.
1276 bool "TI TPS6586x Power Management chips"
1281 If you say yes here you get support for the TPS6586X series of
1282 Power Management chips.
1283 This driver provides common support for accessing the device,
1284 additional drivers must be enabled in order to use the
1285 functionality of the device.
1287 This driver can also be built as a module. If so, the module
1288 will be called tps6586x.
1291 bool "TI TPS65910 Power Management chip"
1293 depends on GPIOLIB || COMPILE_TEST
1299 if you say yes here you get support for the TPS65910 series of
1300 Power Management chips.
1308 config MFD_TPS65912_I2C
1309 tristate "TI TPS65912 Power Management chip with I2C"
1314 If you say yes here you get support for the TPS65912 series of
1315 PM chips with I2C interface.
1317 config MFD_TPS65912_SPI
1318 tristate "TI TPS65912 Power Management chip with SPI"
1321 depends on SPI_MASTER
1323 If you say yes here you get support for the TPS65912 series of
1324 PM chips with SPI interface.
1327 bool "TI TPS80031/TPS80032 Power Management chips"
1333 If you say yes here you get support for the Texas Instruments
1334 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1335 Path and Battery Charger. The device provides five configurable
1336 step-down converters, 11 general purpose LDOs, USB OTG Module,
1337 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1338 Power Path from USB, 32K clock generator.
1341 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1346 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1347 This core driver provides register access and IRQ handling
1348 facilities, and registers devices for the various functions
1349 so that function-specific drivers can bind to them.
1351 These multi-function chips are found on many OMAP2 and OMAP3
1352 boards, providing power management, RTC, GPIO, keypad, a
1353 high speed USB OTG transceiver, an audio codec (on most
1354 versions) and many other features.
1356 config TWL4030_POWER
1357 bool "TI TWL4030 power resources"
1358 depends on TWL4030_CORE && ARM
1360 Say yes here if you want to use the power resources on the
1361 TWL4030 family chips. Most of these resources are regulators,
1362 which have a separate driver; some are control signals, such
1363 as clock request handshaking.
1365 This driver uses board-specific data to initialize the resources
1366 and load scripts controlling which resources are switched off/on
1367 or reset when a sleep, wakeup or warm reset event occurs.
1369 config MFD_TWL4030_AUDIO
1370 bool "TI TWL4030 Audio"
1371 depends on TWL4030_CORE
1376 bool "TI TWL6040 audio codec"
1383 Say yes here if you want support for Texas Instruments TWL6040 audio
1385 This driver provides common support for accessing the device,
1386 additional drivers must be enabled in order to use the
1387 functionality of the device (audio, vibra).
1390 bool "TI TWL92330/Menelaus PM chip"
1391 depends on I2C=y && ARCH_OMAP2
1393 If you say yes here you get support for the Texas Instruments
1394 TWL92330/Menelaus Power Management chip. This include voltage
1395 regulators, Dual slot memory card transceivers, real-time clock
1396 and other features that are often used in portable devices like
1397 cell phones and PDAs.
1399 config MFD_WL1273_CORE
1400 tristate "TI WL1273 FM radio"
1405 This is the core driver for the TI WL1273 FM radio. This MFD
1406 driver connects the radio-wl1273 V4L2 module and the wl1273
1410 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1415 Say yes here to enable support for National Semiconductor / TI
1416 LM3533 Lighting Power chips.
1418 This driver provides common support for accessing the device;
1419 additional drivers must be enabled in order to use the LED,
1420 backlight or ambient-light-sensor functionality of the device.
1422 config MFD_TIMBERDALE
1423 tristate "Timberdale FPGA"
1425 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1427 This is the core driver for the timberdale FPGA. This device is a
1428 multifunction device which exposes numerous platform devices.
1430 The timberdale FPGA can be found on the Intel Atom development board
1431 for in-vehicle infontainment, called Russellville.
1434 bool "Toshiba TC35892 and variants"
1439 Support for the Toshiba TC35892 and variants I/O Expander.
1441 This driver provides common support for accessing the device,
1442 additional drivers must be enabled in order to use the
1443 functionality of the device.
1450 bool "Toshiba T7L66XB"
1451 depends on ARM && HAVE_CLK
1455 Support for Toshiba Mobile IO Controller T7L66XB
1458 bool "Toshiba TC6387XB"
1459 depends on ARM && HAVE_CLK
1463 Support for Toshiba Mobile IO Controller TC6387XB
1466 bool "Toshiba TC6393XB"
1467 depends on ARM && HAVE_CLK
1472 Support for Toshiba Mobile IO Controller TC6393XB
1475 tristate "VIA VX855/VX875 integrated south bridge"
1479 Say yes here to enable support for various functions of the
1480 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1481 and/or vx855_gpio drivers for this to do anything useful.
1489 config MFD_ARIZONA_I2C
1490 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1495 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1496 audio SoC core functionality controlled via I2C.
1498 config MFD_ARIZONA_SPI
1499 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1502 depends on SPI_MASTER
1504 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1505 audio SoC core functionality controlled via SPI.
1508 bool "Cirrus Logic CS47L24 and WM1831"
1509 depends on MFD_ARIZONA
1511 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1514 bool "Wolfson Microelectronics WM5102"
1515 depends on MFD_ARIZONA
1517 Support for Wolfson Microelectronics WM5102 low power audio SoC
1520 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1521 depends on MFD_ARIZONA
1523 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1527 bool "Wolfson Microelectronics WM8997"
1528 depends on MFD_ARIZONA
1530 Support for Wolfson Microelectronics WM8997 low power audio SoC
1533 bool "Wolfson Microelectronics WM8998"
1534 depends on MFD_ARIZONA
1536 Support for Wolfson Microelectronics WM8998 low power audio SoC
1539 bool "Wolfson Microelectronics WM8400"
1544 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1545 CODEC. This driver provides common support for accessing
1546 the device, additional drivers must be enabled in order to use
1547 the functionality of the device.
1552 config MFD_WM831X_I2C
1553 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1560 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1561 when controlled using I2C. This driver provides common support
1562 for accessing the device, additional drivers must be enabled in
1563 order to use the functionality of the device.
1565 config MFD_WM831X_SPI
1566 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1571 depends on SPI_MASTER
1573 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1574 when controlled using SPI. This driver provides common support
1575 for accessing the device, additional drivers must be enabled in
1576 order to use the functionality of the device.
1581 config MFD_WM8350_I2C
1582 bool "Wolfson Microelectronics WM8350 with I2C"
1587 The WM8350 is an integrated audio and power management
1588 subsystem with watchdog and RTC functionality for embedded
1589 systems. This option enables core support for the WM8350 with
1590 I2C as the control interface. Additional options must be
1591 selected to enable support for the functionality of the chip.
1594 tristate "Wolfson Microelectronics WM8994"
1600 The WM8994 is a highly integrated hi-fi CODEC designed for
1601 smartphone applications. As well as audio functionality it
1602 has on board GPIO and regulator functionality which is
1603 supported via the relevant subsystems. This driver provides
1604 core support for the WM8994, in order to use the actual
1605 functionaltiy of the device other drivers must be enabled.
1608 tristate "Support for ST Microelectronics STw481x"
1609 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1613 Select this option to enable the STw481x chip driver used
1614 in various ST Microelectronics and ST-Ericsson embedded
1617 menu "Multimedia Capabilities Port drivers"
1618 depends on ARCH_SA1100
1625 tristate "Support SA11x0 MCP interface"
1626 depends on ARCH_SA1100
1631 tristate "Support for UCB1200 / UCB1300"
1632 depends on MCP_SA11X0
1635 config MCP_UCB1200_TS
1636 tristate "Touchscreen interface support"
1637 depends on MCP_UCB1200 && INPUT
1641 config MFD_VEXPRESS_SYSREG
1642 bool "Versatile Express System Registers"
1643 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1646 select GPIO_GENERIC_PLATFORM
1650 System Registers are the platform configuration block
1651 on the ARM Ltd. Versatile Express board.