2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
22 tristate "Active-semi ACT8945A"
27 Support for the ACT8945A PMIC from Active-semi. This device
28 features three step-down DC/DC converters and four low-dropout
29 linear regulators, along with a complete ActivePath battery
39 Support for the AS3711 PMIC from AMS
42 bool "ams AS3722 Power Management IC"
46 depends on I2C=y && OF
48 The ams AS3722 is a compact system PMU suitable for mobile phones,
49 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
50 controllers, 11 LDOs, RTC, automatic battery, temperature and
51 over current monitoring, GPIOs, ADC and a watchdog.
54 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
57 Say yes here to add support for Analog Devices AD5520 and ADP5501,
58 Multifunction Power Management IC. This includes
59 the I2C driver and the core APIs _only_, you have to select
60 individual components like LCD backlight, LEDs, GPIOs and Kepad
61 under the corresponding menus.
63 config MFD_AAT2870_CORE
64 bool "AnalogicTech AAT2870"
67 depends on GPIOLIB || COMPILE_TEST
69 If you say yes here you get support for the AAT2870.
70 This driver provides common support for accessing the device,
71 additional drivers must be enabled in order to use the
72 functionality of the device.
74 config MFD_ATMEL_FLEXCOM
75 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
79 Select this to get support for Atmel Flexcom. This is a wrapper
80 which embeds a SPI controller, a I2C controller and a USART. Only
81 one function can be used at a time. The choice is done at boot time
82 by the probe function of this MFD driver according to a device tree
85 config MFD_ATMEL_HLCDC
86 tristate "Atmel HLCDC (High-end LCD Controller)"
91 If you say yes here you get support for the HLCDC block.
92 This driver provides common support for accessing the device,
93 additional drivers must be enabled in order to use the
94 functionality of the device.
97 tristate "Broadcom BCM590xx PMUs"
102 Support for the BCM590xx PMUs from Broadcom
109 config MFD_AXP20X_I2C
110 tristate "X-Powers AXP series PMICs with I2C"
115 If you say Y here you get support for the X-Powers AXP series power
116 management ICs (PMICs) controlled with I2C.
117 This driver include only the core APIs. You have to select individual
118 components like regulators or the PEK (Power Enable Key) under the
121 config MFD_AXP20X_RSB
122 tristate "X-Powers AXP series PMICs with RSB"
126 If you say Y here you get support for the X-Powers AXP series power
127 management ICs (PMICs) controlled with RSB.
128 This driver include only the core APIs. You have to select individual
129 components like regulators or the PEK (Power Enable Key) under the
133 tristate "ChromeOS Embedded Controller"
135 select CHROME_PLATFORMS
137 depends on X86 || ARM || ARM64 || COMPILE_TEST
139 If you say Y here you get support for the ChromeOS Embedded
140 Controller (EC) providing keyboard, battery and power services.
141 You also need to enable the driver for the bus you are using. The
142 protocol for talking to the EC is defined by the bus driver.
144 config MFD_CROS_EC_I2C
145 tristate "ChromeOS Embedded Controller (I2C)"
146 depends on MFD_CROS_EC && I2C
149 If you say Y here, you get support for talking to the ChromeOS
150 EC through an I2C bus. This uses a simple byte-level protocol with
151 a checksum. Failing accesses will be retried three times to
154 config MFD_CROS_EC_SPI
155 tristate "ChromeOS Embedded Controller (SPI)"
156 depends on MFD_CROS_EC && SPI
159 If you say Y here, you get support for talking to the ChromeOS EC
160 through a SPI bus, using a byte-level protocol. Since the EC's
161 response time cannot be guaranteed, we support ignoring
162 'pre-amble' bytes before the response actually starts.
166 depends on GPIOLIB && ARM
169 This driver supports the ASIC3 multifunction chip found on many
170 PDAs (mainly iPAQ and HTC based ones)
173 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
176 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
177 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
178 usually found on PXA processors-based platforms. This includes
179 the I2C driver and the core APIs _only_, you have to select
180 individual components like LCD backlight, voltage regulators,
181 LEDs and battery-charger under the corresponding menus.
187 config MFD_DA9052_SPI
188 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
192 depends on SPI_MASTER=y
194 Support for the Dialog Semiconductor DA9052 PMIC
195 when controlled using SPI. This driver provides common support
196 for accessing the device, additional drivers must be enabled in
197 order to use the functionality of the device.
199 config MFD_DA9052_I2C
200 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
206 Support for the Dialog Semiconductor DA9052 PMIC
207 when controlled using I2C. This driver provides common support
208 for accessing the device, additional drivers must be enabled in
209 order to use the functionality of the device.
212 bool "Dialog Semiconductor DA9055 PMIC Support"
218 Say yes here for support of Dialog Semiconductor DA9055. This is
219 a Power Management IC. This driver provides common support for
220 accessing the device as well as the I2C interface to the chip itself.
221 Additional drivers must be enabled in order to use the functionality
224 This driver can be built as a module. If built as a module it will be
228 tristate "Dialog Semiconductor DA9062 PMIC Support"
234 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
235 This includes the I2C driver and core APIs.
236 Additional drivers must be enabled in order to use the functionality
240 tristate "Dialog Semiconductor DA9063 PMIC Support"
246 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
247 This includes the I2C driver and core APIs.
248 Additional drivers must be enabled in order to use the functionality
252 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
258 This adds support for the DA9150 integrated charger and fuel-gauge
259 chip. This driver provides common support for accessing the device.
260 Additional drivers must be enabled in order to use the specific
261 features of the device.
264 tristate "Diolan DLN2 support"
268 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
269 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
270 etc. must be enabled in order to use the functionality of
275 depends on (SPI_MASTER || I2C)
279 Enable support for the Freescale MC13783 and MC13892 PMICs.
280 This driver provides common support for accessing the device,
281 additional drivers must be enabled in order to use the
282 functionality of the device.
284 config MFD_MC13XXX_SPI
285 tristate "Freescale MC13783 and MC13892 SPI interface"
286 depends on SPI_MASTER
290 Select this if your MC13xxx is connected via an SPI bus.
292 config MFD_MC13XXX_I2C
293 tristate "Freescale MC13892 I2C interface"
298 Select this if your MC13xxx is connected via an I2C bus.
300 config MFD_MX25_TSADC
301 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
303 depends on (SOC_IMX25 && OF) || COMPILE_TEST
305 Enable support for the integrated Touchscreen and ADC unit of the
306 i.MX25 processors. They consist of a conversion queue for general
307 purpose ADC and a queue for Touchscreens.
309 config MFD_HI6421_PMIC
310 tristate "HiSilicon Hi6421 PMU/Codec IC"
315 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
316 functions, such as regulators, RTC, codec, Coulomb counter, etc.
317 This driver includes core APIs _only_. You have to select
318 individul components like voltage regulators under corresponding
319 menus in order to enable them.
320 We communicate with the Hi6421 via memory-mapped I/O.
322 config MFD_HI655X_PMIC
323 tristate "HiSilicon Hi655X series PMU/Codec IC"
324 depends on ARCH_HISI || COMPILE_TEST
330 Select this option to enable Hisilicon hi655x series pmic driver.
333 bool "HTC EGPIO support"
334 depends on GPIOLIB && ARM
336 This driver supports the CPLD egpio chip present on
337 several HTC phones. It provides basic support for input
338 pins, output pins, and irqs.
341 tristate "HTC PASIC3 LED/DS1WM chip support"
344 This core driver provides register access for the LED/DS1WM
345 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
346 HTC Magician devices, respectively. Actual functionality is
347 handled by the leds-pasic3 and ds1wm drivers.
350 bool "HTC I2C PLD chip support"
351 depends on I2C=y && GPIOLIB
353 If you say yes here you get support for the supposed CPLD
354 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
355 This device provides input and output GPIOs through an I2C
356 interface to one or more sub-chips.
358 config MFD_INTEL_QUARK_I2C_GPIO
359 tristate "Intel Quark MFD I2C GPIO"
362 depends on COMMON_CLK
365 This MFD provides support for I2C and GPIO that exist only
366 in a single PCI device. It splits the 2 IO devices to
367 their respective IO driver.
368 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
371 tristate "Intel ICH LPC"
375 The LPC bridge function of the Intel ICH provides support for
376 many functional units. This driver provides needed support for
377 other drivers to control these functions, currently GPIO and
381 tristate "Intel SCH LPC"
385 LPC bridge function of the Intel SCH provides support for
386 System Management Bus and General Purpose I/O.
388 config INTEL_SOC_PMIC
389 bool "Support for Intel Atom SoC PMIC"
396 Select this option to enable support for the PMIC device
397 on some Intel SoC systems. The PMIC provides ADC, GPIO,
398 thermal, charger and related power management functions
401 config MFD_INTEL_LPSS
406 config MFD_INTEL_LPSS_ACPI
407 tristate "Intel Low Power Subsystem support in ACPI mode"
408 select MFD_INTEL_LPSS
409 depends on X86 && ACPI
411 This driver supports Intel Low Power Subsystem (LPSS) devices such as
412 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
415 config MFD_INTEL_LPSS_PCI
416 tristate "Intel Low Power Subsystem support in PCI mode"
417 select MFD_INTEL_LPSS
418 depends on X86 && PCI
420 This driver supports Intel Low Power Subsystem (LPSS) devices such as
421 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
424 config MFD_INTEL_MSIC
426 depends on INTEL_SCU_IPC
429 Select this option to enable access to Intel MSIC (Avatele
430 Passage) chip. This chip embeds audio, battery, GPIO, etc.
431 devices used in Intel Medfield platforms.
433 config MFD_IPAQ_MICRO
434 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
435 depends on SA1100_H3100 || SA1100_H3600
438 Select this to get support for the Microcontroller found in
439 the Compaq iPAQ handheld computers. This is an Atmel
440 AT90LS8535 microcontroller flashed with a special iPAQ
441 firmware using the custom protocol implemented in this driver.
443 config MFD_JANZ_CMODIO
444 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
448 This is the core driver for the Janz CMOD-IO PCI MODULbus
449 carrier board. This device is a PCI to MODULbus bridge which may
450 host many different types of MODULbus daughterboards, including
451 CAN and GPIO controllers.
453 config MFD_JZ4740_ADC
454 bool "Janz JZ4740 ADC core"
456 select GENERIC_IRQ_CHIP
457 depends on MACH_JZ4740
459 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
460 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
463 tristate "Kontron module PLD device"
466 This is the core driver for the PLD (Programmable Logic Device) found
467 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
468 device may provide functions like watchdog, GPIO, UART and I2C bus.
470 The following modules are supported:
474 * COMe-bPC2 (ETXexpress-PC)
475 * COMe-bSC# (ETXexpress-SC T#)
480 * COMe-cDC2 (microETXexpress-DC)
482 * COMe-cPC2 (microETXexpress-PC)
485 * COMe-mTT10 (nanoETXexpress-TT)
488 This driver can also be built as a module. If so, the module
489 will be called kempld-core.
492 tristate "Marvell 88PM800"
498 This supports for Marvell 88PM800 Power Management IC.
499 This includes the I2C driver and the core APIs _only_, you have to
500 select individual components like voltage regulators, RTC and
501 battery-charger under the corresponding menus.
504 tristate "Marvell 88PM805"
510 This supports for Marvell 88PM805 Power Management IC. This includes
511 the I2C driver and the core APIs _only_, you have to select individual
512 components like codec device, headset/Mic device under the
516 bool "Marvell 88PM8606/88PM8607"
521 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
522 This includes the I2C driver and the core APIs _only_, you have to
523 select individual components like voltage regulators, RTC and
524 battery-charger under the corresponding menus.
527 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
534 Say yes here to add support for Maxim Semiconductor MAX14577 and
535 MAX77836 Micro-USB ICs with battery charger.
536 This driver provides common support for accessing the device;
537 additional drivers must be enabled in order to use the functionality
541 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
549 Say yes here to add support for Maxim Semiconductor MAX77620 and
550 MAX20024 which are Power Management IC with General purpose pins,
551 RTC, regulators, clock generator, watchdog etc. This driver
552 provides common support for accessing the device; additional drivers
553 must be enabled in order to use the functionality of the device.
556 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
564 Say yes here to add support for Maxim Semiconductor MAX77686 and
565 MAX77802 which are Power Management IC with an RTC on chip.
566 This driver provides common support for accessing the device;
567 additional drivers must be enabled in order to use the functionality
571 tristate "Maxim Semiconductor MAX77693 PMIC Support"
577 Say yes here to add support for Maxim Semiconductor MAX77693.
578 This is a companion Power Management IC with Flash, Haptic, Charger,
579 and MUIC(Micro USB Interface Controller) controls on chip.
580 This driver provides common support for accessing the device;
581 additional drivers must be enabled in order to use the functionality
585 bool "Maxim Semiconductor MAX77843 PMIC Support"
591 Say yes here to add support for Maxim Semiconductor MAX77843.
592 This is companion Power Management IC with LEDs, Haptic, Charger,
593 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
594 This driver provides common support for accessing the device;
595 additional drivers must be enabled in order to use the functionality
599 tristate "Maxim Semiconductor MAX8907 PMIC Support"
605 Say yes here to add support for Maxim Semiconductor MAX8907. This is
606 a Power Management IC. This driver provides common support for
607 accessing the device; additional drivers must be enabled in order
608 to use the functionality of the device.
611 bool "Maxim Semiconductor MAX8925 PMIC Support"
615 Say yes here to add support for Maxim Semiconductor MAX8925. This is
616 a Power Management IC. This driver provides common support for
617 accessing the device, additional drivers must be enabled in order
618 to use the functionality of the device.
621 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
626 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
627 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
628 MUIC controls on chip.
629 This driver provides common support for accessing the device;
630 additional drivers must be enabled in order to use the functionality
634 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
639 Say yes here to add support for Maxim Semiconductor MAX8998 and
640 National Semiconductor LP3974. This is a Power Management IC.
641 This driver provides common support for accessing the device,
642 additional drivers must be enabled in order to use the functionality
646 tristate "MediaTek MT6397 PMIC Support"
650 Say yes here to add support for MediaTek MT6397 PMIC. This is
651 a Power Management IC. This driver provides common support for
652 accessing the device; additional drivers must be enabled in order
653 to use the functionality of the device.
656 tristate "MEN 14F021P00 Board Management Controller Support"
660 Say yes here to add support for the MEN 14F021P00 BMC
661 which is a Board Management Controller connected to the I2C bus.
662 The device supports multiple sub-devices like LED, HWMON and WDT.
663 This driver provides common support for accessing the devices;
664 additional drivers must be enabled in order to use the
665 functionality of the BMC device.
667 This driver can also be built as a module. If so the module
668 will be called menf21bmc.
671 bool "Motorola EZXPCAP Support"
672 depends on SPI_MASTER
674 This enables the PCAP ASIC present on EZX Phones. This is
675 needed for MMC, TouchScreen, Sound, USB, etc..
677 config MFD_VIPERBOARD
678 tristate "Nano River Technologies Viperboard"
683 Say yes here if you want support for Nano River Technologies
685 There are mfd cell drivers available for i2c master, adc and
686 both gpios found on the board. The spi part does not yet
688 You need to select the mfd cell drivers separately.
689 The drivers do not support all features the board exposes.
692 tristate "Nokia Retu and Tahvo multi-function device"
697 Retu and Tahvo are a multi-function devices found on Nokia
698 Internet Tablets (770, N800 and N810).
701 tristate "NXP PCF50633"
705 Say yes here if you have NXP PCF50633 chip on your board.
706 This core driver provides register access and IRQ handling
707 facilities, and registers devices for the various functions
708 so that function-specific drivers can bind to them.
711 tristate "NXP PCF50633 ADC"
712 depends on MFD_PCF50633
714 Say yes here if you want to include support for ADC in the
718 tristate "NXP PCF50633 GPIO"
719 depends on MFD_PCF50633
721 Say yes here if you want to include support GPIO for pins on
725 tristate "Philips UCB1400 Core driver"
729 This enables support for the Philips UCB1400 core functions.
730 The UCB1400 is an AC97 audio codec.
732 To compile this driver as a module, choose M here: the
733 module will be called ucb1400_core.
738 config MFD_PM8921_CORE
739 tristate "Qualcomm PM8921 PMIC chip"
740 depends on (ARM || HEXAGON)
746 If you say yes to this option, support will be included for the
747 built-in PM8921 PMIC chip.
749 This is required if your board has a PM8921 and uses its features,
750 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
752 Say M here if you want to include support for PM8921 chip as a module.
753 This will build a module called "pm8921-core".
756 tristate "Qualcomm Resource Power Manager (RPM)"
757 depends on ARCH_QCOM && OF
759 If you say yes to this option, support will be included for the
760 Resource Power Manager system found in the Qualcomm 8660, 8960 and
763 This is required to access many regulators, clocks and bus
764 frequencies controlled by the RPM on these devices.
766 Say M here if you want to include support for the Qualcomm RPM as a
767 module. This will build a module called "qcom_rpm".
770 tristate "Qualcomm SPMI PMICs"
771 depends on ARCH_QCOM || COMPILE_TEST
776 This enables support for the Qualcomm SPMI PMICs.
777 These PMICs are currently used with the Snapdragon 800 series of
778 SoCs. Note, that this will only be useful paired with descriptions
779 of the independent functions as children nodes in the device tree.
781 Say M here if you want to include support for the SPMI PMIC
782 series as a module. The module will be called "qcom-spmi-pmic".
785 tristate "RDC R-321x southbridge"
789 Say yes here if you want to have support for the RDC R-321x SoC
790 southbridge which provides access to GPIOs and Watchdog using the
791 southbridge PCI device configuration space.
794 tristate "Realtek PCI-E card reader"
798 This supports for Realtek PCI-Express card reader including rts5209,
799 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
800 Realtek card reader supports access to many types of memory cards,
801 such as Memory Stick, Memory Stick Pro, Secure Digital and
805 tristate "Richtek RT5033 Power Management IC"
811 This driver provides for the Richtek RT5033 Power Management IC,
812 which includes the I2C driver and the Core APIs. This driver provides
813 common support for accessing the device. The device supports multiple
814 sub-devices like charger, fuel gauge, flash LED, current source,
818 tristate "Realtek USB card reader"
822 Select this option to get support for Realtek USB 2.0 card readers
823 including RTS5129, RTS5139, RTS5179 and RTS5170.
824 Realtek card reader supports access to many types of memory cards,
825 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
828 bool "Ricoh RC5T583 Power Management system device"
833 Select this option to get support for the RICOH583 Power
834 Management system device.
835 This driver provides common support for accessing the device
836 through i2c interface. The device supports multiple sub-devices
837 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
838 Additional drivers must be enabled in order to use the
839 different functionality of the device.
842 tristate "Rockchip RK808 Power Management chip"
848 If you say yes here you get support for the RK808
849 Power Management chips.
850 This driver provides common support for accessing the device
851 through I2C interface. The device supports multiple sub-devices
852 including interrupts, RTC, LDO & DCDC regulators, and onkey.
855 tristate "Ricoh RN5T567/618 PMIC"
861 Say yes here to add support for the Ricoh RN5T567 or R5T618 PMIC.
862 This driver provides common support for accessing the device,
863 additional drivers must be enabled in order to use the
864 functionality of the device.
867 bool "SAMSUNG Electronics PMIC Series Support"
873 Support for the Samsung Electronics MFD series.
874 This driver provides common support for accessing the device,
875 additional drivers must be enabled in order to use the functionality
878 config MFD_SI476X_CORE
879 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
884 This is the core driver for the SI476x series of AM/FM
885 radio. This MFD driver connects the radio-si476x V4L2 module
886 and the si476x audio codec.
888 To compile this driver as a module, choose M here: the
889 module will be called si476x-core.
892 tristate "Silicon Motion SM501"
894 This is the core driver for the Silicon Motion SM501 multimedia
895 companion chip. This device is a multifunction device which may
896 provide numerous interfaces including USB host controller, USB gadget,
897 asynchronous serial ports, audio functions, and a dual display video
898 interface. The device may be connected by PCI or local bus with
899 varying functions enabled.
901 config MFD_SM501_GPIO
902 bool "Export GPIO via GPIO layer"
903 depends on MFD_SM501 && GPIOLIB
905 This option uses the gpio library layer to export the 64 GPIO
906 lines on the SM501. The platform data is used to supply the
907 base number for the first GPIO line to register.
910 tristate "Skyworks Solutions SKY81452"
915 This is the core driver for the Skyworks SKY81452 backlight and
916 voltage regulator device.
918 This driver can also be built as a module. If so, the module
919 will be called sky81452.
922 bool "SMSC ECE1099 series chips"
927 If you say yes here you get support for the
928 ece1099 chips from SMSC.
930 To compile this driver as a module, choose M here: the
931 module will be called smsc.
934 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
935 default y if ARCH_U300 || ARCH_U8500
937 Say yes here if you have the ABX500 Mixed Signal IC family
938 chips. This core driver expose register access functions.
939 Functionality specific drivers using these functions can
940 remain unchanged when IC changes. Binding of the functions to
941 actual register access is done by the IC core driver.
944 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
945 depends on I2C=y && ABX500_CORE
947 default y if ARCH_U300
949 Select this to enable the AB3100 Mixed Signal IC core
950 functionality. This connects to a AB3100 on the I2C bus
951 and expose a number of symbols needed for dependent devices
952 to read and write registers and subscribe to events from
953 this multi-functional IC. This is needed to use other features
954 of the AB3100 such as battery-backed RTC, charging control,
955 LEDs, vibrator, system power and temperature, power management
959 tristate "ST-Ericsson AB3100 OTP functions"
960 depends on AB3100_CORE
961 default y if AB3100_CORE
963 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
964 programmable memory) support. This exposes a sysfs file to read
968 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
969 depends on ABX500_CORE && MFD_DB8500_PRCMU
974 Select this option to enable access to AB8500 power management
975 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
976 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
977 the irq_chip parts for handling the Mixed Signal chip events.
978 This chip embeds various other multimedia funtionalities as well.
981 bool "Enable debug info via debugfs"
982 depends on AB8500_GPADC && DEBUG_FS
983 default y if DEBUG_FS
985 Select this option if you want debug information using the debug
989 bool "ST-Ericsson AB8500 GPADC driver"
990 depends on AB8500_CORE && REGULATOR_AB8500
993 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
995 config MFD_DB8500_PRCMU
996 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
997 depends on UX500_SOC_DB8500
1000 Select this option to enable support for the DB8500 Power Reset
1001 and Control Management Unit. This is basically an autonomous
1002 system controller running an XP70 microprocessor, which is accessed
1003 through a register map.
1006 bool "STMicroelectronics STMPE"
1007 depends on (I2C=y || SPI_MASTER=y)
1011 Support for the STMPE family of I/O Expanders from
1014 Currently supported devices are:
1016 STMPE811: GPIO, Touchscreen
1017 STMPE1601: GPIO, Keypad
1018 STMPE1801: GPIO, Keypad
1019 STMPE2401: GPIO, Keypad
1020 STMPE2403: GPIO, Keypad
1022 This driver provides common support for accessing the device,
1023 additional drivers must be enabled in order to use the functionality
1024 of the device. Currently available sub drivers are:
1027 Keypad: stmpe-keypad
1028 Touchscreen: stmpe-ts
1030 menu "STMicroelectronics STMPE Interface Drivers"
1031 depends on MFD_STMPE
1034 bool "STMicroelectronics STMPE I2C Interface"
1038 This is used to enable I2C interface of STMPE
1041 bool "STMicroelectronics STMPE SPI Interface"
1042 depends on SPI_MASTER
1044 This is used to enable SPI interface of STMPE
1048 bool "STMicroelectronics STA2X11"
1053 config MFD_SUN6I_PRCM
1054 bool "Allwinner A31 PRCM controller"
1055 depends on ARCH_SUNXI
1058 Support for the PRCM (Power/Reset/Clock Management) unit available
1062 bool "System Controller Register R/W Based on Regmap"
1065 Select this option to enable accessing system control registers
1068 config MFD_DAVINCI_VOICECODEC
1073 config MFD_TI_AM335X_TSCADC
1074 tristate "TI ADC / Touch Screen chip support"
1079 If you say yes here you get support for Texas Instruments series
1080 of Touch Screen /ADC chips.
1081 To compile this driver as a module, choose M here: the
1082 module will be called ti_am335x_tscadc.
1084 config MFD_DM355EVM_MSP
1085 bool "TI DaVinci DM355 EVM microcontroller"
1086 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1088 This driver supports the MSP430 microcontroller used on these
1089 boards. MSP430 firmware manages resets and power sequencing,
1090 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1093 tristate "TI/National Semiconductor LP3943 MFD Driver"
1098 Support for the TI/National Semiconductor LP3943.
1099 This driver consists of GPIO and PWM drivers.
1100 With these functionalities, it can be used for LED string control or
1101 general usage such like a GPIO controller and a PWM controller.
1104 bool "TI LP8788 Power Management Unit Driver"
1110 TI LP8788 PMU supports regulators, battery charger, RTC,
1111 ADC, backlight driver and current sinks.
1113 config MFD_OMAP_USB_HOST
1114 bool "TI OMAP USBHS core and TLL driver"
1115 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1118 This is the core driver for the OAMP EHCI and OHCI drivers.
1119 This MFD driver does the required setup functionalities for
1120 OMAP USB Host drivers.
1123 bool "TI Palmas series chips"
1129 If you say yes here you get support for the Palmas
1130 series of PMIC chips from Texas Instruments.
1133 tristate "TI TPS61050/61052 Boost Converters"
1138 select REGULATOR_FIXED_VOLTAGE
1140 This option enables a driver for the TP61050/TPS61052
1141 high-power "white LED driver". This boost converter is
1142 sometimes used for other things than white LEDs, and
1143 also contains a GPIO pin.
1146 tristate "TI TPS6501x Power Management chips"
1147 depends on I2C && GPIOLIB
1148 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1150 If you say yes here you get support for the TPS6501x series of
1151 Power Management chips. These include voltage regulators,
1152 lithium ion/polymer battery charging, and other features that
1153 are often used in portable devices like cell phones and cameras.
1155 This driver can also be built as a module. If so, the module
1156 will be called tps65010.
1159 tristate "TI TPS6507x Power Management / Touch Screen chips"
1163 If you say yes here you get support for the TPS6507x series of
1164 Power Management / Touch Screen chips. These include voltage
1165 regulators, lithium ion/polymer battery charging, touch screen
1166 and other features that are often used in portable devices.
1167 This driver can also be built as a module. If so, the module
1168 will be called tps6507x.
1171 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1177 If you say yes here you get support for the TPS65086 series of
1178 Power Management chips.
1179 This driver provides common support for accessing the device,
1180 additional drivers must be enabled in order to use the
1181 functionality of the device.
1183 config TPS65911_COMPARATOR
1187 bool "TI TPS65090 Power Management chips"
1193 If you say yes here you get support for the TPS65090 series of
1194 Power Management chips.
1195 This driver provides common support for accessing the device,
1196 additional drivers must be enabled in order to use the
1197 functionality of the device.
1200 tristate "TI TPS65217 Power Management / White LED chips"
1205 If you say yes here you get support for the TPS65217 series of
1206 Power Management / White LED chips.
1207 These include voltage regulators, lithium ion/polymer battery
1208 charger, wled and other features that are often used in portable
1211 This driver can also be built as a module. If so, the module
1212 will be called tps65217.
1215 tristate "TI TPS65218 Power Management chips"
1221 If you say yes here you get support for the TPS65218 series of
1222 Power Management chips.
1223 These include voltage regulators, gpio and other features
1224 that are often used in portable devices. Only regulator
1225 component is currently supported.
1227 This driver can also be built as a module. If so, the module
1228 will be called tps65218.
1231 bool "TI TPS6586x Power Management chips"
1236 If you say yes here you get support for the TPS6586X series of
1237 Power Management chips.
1238 This driver provides common support for accessing the device,
1239 additional drivers must be enabled in order to use the
1240 functionality of the device.
1242 This driver can also be built as a module. If so, the module
1243 will be called tps6586x.
1246 bool "TI TPS65910 Power Management chip"
1248 depends on GPIOLIB || COMPILE_TEST
1254 if you say yes here you get support for the TPS65910 series of
1255 Power Management chips.
1263 config MFD_TPS65912_I2C
1264 tristate "TI TPS65912 Power Management chip with I2C"
1269 If you say yes here you get support for the TPS65912 series of
1270 PM chips with I2C interface.
1272 config MFD_TPS65912_SPI
1273 tristate "TI TPS65912 Power Management chip with SPI"
1276 depends on SPI_MASTER
1278 If you say yes here you get support for the TPS65912 series of
1279 PM chips with SPI interface.
1282 bool "TI TPS80031/TPS80032 Power Management chips"
1288 If you say yes here you get support for the Texas Instruments
1289 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1290 Path and Battery Charger. The device provides five configurable
1291 step-down converters, 11 general purpose LDOs, USB OTG Module,
1292 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1293 Power Path from USB, 32K clock generator.
1296 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1301 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1302 This core driver provides register access and IRQ handling
1303 facilities, and registers devices for the various functions
1304 so that function-specific drivers can bind to them.
1306 These multi-function chips are found on many OMAP2 and OMAP3
1307 boards, providing power management, RTC, GPIO, keypad, a
1308 high speed USB OTG transceiver, an audio codec (on most
1309 versions) and many other features.
1311 config TWL4030_POWER
1312 bool "TI TWL4030 power resources"
1313 depends on TWL4030_CORE && ARM
1315 Say yes here if you want to use the power resources on the
1316 TWL4030 family chips. Most of these resources are regulators,
1317 which have a separate driver; some are control signals, such
1318 as clock request handshaking.
1320 This driver uses board-specific data to initialize the resources
1321 and load scripts controlling which resources are switched off/on
1322 or reset when a sleep, wakeup or warm reset event occurs.
1324 config MFD_TWL4030_AUDIO
1325 bool "TI TWL4030 Audio"
1326 depends on TWL4030_CORE
1331 bool "TI TWL6040 audio codec"
1338 Say yes here if you want support for Texas Instruments TWL6040 audio
1340 This driver provides common support for accessing the device,
1341 additional drivers must be enabled in order to use the
1342 functionality of the device (audio, vibra).
1345 bool "TI TWL92330/Menelaus PM chip"
1346 depends on I2C=y && ARCH_OMAP2
1348 If you say yes here you get support for the Texas Instruments
1349 TWL92330/Menelaus Power Management chip. This include voltage
1350 regulators, Dual slot memory card transceivers, real-time clock
1351 and other features that are often used in portable devices like
1352 cell phones and PDAs.
1354 config MFD_WL1273_CORE
1355 tristate "TI WL1273 FM radio"
1360 This is the core driver for the TI WL1273 FM radio. This MFD
1361 driver connects the radio-wl1273 V4L2 module and the wl1273
1365 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1370 Say yes here to enable support for National Semiconductor / TI
1371 LM3533 Lighting Power chips.
1373 This driver provides common support for accessing the device;
1374 additional drivers must be enabled in order to use the LED,
1375 backlight or ambient-light-sensor functionality of the device.
1377 config MFD_TIMBERDALE
1378 tristate "Timberdale FPGA"
1380 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1382 This is the core driver for the timberdale FPGA. This device is a
1383 multifunction device which exposes numerous platform devices.
1385 The timberdale FPGA can be found on the Intel Atom development board
1386 for in-vehicle infontainment, called Russellville.
1389 bool "Toshiba TC35892 and variants"
1394 Support for the Toshiba TC35892 and variants I/O Expander.
1396 This driver provides common support for accessing the device,
1397 additional drivers must be enabled in order to use the
1398 functionality of the device.
1405 bool "Toshiba T7L66XB"
1406 depends on ARM && HAVE_CLK
1410 Support for Toshiba Mobile IO Controller T7L66XB
1413 bool "Toshiba TC6387XB"
1414 depends on ARM && HAVE_CLK
1418 Support for Toshiba Mobile IO Controller TC6387XB
1421 bool "Toshiba TC6393XB"
1422 depends on ARM && HAVE_CLK
1427 Support for Toshiba Mobile IO Controller TC6393XB
1430 tristate "VIA VX855/VX875 integrated south bridge"
1434 Say yes here to enable support for various functions of the
1435 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1436 and/or vx855_gpio drivers for this to do anything useful.
1444 config MFD_ARIZONA_I2C
1445 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1450 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1451 audio SoC core functionality controlled via I2C.
1453 config MFD_ARIZONA_SPI
1454 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1457 depends on SPI_MASTER
1459 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1460 audio SoC core functionality controlled via SPI.
1463 bool "Cirrus Logic CS47L24 and WM1831"
1464 depends on MFD_ARIZONA
1466 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1469 bool "Wolfson Microelectronics WM5102"
1470 depends on MFD_ARIZONA
1472 Support for Wolfson Microelectronics WM5102 low power audio SoC
1475 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1476 depends on MFD_ARIZONA
1478 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1482 bool "Wolfson Microelectronics WM8997"
1483 depends on MFD_ARIZONA
1485 Support for Wolfson Microelectronics WM8997 low power audio SoC
1488 bool "Wolfson Microelectronics WM8998"
1489 depends on MFD_ARIZONA
1491 Support for Wolfson Microelectronics WM8998 low power audio SoC
1494 bool "Wolfson Microelectronics WM8400"
1499 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1500 CODEC. This driver provides common support for accessing
1501 the device, additional drivers must be enabled in order to use
1502 the functionality of the device.
1507 config MFD_WM831X_I2C
1508 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1515 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1516 when controlled using I2C. This driver provides common support
1517 for accessing the device, additional drivers must be enabled in
1518 order to use the functionality of the device.
1520 config MFD_WM831X_SPI
1521 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1526 depends on SPI_MASTER
1528 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1529 when controlled using SPI. This driver provides common support
1530 for accessing the device, additional drivers must be enabled in
1531 order to use the functionality of the device.
1536 config MFD_WM8350_I2C
1537 bool "Wolfson Microelectronics WM8350 with I2C"
1541 The WM8350 is an integrated audio and power management
1542 subsystem with watchdog and RTC functionality for embedded
1543 systems. This option enables core support for the WM8350 with
1544 I2C as the control interface. Additional options must be
1545 selected to enable support for the functionality of the chip.
1548 tristate "Wolfson Microelectronics WM8994"
1554 The WM8994 is a highly integrated hi-fi CODEC designed for
1555 smartphone applications. As well as audio functionality it
1556 has on board GPIO and regulator functionality which is
1557 supported via the relevant subsystems. This driver provides
1558 core support for the WM8994, in order to use the actual
1559 functionaltiy of the device other drivers must be enabled.
1562 tristate "Support for ST Microelectronics STw481x"
1563 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1567 Select this option to enable the STw481x chip driver used
1568 in various ST Microelectronics and ST-Ericsson embedded
1571 menu "Multimedia Capabilities Port drivers"
1572 depends on ARCH_SA1100
1579 tristate "Support SA11x0 MCP interface"
1580 depends on ARCH_SA1100
1585 tristate "Support for UCB1200 / UCB1300"
1586 depends on MCP_SA11X0
1589 config MCP_UCB1200_TS
1590 tristate "Touchscreen interface support"
1591 depends on MCP_UCB1200 && INPUT
1595 config MFD_VEXPRESS_SYSREG
1596 bool "Versatile Express System Registers"
1597 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1600 select GPIO_GENERIC_PLATFORM
1604 System Registers are the platform configuration block
1605 on the ARM Ltd. Versatile Express board.