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
99 tristate "X-Powers AXP series PMICs with I2C"
104 If you say Y here you get support for the X-Powers AXP series power
105 management ICs (PMICs) controlled with I2C.
106 This driver include only the core APIs. You have to select individual
107 components like regulators or the PEK (Power Enable Key) under the
110 config MFD_AXP20X_RSB
111 tristate "X-Powers AXP series PMICs with RSB"
115 If you say Y here you get support for the X-Powers AXP series power
116 management ICs (PMICs) controlled with RSB.
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
122 tristate "ChromeOS Embedded Controller"
124 select CHROME_PLATFORMS
126 depends on X86 || ARM || COMPILE_TEST
128 If you say Y here you get support for the ChromeOS Embedded
129 Controller (EC) providing keyboard, battery and power services.
130 You also need to enable the driver for the bus you are using. The
131 protocol for talking to the EC is defined by the bus driver.
133 config MFD_CROS_EC_I2C
134 tristate "ChromeOS Embedded Controller (I2C)"
135 depends on MFD_CROS_EC && I2C
138 If you say Y here, you get support for talking to the ChromeOS
139 EC through an I2C bus. This uses a simple byte-level protocol with
140 a checksum. Failing accesses will be retried three times to
143 config MFD_CROS_EC_SPI
144 tristate "ChromeOS Embedded Controller (SPI)"
145 depends on MFD_CROS_EC && SPI
148 If you say Y here, you get support for talking to the ChromeOS EC
149 through a SPI bus, using a byte-level protocol. Since the EC's
150 response time cannot be guaranteed, we support ignoring
151 'pre-amble' bytes before the response actually starts.
155 depends on GPIOLIB && ARM
158 This driver supports the ASIC3 multifunction chip found on many
159 PDAs (mainly iPAQ and HTC based ones)
162 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
165 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
166 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
167 usually found on PXA processors-based platforms. This includes
168 the I2C driver and the core APIs _only_, you have to select
169 individual components like LCD backlight, voltage regulators,
170 LEDs and battery-charger under the corresponding menus.
176 config MFD_DA9052_SPI
177 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
181 depends on SPI_MASTER=y
183 Support for the Dialog Semiconductor DA9052 PMIC
184 when controlled using SPI. This driver provides common support
185 for accessing the device, additional drivers must be enabled in
186 order to use the functionality of the device.
188 config MFD_DA9052_I2C
189 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
195 Support for the Dialog Semiconductor DA9052 PMIC
196 when controlled using I2C. This driver provides common support
197 for accessing the device, additional drivers must be enabled in
198 order to use the functionality of the device.
201 bool "Dialog Semiconductor DA9055 PMIC Support"
207 Say yes here for support of Dialog Semiconductor DA9055. This is
208 a Power Management IC. This driver provides common support for
209 accessing the device as well as the I2C interface to the chip itself.
210 Additional drivers must be enabled in order to use the functionality
213 This driver can be built as a module. If built as a module it will be
217 tristate "Dialog Semiconductor DA9062 PMIC Support"
223 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
224 This includes the I2C driver and core APIs.
225 Additional drivers must be enabled in order to use the functionality
229 tristate "Dialog Semiconductor DA9063 PMIC Support"
235 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
236 This includes the I2C driver and core APIs.
237 Additional drivers must be enabled in order to use the functionality
241 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
247 This adds support for the DA9150 integrated charger and fuel-gauge
248 chip. This driver provides common support for accessing the device.
249 Additional drivers must be enabled in order to use the specific
250 features of the device.
253 tristate "Diolan DLN2 support"
257 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
258 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
259 etc. must be enabled in order to use the functionality of
264 depends on (SPI_MASTER || I2C)
268 Enable support for the Freescale MC13783 and MC13892 PMICs.
269 This driver provides common support for accessing the device,
270 additional drivers must be enabled in order to use the
271 functionality of the device.
273 config MFD_MC13XXX_SPI
274 tristate "Freescale MC13783 and MC13892 SPI interface"
275 depends on SPI_MASTER
279 Select this if your MC13xxx is connected via an SPI bus.
281 config MFD_MC13XXX_I2C
282 tristate "Freescale MC13892 I2C interface"
287 Select this if your MC13xxx is connected via an I2C bus.
289 config MFD_MX25_TSADC
290 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
292 depends on (SOC_IMX25 && OF) || COMPILE_TEST
294 Enable support for the integrated Touchscreen and ADC unit of the
295 i.MX25 processors. They consist of a conversion queue for general
296 purpose ADC and a queue for Touchscreens.
298 config MFD_HI6421_PMIC
299 tristate "HiSilicon Hi6421 PMU/Codec IC"
304 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
305 functions, such as regulators, RTC, codec, Coulomb counter, etc.
306 This driver includes core APIs _only_. You have to select
307 individul components like voltage regulators under corresponding
308 menus in order to enable them.
309 We communicate with the Hi6421 via memory-mapped I/O.
312 bool "HTC EGPIO support"
313 depends on GPIOLIB && ARM
315 This driver supports the CPLD egpio chip present on
316 several HTC phones. It provides basic support for input
317 pins, output pins, and irqs.
320 tristate "HTC PASIC3 LED/DS1WM chip support"
323 This core driver provides register access for the LED/DS1WM
324 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
325 HTC Magician devices, respectively. Actual functionality is
326 handled by the leds-pasic3 and ds1wm drivers.
329 bool "HTC I2C PLD chip support"
330 depends on I2C=y && GPIOLIB
332 If you say yes here you get support for the supposed CPLD
333 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
334 This device provides input and output GPIOs through an I2C
335 interface to one or more sub-chips.
337 config MFD_INTEL_QUARK_I2C_GPIO
338 tristate "Intel Quark MFD I2C GPIO"
341 depends on COMMON_CLK
344 This MFD provides support for I2C and GPIO that exist only
345 in a single PCI device. It splits the 2 IO devices to
346 their respective IO driver.
347 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
350 tristate "Intel ICH LPC"
354 The LPC bridge function of the Intel ICH provides support for
355 many functional units. This driver provides needed support for
356 other drivers to control these functions, currently GPIO and
360 tristate "Intel SCH LPC"
364 LPC bridge function of the Intel SCH provides support for
365 System Management Bus and General Purpose I/O.
367 config INTEL_SOC_PMIC
368 bool "Support for Intel Atom SoC PMIC"
375 Select this option to enable support for the PMIC device
376 on some Intel SoC systems. The PMIC provides ADC, GPIO,
377 thermal, charger and related power management functions
380 config MFD_INTEL_LPSS
385 config MFD_INTEL_LPSS_ACPI
386 tristate "Intel Low Power Subsystem support in ACPI mode"
387 select MFD_INTEL_LPSS
388 depends on X86 && ACPI
390 This driver supports Intel Low Power Subsystem (LPSS) devices such as
391 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
394 config MFD_INTEL_LPSS_PCI
395 tristate "Intel Low Power Subsystem support in PCI mode"
396 select MFD_INTEL_LPSS
397 depends on X86 && PCI
399 This driver supports Intel Low Power Subsystem (LPSS) devices such as
400 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
403 config MFD_INTEL_MSIC
405 depends on INTEL_SCU_IPC
408 Select this option to enable access to Intel MSIC (Avatele
409 Passage) chip. This chip embeds audio, battery, GPIO, etc.
410 devices used in Intel Medfield platforms.
412 config MFD_IPAQ_MICRO
413 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
414 depends on SA1100_H3100 || SA1100_H3600
417 Select this to get support for the Microcontroller found in
418 the Compaq iPAQ handheld computers. This is an Atmel
419 AT90LS8535 microcontroller flashed with a special iPAQ
420 firmware using the custom protocol implemented in this driver.
422 config MFD_JANZ_CMODIO
423 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
427 This is the core driver for the Janz CMOD-IO PCI MODULbus
428 carrier board. This device is a PCI to MODULbus bridge which may
429 host many different types of MODULbus daughterboards, including
430 CAN and GPIO controllers.
432 config MFD_JZ4740_ADC
433 bool "Janz JZ4740 ADC core"
435 select GENERIC_IRQ_CHIP
436 depends on MACH_JZ4740
438 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
439 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
442 tristate "Kontron module PLD device"
445 This is the core driver for the PLD (Programmable Logic Device) found
446 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
447 device may provide functions like watchdog, GPIO, UART and I2C bus.
449 The following modules are supported:
453 * COMe-bPC2 (ETXexpress-PC)
454 * COMe-bSC# (ETXexpress-SC T#)
459 * COMe-cDC2 (microETXexpress-DC)
461 * COMe-cPC2 (microETXexpress-PC)
464 * COMe-mTT10 (nanoETXexpress-TT)
467 This driver can also be built as a module. If so, the module
468 will be called kempld-core.
471 tristate "Marvell 88PM800"
477 This supports for Marvell 88PM800 Power Management IC.
478 This includes the I2C driver and the core APIs _only_, you have to
479 select individual components like voltage regulators, RTC and
480 battery-charger under the corresponding menus.
483 tristate "Marvell 88PM805"
489 This supports for Marvell 88PM805 Power Management IC. This includes
490 the I2C driver and the core APIs _only_, you have to select individual
491 components like codec device, headset/Mic device under the
495 bool "Marvell 88PM8606/88PM8607"
500 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
501 This includes the I2C driver and the core APIs _only_, you have to
502 select individual components like voltage regulators, RTC and
503 battery-charger under the corresponding menus.
506 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
513 Say yes here to add support for Maxim Semiconductor MAX14577 and
514 MAX77836 Micro-USB ICs with battery charger.
515 This driver provides common support for accessing the device;
516 additional drivers must be enabled in order to use the functionality
520 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
528 Say yes here to add support for Maxim Semiconductor MAX77686 and
529 MAX77802 which are Power Management IC with an RTC on chip.
530 This driver provides common support for accessing the device;
531 additional drivers must be enabled in order to use the functionality
535 bool "Maxim Semiconductor MAX77693 PMIC Support"
541 Say yes here to add support for Maxim Semiconductor MAX77693.
542 This is a companion Power Management IC with Flash, Haptic, Charger,
543 and MUIC(Micro USB Interface Controller) controls on chip.
544 This driver provides common support for accessing the device;
545 additional drivers must be enabled in order to use the functionality
549 bool "Maxim Semiconductor MAX77843 PMIC Support"
555 Say yes here to add support for Maxim Semiconductor MAX77843.
556 This is companion Power Management IC with LEDs, Haptic, Charger,
557 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
558 This driver provides common support for accessing the device;
559 additional drivers must be enabled in order to use the functionality
563 tristate "Maxim Semiconductor MAX8907 PMIC Support"
569 Say yes here to add support for Maxim Semiconductor MAX8907. This is
570 a Power Management IC. This driver provides common support for
571 accessing the device; additional drivers must be enabled in order
572 to use the functionality of the device.
575 bool "Maxim Semiconductor MAX8925 PMIC Support"
579 Say yes here to add support for Maxim Semiconductor MAX8925. This is
580 a Power Management IC. This driver provides common support for
581 accessing the device, additional drivers must be enabled in order
582 to use the functionality of the device.
585 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
590 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
591 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
592 MUIC controls on chip.
593 This driver provides common support for accessing the device;
594 additional drivers must be enabled in order to use the functionality
598 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
603 Say yes here to add support for Maxim Semiconductor MAX8998 and
604 National Semiconductor LP3974. This is a Power Management IC.
605 This driver provides common support for accessing the device,
606 additional drivers must be enabled in order to use the functionality
610 tristate "MediaTek MT6397 PMIC Support"
614 Say yes here to add support for MediaTek MT6397 PMIC. This is
615 a Power Management IC. This driver provides common support for
616 accessing the device; additional drivers must be enabled in order
617 to use the functionality of the device.
620 tristate "MEN 14F021P00 Board Management Controller Support"
624 Say yes here to add support for the MEN 14F021P00 BMC
625 which is a Board Management Controller connected to the I2C bus.
626 The device supports multiple sub-devices like LED, HWMON and WDT.
627 This driver provides common support for accessing the devices;
628 additional drivers must be enabled in order to use the
629 functionality of the BMC device.
631 This driver can also be built as a module. If so the module
632 will be called menf21bmc.
635 bool "Motorola EZXPCAP Support"
636 depends on SPI_MASTER
638 This enables the PCAP ASIC present on EZX Phones. This is
639 needed for MMC, TouchScreen, Sound, USB, etc..
641 config MFD_VIPERBOARD
642 tristate "Nano River Technologies Viperboard"
647 Say yes here if you want support for Nano River Technologies
649 There are mfd cell drivers available for i2c master, adc and
650 both gpios found on the board. The spi part does not yet
652 You need to select the mfd cell drivers separately.
653 The drivers do not support all features the board exposes.
656 tristate "Nokia Retu and Tahvo multi-function device"
661 Retu and Tahvo are a multi-function devices found on Nokia
662 Internet Tablets (770, N800 and N810).
665 tristate "NXP PCF50633"
669 Say yes here if you have NXP PCF50633 chip on your board.
670 This core driver provides register access and IRQ handling
671 facilities, and registers devices for the various functions
672 so that function-specific drivers can bind to them.
675 tristate "NXP PCF50633 ADC"
676 depends on MFD_PCF50633
678 Say yes here if you want to include support for ADC in the
682 tristate "NXP PCF50633 GPIO"
683 depends on MFD_PCF50633
685 Say yes here if you want to include support GPIO for pins on
689 tristate "Philips UCB1400 Core driver"
693 This enables support for the Philips UCB1400 core functions.
694 The UCB1400 is an AC97 audio codec.
696 To compile this driver as a module, choose M here: the
697 module will be called ucb1400_core.
702 config MFD_PM8921_CORE
703 tristate "Qualcomm PM8921 PMIC chip"
704 depends on (ARM || HEXAGON)
710 If you say yes to this option, support will be included for the
711 built-in PM8921 PMIC chip.
713 This is required if your board has a PM8921 and uses its features,
714 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
716 Say M here if you want to include support for PM8921 chip as a module.
717 This will build a module called "pm8921-core".
720 tristate "Qualcomm Resource Power Manager (RPM)"
721 depends on ARCH_QCOM && OF
723 If you say yes to this option, support will be included for the
724 Resource Power Manager system found in the Qualcomm 8660, 8960 and
727 This is required to access many regulators, clocks and bus
728 frequencies controlled by the RPM on these devices.
730 Say M here if you want to include support for the Qualcomm RPM as a
731 module. This will build a module called "qcom_rpm".
734 tristate "Qualcomm SPMI PMICs"
735 depends on ARCH_QCOM || COMPILE_TEST
740 This enables support for the Qualcomm SPMI PMICs.
741 These PMICs are currently used with the Snapdragon 800 series of
742 SoCs. Note, that this will only be useful paired with descriptions
743 of the independent functions as children nodes in the device tree.
745 Say M here if you want to include support for the SPMI PMIC
746 series as a module. The module will be called "qcom-spmi-pmic".
749 tristate "RDC R-321x southbridge"
753 Say yes here if you want to have support for the RDC R-321x SoC
754 southbridge which provides access to GPIOs and Watchdog using the
755 southbridge PCI device configuration space.
758 tristate "Realtek PCI-E card reader"
762 This supports for Realtek PCI-Express card reader including rts5209,
763 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
764 Realtek card reader supports access to many types of memory cards,
765 such as Memory Stick, Memory Stick Pro, Secure Digital and
769 tristate "Richtek RT5033 Power Management IC"
775 This driver provides for the Richtek RT5033 Power Management IC,
776 which includes the I2C driver and the Core APIs. This driver provides
777 common support for accessing the device. The device supports multiple
778 sub-devices like charger, fuel gauge, flash LED, current source,
782 tristate "Realtek USB card reader"
786 Select this option to get support for Realtek USB 2.0 card readers
787 including RTS5129, RTS5139, RTS5179 and RTS5170.
788 Realtek card reader supports access to many types of memory cards,
789 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
792 bool "Ricoh RC5T583 Power Management system device"
797 Select this option to get support for the RICOH583 Power
798 Management system device.
799 This driver provides common support for accessing the device
800 through i2c interface. The device supports multiple sub-devices
801 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
802 Additional drivers must be enabled in order to use the
803 different functionality of the device.
806 tristate "Rockchip RK808 Power Management chip"
812 If you say yes here you get support for the RK808
813 Power Management chips.
814 This driver provides common support for accessing the device
815 through I2C interface. The device supports multiple sub-devices
816 including interrupts, RTC, LDO & DCDC regulators, and onkey.
819 tristate "Ricoh RN5T5618 PMIC"
824 Say yes here to add support for the Ricoh RN5T618 PMIC. This
825 driver provides common support for accessing the device,
826 additional drivers must be enabled in order to use the
827 functionality of the device.
830 bool "SAMSUNG Electronics PMIC Series Support"
836 Support for the Samsung Electronics MFD series.
837 This driver provides common support for accessing the device,
838 additional drivers must be enabled in order to use the functionality
841 config MFD_SI476X_CORE
842 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
847 This is the core driver for the SI476x series of AM/FM
848 radio. This MFD driver connects the radio-si476x V4L2 module
849 and the si476x audio codec.
851 To compile this driver as a module, choose M here: the
852 module will be called si476x-core.
855 tristate "Silicon Motion SM501"
857 This is the core driver for the Silicon Motion SM501 multimedia
858 companion chip. This device is a multifunction device which may
859 provide numerous interfaces including USB host controller, USB gadget,
860 asynchronous serial ports, audio functions, and a dual display video
861 interface. The device may be connected by PCI or local bus with
862 varying functions enabled.
864 config MFD_SM501_GPIO
865 bool "Export GPIO via GPIO layer"
866 depends on MFD_SM501 && GPIOLIB
868 This option uses the gpio library layer to export the 64 GPIO
869 lines on the SM501. The platform data is used to supply the
870 base number for the first GPIO line to register.
873 tristate "Skyworks Solutions SKY81452"
878 This is the core driver for the Skyworks SKY81452 backlight and
879 voltage regulator device.
881 This driver can also be built as a module. If so, the module
882 will be called sky81452.
885 bool "SMSC ECE1099 series chips"
890 If you say yes here you get support for the
891 ece1099 chips from SMSC.
893 To compile this driver as a module, choose M here: the
894 module will be called smsc.
897 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
898 default y if ARCH_U300 || ARCH_U8500
900 Say yes here if you have the ABX500 Mixed Signal IC family
901 chips. This core driver expose register access functions.
902 Functionality specific drivers using these functions can
903 remain unchanged when IC changes. Binding of the functions to
904 actual register access is done by the IC core driver.
907 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
908 depends on I2C=y && ABX500_CORE
910 default y if ARCH_U300
912 Select this to enable the AB3100 Mixed Signal IC core
913 functionality. This connects to a AB3100 on the I2C bus
914 and expose a number of symbols needed for dependent devices
915 to read and write registers and subscribe to events from
916 this multi-functional IC. This is needed to use other features
917 of the AB3100 such as battery-backed RTC, charging control,
918 LEDs, vibrator, system power and temperature, power management
922 tristate "ST-Ericsson AB3100 OTP functions"
923 depends on AB3100_CORE
924 default y if AB3100_CORE
926 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
927 programmable memory) support. This exposes a sysfs file to read
931 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
932 depends on ABX500_CORE && MFD_DB8500_PRCMU
937 Select this option to enable access to AB8500 power management
938 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
939 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
940 the irq_chip parts for handling the Mixed Signal chip events.
941 This chip embeds various other multimedia funtionalities as well.
944 bool "Enable debug info via debugfs"
945 depends on AB8500_GPADC && DEBUG_FS
946 default y if DEBUG_FS
948 Select this option if you want debug information using the debug
952 bool "ST-Ericsson AB8500 GPADC driver"
953 depends on AB8500_CORE && REGULATOR_AB8500
956 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
958 config MFD_DB8500_PRCMU
959 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
960 depends on UX500_SOC_DB8500
963 Select this option to enable support for the DB8500 Power Reset
964 and Control Management Unit. This is basically an autonomous
965 system controller running an XP70 microprocessor, which is accessed
966 through a register map.
969 bool "STMicroelectronics STMPE"
970 depends on (I2C=y || SPI_MASTER=y)
974 Support for the STMPE family of I/O Expanders from
977 Currently supported devices are:
979 STMPE811: GPIO, Touchscreen
980 STMPE1601: GPIO, Keypad
981 STMPE1801: GPIO, Keypad
982 STMPE2401: GPIO, Keypad
983 STMPE2403: GPIO, Keypad
985 This driver provides common support for accessing the device,
986 additional drivers must be enabled in order to use the functionality
987 of the device. Currently available sub drivers are:
991 Touchscreen: stmpe-ts
993 menu "STMicroelectronics STMPE Interface Drivers"
997 bool "STMicroelectronics STMPE I2C Interface"
1001 This is used to enable I2C interface of STMPE
1004 bool "STMicroelectronics STMPE SPI Interface"
1005 depends on SPI_MASTER
1007 This is used to enable SPI interface of STMPE
1011 bool "STMicroelectronics STA2X11"
1016 config MFD_SUN6I_PRCM
1017 bool "Allwinner A31 PRCM controller"
1018 depends on ARCH_SUNXI
1021 Support for the PRCM (Power/Reset/Clock Management) unit available
1025 bool "System Controller Register R/W Based on Regmap"
1028 Select this option to enable accessing system control registers
1031 config MFD_DAVINCI_VOICECODEC
1036 config MFD_TI_AM335X_TSCADC
1037 tristate "TI ADC / Touch Screen chip support"
1042 If you say yes here you get support for Texas Instruments series
1043 of Touch Screen /ADC chips.
1044 To compile this driver as a module, choose M here: the
1045 module will be called ti_am335x_tscadc.
1047 config MFD_DM355EVM_MSP
1048 bool "TI DaVinci DM355 EVM microcontroller"
1049 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1051 This driver supports the MSP430 microcontroller used on these
1052 boards. MSP430 firmware manages resets and power sequencing,
1053 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1056 tristate "TI/National Semiconductor LP3943 MFD Driver"
1061 Support for the TI/National Semiconductor LP3943.
1062 This driver consists of GPIO and PWM drivers.
1063 With these functionalities, it can be used for LED string control or
1064 general usage such like a GPIO controller and a PWM controller.
1067 bool "TI LP8788 Power Management Unit Driver"
1073 TI LP8788 PMU supports regulators, battery charger, RTC,
1074 ADC, backlight driver and current sinks.
1076 config MFD_OMAP_USB_HOST
1077 bool "TI OMAP USBHS core and TLL driver"
1078 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1081 This is the core driver for the OAMP EHCI and OHCI drivers.
1082 This MFD driver does the required setup functionalities for
1083 OMAP USB Host drivers.
1086 bool "TI Palmas series chips"
1092 If you say yes here you get support for the Palmas
1093 series of PMIC chips from Texas Instruments.
1096 tristate "TI TPS61050/61052 Boost Converters"
1101 select REGULATOR_FIXED_VOLTAGE
1103 This option enables a driver for the TP61050/TPS61052
1104 high-power "white LED driver". This boost converter is
1105 sometimes used for other things than white LEDs, and
1106 also contains a GPIO pin.
1109 tristate "TI TPS6501x Power Management chips"
1110 depends on I2C && GPIOLIB
1111 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1113 If you say yes here you get support for the TPS6501x series of
1114 Power Management chips. These include voltage regulators,
1115 lithium ion/polymer battery charging, and other features that
1116 are often used in portable devices like cell phones and cameras.
1118 This driver can also be built as a module. If so, the module
1119 will be called tps65010.
1122 tristate "TI TPS6507x Power Management / Touch Screen chips"
1126 If you say yes here you get support for the TPS6507x series of
1127 Power Management / Touch Screen chips. These include voltage
1128 regulators, lithium ion/polymer battery charging, touch screen
1129 and other features that are often used in portable devices.
1130 This driver can also be built as a module. If so, the module
1131 will be called tps6507x.
1133 config TPS65911_COMPARATOR
1137 bool "TI TPS65090 Power Management chips"
1143 If you say yes here you get support for the TPS65090 series of
1144 Power Management chips.
1145 This driver provides common support for accessing the device,
1146 additional drivers must be enabled in order to use the
1147 functionality of the device.
1150 tristate "TI TPS65217 Power Management / White LED chips"
1155 If you say yes here you get support for the TPS65217 series of
1156 Power Management / White LED chips.
1157 These include voltage regulators, lithium ion/polymer battery
1158 charger, wled and other features that are often used in portable
1161 This driver can also be built as a module. If so, the module
1162 will be called tps65217.
1165 tristate "TI TPS65218 Power Management chips"
1171 If you say yes here you get support for the TPS65218 series of
1172 Power Management chips.
1173 These include voltage regulators, gpio and other features
1174 that are often used in portable devices. Only regulator
1175 component is currently supported.
1177 This driver can also be built as a module. If so, the module
1178 will be called tps65218.
1181 bool "TI TPS6586x Power Management chips"
1186 If you say yes here you get support for the TPS6586X series of
1187 Power Management chips.
1188 This driver provides common support for accessing the device,
1189 additional drivers must be enabled in order to use the
1190 functionality of the device.
1192 This driver can also be built as a module. If so, the module
1193 will be called tps6586x.
1196 bool "TI TPS65910 Power Management chip"
1198 depends on GPIOLIB || COMPILE_TEST
1204 if you say yes here you get support for the TPS65910 series of
1205 Power Management chips.
1213 config MFD_TPS65912_I2C
1214 tristate "TI TPS65912 Power Management chip with I2C"
1219 If you say yes here you get support for the TPS65912 series of
1220 PM chips with I2C interface.
1222 config MFD_TPS65912_SPI
1223 tristate "TI TPS65912 Power Management chip with SPI"
1226 depends on SPI_MASTER
1228 If you say yes here you get support for the TPS65912 series of
1229 PM chips with SPI interface.
1232 bool "TI TPS80031/TPS80032 Power Management chips"
1238 If you say yes here you get support for the Texas Instruments
1239 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1240 Path and Battery Charger. The device provides five configurable
1241 step-down converters, 11 general purpose LDOs, USB OTG Module,
1242 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1243 Power Path from USB, 32K clock generator.
1246 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1251 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1252 This core driver provides register access and IRQ handling
1253 facilities, and registers devices for the various functions
1254 so that function-specific drivers can bind to them.
1256 These multi-function chips are found on many OMAP2 and OMAP3
1257 boards, providing power management, RTC, GPIO, keypad, a
1258 high speed USB OTG transceiver, an audio codec (on most
1259 versions) and many other features.
1261 config TWL4030_POWER
1262 bool "TI TWL4030 power resources"
1263 depends on TWL4030_CORE && ARM
1265 Say yes here if you want to use the power resources on the
1266 TWL4030 family chips. Most of these resources are regulators,
1267 which have a separate driver; some are control signals, such
1268 as clock request handshaking.
1270 This driver uses board-specific data to initialize the resources
1271 and load scripts controlling which resources are switched off/on
1272 or reset when a sleep, wakeup or warm reset event occurs.
1274 config MFD_TWL4030_AUDIO
1275 bool "TI TWL4030 Audio"
1276 depends on TWL4030_CORE
1281 bool "TI TWL6040 audio codec"
1288 Say yes here if you want support for Texas Instruments TWL6040 audio
1290 This driver provides common support for accessing the device,
1291 additional drivers must be enabled in order to use the
1292 functionality of the device (audio, vibra).
1295 bool "TI TWL92330/Menelaus PM chip"
1296 depends on I2C=y && ARCH_OMAP2
1298 If you say yes here you get support for the Texas Instruments
1299 TWL92330/Menelaus Power Management chip. This include voltage
1300 regulators, Dual slot memory card transceivers, real-time clock
1301 and other features that are often used in portable devices like
1302 cell phones and PDAs.
1304 config MFD_WL1273_CORE
1305 tristate "TI WL1273 FM radio"
1310 This is the core driver for the TI WL1273 FM radio. This MFD
1311 driver connects the radio-wl1273 V4L2 module and the wl1273
1315 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1320 Say yes here to enable support for National Semiconductor / TI
1321 LM3533 Lighting Power chips.
1323 This driver provides common support for accessing the device;
1324 additional drivers must be enabled in order to use the LED,
1325 backlight or ambient-light-sensor functionality of the device.
1327 config MFD_TIMBERDALE
1328 tristate "Timberdale FPGA"
1330 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1332 This is the core driver for the timberdale FPGA. This device is a
1333 multifunction device which exposes numerous platform devices.
1335 The timberdale FPGA can be found on the Intel Atom development board
1336 for in-vehicle infontainment, called Russellville.
1339 bool "Toshiba TC35892 and variants"
1344 Support for the Toshiba TC35892 and variants I/O Expander.
1346 This driver provides common support for accessing the device,
1347 additional drivers must be enabled in order to use the
1348 functionality of the device.
1355 bool "Toshiba T7L66XB"
1356 depends on ARM && HAVE_CLK
1360 Support for Toshiba Mobile IO Controller T7L66XB
1363 bool "Toshiba TC6387XB"
1364 depends on ARM && HAVE_CLK
1368 Support for Toshiba Mobile IO Controller TC6387XB
1371 bool "Toshiba TC6393XB"
1372 depends on ARM && HAVE_CLK
1377 Support for Toshiba Mobile IO Controller TC6393XB
1380 tristate "VIA VX855/VX875 integrated south bridge"
1384 Say yes here to enable support for various functions of the
1385 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1386 and/or vx855_gpio drivers for this to do anything useful.
1394 config MFD_ARIZONA_I2C
1395 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1401 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1402 audio SoC core functionality controlled via I2C.
1404 config MFD_ARIZONA_SPI
1405 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1409 depends on SPI_MASTER
1411 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1412 audio SoC core functionality controlled via I2C.
1415 bool "Cirrus Logic CS47L24 and WM1831"
1416 depends on MFD_ARIZONA
1418 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1421 bool "Wolfson Microelectronics WM5102"
1422 depends on MFD_ARIZONA
1424 Support for Wolfson Microelectronics WM5102 low power audio SoC
1427 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1428 depends on MFD_ARIZONA
1430 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1434 bool "Wolfson Microelectronics WM8997"
1435 depends on MFD_ARIZONA
1437 Support for Wolfson Microelectronics WM8997 low power audio SoC
1440 bool "Wolfson Microelectronics WM8998"
1441 depends on MFD_ARIZONA
1443 Support for Wolfson Microelectronics WM8998 low power audio SoC
1446 bool "Wolfson Microelectronics WM8400"
1451 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1452 CODEC. This driver provides common support for accessing
1453 the device, additional drivers must be enabled in order to use
1454 the functionality of the device.
1459 config MFD_WM831X_I2C
1460 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1467 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1468 when controlled using I2C. This driver provides common support
1469 for accessing the device, additional drivers must be enabled in
1470 order to use the functionality of the device.
1472 config MFD_WM831X_SPI
1473 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1478 depends on SPI_MASTER
1480 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1481 when controlled using SPI. This driver provides common support
1482 for accessing the device, additional drivers must be enabled in
1483 order to use the functionality of the device.
1488 config MFD_WM8350_I2C
1489 bool "Wolfson Microelectronics WM8350 with I2C"
1493 The WM8350 is an integrated audio and power management
1494 subsystem with watchdog and RTC functionality for embedded
1495 systems. This option enables core support for the WM8350 with
1496 I2C as the control interface. Additional options must be
1497 selected to enable support for the functionality of the chip.
1500 tristate "Wolfson Microelectronics WM8994"
1506 The WM8994 is a highly integrated hi-fi CODEC designed for
1507 smartphone applications. As well as audio functionality it
1508 has on board GPIO and regulator functionality which is
1509 supported via the relevant subsystems. This driver provides
1510 core support for the WM8994, in order to use the actual
1511 functionaltiy of the device other drivers must be enabled.
1514 tristate "Support for ST Microelectronics STw481x"
1515 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1519 Select this option to enable the STw481x chip driver used
1520 in various ST Microelectronics and ST-Ericsson embedded
1523 menu "Multimedia Capabilities Port drivers"
1524 depends on ARCH_SA1100
1531 tristate "Support SA11x0 MCP interface"
1532 depends on ARCH_SA1100
1537 tristate "Support for UCB1200 / UCB1300"
1538 depends on MCP_SA11X0
1541 config MCP_UCB1200_TS
1542 tristate "Touchscreen interface support"
1543 depends on MCP_UCB1200 && INPUT
1547 config MFD_VEXPRESS_SYSREG
1548 bool "Versatile Express System Registers"
1549 depends on VEXPRESS_CONFIG && GPIOLIB
1552 select GPIO_GENERIC_PLATFORM
1556 System Registers are the platform configuration block
1557 on the ARM Ltd. Versatile Express board.