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_FLEXCOM
64 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
68 Select this to get support for Atmel Flexcom. This is a wrapper
69 which embeds a SPI controller, a I2C controller and a USART. Only
70 one function can be used at a time. The choice is done at boot time
71 by the probe function of this MFD driver according to a device tree
74 config MFD_ATMEL_HLCDC
75 tristate "Atmel HLCDC (High-end LCD Controller)"
80 If you say yes here you get support for the HLCDC block.
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.
86 tristate "Broadcom BCM590xx PMUs"
91 Support for the BCM590xx PMUs from Broadcom
94 bool "X-Powers AXP20X"
100 If you say Y here you get support for the X-Powers AXP202, AXP209 and
101 AXP288 power management IC (PMIC).
102 This driver include only the core APIs. You have to select individual
103 components like regulators or the PEK (Power Enable Key) under the
107 tristate "ChromeOS Embedded Controller"
109 select CHROME_PLATFORMS
111 depends on X86 || ARM || COMPILE_TEST
113 If you say Y here you get support for the ChromeOS Embedded
114 Controller (EC) providing keyboard, battery and power services.
115 You also need to enable the driver for the bus you are using. The
116 protocol for talking to the EC is defined by the bus driver.
118 config MFD_CROS_EC_I2C
119 tristate "ChromeOS Embedded Controller (I2C)"
120 depends on MFD_CROS_EC && I2C
123 If you say Y here, you get support for talking to the ChromeOS
124 EC through an I2C bus. This uses a simple byte-level protocol with
125 a checksum. Failing accesses will be retried three times to
128 config MFD_CROS_EC_SPI
129 tristate "ChromeOS Embedded Controller (SPI)"
130 depends on MFD_CROS_EC && SPI
133 If you say Y here, you get support for talking to the ChromeOS EC
134 through a SPI bus, using a byte-level protocol. Since the EC's
135 response time cannot be guaranteed, we support ignoring
136 'pre-amble' bytes before the response actually starts.
140 depends on GPIOLIB && ARM
143 This driver supports the ASIC3 multifunction chip found on many
144 PDAs (mainly iPAQ and HTC based ones)
147 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
150 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
151 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
152 usually found on PXA processors-based platforms. This includes
153 the I2C driver and the core APIs _only_, you have to select
154 individual components like LCD backlight, voltage regulators,
155 LEDs and battery-charger under the corresponding menus.
161 config MFD_DA9052_SPI
162 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
166 depends on SPI_MASTER=y
168 Support for the Dialog Semiconductor DA9052 PMIC
169 when controlled using SPI. 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.
173 config MFD_DA9052_I2C
174 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
180 Support for the Dialog Semiconductor DA9052 PMIC
181 when controlled using I2C. This driver provides common support
182 for accessing the device, additional drivers must be enabled in
183 order to use the functionality of the device.
186 bool "Dialog Semiconductor DA9055 PMIC Support"
192 Say yes here for support of Dialog Semiconductor DA9055. This is
193 a Power Management IC. This driver provides common support for
194 accessing the device as well as the I2C interface to the chip itself.
195 Additional drivers must be enabled in order to use the functionality
198 This driver can be built as a module. If built as a module it will be
202 tristate "Dialog Semiconductor DA9062 PMIC Support"
208 Say yes here for support for the Dialog Semiconductor DA9062 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 DA9063 PMIC Support"
220 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
221 This includes the I2C driver and core APIs.
222 Additional drivers must be enabled in order to use the functionality
226 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
232 This adds support for the DA9150 integrated charger and fuel-gauge
233 chip. This driver provides common support for accessing the device.
234 Additional drivers must be enabled in order to use the specific
235 features of the device.
238 tristate "Diolan DLN2 support"
242 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
243 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
244 etc. must be enabled in order to use the functionality of
249 depends on (SPI_MASTER || I2C)
253 Enable support for the Freescale MC13783 and MC13892 PMICs.
254 This driver provides common support for accessing the device,
255 additional drivers must be enabled in order to use the
256 functionality of the device.
258 config MFD_MC13XXX_SPI
259 tristate "Freescale MC13783 and MC13892 SPI interface"
260 depends on SPI_MASTER
264 Select this if your MC13xxx is connected via an SPI bus.
266 config MFD_MC13XXX_I2C
267 tristate "Freescale MC13892 I2C interface"
272 Select this if your MC13xxx is connected via an I2C bus.
274 config MFD_HI6421_PMIC
275 tristate "HiSilicon Hi6421 PMU/Codec IC"
280 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
281 functions, such as regulators, RTC, codec, Coulomb counter, etc.
282 This driver includes core APIs _only_. You have to select
283 individul components like voltage regulators under corresponding
284 menus in order to enable them.
285 We communicate with the Hi6421 via memory-mapped I/O.
288 bool "HTC EGPIO support"
289 depends on GPIOLIB && ARM
291 This driver supports the CPLD egpio chip present on
292 several HTC phones. It provides basic support for input
293 pins, output pins, and irqs.
296 tristate "HTC PASIC3 LED/DS1WM chip support"
299 This core driver provides register access for the LED/DS1WM
300 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
301 HTC Magician devices, respectively. Actual functionality is
302 handled by the leds-pasic3 and ds1wm drivers.
305 bool "HTC I2C PLD chip support"
306 depends on I2C=y && GPIOLIB
308 If you say yes here you get support for the supposed CPLD
309 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
310 This device provides input and output GPIOs through an I2C
311 interface to one or more sub-chips.
313 config MFD_INTEL_QUARK_I2C_GPIO
314 tristate "Intel Quark MFD I2C GPIO"
317 depends on COMMON_CLK
320 This MFD provides support for I2C and GPIO that exist only
321 in a single PCI device. It splits the 2 IO devices to
322 their respective IO driver.
323 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
326 tristate "Intel ICH LPC"
330 The LPC bridge function of the Intel ICH provides support for
331 many functional units. This driver provides needed support for
332 other drivers to control these functions, currently GPIO and
336 tristate "Intel SCH LPC"
340 LPC bridge function of the Intel SCH provides support for
341 System Management Bus and General Purpose I/O.
343 config INTEL_SOC_PMIC
344 bool "Support for Intel Atom SoC PMIC"
351 Select this option to enable support for the PMIC device
352 on some Intel SoC systems. The PMIC provides ADC, GPIO,
353 thermal, charger and related power management functions
356 config MFD_INTEL_LPSS
361 config MFD_INTEL_LPSS_ACPI
362 tristate "Intel Low Power Subsystem support in ACPI mode"
363 select MFD_INTEL_LPSS
364 depends on X86 && ACPI
366 This driver supports Intel Low Power Subsystem (LPSS) devices such as
367 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
370 config MFD_INTEL_LPSS_PCI
371 tristate "Intel Low Power Subsystem support in PCI mode"
372 select MFD_INTEL_LPSS
373 depends on X86 && PCI
375 This driver supports Intel Low Power Subsystem (LPSS) devices such as
376 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
379 config MFD_INTEL_MSIC
381 depends on INTEL_SCU_IPC
384 Select this option to enable access to Intel MSIC (Avatele
385 Passage) chip. This chip embeds audio, battery, GPIO, etc.
386 devices used in Intel Medfield platforms.
388 config MFD_IPAQ_MICRO
389 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
390 depends on SA1100_H3100 || SA1100_H3600
393 Select this to get support for the Microcontroller found in
394 the Compaq iPAQ handheld computers. This is an Atmel
395 AT90LS8535 microcontroller flashed with a special iPAQ
396 firmware using the custom protocol implemented in this driver.
398 config MFD_JANZ_CMODIO
399 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
403 This is the core driver for the Janz CMOD-IO PCI MODULbus
404 carrier board. This device is a PCI to MODULbus bridge which may
405 host many different types of MODULbus daughterboards, including
406 CAN and GPIO controllers.
408 config MFD_JZ4740_ADC
409 bool "Janz JZ4740 ADC core"
411 select GENERIC_IRQ_CHIP
412 depends on MACH_JZ4740
414 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
415 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
418 tristate "Kontron module PLD device"
421 This is the core driver for the PLD (Programmable Logic Device) found
422 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
423 device may provide functions like watchdog, GPIO, UART and I2C bus.
425 The following modules are supported:
429 * COMe-bPC2 (ETXexpress-PC)
430 * COMe-bSC# (ETXexpress-SC T#)
435 * COMe-cDC2 (microETXexpress-DC)
437 * COMe-cPC2 (microETXexpress-PC)
440 * COMe-mTT10 (nanoETXexpress-TT)
443 This driver can also be built as a module. If so, the module
444 will be called kempld-core.
447 tristate "Marvell 88PM800"
453 This supports for Marvell 88PM800 Power Management IC.
454 This includes the I2C driver and the core APIs _only_, you have to
455 select individual components like voltage regulators, RTC and
456 battery-charger under the corresponding menus.
459 tristate "Marvell 88PM805"
465 This supports for Marvell 88PM805 Power Management IC. This includes
466 the I2C driver and the core APIs _only_, you have to select individual
467 components like codec device, headset/Mic device under the
471 bool "Marvell 88PM8606/88PM8607"
476 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
477 This includes the I2C driver and the core APIs _only_, you have to
478 select individual components like voltage regulators, RTC and
479 battery-charger under the corresponding menus.
482 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
489 Say yes here to add support for Maxim Semiconductor MAX14577 and
490 MAX77836 Micro-USB ICs with battery charger.
491 This driver provides common support for accessing the device;
492 additional drivers must be enabled in order to use the functionality
496 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
504 Say yes here to add support for Maxim Semiconductor MAX77686 and
505 MAX77802 which are Power Management IC with an RTC on chip.
506 This driver provides common support for accessing the device;
507 additional drivers must be enabled in order to use the functionality
511 bool "Maxim Semiconductor MAX77693 PMIC Support"
517 Say yes here to add support for Maxim Semiconductor MAX77693.
518 This is a companion Power Management IC with Flash, Haptic, Charger,
519 and MUIC(Micro USB Interface Controller) controls on chip.
520 This driver provides common support for accessing the device;
521 additional drivers must be enabled in order to use the functionality
525 bool "Maxim Semiconductor MAX77843 PMIC Support"
531 Say yes here to add support for Maxim Semiconductor MAX77843.
532 This is companion Power Management IC with LEDs, Haptic, Charger,
533 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
534 This driver provides common support for accessing the device;
535 additional drivers must be enabled in order to use the functionality
539 tristate "Maxim Semiconductor MAX8907 PMIC Support"
545 Say yes here to add support for Maxim Semiconductor MAX8907. This is
546 a Power Management IC. This driver provides common support for
547 accessing the device; additional drivers must be enabled in order
548 to use the functionality of the device.
551 bool "Maxim Semiconductor MAX8925 PMIC Support"
555 Say yes here to add support for Maxim Semiconductor MAX8925. This is
556 a Power Management IC. This driver provides common support for
557 accessing the device, additional drivers must be enabled in order
558 to use the functionality of the device.
561 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
566 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
567 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
568 MUIC 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 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
579 Say yes here to add support for Maxim Semiconductor MAX8998 and
580 National Semiconductor LP3974. This is a Power Management IC.
581 This driver provides common support for accessing the device,
582 additional drivers must be enabled in order to use the functionality
586 tristate "MediaTek MT6397 PMIC Support"
590 Say yes here to add support for MediaTek MT6397 PMIC. 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 tristate "MEN 14F021P00 Board Management Controller Support"
600 Say yes here to add support for the MEN 14F021P00 BMC
601 which is a Board Management Controller connected to the I2C bus.
602 The device supports multiple sub-devices like LED, HWMON and WDT.
603 This driver provides common support for accessing the devices;
604 additional drivers must be enabled in order to use the
605 functionality of the BMC device.
607 This driver can also be built as a module. If so the module
608 will be called menf21bmc.
611 bool "Motorola EZXPCAP Support"
612 depends on SPI_MASTER
614 This enables the PCAP ASIC present on EZX Phones. This is
615 needed for MMC, TouchScreen, Sound, USB, etc..
617 config MFD_VIPERBOARD
618 tristate "Nano River Technologies Viperboard"
623 Say yes here if you want support for Nano River Technologies
625 There are mfd cell drivers available for i2c master, adc and
626 both gpios found on the board. The spi part does not yet
628 You need to select the mfd cell drivers separately.
629 The drivers do not support all features the board exposes.
632 tristate "Nokia Retu and Tahvo multi-function device"
637 Retu and Tahvo are a multi-function devices found on Nokia
638 Internet Tablets (770, N800 and N810).
641 tristate "NXP PCF50633"
645 Say yes here if you have NXP PCF50633 chip on your board.
646 This core driver provides register access and IRQ handling
647 facilities, and registers devices for the various functions
648 so that function-specific drivers can bind to them.
651 tristate "NXP PCF50633 ADC"
652 depends on MFD_PCF50633
654 Say yes here if you want to include support for ADC in the
658 tristate "NXP PCF50633 GPIO"
659 depends on MFD_PCF50633
661 Say yes here if you want to include support GPIO for pins on
665 tristate "Philips UCB1400 Core driver"
669 This enables support for the Philips UCB1400 core functions.
670 The UCB1400 is an AC97 audio codec.
672 To compile this driver as a module, choose M here: the
673 module will be called ucb1400_core.
678 config MFD_PM8921_CORE
679 tristate "Qualcomm PM8921 PMIC chip"
680 depends on (ARM || HEXAGON)
686 If you say yes to this option, support will be included for the
687 built-in PM8921 PMIC chip.
689 This is required if your board has a PM8921 and uses its features,
690 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
692 Say M here if you want to include support for PM8921 chip as a module.
693 This will build a module called "pm8921-core".
696 tristate "Qualcomm Resource Power Manager (RPM)"
697 depends on ARCH_QCOM && OF
699 If you say yes to this option, support will be included for the
700 Resource Power Manager system found in the Qualcomm 8660, 8960 and
703 This is required to access many regulators, clocks and bus
704 frequencies controlled by the RPM on these devices.
706 Say M here if you want to include support for the Qualcomm RPM as a
707 module. This will build a module called "qcom_rpm".
710 tristate "Qualcomm SPMI PMICs"
711 depends on ARCH_QCOM || COMPILE_TEST
716 This enables support for the Qualcomm SPMI PMICs.
717 These PMICs are currently used with the Snapdragon 800 series of
718 SoCs. Note, that this will only be useful paired with descriptions
719 of the independent functions as children nodes in the device tree.
721 Say M here if you want to include support for the SPMI PMIC
722 series as a module. The module will be called "qcom-spmi-pmic".
725 tristate "RDC R-321x southbridge"
729 Say yes here if you want to have support for the RDC R-321x SoC
730 southbridge which provides access to GPIOs and Watchdog using the
731 southbridge PCI device configuration space.
734 tristate "Realtek PCI-E card reader"
738 This supports for Realtek PCI-Express card reader including rts5209,
739 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
740 Realtek card reader supports access to many types of memory cards,
741 such as Memory Stick, Memory Stick Pro, Secure Digital and
745 tristate "Richtek RT5033 Power Management IC"
751 This driver provides for the Richtek RT5033 Power Management IC,
752 which includes the I2C driver and the Core APIs. This driver provides
753 common support for accessing the device. The device supports multiple
754 sub-devices like charger, fuel gauge, flash LED, current source,
758 tristate "Realtek USB card reader"
762 Select this option to get support for Realtek USB 2.0 card readers
763 including RTS5129, RTS5139, RTS5179 and RTS5170.
764 Realtek card reader supports access to many types of memory cards,
765 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
768 bool "Ricoh RC5T583 Power Management system device"
773 Select this option to get support for the RICOH583 Power
774 Management system device.
775 This driver provides common support for accessing the device
776 through i2c interface. The device supports multiple sub-devices
777 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
778 Additional drivers must be enabled in order to use the
779 different functionality of the device.
782 tristate "Rockchip RK808 Power Management chip"
788 If you say yes here you get support for the RK808
789 Power Management chips.
790 This driver provides common support for accessing the device
791 through I2C interface. The device supports multiple sub-devices
792 including interrupts, RTC, LDO & DCDC regulators, and onkey.
795 tristate "Ricoh RN5T5618 PMIC"
800 Say yes here to add support for the Ricoh RN5T618 PMIC. This
801 driver provides common support for accessing the device,
802 additional drivers must be enabled in order to use the
803 functionality of the device.
806 bool "SAMSUNG Electronics PMIC Series Support"
812 Support for the Samsung Electronics MFD series.
813 This driver provides common support for accessing the device,
814 additional drivers must be enabled in order to use the functionality
817 config MFD_SI476X_CORE
818 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
823 This is the core driver for the SI476x series of AM/FM
824 radio. This MFD driver connects the radio-si476x V4L2 module
825 and the si476x audio codec.
827 To compile this driver as a module, choose M here: the
828 module will be called si476x-core.
831 tristate "Silicon Motion SM501"
833 This is the core driver for the Silicon Motion SM501 multimedia
834 companion chip. This device is a multifunction device which may
835 provide numerous interfaces including USB host controller, USB gadget,
836 asynchronous serial ports, audio functions, and a dual display video
837 interface. The device may be connected by PCI or local bus with
838 varying functions enabled.
840 config MFD_SM501_GPIO
841 bool "Export GPIO via GPIO layer"
842 depends on MFD_SM501 && GPIOLIB
844 This option uses the gpio library layer to export the 64 GPIO
845 lines on the SM501. The platform data is used to supply the
846 base number for the first GPIO line to register.
849 tristate "Skyworks Solutions SKY81452"
854 This is the core driver for the Skyworks SKY81452 backlight and
855 voltage regulator device.
857 This driver can also be built as a module. If so, the module
858 will be called sky81452.
861 bool "SMSC ECE1099 series chips"
866 If you say yes here you get support for the
867 ece1099 chips from SMSC.
869 To compile this driver as a module, choose M here: the
870 module will be called smsc.
873 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
874 default y if ARCH_U300 || ARCH_U8500
876 Say yes here if you have the ABX500 Mixed Signal IC family
877 chips. This core driver expose register access functions.
878 Functionality specific drivers using these functions can
879 remain unchanged when IC changes. Binding of the functions to
880 actual register access is done by the IC core driver.
883 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
884 depends on I2C=y && ABX500_CORE
886 default y if ARCH_U300
888 Select this to enable the AB3100 Mixed Signal IC core
889 functionality. This connects to a AB3100 on the I2C bus
890 and expose a number of symbols needed for dependent devices
891 to read and write registers and subscribe to events from
892 this multi-functional IC. This is needed to use other features
893 of the AB3100 such as battery-backed RTC, charging control,
894 LEDs, vibrator, system power and temperature, power management
898 tristate "ST-Ericsson AB3100 OTP functions"
899 depends on AB3100_CORE
900 default y if AB3100_CORE
902 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
903 programmable memory) support. This exposes a sysfs file to read
907 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
908 depends on ABX500_CORE && MFD_DB8500_PRCMU
913 Select this option to enable access to AB8500 power management
914 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
915 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
916 the irq_chip parts for handling the Mixed Signal chip events.
917 This chip embeds various other multimedia funtionalities as well.
920 bool "Enable debug info via debugfs"
921 depends on AB8500_GPADC && DEBUG_FS
922 default y if DEBUG_FS
924 Select this option if you want debug information using the debug
928 bool "ST-Ericsson AB8500 GPADC driver"
929 depends on AB8500_CORE && REGULATOR_AB8500
932 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
934 config MFD_DB8500_PRCMU
935 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
936 depends on UX500_SOC_DB8500
939 Select this option to enable support for the DB8500 Power Reset
940 and Control Management Unit. This is basically an autonomous
941 system controller running an XP70 microprocessor, which is accessed
942 through a register map.
945 bool "STMicroelectronics STMPE"
946 depends on (I2C=y || SPI_MASTER=y)
950 Support for the STMPE family of I/O Expanders from
953 Currently supported devices are:
955 STMPE811: GPIO, Touchscreen
956 STMPE1601: GPIO, Keypad
957 STMPE1801: GPIO, Keypad
958 STMPE2401: GPIO, Keypad
959 STMPE2403: GPIO, Keypad
961 This driver provides common support for accessing the device,
962 additional drivers must be enabled in order to use the functionality
963 of the device. Currently available sub drivers are:
967 Touchscreen: stmpe-ts
969 menu "STMicroelectronics STMPE Interface Drivers"
973 bool "STMicroelectronics STMPE I2C Interface"
977 This is used to enable I2C interface of STMPE
980 bool "STMicroelectronics STMPE SPI Interface"
981 depends on SPI_MASTER
983 This is used to enable SPI interface of STMPE
987 bool "STMicroelectronics STA2X11"
992 config MFD_SUN6I_PRCM
993 bool "Allwinner A31 PRCM controller"
994 depends on ARCH_SUNXI
997 Support for the PRCM (Power/Reset/Clock Management) unit available
1001 bool "System Controller Register R/W Based on Regmap"
1004 Select this option to enable accessing system control registers
1007 config MFD_DAVINCI_VOICECODEC
1012 config MFD_TI_AM335X_TSCADC
1013 tristate "TI ADC / Touch Screen chip support"
1018 If you say yes here you get support for Texas Instruments series
1019 of Touch Screen /ADC chips.
1020 To compile this driver as a module, choose M here: the
1021 module will be called ti_am335x_tscadc.
1023 config MFD_DM355EVM_MSP
1024 bool "TI DaVinci DM355 EVM microcontroller"
1025 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1027 This driver supports the MSP430 microcontroller used on these
1028 boards. MSP430 firmware manages resets and power sequencing,
1029 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1032 tristate "TI/National Semiconductor LP3943 MFD Driver"
1037 Support for the TI/National Semiconductor LP3943.
1038 This driver consists of GPIO and PWM drivers.
1039 With these functionalities, it can be used for LED string control or
1040 general usage such like a GPIO controller and a PWM controller.
1043 bool "TI LP8788 Power Management Unit Driver"
1049 TI LP8788 PMU supports regulators, battery charger, RTC,
1050 ADC, backlight driver and current sinks.
1052 config MFD_OMAP_USB_HOST
1053 bool "TI OMAP USBHS core and TLL driver"
1054 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1057 This is the core driver for the OAMP EHCI and OHCI drivers.
1058 This MFD driver does the required setup functionalities for
1059 OMAP USB Host drivers.
1062 bool "TI Palmas series chips"
1068 If you say yes here you get support for the Palmas
1069 series of PMIC chips from Texas Instruments.
1072 tristate "TI TPS61050/61052 Boost Converters"
1077 select REGULATOR_FIXED_VOLTAGE
1079 This option enables a driver for the TP61050/TPS61052
1080 high-power "white LED driver". This boost converter is
1081 sometimes used for other things than white LEDs, and
1082 also contains a GPIO pin.
1085 tristate "TI TPS6501x Power Management chips"
1086 depends on I2C && GPIOLIB
1087 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1089 If you say yes here you get support for the TPS6501x series of
1090 Power Management chips. These include voltage regulators,
1091 lithium ion/polymer battery charging, and other features that
1092 are often used in portable devices like cell phones and cameras.
1094 This driver can also be built as a module. If so, the module
1095 will be called tps65010.
1098 tristate "TI TPS6507x Power Management / Touch Screen chips"
1102 If you say yes here you get support for the TPS6507x series of
1103 Power Management / Touch Screen chips. These include voltage
1104 regulators, lithium ion/polymer battery charging, touch screen
1105 and other features that are often used in portable devices.
1106 This driver can also be built as a module. If so, the module
1107 will be called tps6507x.
1110 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1116 If you say yes here you get support for the TPS65086 series of
1117 Power Management chips.
1118 This driver provides common support for accessing the device,
1119 additional drivers must be enabled in order to use the
1120 functionality of the device.
1122 config TPS65911_COMPARATOR
1126 bool "TI TPS65090 Power Management chips"
1132 If you say yes here you get support for the TPS65090 series of
1133 Power Management chips.
1134 This driver provides common support for accessing the device,
1135 additional drivers must be enabled in order to use the
1136 functionality of the device.
1139 tristate "TI TPS65217 Power Management / White LED chips"
1144 If you say yes here you get support for the TPS65217 series of
1145 Power Management / White LED chips.
1146 These include voltage regulators, lithium ion/polymer battery
1147 charger, wled and other features that are often used in portable
1150 This driver can also be built as a module. If so, the module
1151 will be called tps65217.
1154 tristate "TI TPS65218 Power Management chips"
1160 If you say yes here you get support for the TPS65218 series of
1161 Power Management chips.
1162 These include voltage regulators, gpio and other features
1163 that are often used in portable devices. Only regulator
1164 component is currently supported.
1166 This driver can also be built as a module. If so, the module
1167 will be called tps65218.
1170 bool "TI TPS6586x Power Management chips"
1175 If you say yes here you get support for the TPS6586X series of
1176 Power Management chips.
1177 This driver provides common support for accessing the device,
1178 additional drivers must be enabled in order to use the
1179 functionality of the device.
1181 This driver can also be built as a module. If so, the module
1182 will be called tps6586x.
1185 bool "TI TPS65910 Power Management chip"
1187 depends on GPIOLIB || COMPILE_TEST
1193 if you say yes here you get support for the TPS65910 series of
1194 Power Management chips.
1197 bool "TI TPS65912 Power Management chip"
1201 If you say yes here you get support for the TPS65912 series of
1204 config MFD_TPS65912_I2C
1205 bool "TI TPS65912 Power Management chip with I2C"
1208 depends on I2C=y && GPIOLIB
1210 If you say yes here you get support for the TPS65912 series of
1211 PM chips with I2C interface.
1213 config MFD_TPS65912_SPI
1214 bool "TI TPS65912 Power Management chip with SPI"
1217 depends on SPI_MASTER && GPIOLIB
1219 If you say yes here you get support for the TPS65912 series of
1220 PM chips with SPI interface.
1223 bool "TI TPS80031/TPS80032 Power Management chips"
1229 If you say yes here you get support for the Texas Instruments
1230 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1231 Path and Battery Charger. The device provides five configurable
1232 step-down converters, 11 general purpose LDOs, USB OTG Module,
1233 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1234 Power Path from USB, 32K clock generator.
1237 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1242 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1243 This core driver provides register access and IRQ handling
1244 facilities, and registers devices for the various functions
1245 so that function-specific drivers can bind to them.
1247 These multi-function chips are found on many OMAP2 and OMAP3
1248 boards, providing power management, RTC, GPIO, keypad, a
1249 high speed USB OTG transceiver, an audio codec (on most
1250 versions) and many other features.
1252 config TWL4030_POWER
1253 bool "TI TWL4030 power resources"
1254 depends on TWL4030_CORE && ARM
1256 Say yes here if you want to use the power resources on the
1257 TWL4030 family chips. Most of these resources are regulators,
1258 which have a separate driver; some are control signals, such
1259 as clock request handshaking.
1261 This driver uses board-specific data to initialize the resources
1262 and load scripts controlling which resources are switched off/on
1263 or reset when a sleep, wakeup or warm reset event occurs.
1265 config MFD_TWL4030_AUDIO
1266 bool "TI TWL4030 Audio"
1267 depends on TWL4030_CORE
1272 bool "TI TWL6040 audio codec"
1279 Say yes here if you want support for Texas Instruments TWL6040 audio
1281 This driver provides common support for accessing the device,
1282 additional drivers must be enabled in order to use the
1283 functionality of the device (audio, vibra).
1286 bool "TI TWL92330/Menelaus PM chip"
1287 depends on I2C=y && ARCH_OMAP2
1289 If you say yes here you get support for the Texas Instruments
1290 TWL92330/Menelaus Power Management chip. This include voltage
1291 regulators, Dual slot memory card transceivers, real-time clock
1292 and other features that are often used in portable devices like
1293 cell phones and PDAs.
1295 config MFD_WL1273_CORE
1296 tristate "TI WL1273 FM radio"
1301 This is the core driver for the TI WL1273 FM radio. This MFD
1302 driver connects the radio-wl1273 V4L2 module and the wl1273
1306 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1311 Say yes here to enable support for National Semiconductor / TI
1312 LM3533 Lighting Power chips.
1314 This driver provides common support for accessing the device;
1315 additional drivers must be enabled in order to use the LED,
1316 backlight or ambient-light-sensor functionality of the device.
1318 config MFD_TIMBERDALE
1319 tristate "Timberdale FPGA"
1321 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1323 This is the core driver for the timberdale FPGA. This device is a
1324 multifunction device which exposes numerous platform devices.
1326 The timberdale FPGA can be found on the Intel Atom development board
1327 for in-vehicle infontainment, called Russellville.
1330 bool "Toshiba TC35892 and variants"
1335 Support for the Toshiba TC35892 and variants I/O Expander.
1337 This driver provides common support for accessing the device,
1338 additional drivers must be enabled in order to use the
1339 functionality of the device.
1346 bool "Toshiba T7L66XB"
1347 depends on ARM && HAVE_CLK
1351 Support for Toshiba Mobile IO Controller T7L66XB
1354 bool "Toshiba TC6387XB"
1355 depends on ARM && HAVE_CLK
1359 Support for Toshiba Mobile IO Controller TC6387XB
1362 bool "Toshiba TC6393XB"
1363 depends on ARM && HAVE_CLK
1368 Support for Toshiba Mobile IO Controller TC6393XB
1371 tristate "VIA VX855/VX875 integrated south bridge"
1375 Say yes here to enable support for various functions of the
1376 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1377 and/or vx855_gpio drivers for this to do anything useful.
1385 config MFD_ARIZONA_I2C
1386 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1392 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1393 audio SoC core functionality controlled via I2C.
1395 config MFD_ARIZONA_SPI
1396 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1400 depends on SPI_MASTER
1402 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1403 audio SoC core functionality controlled via I2C.
1406 bool "Cirrus Logic CS47L24 and WM1831"
1407 depends on MFD_ARIZONA
1409 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1412 bool "Wolfson Microelectronics WM5102"
1413 depends on MFD_ARIZONA
1415 Support for Wolfson Microelectronics WM5102 low power audio SoC
1418 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1419 depends on MFD_ARIZONA
1421 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1425 bool "Wolfson Microelectronics WM8997"
1426 depends on MFD_ARIZONA
1428 Support for Wolfson Microelectronics WM8997 low power audio SoC
1431 bool "Wolfson Microelectronics WM8998"
1432 depends on MFD_ARIZONA
1434 Support for Wolfson Microelectronics WM8998 low power audio SoC
1437 bool "Wolfson Microelectronics WM8400"
1442 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1443 CODEC. This driver provides common support for accessing
1444 the device, additional drivers must be enabled in order to use
1445 the functionality of the device.
1450 config MFD_WM831X_I2C
1451 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1458 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1459 when controlled using I2C. This driver provides common support
1460 for accessing the device, additional drivers must be enabled in
1461 order to use the functionality of the device.
1463 config MFD_WM831X_SPI
1464 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1469 depends on SPI_MASTER
1471 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1472 when controlled using SPI. This driver provides common support
1473 for accessing the device, additional drivers must be enabled in
1474 order to use the functionality of the device.
1479 config MFD_WM8350_I2C
1480 bool "Wolfson Microelectronics WM8350 with I2C"
1484 The WM8350 is an integrated audio and power management
1485 subsystem with watchdog and RTC functionality for embedded
1486 systems. This option enables core support for the WM8350 with
1487 I2C as the control interface. Additional options must be
1488 selected to enable support for the functionality of the chip.
1491 tristate "Wolfson Microelectronics WM8994"
1497 The WM8994 is a highly integrated hi-fi CODEC designed for
1498 smartphone applications. As well as audio functionality it
1499 has on board GPIO and regulator functionality which is
1500 supported via the relevant subsystems. This driver provides
1501 core support for the WM8994, in order to use the actual
1502 functionaltiy of the device other drivers must be enabled.
1505 tristate "Support for ST Microelectronics STw481x"
1506 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1510 Select this option to enable the STw481x chip driver used
1511 in various ST Microelectronics and ST-Ericsson embedded
1514 menu "Multimedia Capabilities Port drivers"
1515 depends on ARCH_SA1100
1522 tristate "Support SA11x0 MCP interface"
1523 depends on ARCH_SA1100
1528 tristate "Support for UCB1200 / UCB1300"
1529 depends on MCP_SA11X0
1532 config MCP_UCB1200_TS
1533 tristate "Touchscreen interface support"
1534 depends on MCP_UCB1200 && INPUT
1538 config MFD_VEXPRESS_SYSREG
1539 bool "Versatile Express System Registers"
1540 depends on VEXPRESS_CONFIG && GPIOLIB
1543 select GPIO_GENERIC_PLATFORM
1547 System Registers are the platform configuration block
1548 on the ARM Ltd. Versatile Express board.