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.
28 Support for the AS3711 PMIC from AMS
31 bool "ams AS3722 Power Management IC"
35 depends on I2C=y && OF
37 The ams AS3722 is a compact system PMU suitable for mobile phones,
38 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
39 controllers, 11 LDOs, RTC, automatic battery, temperature and
40 over current monitoring, GPIOs, ADC and a watchdog.
43 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
46 Say yes here to add support for Analog Devices AD5520 and ADP5501,
47 Multifunction Power Management IC. This includes
48 the I2C driver and the core APIs _only_, you have to select
49 individual components like LCD backlight, LEDs, GPIOs and Kepad
50 under the corresponding menus.
52 config MFD_AAT2870_CORE
53 bool "AnalogicTech AAT2870"
56 depends on GPIOLIB || COMPILE_TEST
58 If you say yes here you get support for the AAT2870.
59 This driver provides common support for accessing the device,
60 additional drivers must be enabled in order to use the
61 functionality of the device.
63 config MFD_ATMEL_HLCDC
64 tristate "Atmel HLCDC (High-end LCD Controller)"
69 If you say yes here you get support for the HLCDC block.
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.
75 tristate "Broadcom BCM590xx PMUs"
80 Support for the BCM590xx PMUs from Broadcom
83 bool "X-Powers AXP20X"
89 If you say Y here you get support for the X-Powers AXP202, AXP209 and
90 AXP288 power management IC (PMIC).
91 This driver include only the core APIs. You have to select individual
92 components like regulators or the PEK (Power Enable Key) under the
96 tristate "ChromeOS Embedded Controller"
98 select CHROME_PLATFORMS
101 If you say Y here you get support for the ChromeOS Embedded
102 Controller (EC) providing keyboard, battery and power services.
103 You also need to enable the driver for the bus you are using. The
104 protocol for talking to the EC is defined by the bus driver.
106 config MFD_CROS_EC_I2C
107 tristate "ChromeOS Embedded Controller (I2C)"
108 depends on MFD_CROS_EC && I2C
111 If you say Y here, you get support for talking to the ChromeOS
112 EC through an I2C bus. This uses a simple byte-level protocol with
113 a checksum. Failing accesses will be retried three times to
116 config MFD_CROS_EC_SPI
117 tristate "ChromeOS Embedded Controller (SPI)"
118 depends on MFD_CROS_EC && SPI
121 If you say Y here, you get support for talking to the ChromeOS EC
122 through a SPI bus, using a byte-level protocol. Since the EC's
123 response time cannot be guaranteed, we support ignoring
124 'pre-amble' bytes before the response actually starts.
128 depends on GPIOLIB && ARM
131 This driver supports the ASIC3 multifunction chip found on many
132 PDAs (mainly iPAQ and HTC based ones)
135 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
138 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
139 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
140 usually found on PXA processors-based platforms. This includes
141 the I2C driver and the core APIs _only_, you have to select
142 individual components like LCD backlight, voltage regulators,
143 LEDs and battery-charger under the corresponding menus.
149 config MFD_DA9052_SPI
150 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
154 depends on SPI_MASTER=y
156 Support for the Dialog Semiconductor DA9052 PMIC
157 when controlled using SPI. This driver provides common support
158 for accessing the device, additional drivers must be enabled in
159 order to use the functionality of the device.
161 config MFD_DA9052_I2C
162 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
168 Support for the Dialog Semiconductor DA9052 PMIC
169 when controlled using I2C. This driver provides common support
170 for accessing the device, additional drivers must be enabled in
171 order to use the functionality of the device.
174 bool "Dialog Semiconductor DA9055 PMIC Support"
180 Say yes here for support of Dialog Semiconductor DA9055. This is
181 a Power Management IC. This driver provides common support for
182 accessing the device as well as the I2C interface to the chip itself.
183 Additional drivers must be enabled in order to use the functionality
186 This driver can be built as a module. If built as a module it will be
190 tristate "Dialog Semiconductor DA9062 PMIC Support"
196 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
197 This includes the I2C driver and core APIs.
198 Additional drivers must be enabled in order to use the functionality
202 bool "Dialog Semiconductor DA9063 PMIC Support"
208 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
209 This includes the I2C driver and core APIs.
210 Additional drivers must be enabled in order to use the functionality
214 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
220 This adds support for the DA9150 integrated charger and fuel-gauge
221 chip. This driver provides common support for accessing the device.
222 Additional drivers must be enabled in order to use the specific
223 features of the device.
226 tristate "Diolan DLN2 support"
230 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
231 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
232 etc. must be enabled in order to use the functionality of
237 depends on (SPI_MASTER || I2C)
241 Enable support for the Freescale MC13783 and MC13892 PMICs.
242 This driver provides common support for accessing the device,
243 additional drivers must be enabled in order to use the
244 functionality of the device.
246 config MFD_MC13XXX_SPI
247 tristate "Freescale MC13783 and MC13892 SPI interface"
248 depends on SPI_MASTER
252 Select this if your MC13xxx is connected via an SPI bus.
254 config MFD_MC13XXX_I2C
255 tristate "Freescale MC13892 I2C interface"
260 Select this if your MC13xxx is connected via an I2C bus.
262 config MFD_HI6421_PMIC
263 tristate "HiSilicon Hi6421 PMU/Codec IC"
268 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
269 functions, such as regulators, RTC, codec, Coulomb counter, etc.
270 This driver includes core APIs _only_. You have to select
271 individul components like voltage regulators under corresponding
272 menus in order to enable them.
273 We communicate with the Hi6421 via memory-mapped I/O.
276 bool "HTC EGPIO support"
277 depends on GPIOLIB && ARM
279 This driver supports the CPLD egpio chip present on
280 several HTC phones. It provides basic support for input
281 pins, output pins, and irqs.
284 tristate "HTC PASIC3 LED/DS1WM chip support"
287 This core driver provides register access for the LED/DS1WM
288 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
289 HTC Magician devices, respectively. Actual functionality is
290 handled by the leds-pasic3 and ds1wm drivers.
293 bool "HTC I2C PLD chip support"
294 depends on I2C=y && GPIOLIB
296 If you say yes here you get support for the supposed CPLD
297 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
298 This device provides input and output GPIOs through an I2C
299 interface to one or more sub-chips.
301 config MFD_INTEL_QUARK_I2C_GPIO
302 tristate "Intel Quark MFD I2C GPIO"
305 depends on COMMON_CLK
308 This MFD provides support for I2C and GPIO that exist only
309 in a single PCI device. It splits the 2 IO devices to
310 their respective IO driver.
311 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
314 tristate "Intel ICH LPC"
318 The LPC bridge function of the Intel ICH provides support for
319 many functional units. This driver provides needed support for
320 other drivers to control these functions, currently GPIO and
324 tristate "Intel SCH LPC"
328 LPC bridge function of the Intel SCH provides support for
329 System Management Bus and General Purpose I/O.
331 config INTEL_SOC_PMIC
332 bool "Support for Intel Atom SoC PMIC"
338 Select this option to enable support for the PMIC device
339 on some Intel SoC systems. The PMIC provides ADC, GPIO,
340 thermal, charger and related power management functions
343 config MFD_INTEL_LPSS
348 config MFD_INTEL_LPSS_ACPI
349 tristate "Intel Low Power Subsystem support in ACPI mode"
350 select MFD_INTEL_LPSS
351 depends on X86 && ACPI
353 This driver supports Intel Low Power Subsystem (LPSS) devices such as
354 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
357 config MFD_INTEL_LPSS_PCI
358 tristate "Intel Low Power Subsystem support in PCI mode"
359 select MFD_INTEL_LPSS
360 depends on X86 && PCI
362 This driver supports Intel Low Power Subsystem (LPSS) devices such as
363 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
366 config MFD_INTEL_MSIC
368 depends on INTEL_SCU_IPC
371 Select this option to enable access to Intel MSIC (Avatele
372 Passage) chip. This chip embeds audio, battery, GPIO, etc.
373 devices used in Intel Medfield platforms.
375 config MFD_IPAQ_MICRO
376 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
377 depends on SA1100_H3100 || SA1100_H3600
380 Select this to get support for the Microcontroller found in
381 the Compaq iPAQ handheld computers. This is an Atmel
382 AT90LS8535 microcontroller flashed with a special iPAQ
383 firmware using the custom protocol implemented in this driver.
385 config MFD_JANZ_CMODIO
386 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
390 This is the core driver for the Janz CMOD-IO PCI MODULbus
391 carrier board. This device is a PCI to MODULbus bridge which may
392 host many different types of MODULbus daughterboards, including
393 CAN and GPIO controllers.
395 config MFD_JZ4740_ADC
396 bool "Janz JZ4740 ADC core"
398 select GENERIC_IRQ_CHIP
399 depends on MACH_JZ4740
401 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
402 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
405 tristate "Kontron module PLD device"
408 This is the core driver for the PLD (Programmable Logic Device) found
409 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
410 device may provide functions like watchdog, GPIO, UART and I2C bus.
412 The following modules are supported:
416 * COMe-bPC2 (ETXexpress-PC)
417 * COMe-bSC# (ETXexpress-SC T#)
422 * COMe-cDC2 (microETXexpress-DC)
424 * COMe-cPC2 (microETXexpress-PC)
427 * COMe-mTT10 (nanoETXexpress-TT)
430 This driver can also be built as a module. If so, the module
431 will be called kempld-core.
434 tristate "Marvell 88PM800"
440 This supports for Marvell 88PM800 Power Management IC.
441 This includes the I2C driver and the core APIs _only_, you have to
442 select individual components like voltage regulators, RTC and
443 battery-charger under the corresponding menus.
446 tristate "Marvell 88PM805"
452 This supports for Marvell 88PM805 Power Management IC. This includes
453 the I2C driver and the core APIs _only_, you have to select individual
454 components like codec device, headset/Mic device under the
458 bool "Marvell 88PM8606/88PM8607"
463 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
464 This includes the I2C driver and the core APIs _only_, you have to
465 select individual components like voltage regulators, RTC and
466 battery-charger under the corresponding menus.
469 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
476 Say yes here to add support for Maxim Semiconductor MAX14577 and
477 MAX77836 Micro-USB ICs with battery charger.
478 This driver provides common support for accessing the device;
479 additional drivers must be enabled in order to use the functionality
483 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
491 Say yes here to add support for Maxim Semiconductor MAX77686 and
492 MAX77802 which are Power Management IC with an RTC on chip.
493 This driver provides common support for accessing the device;
494 additional drivers must be enabled in order to use the functionality
498 bool "Maxim Semiconductor MAX77693 PMIC Support"
504 Say yes here to add support for Maxim Semiconductor MAX77693.
505 This is a companion Power Management IC with Flash, Haptic, Charger,
506 and MUIC(Micro USB Interface Controller) controls on chip.
507 This driver provides common support for accessing the device;
508 additional drivers must be enabled in order to use the functionality
512 bool "Maxim Semiconductor MAX77843 PMIC Support"
518 Say yes here to add support for Maxim Semiconductor MAX77843.
519 This is companion Power Management IC with LEDs, Haptic, Charger,
520 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
521 This driver provides common support for accessing the device;
522 additional drivers must be enabled in order to use the functionality
526 tristate "Maxim Semiconductor MAX8907 PMIC Support"
532 Say yes here to add support for Maxim Semiconductor MAX8907. This is
533 a Power Management IC. This driver provides common support for
534 accessing the device; additional drivers must be enabled in order
535 to use the functionality of the device.
538 bool "Maxim Semiconductor MAX8925 PMIC Support"
542 Say yes here to add support for Maxim Semiconductor MAX8925. This is
543 a Power Management IC. This driver provides common support for
544 accessing the device, additional drivers must be enabled in order
545 to use the functionality of the device.
548 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
553 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
554 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
555 MUIC controls on chip.
556 This driver provides common support for accessing the device;
557 additional drivers must be enabled in order to use the functionality
561 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
566 Say yes here to add support for Maxim Semiconductor MAX8998 and
567 National Semiconductor LP3974. This is a Power Management IC.
568 This driver provides common support for accessing the device,
569 additional drivers must be enabled in order to use the functionality
573 tristate "MediaTek MT6397 PMIC Support"
577 Say yes here to add support for MediaTek MT6397 PMIC. This is
578 a Power Management IC. This driver provides common support for
579 accessing the device; additional drivers must be enabled in order
580 to use the functionality of the device.
583 tristate "MEN 14F021P00 Board Management Controller Support"
587 Say yes here to add support for the MEN 14F021P00 BMC
588 which is a Board Management Controller connected to the I2C bus.
589 The device supports multiple sub-devices like LED, HWMON and WDT.
590 This driver provides common support for accessing the devices;
591 additional drivers must be enabled in order to use the
592 functionality of the BMC device.
594 This driver can also be built as a module. If so the module
595 will be called menf21bmc.
598 bool "Motorola EZXPCAP Support"
599 depends on SPI_MASTER
601 This enables the PCAP ASIC present on EZX Phones. This is
602 needed for MMC, TouchScreen, Sound, USB, etc..
604 config MFD_VIPERBOARD
605 tristate "Nano River Technologies Viperboard"
610 Say yes here if you want support for Nano River Technologies
612 There are mfd cell drivers available for i2c master, adc and
613 both gpios found on the board. The spi part does not yet
615 You need to select the mfd cell drivers separately.
616 The drivers do not support all features the board exposes.
619 tristate "Nokia Retu and Tahvo multi-function device"
624 Retu and Tahvo are a multi-function devices found on Nokia
625 Internet Tablets (770, N800 and N810).
628 tristate "NXP PCF50633"
632 Say yes here if you have NXP PCF50633 chip on your board.
633 This core driver provides register access and IRQ handling
634 facilities, and registers devices for the various functions
635 so that function-specific drivers can bind to them.
638 tristate "NXP PCF50633 ADC"
639 depends on MFD_PCF50633
641 Say yes here if you want to include support for ADC in the
645 tristate "NXP PCF50633 GPIO"
646 depends on MFD_PCF50633
648 Say yes here if you want to include support GPIO for pins on
652 tristate "Philips UCB1400 Core driver"
656 This enables support for the Philips UCB1400 core functions.
657 The UCB1400 is an AC97 audio codec.
659 To compile this driver as a module, choose M here: the
660 module will be called ucb1400_core.
665 config MFD_PM8921_CORE
666 tristate "Qualcomm PM8921 PMIC chip"
667 depends on (ARM || HEXAGON)
673 If you say yes to this option, support will be included for the
674 built-in PM8921 PMIC chip.
676 This is required if your board has a PM8921 and uses its features,
677 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
679 Say M here if you want to include support for PM8921 chip as a module.
680 This will build a module called "pm8921-core".
683 tristate "Qualcomm Resource Power Manager (RPM)"
684 depends on ARCH_QCOM && OF
686 If you say yes to this option, support will be included for the
687 Resource Power Manager system found in the Qualcomm 8660, 8960 and
690 This is required to access many regulators, clocks and bus
691 frequencies controlled by the RPM on these devices.
693 Say M here if you want to include support for the Qualcomm RPM as a
694 module. This will build a module called "qcom_rpm".
697 tristate "Qualcomm SPMI PMICs"
698 depends on ARCH_QCOM || COMPILE_TEST
703 This enables support for the Qualcomm SPMI PMICs.
704 These PMICs are currently used with the Snapdragon 800 series of
705 SoCs. Note, that this will only be useful paired with descriptions
706 of the independent functions as children nodes in the device tree.
708 Say M here if you want to include support for the SPMI PMIC
709 series as a module. The module will be called "qcom-spmi-pmic".
712 tristate "RDC R-321x southbridge"
716 Say yes here if you want to have support for the RDC R-321x SoC
717 southbridge which provides access to GPIOs and Watchdog using the
718 southbridge PCI device configuration space.
721 tristate "Realtek PCI-E card reader"
725 This supports for Realtek PCI-Express card reader including rts5209,
726 rts5229, rtl8411, etc. Realtek card reader supports access to many
727 types of memory cards, such as Memory Stick, Memory Stick Pro,
728 Secure Digital and MultiMediaCard.
731 tristate "Richtek RT5033 Power Management IC"
737 This driver provides for the Richtek RT5033 Power Management IC,
738 which includes the I2C driver and the Core APIs. This driver provides
739 common support for accessing the device. The device supports multiple
740 sub-devices like charger, fuel gauge, flash LED, current source,
744 tristate "Realtek USB card reader"
748 Select this option to get support for Realtek USB 2.0 card readers
749 including RTS5129, RTS5139, RTS5179 and RTS5170.
750 Realtek card reader supports access to many types of memory cards,
751 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
754 bool "Ricoh RC5T583 Power Management system device"
759 Select this option to get support for the RICOH583 Power
760 Management system device.
761 This driver provides common support for accessing the device
762 through i2c interface. The device supports multiple sub-devices
763 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
764 Additional drivers must be enabled in order to use the
765 different functionality of the device.
768 tristate "Rockchip RK808 Power Management chip"
774 If you say yes here you get support for the RK808
775 Power Management chips.
776 This driver provides common support for accessing the device
777 through I2C interface. The device supports multiple sub-devices
778 including interrupts, RTC, LDO & DCDC regulators, and onkey.
781 tristate "Ricoh RN5T5618 PMIC"
786 Say yes here to add support for the Ricoh RN5T618 PMIC. This
787 driver provides common support for accessing the device,
788 additional drivers must be enabled in order to use the
789 functionality of the device.
792 bool "SAMSUNG Electronics PMIC Series Support"
798 Support for the Samsung Electronics MFD series.
799 This driver provides common support for accessing the device,
800 additional drivers must be enabled in order to use the functionality
803 config MFD_SI476X_CORE
804 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
809 This is the core driver for the SI476x series of AM/FM
810 radio. This MFD driver connects the radio-si476x V4L2 module
811 and the si476x audio codec.
813 To compile this driver as a module, choose M here: the
814 module will be called si476x-core.
817 tristate "Silicon Motion SM501"
819 This is the core driver for the Silicon Motion SM501 multimedia
820 companion chip. This device is a multifunction device which may
821 provide numerous interfaces including USB host controller, USB gadget,
822 asynchronous serial ports, audio functions, and a dual display video
823 interface. The device may be connected by PCI or local bus with
824 varying functions enabled.
826 config MFD_SM501_GPIO
827 bool "Export GPIO via GPIO layer"
828 depends on MFD_SM501 && GPIOLIB
830 This option uses the gpio library layer to export the 64 GPIO
831 lines on the SM501. The platform data is used to supply the
832 base number for the first GPIO line to register.
835 tristate "Skyworks Solutions SKY81452"
840 This is the core driver for the Skyworks SKY81452 backlight and
841 voltage regulator device.
843 This driver can also be built as a module. If so, the module
844 will be called sky81452.
847 bool "SMSC ECE1099 series chips"
852 If you say yes here you get support for the
853 ece1099 chips from SMSC.
855 To compile this driver as a module, choose M here: the
856 module will be called smsc.
859 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
860 default y if ARCH_U300 || ARCH_U8500
862 Say yes here if you have the ABX500 Mixed Signal IC family
863 chips. This core driver expose register access functions.
864 Functionality specific drivers using these functions can
865 remain unchanged when IC changes. Binding of the functions to
866 actual register access is done by the IC core driver.
869 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
870 depends on I2C=y && ABX500_CORE
872 default y if ARCH_U300
874 Select this to enable the AB3100 Mixed Signal IC core
875 functionality. This connects to a AB3100 on the I2C bus
876 and expose a number of symbols needed for dependent devices
877 to read and write registers and subscribe to events from
878 this multi-functional IC. This is needed to use other features
879 of the AB3100 such as battery-backed RTC, charging control,
880 LEDs, vibrator, system power and temperature, power management
884 tristate "ST-Ericsson AB3100 OTP functions"
885 depends on AB3100_CORE
886 default y if AB3100_CORE
888 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
889 programmable memory) support. This exposes a sysfs file to read
893 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
894 depends on ABX500_CORE && MFD_DB8500_PRCMU
899 Select this option to enable access to AB8500 power management
900 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
901 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
902 the irq_chip parts for handling the Mixed Signal chip events.
903 This chip embeds various other multimedia funtionalities as well.
906 bool "Enable debug info via debugfs"
907 depends on AB8500_GPADC && DEBUG_FS
908 default y if DEBUG_FS
910 Select this option if you want debug information using the debug
914 bool "ST-Ericsson AB8500 GPADC driver"
915 depends on AB8500_CORE && REGULATOR_AB8500
918 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
920 config MFD_DB8500_PRCMU
921 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
922 depends on UX500_SOC_DB8500
925 Select this option to enable support for the DB8500 Power Reset
926 and Control Management Unit. This is basically an autonomous
927 system controller running an XP70 microprocessor, which is accessed
928 through a register map.
931 bool "STMicroelectronics STMPE"
932 depends on (I2C=y || SPI_MASTER=y)
936 Support for the STMPE family of I/O Expanders from
939 Currently supported devices are:
941 STMPE811: GPIO, Touchscreen
942 STMPE1601: GPIO, Keypad
943 STMPE1801: GPIO, Keypad
944 STMPE2401: GPIO, Keypad
945 STMPE2403: GPIO, Keypad
947 This driver provides common support for accessing the device,
948 additional drivers must be enabled in order to use the functionality
949 of the device. Currently available sub drivers are:
953 Touchscreen: stmpe-ts
955 menu "STMicroelectronics STMPE Interface Drivers"
959 bool "STMicroelectronics STMPE I2C Interface"
963 This is used to enable I2C interface of STMPE
966 bool "STMicroelectronics STMPE SPI Interface"
967 depends on SPI_MASTER
969 This is used to enable SPI interface of STMPE
973 bool "STMicroelectronics STA2X11"
978 config MFD_SUN6I_PRCM
979 bool "Allwinner A31 PRCM controller"
980 depends on ARCH_SUNXI
983 Support for the PRCM (Power/Reset/Clock Management) unit available
987 bool "System Controller Register R/W Based on Regmap"
990 Select this option to enable accessing system control registers
993 config MFD_DAVINCI_VOICECODEC
998 config MFD_TI_AM335X_TSCADC
999 tristate "TI ADC / Touch Screen chip support"
1004 If you say yes here you get support for Texas Instruments series
1005 of Touch Screen /ADC chips.
1006 To compile this driver as a module, choose M here: the
1007 module will be called ti_am335x_tscadc.
1009 config MFD_DM355EVM_MSP
1010 bool "TI DaVinci DM355 EVM microcontroller"
1011 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1013 This driver supports the MSP430 microcontroller used on these
1014 boards. MSP430 firmware manages resets and power sequencing,
1015 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1018 tristate "TI/National Semiconductor LP3943 MFD Driver"
1023 Support for the TI/National Semiconductor LP3943.
1024 This driver consists of GPIO and PWM drivers.
1025 With these functionalities, it can be used for LED string control or
1026 general usage such like a GPIO controller and a PWM controller.
1029 bool "TI LP8788 Power Management Unit Driver"
1035 TI LP8788 PMU supports regulators, battery charger, RTC,
1036 ADC, backlight driver and current sinks.
1038 config MFD_OMAP_USB_HOST
1039 bool "TI OMAP USBHS core and TLL driver"
1040 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1043 This is the core driver for the OAMP EHCI and OHCI drivers.
1044 This MFD driver does the required setup functionalities for
1045 OMAP USB Host drivers.
1048 bool "TI Palmas series chips"
1054 If you say yes here you get support for the Palmas
1055 series of PMIC chips from Texas Instruments.
1058 tristate "TI TPS61050/61052 Boost Converters"
1062 select REGULATOR_FIXED_VOLTAGE
1064 This option enables a driver for the TP61050/TPS61052
1065 high-power "white LED driver". This boost converter is
1066 sometimes used for other things than white LEDs, and
1067 also contains a GPIO pin.
1070 tristate "TI TPS6501x Power Management chips"
1071 depends on I2C && GPIOLIB
1072 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1074 If you say yes here you get support for the TPS6501x series of
1075 Power Management chips. These include voltage regulators,
1076 lithium ion/polymer battery charging, and other features that
1077 are often used in portable devices like cell phones and cameras.
1079 This driver can also be built as a module. If so, the module
1080 will be called tps65010.
1083 tristate "TI TPS6507x Power Management / Touch Screen chips"
1087 If you say yes here you get support for the TPS6507x series of
1088 Power Management / Touch Screen chips. These include voltage
1089 regulators, lithium ion/polymer battery charging, touch screen
1090 and other features that are often used in portable devices.
1091 This driver can also be built as a module. If so, the module
1092 will be called tps6507x.
1094 config TPS65911_COMPARATOR
1098 bool "TI TPS65090 Power Management chips"
1104 If you say yes here you get support for the TPS65090 series of
1105 Power Management chips.
1106 This driver provides common support for accessing the device,
1107 additional drivers must be enabled in order to use the
1108 functionality of the device.
1111 tristate "TI TPS65217 Power Management / White LED chips"
1116 If you say yes here you get support for the TPS65217 series of
1117 Power Management / White LED chips.
1118 These include voltage regulators, lithium ion/polymer battery
1119 charger, wled and other features that are often used in portable
1122 This driver can also be built as a module. If so, the module
1123 will be called tps65217.
1126 tristate "TI TPS65218 Power Management chips"
1132 If you say yes here you get support for the TPS65218 series of
1133 Power Management chips.
1134 These include voltage regulators, gpio and other features
1135 that are often used in portable devices. Only regulator
1136 component is currently supported.
1138 This driver can also be built as a module. If so, the module
1139 will be called tps65218.
1142 bool "TI TPS6586x Power Management chips"
1147 If you say yes here you get support for the TPS6586X series of
1148 Power Management chips.
1149 This driver provides common support for accessing the device,
1150 additional drivers must be enabled in order to use the
1151 functionality of the device.
1153 This driver can also be built as a module. If so, the module
1154 will be called tps6586x.
1157 bool "TI TPS65910 Power Management chip"
1159 depends on GPIOLIB || COMPILE_TEST
1165 if you say yes here you get support for the TPS65910 series of
1166 Power Management chips.
1169 bool "TI TPS65912 Power Management chip"
1173 If you say yes here you get support for the TPS65912 series of
1176 config MFD_TPS65912_I2C
1177 bool "TI TPS65912 Power Management chip with I2C"
1180 depends on I2C=y && GPIOLIB
1182 If you say yes here you get support for the TPS65912 series of
1183 PM chips with I2C interface.
1185 config MFD_TPS65912_SPI
1186 bool "TI TPS65912 Power Management chip with SPI"
1189 depends on SPI_MASTER && GPIOLIB
1191 If you say yes here you get support for the TPS65912 series of
1192 PM chips with SPI interface.
1195 bool "TI TPS80031/TPS80032 Power Management chips"
1201 If you say yes here you get support for the Texas Instruments
1202 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1203 Path and Battery Charger. The device provides five configurable
1204 step-down converters, 11 general purpose LDOs, USB OTG Module,
1205 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1206 Power Path from USB, 32K clock generator.
1209 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1214 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1215 This core driver provides register access and IRQ handling
1216 facilities, and registers devices for the various functions
1217 so that function-specific drivers can bind to them.
1219 These multi-function chips are found on many OMAP2 and OMAP3
1220 boards, providing power management, RTC, GPIO, keypad, a
1221 high speed USB OTG transceiver, an audio codec (on most
1222 versions) and many other features.
1224 config TWL4030_POWER
1225 bool "TI TWL4030 power resources"
1226 depends on TWL4030_CORE && ARM
1228 Say yes here if you want to use the power resources on the
1229 TWL4030 family chips. Most of these resources are regulators,
1230 which have a separate driver; some are control signals, such
1231 as clock request handshaking.
1233 This driver uses board-specific data to initialize the resources
1234 and load scripts controlling which resources are switched off/on
1235 or reset when a sleep, wakeup or warm reset event occurs.
1237 config MFD_TWL4030_AUDIO
1238 bool "TI TWL4030 Audio"
1239 depends on TWL4030_CORE
1244 bool "TI TWL6040 audio codec"
1251 Say yes here if you want support for Texas Instruments TWL6040 audio
1253 This driver provides common support for accessing the device,
1254 additional drivers must be enabled in order to use the
1255 functionality of the device (audio, vibra).
1258 bool "TI TWL92330/Menelaus PM chip"
1259 depends on I2C=y && ARCH_OMAP2
1261 If you say yes here you get support for the Texas Instruments
1262 TWL92330/Menelaus Power Management chip. This include voltage
1263 regulators, Dual slot memory card transceivers, real-time clock
1264 and other features that are often used in portable devices like
1265 cell phones and PDAs.
1267 config MFD_WL1273_CORE
1268 tristate "TI WL1273 FM radio"
1273 This is the core driver for the TI WL1273 FM radio. This MFD
1274 driver connects the radio-wl1273 V4L2 module and the wl1273
1278 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1283 Say yes here to enable support for National Semiconductor / TI
1284 LM3533 Lighting Power chips.
1286 This driver provides common support for accessing the device;
1287 additional drivers must be enabled in order to use the LED,
1288 backlight or ambient-light-sensor functionality of the device.
1290 config MFD_TIMBERDALE
1291 tristate "Timberdale FPGA"
1293 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1295 This is the core driver for the timberdale FPGA. This device is a
1296 multifunction device which exposes numerous platform devices.
1298 The timberdale FPGA can be found on the Intel Atom development board
1299 for in-vehicle infontainment, called Russellville.
1302 bool "Toshiba TC35892 and variants"
1307 Support for the Toshiba TC35892 and variants I/O Expander.
1309 This driver provides common support for accessing the device,
1310 additional drivers must be enabled in order to use the
1311 functionality of the device.
1318 bool "Toshiba T7L66XB"
1319 depends on ARM && HAVE_CLK
1323 Support for Toshiba Mobile IO Controller T7L66XB
1326 bool "Toshiba TC6387XB"
1327 depends on ARM && HAVE_CLK
1331 Support for Toshiba Mobile IO Controller TC6387XB
1334 bool "Toshiba TC6393XB"
1335 depends on ARM && HAVE_CLK
1340 Support for Toshiba Mobile IO Controller TC6393XB
1343 tristate "VIA VX855/VX875 integrated south bridge"
1347 Say yes here to enable support for various functions of the
1348 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1349 and/or vx855_gpio drivers for this to do anything useful.
1357 config MFD_ARIZONA_I2C
1358 tristate "Wolfson Microelectronics Arizona platform with I2C"
1364 Support for the Wolfson Microelectronics Arizona platform audio SoC
1365 core functionality controlled via I2C.
1367 config MFD_ARIZONA_SPI
1368 tristate "Wolfson Microelectronics Arizona platform with SPI"
1372 depends on SPI_MASTER
1374 Support for the Wolfson Microelectronics Arizona platform audio SoC
1375 core functionality controlled via I2C.
1378 bool "Wolfson Microelectronics WM5102"
1379 depends on MFD_ARIZONA
1381 Support for Wolfson Microelectronics WM5102 low power audio SoC
1384 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1385 depends on MFD_ARIZONA
1387 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1391 bool "Wolfson Microelectronics WM8997"
1392 depends on MFD_ARIZONA
1394 Support for Wolfson Microelectronics WM8997 low power audio SoC
1397 bool "Wolfson Microelectronics WM8998"
1398 depends on MFD_ARIZONA
1400 Support for Wolfson Microelectronics WM8998 low power audio SoC
1403 bool "Wolfson Microelectronics WM8400"
1408 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1409 CODEC. This driver provides common support for accessing
1410 the device, additional drivers must be enabled in order to use
1411 the functionality of the device.
1416 config MFD_WM831X_I2C
1417 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1424 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1425 when controlled using I2C. This driver provides common support
1426 for accessing the device, additional drivers must be enabled in
1427 order to use the functionality of the device.
1429 config MFD_WM831X_SPI
1430 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1435 depends on SPI_MASTER
1437 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1438 when controlled using SPI. This driver provides common support
1439 for accessing the device, additional drivers must be enabled in
1440 order to use the functionality of the device.
1445 config MFD_WM8350_I2C
1446 bool "Wolfson Microelectronics WM8350 with I2C"
1450 The WM8350 is an integrated audio and power management
1451 subsystem with watchdog and RTC functionality for embedded
1452 systems. This option enables core support for the WM8350 with
1453 I2C as the control interface. Additional options must be
1454 selected to enable support for the functionality of the chip.
1457 tristate "Wolfson Microelectronics WM8994"
1463 The WM8994 is a highly integrated hi-fi CODEC designed for
1464 smartphone applications. As well as audio functionality it
1465 has on board GPIO and regulator functionality which is
1466 supported via the relevant subsystems. This driver provides
1467 core support for the WM8994, in order to use the actual
1468 functionaltiy of the device other drivers must be enabled.
1471 tristate "Support for ST Microelectronics STw481x"
1472 depends on I2C && ARCH_NOMADIK
1476 Select this option to enable the STw481x chip driver used
1477 in various ST Microelectronics and ST-Ericsson embedded
1480 menu "Multimedia Capabilities Port drivers"
1481 depends on ARCH_SA1100
1488 tristate "Support SA11x0 MCP interface"
1489 depends on ARCH_SA1100
1494 tristate "Support for UCB1200 / UCB1300"
1495 depends on MCP_SA11X0
1498 config MCP_UCB1200_TS
1499 tristate "Touchscreen interface support"
1500 depends on MCP_UCB1200 && INPUT
1504 config MFD_VEXPRESS_SYSREG
1505 bool "Versatile Express System Registers"
1506 depends on VEXPRESS_CONFIG && GPIOLIB
1509 select GPIO_GENERIC_PLATFORM
1513 System Registers are the platform configuration block
1514 on the ARM Ltd. Versatile Express board.