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.
22 tristate "Active-semi ACT8945A"
27 Support for the ACT8945A PMIC from Active-semi. This device
28 features three step-down DC/DC converters and four low-dropout
29 linear regulators, along with a complete ActivePath battery
39 Support for the AS3711 PMIC from AMS
42 bool "ams AS3722 Power Management IC"
46 depends on I2C=y && OF
48 The ams AS3722 is a compact system PMU suitable for mobile phones,
49 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
50 controllers, 11 LDOs, RTC, automatic battery, temperature and
51 over current monitoring, GPIOs, ADC and a watchdog.
54 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
57 Say yes here to add support for Analog Devices AD5520 and ADP5501,
58 Multifunction Power Management IC. This includes
59 the I2C driver and the core APIs _only_, you have to select
60 individual components like LCD backlight, LEDs, GPIOs and Kepad
61 under the corresponding menus.
63 config MFD_AAT2870_CORE
64 bool "AnalogicTech AAT2870"
67 depends on GPIOLIB || COMPILE_TEST
69 If you say yes here you get support for the AAT2870.
70 This driver provides common support for accessing the device,
71 additional drivers must be enabled in order to use the
72 functionality of the device.
74 config MFD_ATMEL_FLEXCOM
75 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
79 Select this to get support for Atmel Flexcom. This is a wrapper
80 which embeds a SPI controller, a I2C controller and a USART. Only
81 one function can be used at a time. The choice is done at boot time
82 by the probe function of this MFD driver according to a device tree
85 config MFD_ATMEL_HLCDC
86 tristate "Atmel HLCDC (High-end LCD Controller)"
91 If you say yes here you get support for the HLCDC block.
92 This driver provides common support for accessing the device,
93 additional drivers must be enabled in order to use the
94 functionality of the device.
97 tristate "Broadcom BCM590xx PMUs"
102 Support for the BCM590xx PMUs from Broadcom
109 config MFD_AXP20X_I2C
110 tristate "X-Powers AXP series PMICs with I2C"
115 If you say Y here you get support for the X-Powers AXP series power
116 management ICs (PMICs) controlled with I2C.
117 This driver include only the core APIs. You have to select individual
118 components like regulators or the PEK (Power Enable Key) under the
121 config MFD_AXP20X_RSB
122 tristate "X-Powers AXP series PMICs with RSB"
126 If you say Y here you get support for the X-Powers AXP series power
127 management ICs (PMICs) controlled with RSB.
128 This driver include only the core APIs. You have to select individual
129 components like regulators or the PEK (Power Enable Key) under the
133 tristate "ChromeOS Embedded Controller"
135 select CHROME_PLATFORMS
137 depends on X86 || ARM || COMPILE_TEST
139 If you say Y here you get support for the ChromeOS Embedded
140 Controller (EC) providing keyboard, battery and power services.
141 You also need to enable the driver for the bus you are using. The
142 protocol for talking to the EC is defined by the bus driver.
144 config MFD_CROS_EC_I2C
145 tristate "ChromeOS Embedded Controller (I2C)"
146 depends on MFD_CROS_EC && I2C
149 If you say Y here, you get support for talking to the ChromeOS
150 EC through an I2C bus. This uses a simple byte-level protocol with
151 a checksum. Failing accesses will be retried three times to
154 config MFD_CROS_EC_SPI
155 tristate "ChromeOS Embedded Controller (SPI)"
156 depends on MFD_CROS_EC && SPI
159 If you say Y here, you get support for talking to the ChromeOS EC
160 through a SPI bus, using a byte-level protocol. Since the EC's
161 response time cannot be guaranteed, we support ignoring
162 'pre-amble' bytes before the response actually starts.
166 depends on GPIOLIB && ARM
169 This driver supports the ASIC3 multifunction chip found on many
170 PDAs (mainly iPAQ and HTC based ones)
173 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
176 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
177 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
178 usually found on PXA processors-based platforms. This includes
179 the I2C driver and the core APIs _only_, you have to select
180 individual components like LCD backlight, voltage regulators,
181 LEDs and battery-charger under the corresponding menus.
187 config MFD_DA9052_SPI
188 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
192 depends on SPI_MASTER=y
194 Support for the Dialog Semiconductor DA9052 PMIC
195 when controlled using SPI. This driver provides common support
196 for accessing the device, additional drivers must be enabled in
197 order to use the functionality of the device.
199 config MFD_DA9052_I2C
200 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
206 Support for the Dialog Semiconductor DA9052 PMIC
207 when controlled using I2C. This driver provides common support
208 for accessing the device, additional drivers must be enabled in
209 order to use the functionality of the device.
212 bool "Dialog Semiconductor DA9055 PMIC Support"
218 Say yes here for support of Dialog Semiconductor DA9055. This is
219 a Power Management IC. This driver provides common support for
220 accessing the device as well as the I2C interface to the chip itself.
221 Additional drivers must be enabled in order to use the functionality
224 This driver can be built as a module. If built as a module it will be
228 tristate "Dialog Semiconductor DA9062 PMIC Support"
234 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
235 This includes the I2C driver and core APIs.
236 Additional drivers must be enabled in order to use the functionality
240 tristate "Dialog Semiconductor DA9063 PMIC Support"
246 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
247 This includes the I2C driver and core APIs.
248 Additional drivers must be enabled in order to use the functionality
252 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
258 This adds support for the DA9150 integrated charger and fuel-gauge
259 chip. This driver provides common support for accessing the device.
260 Additional drivers must be enabled in order to use the specific
261 features of the device.
264 tristate "Diolan DLN2 support"
268 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
269 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
270 etc. must be enabled in order to use the functionality of
275 depends on (SPI_MASTER || I2C)
279 Enable support for the Freescale MC13783 and MC13892 PMICs.
280 This driver provides common support for accessing the device,
281 additional drivers must be enabled in order to use the
282 functionality of the device.
284 config MFD_MC13XXX_SPI
285 tristate "Freescale MC13783 and MC13892 SPI interface"
286 depends on SPI_MASTER
290 Select this if your MC13xxx is connected via an SPI bus.
292 config MFD_MC13XXX_I2C
293 tristate "Freescale MC13892 I2C interface"
298 Select this if your MC13xxx is connected via an I2C bus.
300 config MFD_MX25_TSADC
301 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
303 depends on (SOC_IMX25 && OF) || COMPILE_TEST
305 Enable support for the integrated Touchscreen and ADC unit of the
306 i.MX25 processors. They consist of a conversion queue for general
307 purpose ADC and a queue for Touchscreens.
309 config MFD_HI6421_PMIC
310 tristate "HiSilicon Hi6421 PMU/Codec IC"
315 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
316 functions, such as regulators, RTC, codec, Coulomb counter, etc.
317 This driver includes core APIs _only_. You have to select
318 individul components like voltage regulators under corresponding
319 menus in order to enable them.
320 We communicate with the Hi6421 via memory-mapped I/O.
323 bool "HTC EGPIO support"
324 depends on GPIOLIB && ARM
326 This driver supports the CPLD egpio chip present on
327 several HTC phones. It provides basic support for input
328 pins, output pins, and irqs.
331 tristate "HTC PASIC3 LED/DS1WM chip support"
334 This core driver provides register access for the LED/DS1WM
335 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
336 HTC Magician devices, respectively. Actual functionality is
337 handled by the leds-pasic3 and ds1wm drivers.
340 bool "HTC I2C PLD chip support"
341 depends on I2C=y && GPIOLIB
343 If you say yes here you get support for the supposed CPLD
344 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
345 This device provides input and output GPIOs through an I2C
346 interface to one or more sub-chips.
348 config MFD_INTEL_QUARK_I2C_GPIO
349 tristate "Intel Quark MFD I2C GPIO"
352 depends on COMMON_CLK
355 This MFD provides support for I2C and GPIO that exist only
356 in a single PCI device. It splits the 2 IO devices to
357 their respective IO driver.
358 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
361 tristate "Intel ICH LPC"
365 The LPC bridge function of the Intel ICH provides support for
366 many functional units. This driver provides needed support for
367 other drivers to control these functions, currently GPIO and
371 tristate "Intel SCH LPC"
375 LPC bridge function of the Intel SCH provides support for
376 System Management Bus and General Purpose I/O.
378 config INTEL_SOC_PMIC
379 bool "Support for Intel Atom SoC PMIC"
386 Select this option to enable support for the PMIC device
387 on some Intel SoC systems. The PMIC provides ADC, GPIO,
388 thermal, charger and related power management functions
391 config MFD_INTEL_LPSS
396 config MFD_INTEL_LPSS_ACPI
397 tristate "Intel Low Power Subsystem support in ACPI mode"
398 select MFD_INTEL_LPSS
399 depends on X86 && ACPI
401 This driver supports Intel Low Power Subsystem (LPSS) devices such as
402 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
405 config MFD_INTEL_LPSS_PCI
406 tristate "Intel Low Power Subsystem support in PCI mode"
407 select MFD_INTEL_LPSS
408 depends on X86 && PCI
410 This driver supports Intel Low Power Subsystem (LPSS) devices such as
411 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
414 config MFD_INTEL_MSIC
416 depends on INTEL_SCU_IPC
419 Select this option to enable access to Intel MSIC (Avatele
420 Passage) chip. This chip embeds audio, battery, GPIO, etc.
421 devices used in Intel Medfield platforms.
423 config MFD_IPAQ_MICRO
424 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
425 depends on SA1100_H3100 || SA1100_H3600
428 Select this to get support for the Microcontroller found in
429 the Compaq iPAQ handheld computers. This is an Atmel
430 AT90LS8535 microcontroller flashed with a special iPAQ
431 firmware using the custom protocol implemented in this driver.
433 config MFD_JANZ_CMODIO
434 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
438 This is the core driver for the Janz CMOD-IO PCI MODULbus
439 carrier board. This device is a PCI to MODULbus bridge which may
440 host many different types of MODULbus daughterboards, including
441 CAN and GPIO controllers.
443 config MFD_JZ4740_ADC
444 bool "Janz JZ4740 ADC core"
446 select GENERIC_IRQ_CHIP
447 depends on MACH_JZ4740
449 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
450 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
453 tristate "Kontron module PLD device"
456 This is the core driver for the PLD (Programmable Logic Device) found
457 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
458 device may provide functions like watchdog, GPIO, UART and I2C bus.
460 The following modules are supported:
464 * COMe-bPC2 (ETXexpress-PC)
465 * COMe-bSC# (ETXexpress-SC T#)
470 * COMe-cDC2 (microETXexpress-DC)
472 * COMe-cPC2 (microETXexpress-PC)
475 * COMe-mTT10 (nanoETXexpress-TT)
478 This driver can also be built as a module. If so, the module
479 will be called kempld-core.
482 tristate "Marvell 88PM800"
488 This supports for Marvell 88PM800 Power Management IC.
489 This includes the I2C driver and the core APIs _only_, you have to
490 select individual components like voltage regulators, RTC and
491 battery-charger under the corresponding menus.
494 tristate "Marvell 88PM805"
500 This supports for Marvell 88PM805 Power Management IC. This includes
501 the I2C driver and the core APIs _only_, you have to select individual
502 components like codec device, headset/Mic device under the
506 bool "Marvell 88PM8606/88PM8607"
511 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
512 This includes the I2C driver and the core APIs _only_, you have to
513 select individual components like voltage regulators, RTC and
514 battery-charger under the corresponding menus.
517 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
524 Say yes here to add support for Maxim Semiconductor MAX14577 and
525 MAX77836 Micro-USB ICs with battery charger.
526 This driver provides common support for accessing the device;
527 additional drivers must be enabled in order to use the functionality
531 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
539 Say yes here to add support for Maxim Semiconductor MAX77686 and
540 MAX77802 which are Power Management IC with an RTC on chip.
541 This driver provides common support for accessing the device;
542 additional drivers must be enabled in order to use the functionality
546 bool "Maxim Semiconductor MAX77693 PMIC Support"
552 Say yes here to add support for Maxim Semiconductor MAX77693.
553 This is a companion Power Management IC with Flash, Haptic, Charger,
554 and MUIC(Micro USB Interface Controller) controls on chip.
555 This driver provides common support for accessing the device;
556 additional drivers must be enabled in order to use the functionality
560 bool "Maxim Semiconductor MAX77843 PMIC Support"
566 Say yes here to add support for Maxim Semiconductor MAX77843.
567 This is companion Power Management IC with LEDs, Haptic, Charger,
568 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
569 This driver provides common support for accessing the device;
570 additional drivers must be enabled in order to use the functionality
574 tristate "Maxim Semiconductor MAX8907 PMIC Support"
580 Say yes here to add support for Maxim Semiconductor MAX8907. This is
581 a Power Management IC. This driver provides common support for
582 accessing the device; additional drivers must be enabled in order
583 to use the functionality of the device.
586 bool "Maxim Semiconductor MAX8925 PMIC Support"
590 Say yes here to add support for Maxim Semiconductor MAX8925. This is
591 a Power Management IC. This driver provides common support for
592 accessing the device, additional drivers must be enabled in order
593 to use the functionality of the device.
596 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
601 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
602 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
603 MUIC controls on chip.
604 This driver provides common support for accessing the device;
605 additional drivers must be enabled in order to use the functionality
609 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
614 Say yes here to add support for Maxim Semiconductor MAX8998 and
615 National Semiconductor LP3974. This is a Power Management IC.
616 This driver provides common support for accessing the device,
617 additional drivers must be enabled in order to use the functionality
621 tristate "MediaTek MT6397 PMIC Support"
625 Say yes here to add support for MediaTek MT6397 PMIC. This is
626 a Power Management IC. This driver provides common support for
627 accessing the device; additional drivers must be enabled in order
628 to use the functionality of the device.
631 tristate "MEN 14F021P00 Board Management Controller Support"
635 Say yes here to add support for the MEN 14F021P00 BMC
636 which is a Board Management Controller connected to the I2C bus.
637 The device supports multiple sub-devices like LED, HWMON and WDT.
638 This driver provides common support for accessing the devices;
639 additional drivers must be enabled in order to use the
640 functionality of the BMC device.
642 This driver can also be built as a module. If so the module
643 will be called menf21bmc.
646 bool "Motorola EZXPCAP Support"
647 depends on SPI_MASTER
649 This enables the PCAP ASIC present on EZX Phones. This is
650 needed for MMC, TouchScreen, Sound, USB, etc..
652 config MFD_VIPERBOARD
653 tristate "Nano River Technologies Viperboard"
658 Say yes here if you want support for Nano River Technologies
660 There are mfd cell drivers available for i2c master, adc and
661 both gpios found on the board. The spi part does not yet
663 You need to select the mfd cell drivers separately.
664 The drivers do not support all features the board exposes.
667 tristate "Nokia Retu and Tahvo multi-function device"
672 Retu and Tahvo are a multi-function devices found on Nokia
673 Internet Tablets (770, N800 and N810).
676 tristate "NXP PCF50633"
680 Say yes here if you have NXP PCF50633 chip on your board.
681 This core driver provides register access and IRQ handling
682 facilities, and registers devices for the various functions
683 so that function-specific drivers can bind to them.
686 tristate "NXP PCF50633 ADC"
687 depends on MFD_PCF50633
689 Say yes here if you want to include support for ADC in the
693 tristate "NXP PCF50633 GPIO"
694 depends on MFD_PCF50633
696 Say yes here if you want to include support GPIO for pins on
700 tristate "Philips UCB1400 Core driver"
704 This enables support for the Philips UCB1400 core functions.
705 The UCB1400 is an AC97 audio codec.
707 To compile this driver as a module, choose M here: the
708 module will be called ucb1400_core.
713 config MFD_PM8921_CORE
714 tristate "Qualcomm PM8921 PMIC chip"
715 depends on (ARM || HEXAGON)
721 If you say yes to this option, support will be included for the
722 built-in PM8921 PMIC chip.
724 This is required if your board has a PM8921 and uses its features,
725 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
727 Say M here if you want to include support for PM8921 chip as a module.
728 This will build a module called "pm8921-core".
731 tristate "Qualcomm Resource Power Manager (RPM)"
732 depends on ARCH_QCOM && OF
734 If you say yes to this option, support will be included for the
735 Resource Power Manager system found in the Qualcomm 8660, 8960 and
738 This is required to access many regulators, clocks and bus
739 frequencies controlled by the RPM on these devices.
741 Say M here if you want to include support for the Qualcomm RPM as a
742 module. This will build a module called "qcom_rpm".
745 tristate "Qualcomm SPMI PMICs"
746 depends on ARCH_QCOM || COMPILE_TEST
751 This enables support for the Qualcomm SPMI PMICs.
752 These PMICs are currently used with the Snapdragon 800 series of
753 SoCs. Note, that this will only be useful paired with descriptions
754 of the independent functions as children nodes in the device tree.
756 Say M here if you want to include support for the SPMI PMIC
757 series as a module. The module will be called "qcom-spmi-pmic".
760 tristate "RDC R-321x southbridge"
764 Say yes here if you want to have support for the RDC R-321x SoC
765 southbridge which provides access to GPIOs and Watchdog using the
766 southbridge PCI device configuration space.
769 tristate "Realtek PCI-E card reader"
773 This supports for Realtek PCI-Express card reader including rts5209,
774 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
775 Realtek card reader supports access to many types of memory cards,
776 such as Memory Stick, Memory Stick Pro, Secure Digital and
780 tristate "Richtek RT5033 Power Management IC"
786 This driver provides for the Richtek RT5033 Power Management IC,
787 which includes the I2C driver and the Core APIs. This driver provides
788 common support for accessing the device. The device supports multiple
789 sub-devices like charger, fuel gauge, flash LED, current source,
793 tristate "Realtek USB card reader"
797 Select this option to get support for Realtek USB 2.0 card readers
798 including RTS5129, RTS5139, RTS5179 and RTS5170.
799 Realtek card reader supports access to many types of memory cards,
800 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
803 bool "Ricoh RC5T583 Power Management system device"
808 Select this option to get support for the RICOH583 Power
809 Management system device.
810 This driver provides common support for accessing the device
811 through i2c interface. The device supports multiple sub-devices
812 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
813 Additional drivers must be enabled in order to use the
814 different functionality of the device.
817 tristate "Rockchip RK808 Power Management chip"
823 If you say yes here you get support for the RK808
824 Power Management chips.
825 This driver provides common support for accessing the device
826 through I2C interface. The device supports multiple sub-devices
827 including interrupts, RTC, LDO & DCDC regulators, and onkey.
830 tristate "Ricoh RN5T5618 PMIC"
835 Say yes here to add support for the Ricoh RN5T618 PMIC. This
836 driver provides common support for accessing the device,
837 additional drivers must be enabled in order to use the
838 functionality of the device.
841 bool "SAMSUNG Electronics PMIC Series Support"
847 Support for the Samsung Electronics MFD series.
848 This driver provides common support for accessing the device,
849 additional drivers must be enabled in order to use the functionality
852 config MFD_SI476X_CORE
853 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
858 This is the core driver for the SI476x series of AM/FM
859 radio. This MFD driver connects the radio-si476x V4L2 module
860 and the si476x audio codec.
862 To compile this driver as a module, choose M here: the
863 module will be called si476x-core.
866 tristate "Silicon Motion SM501"
868 This is the core driver for the Silicon Motion SM501 multimedia
869 companion chip. This device is a multifunction device which may
870 provide numerous interfaces including USB host controller, USB gadget,
871 asynchronous serial ports, audio functions, and a dual display video
872 interface. The device may be connected by PCI or local bus with
873 varying functions enabled.
875 config MFD_SM501_GPIO
876 bool "Export GPIO via GPIO layer"
877 depends on MFD_SM501 && GPIOLIB
879 This option uses the gpio library layer to export the 64 GPIO
880 lines on the SM501. The platform data is used to supply the
881 base number for the first GPIO line to register.
884 tristate "Skyworks Solutions SKY81452"
889 This is the core driver for the Skyworks SKY81452 backlight and
890 voltage regulator device.
892 This driver can also be built as a module. If so, the module
893 will be called sky81452.
896 bool "SMSC ECE1099 series chips"
901 If you say yes here you get support for the
902 ece1099 chips from SMSC.
904 To compile this driver as a module, choose M here: the
905 module will be called smsc.
908 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
909 default y if ARCH_U300 || ARCH_U8500
911 Say yes here if you have the ABX500 Mixed Signal IC family
912 chips. This core driver expose register access functions.
913 Functionality specific drivers using these functions can
914 remain unchanged when IC changes. Binding of the functions to
915 actual register access is done by the IC core driver.
918 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
919 depends on I2C=y && ABX500_CORE
921 default y if ARCH_U300
923 Select this to enable the AB3100 Mixed Signal IC core
924 functionality. This connects to a AB3100 on the I2C bus
925 and expose a number of symbols needed for dependent devices
926 to read and write registers and subscribe to events from
927 this multi-functional IC. This is needed to use other features
928 of the AB3100 such as battery-backed RTC, charging control,
929 LEDs, vibrator, system power and temperature, power management
933 tristate "ST-Ericsson AB3100 OTP functions"
934 depends on AB3100_CORE
935 default y if AB3100_CORE
937 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
938 programmable memory) support. This exposes a sysfs file to read
942 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
943 depends on ABX500_CORE && MFD_DB8500_PRCMU
948 Select this option to enable access to AB8500 power management
949 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
950 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
951 the irq_chip parts for handling the Mixed Signal chip events.
952 This chip embeds various other multimedia funtionalities as well.
955 bool "Enable debug info via debugfs"
956 depends on AB8500_GPADC && DEBUG_FS
957 default y if DEBUG_FS
959 Select this option if you want debug information using the debug
963 bool "ST-Ericsson AB8500 GPADC driver"
964 depends on AB8500_CORE && REGULATOR_AB8500
967 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
969 config MFD_DB8500_PRCMU
970 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
971 depends on UX500_SOC_DB8500
974 Select this option to enable support for the DB8500 Power Reset
975 and Control Management Unit. This is basically an autonomous
976 system controller running an XP70 microprocessor, which is accessed
977 through a register map.
980 bool "STMicroelectronics STMPE"
981 depends on (I2C=y || SPI_MASTER=y)
985 Support for the STMPE family of I/O Expanders from
988 Currently supported devices are:
990 STMPE811: GPIO, Touchscreen
991 STMPE1601: GPIO, Keypad
992 STMPE1801: GPIO, Keypad
993 STMPE2401: GPIO, Keypad
994 STMPE2403: GPIO, Keypad
996 This driver provides common support for accessing the device,
997 additional drivers must be enabled in order to use the functionality
998 of the device. Currently available sub drivers are:
1001 Keypad: stmpe-keypad
1002 Touchscreen: stmpe-ts
1004 menu "STMicroelectronics STMPE Interface Drivers"
1005 depends on MFD_STMPE
1008 bool "STMicroelectronics STMPE I2C Interface"
1012 This is used to enable I2C interface of STMPE
1015 bool "STMicroelectronics STMPE SPI Interface"
1016 depends on SPI_MASTER
1018 This is used to enable SPI interface of STMPE
1022 bool "STMicroelectronics STA2X11"
1027 config MFD_SUN6I_PRCM
1028 bool "Allwinner A31 PRCM controller"
1029 depends on ARCH_SUNXI
1032 Support for the PRCM (Power/Reset/Clock Management) unit available
1036 bool "System Controller Register R/W Based on Regmap"
1039 Select this option to enable accessing system control registers
1042 config MFD_DAVINCI_VOICECODEC
1047 config MFD_TI_AM335X_TSCADC
1048 tristate "TI ADC / Touch Screen chip support"
1053 If you say yes here you get support for Texas Instruments series
1054 of Touch Screen /ADC chips.
1055 To compile this driver as a module, choose M here: the
1056 module will be called ti_am335x_tscadc.
1058 config MFD_DM355EVM_MSP
1059 bool "TI DaVinci DM355 EVM microcontroller"
1060 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1062 This driver supports the MSP430 microcontroller used on these
1063 boards. MSP430 firmware manages resets and power sequencing,
1064 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1067 tristate "TI/National Semiconductor LP3943 MFD Driver"
1072 Support for the TI/National Semiconductor LP3943.
1073 This driver consists of GPIO and PWM drivers.
1074 With these functionalities, it can be used for LED string control or
1075 general usage such like a GPIO controller and a PWM controller.
1078 bool "TI LP8788 Power Management Unit Driver"
1084 TI LP8788 PMU supports regulators, battery charger, RTC,
1085 ADC, backlight driver and current sinks.
1087 config MFD_OMAP_USB_HOST
1088 bool "TI OMAP USBHS core and TLL driver"
1089 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1092 This is the core driver for the OAMP EHCI and OHCI drivers.
1093 This MFD driver does the required setup functionalities for
1094 OMAP USB Host drivers.
1097 bool "TI Palmas series chips"
1103 If you say yes here you get support for the Palmas
1104 series of PMIC chips from Texas Instruments.
1107 tristate "TI TPS61050/61052 Boost Converters"
1112 select REGULATOR_FIXED_VOLTAGE
1114 This option enables a driver for the TP61050/TPS61052
1115 high-power "white LED driver". This boost converter is
1116 sometimes used for other things than white LEDs, and
1117 also contains a GPIO pin.
1120 tristate "TI TPS6501x Power Management chips"
1121 depends on I2C && GPIOLIB
1122 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1124 If you say yes here you get support for the TPS6501x series of
1125 Power Management chips. These include voltage regulators,
1126 lithium ion/polymer battery charging, and other features that
1127 are often used in portable devices like cell phones and cameras.
1129 This driver can also be built as a module. If so, the module
1130 will be called tps65010.
1133 tristate "TI TPS6507x Power Management / Touch Screen chips"
1137 If you say yes here you get support for the TPS6507x series of
1138 Power Management / Touch Screen chips. These include voltage
1139 regulators, lithium ion/polymer battery charging, touch screen
1140 and other features that are often used in portable devices.
1141 This driver can also be built as a module. If so, the module
1142 will be called tps6507x.
1145 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1151 If you say yes here you get support for the TPS65086 series of
1152 Power Management chips.
1153 This driver provides common support for accessing the device,
1154 additional drivers must be enabled in order to use the
1155 functionality of the device.
1157 config TPS65911_COMPARATOR
1161 bool "TI TPS65090 Power Management chips"
1167 If you say yes here you get support for the TPS65090 series of
1168 Power Management chips.
1169 This driver provides common support for accessing the device,
1170 additional drivers must be enabled in order to use the
1171 functionality of the device.
1174 tristate "TI TPS65217 Power Management / White LED chips"
1179 If you say yes here you get support for the TPS65217 series of
1180 Power Management / White LED chips.
1181 These include voltage regulators, lithium ion/polymer battery
1182 charger, wled and other features that are often used in portable
1185 This driver can also be built as a module. If so, the module
1186 will be called tps65217.
1189 tristate "TI TPS65218 Power Management chips"
1195 If you say yes here you get support for the TPS65218 series of
1196 Power Management chips.
1197 These include voltage regulators, gpio and other features
1198 that are often used in portable devices. Only regulator
1199 component is currently supported.
1201 This driver can also be built as a module. If so, the module
1202 will be called tps65218.
1205 bool "TI TPS6586x Power Management chips"
1210 If you say yes here you get support for the TPS6586X series of
1211 Power Management chips.
1212 This driver provides common support for accessing the device,
1213 additional drivers must be enabled in order to use the
1214 functionality of the device.
1216 This driver can also be built as a module. If so, the module
1217 will be called tps6586x.
1220 bool "TI TPS65910 Power Management chip"
1222 depends on GPIOLIB || COMPILE_TEST
1228 if you say yes here you get support for the TPS65910 series of
1229 Power Management chips.
1237 config MFD_TPS65912_I2C
1238 tristate "TI TPS65912 Power Management chip with I2C"
1243 If you say yes here you get support for the TPS65912 series of
1244 PM chips with I2C interface.
1246 config MFD_TPS65912_SPI
1247 tristate "TI TPS65912 Power Management chip with SPI"
1250 depends on SPI_MASTER
1252 If you say yes here you get support for the TPS65912 series of
1253 PM chips with SPI interface.
1256 bool "TI TPS80031/TPS80032 Power Management chips"
1262 If you say yes here you get support for the Texas Instruments
1263 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1264 Path and Battery Charger. The device provides five configurable
1265 step-down converters, 11 general purpose LDOs, USB OTG Module,
1266 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1267 Power Path from USB, 32K clock generator.
1270 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1275 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1276 This core driver provides register access and IRQ handling
1277 facilities, and registers devices for the various functions
1278 so that function-specific drivers can bind to them.
1280 These multi-function chips are found on many OMAP2 and OMAP3
1281 boards, providing power management, RTC, GPIO, keypad, a
1282 high speed USB OTG transceiver, an audio codec (on most
1283 versions) and many other features.
1285 config TWL4030_POWER
1286 bool "TI TWL4030 power resources"
1287 depends on TWL4030_CORE && ARM
1289 Say yes here if you want to use the power resources on the
1290 TWL4030 family chips. Most of these resources are regulators,
1291 which have a separate driver; some are control signals, such
1292 as clock request handshaking.
1294 This driver uses board-specific data to initialize the resources
1295 and load scripts controlling which resources are switched off/on
1296 or reset when a sleep, wakeup or warm reset event occurs.
1298 config MFD_TWL4030_AUDIO
1299 bool "TI TWL4030 Audio"
1300 depends on TWL4030_CORE
1305 bool "TI TWL6040 audio codec"
1312 Say yes here if you want support for Texas Instruments TWL6040 audio
1314 This driver provides common support for accessing the device,
1315 additional drivers must be enabled in order to use the
1316 functionality of the device (audio, vibra).
1319 bool "TI TWL92330/Menelaus PM chip"
1320 depends on I2C=y && ARCH_OMAP2
1322 If you say yes here you get support for the Texas Instruments
1323 TWL92330/Menelaus Power Management chip. This include voltage
1324 regulators, Dual slot memory card transceivers, real-time clock
1325 and other features that are often used in portable devices like
1326 cell phones and PDAs.
1328 config MFD_WL1273_CORE
1329 tristate "TI WL1273 FM radio"
1334 This is the core driver for the TI WL1273 FM radio. This MFD
1335 driver connects the radio-wl1273 V4L2 module and the wl1273
1339 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1344 Say yes here to enable support for National Semiconductor / TI
1345 LM3533 Lighting Power chips.
1347 This driver provides common support for accessing the device;
1348 additional drivers must be enabled in order to use the LED,
1349 backlight or ambient-light-sensor functionality of the device.
1351 config MFD_TIMBERDALE
1352 tristate "Timberdale FPGA"
1354 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1356 This is the core driver for the timberdale FPGA. This device is a
1357 multifunction device which exposes numerous platform devices.
1359 The timberdale FPGA can be found on the Intel Atom development board
1360 for in-vehicle infontainment, called Russellville.
1363 bool "Toshiba TC35892 and variants"
1368 Support for the Toshiba TC35892 and variants I/O Expander.
1370 This driver provides common support for accessing the device,
1371 additional drivers must be enabled in order to use the
1372 functionality of the device.
1379 bool "Toshiba T7L66XB"
1380 depends on ARM && HAVE_CLK
1384 Support for Toshiba Mobile IO Controller T7L66XB
1387 bool "Toshiba TC6387XB"
1388 depends on ARM && HAVE_CLK
1392 Support for Toshiba Mobile IO Controller TC6387XB
1395 bool "Toshiba TC6393XB"
1396 depends on ARM && HAVE_CLK
1401 Support for Toshiba Mobile IO Controller TC6393XB
1404 tristate "VIA VX855/VX875 integrated south bridge"
1408 Say yes here to enable support for various functions of the
1409 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1410 and/or vx855_gpio drivers for this to do anything useful.
1418 config MFD_ARIZONA_I2C
1419 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1424 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1425 audio SoC core functionality controlled via I2C.
1427 config MFD_ARIZONA_SPI
1428 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1431 depends on SPI_MASTER
1433 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1434 audio SoC core functionality controlled via SPI.
1437 bool "Cirrus Logic CS47L24 and WM1831"
1438 depends on MFD_ARIZONA
1440 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1443 bool "Wolfson Microelectronics WM5102"
1444 depends on MFD_ARIZONA
1446 Support for Wolfson Microelectronics WM5102 low power audio SoC
1449 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1450 depends on MFD_ARIZONA
1452 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1456 bool "Wolfson Microelectronics WM8997"
1457 depends on MFD_ARIZONA
1459 Support for Wolfson Microelectronics WM8997 low power audio SoC
1462 bool "Wolfson Microelectronics WM8998"
1463 depends on MFD_ARIZONA
1465 Support for Wolfson Microelectronics WM8998 low power audio SoC
1468 bool "Wolfson Microelectronics WM8400"
1473 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1474 CODEC. This driver provides common support for accessing
1475 the device, additional drivers must be enabled in order to use
1476 the functionality of the device.
1481 config MFD_WM831X_I2C
1482 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1489 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1490 when controlled using I2C. This driver provides common support
1491 for accessing the device, additional drivers must be enabled in
1492 order to use the functionality of the device.
1494 config MFD_WM831X_SPI
1495 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1500 depends on SPI_MASTER
1502 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1503 when controlled using SPI. This driver provides common support
1504 for accessing the device, additional drivers must be enabled in
1505 order to use the functionality of the device.
1510 config MFD_WM8350_I2C
1511 bool "Wolfson Microelectronics WM8350 with I2C"
1515 The WM8350 is an integrated audio and power management
1516 subsystem with watchdog and RTC functionality for embedded
1517 systems. This option enables core support for the WM8350 with
1518 I2C as the control interface. Additional options must be
1519 selected to enable support for the functionality of the chip.
1522 tristate "Wolfson Microelectronics WM8994"
1528 The WM8994 is a highly integrated hi-fi CODEC designed for
1529 smartphone applications. As well as audio functionality it
1530 has on board GPIO and regulator functionality which is
1531 supported via the relevant subsystems. This driver provides
1532 core support for the WM8994, in order to use the actual
1533 functionaltiy of the device other drivers must be enabled.
1536 tristate "Support for ST Microelectronics STw481x"
1537 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1541 Select this option to enable the STw481x chip driver used
1542 in various ST Microelectronics and ST-Ericsson embedded
1545 menu "Multimedia Capabilities Port drivers"
1546 depends on ARCH_SA1100
1553 tristate "Support SA11x0 MCP interface"
1554 depends on ARCH_SA1100
1559 tristate "Support for UCB1200 / UCB1300"
1560 depends on MCP_SA11X0
1563 config MCP_UCB1200_TS
1564 tristate "Touchscreen interface support"
1565 depends on MCP_UCB1200 && INPUT
1569 config MFD_VEXPRESS_SYSREG
1570 bool "Versatile Express System Registers"
1571 depends on VEXPRESS_CONFIG && GPIOLIB
1574 select GPIO_GENERIC_PLATFORM
1578 System Registers are the platform configuration block
1579 on the ARM Ltd. Versatile Express board.