2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
28 Support for the AS3711 PMIC from AMS
31 bool "ams AS3722 Power Management IC"
35 depends on I2C=y && OF
37 The ams AS3722 is a compact system PMU suitable for mobile phones,
38 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
39 controllers, 11 LDOs, RTC, automatic battery, temperature and
40 over current monitoring, GPIOs, ADC and a watchdog.
43 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
46 Say yes here to add support for Analog Devices AD5520 and ADP5501,
47 Multifunction Power Management IC. This includes
48 the I2C driver and the core APIs _only_, you have to select
49 individual components like LCD backlight, LEDs, GPIOs and Kepad
50 under the corresponding menus.
52 config MFD_AAT2870_CORE
53 bool "AnalogicTech AAT2870"
56 depends on GPIOLIB || COMPILE_TEST
58 If you say yes here you get support for the AAT2870.
59 This driver provides common support for accessing the device,
60 additional drivers must be enabled in order to use the
61 functionality of the device.
63 config MFD_ATMEL_HLCDC
64 tristate "Atmel HLCDC (High-end LCD Controller)"
69 If you say yes here you get support for the HLCDC block.
70 This driver provides common support for accessing the device,
71 additional drivers must be enabled in order to use the
72 functionality of the device.
75 tristate "Broadcom BCM590xx PMUs"
80 Support for the BCM590xx PMUs from Broadcom
83 bool "X-Powers AXP20X"
89 If you say Y here you get support for the X-Powers AXP202, AXP209 and
90 AXP288 power management IC (PMIC).
91 This driver include only the core APIs. You have to select individual
92 components like regulators or the PEK (Power Enable Key) under the
96 tristate "ChromeOS Embedded Controller"
98 select CHROME_PLATFORMS
100 depends on X86 || ARM || COMPILE_TEST
102 If you say Y here you get support for the ChromeOS Embedded
103 Controller (EC) providing keyboard, battery and power services.
104 You also need to enable the driver for the bus you are using. The
105 protocol for talking to the EC is defined by the bus driver.
107 config MFD_CROS_EC_I2C
108 tristate "ChromeOS Embedded Controller (I2C)"
109 depends on MFD_CROS_EC && I2C
112 If you say Y here, you get support for talking to the ChromeOS
113 EC through an I2C bus. This uses a simple byte-level protocol with
114 a checksum. Failing accesses will be retried three times to
117 config MFD_CROS_EC_SPI
118 tristate "ChromeOS Embedded Controller (SPI)"
119 depends on MFD_CROS_EC && SPI
122 If you say Y here, you get support for talking to the ChromeOS EC
123 through a SPI bus, using a byte-level protocol. Since the EC's
124 response time cannot be guaranteed, we support ignoring
125 'pre-amble' bytes before the response actually starts.
129 depends on GPIOLIB && ARM
132 This driver supports the ASIC3 multifunction chip found on many
133 PDAs (mainly iPAQ and HTC based ones)
136 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
139 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
140 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
141 usually found on PXA processors-based platforms. This includes
142 the I2C driver and the core APIs _only_, you have to select
143 individual components like LCD backlight, voltage regulators,
144 LEDs and battery-charger under the corresponding menus.
150 config MFD_DA9052_SPI
151 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
155 depends on SPI_MASTER=y
157 Support for the Dialog Semiconductor DA9052 PMIC
158 when controlled using SPI. This driver provides common support
159 for accessing the device, additional drivers must be enabled in
160 order to use the functionality of the device.
162 config MFD_DA9052_I2C
163 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
169 Support for the Dialog Semiconductor DA9052 PMIC
170 when controlled using I2C. This driver provides common support
171 for accessing the device, additional drivers must be enabled in
172 order to use the functionality of the device.
175 bool "Dialog Semiconductor DA9055 PMIC Support"
181 Say yes here for support of Dialog Semiconductor DA9055. This is
182 a Power Management IC. This driver provides common support for
183 accessing the device as well as the I2C interface to the chip itself.
184 Additional drivers must be enabled in order to use the functionality
187 This driver can be built as a module. If built as a module it will be
191 tristate "Dialog Semiconductor DA9062 PMIC Support"
197 Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
198 This includes the I2C driver and core APIs.
199 Additional drivers must be enabled in order to use the functionality
203 bool "Dialog Semiconductor DA9063 PMIC Support"
209 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
210 This includes the I2C driver and core APIs.
211 Additional drivers must be enabled in order to use the functionality
215 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
221 This adds support for the DA9150 integrated charger and fuel-gauge
222 chip. This driver provides common support for accessing the device.
223 Additional drivers must be enabled in order to use the specific
224 features of the device.
227 tristate "Diolan DLN2 support"
231 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
232 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
233 etc. must be enabled in order to use the functionality of
238 depends on (SPI_MASTER || I2C)
242 Enable support for the Freescale MC13783 and MC13892 PMICs.
243 This driver provides common support for accessing the device,
244 additional drivers must be enabled in order to use the
245 functionality of the device.
247 config MFD_MC13XXX_SPI
248 tristate "Freescale MC13783 and MC13892 SPI interface"
249 depends on SPI_MASTER
253 Select this if your MC13xxx is connected via an SPI bus.
255 config MFD_MC13XXX_I2C
256 tristate "Freescale MC13892 I2C interface"
261 Select this if your MC13xxx is connected via an I2C bus.
263 config MFD_HI6421_PMIC
264 tristate "HiSilicon Hi6421 PMU/Codec IC"
269 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
270 functions, such as regulators, RTC, codec, Coulomb counter, etc.
271 This driver includes core APIs _only_. You have to select
272 individul components like voltage regulators under corresponding
273 menus in order to enable them.
274 We communicate with the Hi6421 via memory-mapped I/O.
277 bool "HTC EGPIO support"
278 depends on GPIOLIB && ARM
280 This driver supports the CPLD egpio chip present on
281 several HTC phones. It provides basic support for input
282 pins, output pins, and irqs.
285 tristate "HTC PASIC3 LED/DS1WM chip support"
288 This core driver provides register access for the LED/DS1WM
289 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
290 HTC Magician devices, respectively. Actual functionality is
291 handled by the leds-pasic3 and ds1wm drivers.
294 bool "HTC I2C PLD chip support"
295 depends on I2C=y && GPIOLIB
297 If you say yes here you get support for the supposed CPLD
298 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
299 This device provides input and output GPIOs through an I2C
300 interface to one or more sub-chips.
302 config MFD_INTEL_QUARK_I2C_GPIO
303 tristate "Intel Quark MFD I2C GPIO"
306 depends on COMMON_CLK
309 This MFD provides support for I2C and GPIO that exist only
310 in a single PCI device. It splits the 2 IO devices to
311 their respective IO driver.
312 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
315 tristate "Intel ICH LPC"
319 The LPC bridge function of the Intel ICH provides support for
320 many functional units. This driver provides needed support for
321 other drivers to control these functions, currently GPIO and
325 tristate "Intel SCH LPC"
329 LPC bridge function of the Intel SCH provides support for
330 System Management Bus and General Purpose I/O.
332 config INTEL_SOC_PMIC
333 bool "Support for Intel Atom SoC PMIC"
340 Select this option to enable support for the PMIC device
341 on some Intel SoC systems. The PMIC provides ADC, GPIO,
342 thermal, charger and related power management functions
345 config MFD_INTEL_LPSS
350 config MFD_INTEL_LPSS_ACPI
351 tristate "Intel Low Power Subsystem support in ACPI mode"
352 select MFD_INTEL_LPSS
353 depends on X86 && ACPI
355 This driver supports Intel Low Power Subsystem (LPSS) devices such as
356 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
359 config MFD_INTEL_LPSS_PCI
360 tristate "Intel Low Power Subsystem support in PCI mode"
361 select MFD_INTEL_LPSS
362 depends on X86 && PCI
364 This driver supports Intel Low Power Subsystem (LPSS) devices such as
365 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
368 config MFD_INTEL_MSIC
370 depends on INTEL_SCU_IPC
373 Select this option to enable access to Intel MSIC (Avatele
374 Passage) chip. This chip embeds audio, battery, GPIO, etc.
375 devices used in Intel Medfield platforms.
377 config MFD_IPAQ_MICRO
378 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
379 depends on SA1100_H3100 || SA1100_H3600
382 Select this to get support for the Microcontroller found in
383 the Compaq iPAQ handheld computers. This is an Atmel
384 AT90LS8535 microcontroller flashed with a special iPAQ
385 firmware using the custom protocol implemented in this driver.
387 config MFD_JANZ_CMODIO
388 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
392 This is the core driver for the Janz CMOD-IO PCI MODULbus
393 carrier board. This device is a PCI to MODULbus bridge which may
394 host many different types of MODULbus daughterboards, including
395 CAN and GPIO controllers.
397 config MFD_JZ4740_ADC
398 bool "Janz JZ4740 ADC core"
400 select GENERIC_IRQ_CHIP
401 depends on MACH_JZ4740
403 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
404 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
407 tristate "Kontron module PLD device"
410 This is the core driver for the PLD (Programmable Logic Device) found
411 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
412 device may provide functions like watchdog, GPIO, UART and I2C bus.
414 The following modules are supported:
418 * COMe-bPC2 (ETXexpress-PC)
419 * COMe-bSC# (ETXexpress-SC T#)
424 * COMe-cDC2 (microETXexpress-DC)
426 * COMe-cPC2 (microETXexpress-PC)
429 * COMe-mTT10 (nanoETXexpress-TT)
432 This driver can also be built as a module. If so, the module
433 will be called kempld-core.
436 tristate "Marvell 88PM800"
442 This supports for Marvell 88PM800 Power Management IC.
443 This includes the I2C driver and the core APIs _only_, you have to
444 select individual components like voltage regulators, RTC and
445 battery-charger under the corresponding menus.
448 tristate "Marvell 88PM805"
454 This supports for Marvell 88PM805 Power Management IC. This includes
455 the I2C driver and the core APIs _only_, you have to select individual
456 components like codec device, headset/Mic device under the
460 bool "Marvell 88PM8606/88PM8607"
465 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
466 This includes the I2C driver and the core APIs _only_, you have to
467 select individual components like voltage regulators, RTC and
468 battery-charger under the corresponding menus.
471 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
478 Say yes here to add support for Maxim Semiconductor MAX14577 and
479 MAX77836 Micro-USB ICs with battery charger.
480 This driver provides common support for accessing the device;
481 additional drivers must be enabled in order to use the functionality
485 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
493 Say yes here to add support for Maxim Semiconductor MAX77686 and
494 MAX77802 which are Power Management IC with an RTC on chip.
495 This driver provides common support for accessing the device;
496 additional drivers must be enabled in order to use the functionality
500 bool "Maxim Semiconductor MAX77693 PMIC Support"
506 Say yes here to add support for Maxim Semiconductor MAX77693.
507 This is a companion Power Management IC with Flash, Haptic, Charger,
508 and MUIC(Micro USB Interface Controller) controls on chip.
509 This driver provides common support for accessing the device;
510 additional drivers must be enabled in order to use the functionality
514 bool "Maxim Semiconductor MAX77843 PMIC Support"
520 Say yes here to add support for Maxim Semiconductor MAX77843.
521 This is companion Power Management IC with LEDs, Haptic, Charger,
522 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
523 This driver provides common support for accessing the device;
524 additional drivers must be enabled in order to use the functionality
528 tristate "Maxim Semiconductor MAX8907 PMIC Support"
534 Say yes here to add support for Maxim Semiconductor MAX8907. This is
535 a Power Management IC. This driver provides common support for
536 accessing the device; additional drivers must be enabled in order
537 to use the functionality of the device.
540 bool "Maxim Semiconductor MAX8925 PMIC Support"
544 Say yes here to add support for Maxim Semiconductor MAX8925. This is
545 a Power Management IC. This driver provides common support for
546 accessing the device, additional drivers must be enabled in order
547 to use the functionality of the device.
550 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
555 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
556 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
557 MUIC 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 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
568 Say yes here to add support for Maxim Semiconductor MAX8998 and
569 National Semiconductor LP3974. This is a Power Management IC.
570 This driver provides common support for accessing the device,
571 additional drivers must be enabled in order to use the functionality
575 tristate "MediaTek MT6397 PMIC Support"
579 Say yes here to add support for MediaTek MT6397 PMIC. 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 tristate "MEN 14F021P00 Board Management Controller Support"
589 Say yes here to add support for the MEN 14F021P00 BMC
590 which is a Board Management Controller connected to the I2C bus.
591 The device supports multiple sub-devices like LED, HWMON and WDT.
592 This driver provides common support for accessing the devices;
593 additional drivers must be enabled in order to use the
594 functionality of the BMC device.
596 This driver can also be built as a module. If so the module
597 will be called menf21bmc.
600 bool "Motorola EZXPCAP Support"
601 depends on SPI_MASTER
603 This enables the PCAP ASIC present on EZX Phones. This is
604 needed for MMC, TouchScreen, Sound, USB, etc..
606 config MFD_VIPERBOARD
607 tristate "Nano River Technologies Viperboard"
612 Say yes here if you want support for Nano River Technologies
614 There are mfd cell drivers available for i2c master, adc and
615 both gpios found on the board. The spi part does not yet
617 You need to select the mfd cell drivers separately.
618 The drivers do not support all features the board exposes.
621 tristate "Nokia Retu and Tahvo multi-function device"
626 Retu and Tahvo are a multi-function devices found on Nokia
627 Internet Tablets (770, N800 and N810).
630 tristate "NXP PCF50633"
634 Say yes here if you have NXP PCF50633 chip on your board.
635 This core driver provides register access and IRQ handling
636 facilities, and registers devices for the various functions
637 so that function-specific drivers can bind to them.
640 tristate "NXP PCF50633 ADC"
641 depends on MFD_PCF50633
643 Say yes here if you want to include support for ADC in the
647 tristate "NXP PCF50633 GPIO"
648 depends on MFD_PCF50633
650 Say yes here if you want to include support GPIO for pins on
654 tristate "Philips UCB1400 Core driver"
658 This enables support for the Philips UCB1400 core functions.
659 The UCB1400 is an AC97 audio codec.
661 To compile this driver as a module, choose M here: the
662 module will be called ucb1400_core.
667 config MFD_PM8921_CORE
668 tristate "Qualcomm PM8921 PMIC chip"
669 depends on (ARM || HEXAGON)
675 If you say yes to this option, support will be included for the
676 built-in PM8921 PMIC chip.
678 This is required if your board has a PM8921 and uses its features,
679 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
681 Say M here if you want to include support for PM8921 chip as a module.
682 This will build a module called "pm8921-core".
685 tristate "Qualcomm Resource Power Manager (RPM)"
686 depends on ARCH_QCOM && OF
688 If you say yes to this option, support will be included for the
689 Resource Power Manager system found in the Qualcomm 8660, 8960 and
692 This is required to access many regulators, clocks and bus
693 frequencies controlled by the RPM on these devices.
695 Say M here if you want to include support for the Qualcomm RPM as a
696 module. This will build a module called "qcom_rpm".
699 tristate "Qualcomm SPMI PMICs"
700 depends on ARCH_QCOM || COMPILE_TEST
705 This enables support for the Qualcomm SPMI PMICs.
706 These PMICs are currently used with the Snapdragon 800 series of
707 SoCs. Note, that this will only be useful paired with descriptions
708 of the independent functions as children nodes in the device tree.
710 Say M here if you want to include support for the SPMI PMIC
711 series as a module. The module will be called "qcom-spmi-pmic".
714 tristate "RDC R-321x southbridge"
718 Say yes here if you want to have support for the RDC R-321x SoC
719 southbridge which provides access to GPIOs and Watchdog using the
720 southbridge PCI device configuration space.
723 tristate "Realtek PCI-E card reader"
727 This supports for Realtek PCI-Express card reader including rts5209,
728 rts5229, rtl8411, etc. Realtek card reader supports access to many
729 types of memory cards, such as Memory Stick, Memory Stick Pro,
730 Secure Digital and MultiMediaCard.
733 tristate "Richtek RT5033 Power Management IC"
739 This driver provides for the Richtek RT5033 Power Management IC,
740 which includes the I2C driver and the Core APIs. This driver provides
741 common support for accessing the device. The device supports multiple
742 sub-devices like charger, fuel gauge, flash LED, current source,
746 tristate "Realtek USB card reader"
750 Select this option to get support for Realtek USB 2.0 card readers
751 including RTS5129, RTS5139, RTS5179 and RTS5170.
752 Realtek card reader supports access to many types of memory cards,
753 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
756 bool "Ricoh RC5T583 Power Management system device"
761 Select this option to get support for the RICOH583 Power
762 Management system device.
763 This driver provides common support for accessing the device
764 through i2c interface. The device supports multiple sub-devices
765 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
766 Additional drivers must be enabled in order to use the
767 different functionality of the device.
770 tristate "Rockchip RK808 Power Management chip"
776 If you say yes here you get support for the RK808
777 Power Management chips.
778 This driver provides common support for accessing the device
779 through I2C interface. The device supports multiple sub-devices
780 including interrupts, RTC, LDO & DCDC regulators, and onkey.
783 tristate "Ricoh RN5T5618 PMIC"
788 Say yes here to add support for the Ricoh RN5T618 PMIC. This
789 driver provides common support for accessing the device,
790 additional drivers must be enabled in order to use the
791 functionality of the device.
794 bool "SAMSUNG Electronics PMIC Series Support"
800 Support for the Samsung Electronics MFD series.
801 This driver provides common support for accessing the device,
802 additional drivers must be enabled in order to use the functionality
805 config MFD_SI476X_CORE
806 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
811 This is the core driver for the SI476x series of AM/FM
812 radio. This MFD driver connects the radio-si476x V4L2 module
813 and the si476x audio codec.
815 To compile this driver as a module, choose M here: the
816 module will be called si476x-core.
819 tristate "Silicon Motion SM501"
821 This is the core driver for the Silicon Motion SM501 multimedia
822 companion chip. This device is a multifunction device which may
823 provide numerous interfaces including USB host controller, USB gadget,
824 asynchronous serial ports, audio functions, and a dual display video
825 interface. The device may be connected by PCI or local bus with
826 varying functions enabled.
828 config MFD_SM501_GPIO
829 bool "Export GPIO via GPIO layer"
830 depends on MFD_SM501 && GPIOLIB
832 This option uses the gpio library layer to export the 64 GPIO
833 lines on the SM501. The platform data is used to supply the
834 base number for the first GPIO line to register.
837 tristate "Skyworks Solutions SKY81452"
842 This is the core driver for the Skyworks SKY81452 backlight and
843 voltage regulator device.
845 This driver can also be built as a module. If so, the module
846 will be called sky81452.
849 bool "SMSC ECE1099 series chips"
854 If you say yes here you get support for the
855 ece1099 chips from SMSC.
857 To compile this driver as a module, choose M here: the
858 module will be called smsc.
861 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
862 default y if ARCH_U300 || ARCH_U8500
864 Say yes here if you have the ABX500 Mixed Signal IC family
865 chips. This core driver expose register access functions.
866 Functionality specific drivers using these functions can
867 remain unchanged when IC changes. Binding of the functions to
868 actual register access is done by the IC core driver.
871 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
872 depends on I2C=y && ABX500_CORE
874 default y if ARCH_U300
876 Select this to enable the AB3100 Mixed Signal IC core
877 functionality. This connects to a AB3100 on the I2C bus
878 and expose a number of symbols needed for dependent devices
879 to read and write registers and subscribe to events from
880 this multi-functional IC. This is needed to use other features
881 of the AB3100 such as battery-backed RTC, charging control,
882 LEDs, vibrator, system power and temperature, power management
886 tristate "ST-Ericsson AB3100 OTP functions"
887 depends on AB3100_CORE
888 default y if AB3100_CORE
890 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
891 programmable memory) support. This exposes a sysfs file to read
895 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
896 depends on ABX500_CORE && MFD_DB8500_PRCMU
901 Select this option to enable access to AB8500 power management
902 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
903 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
904 the irq_chip parts for handling the Mixed Signal chip events.
905 This chip embeds various other multimedia funtionalities as well.
908 bool "Enable debug info via debugfs"
909 depends on AB8500_GPADC && DEBUG_FS
910 default y if DEBUG_FS
912 Select this option if you want debug information using the debug
916 bool "ST-Ericsson AB8500 GPADC driver"
917 depends on AB8500_CORE && REGULATOR_AB8500
920 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
922 config MFD_DB8500_PRCMU
923 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
924 depends on UX500_SOC_DB8500
927 Select this option to enable support for the DB8500 Power Reset
928 and Control Management Unit. This is basically an autonomous
929 system controller running an XP70 microprocessor, which is accessed
930 through a register map.
933 bool "STMicroelectronics STMPE"
934 depends on (I2C=y || SPI_MASTER=y)
938 Support for the STMPE family of I/O Expanders from
941 Currently supported devices are:
943 STMPE811: GPIO, Touchscreen
944 STMPE1601: GPIO, Keypad
945 STMPE1801: GPIO, Keypad
946 STMPE2401: GPIO, Keypad
947 STMPE2403: GPIO, Keypad
949 This driver provides common support for accessing the device,
950 additional drivers must be enabled in order to use the functionality
951 of the device. Currently available sub drivers are:
955 Touchscreen: stmpe-ts
957 menu "STMicroelectronics STMPE Interface Drivers"
961 bool "STMicroelectronics STMPE I2C Interface"
965 This is used to enable I2C interface of STMPE
968 bool "STMicroelectronics STMPE SPI Interface"
969 depends on SPI_MASTER
971 This is used to enable SPI interface of STMPE
975 bool "STMicroelectronics STA2X11"
980 config MFD_SUN6I_PRCM
981 bool "Allwinner A31 PRCM controller"
982 depends on ARCH_SUNXI
985 Support for the PRCM (Power/Reset/Clock Management) unit available
989 bool "System Controller Register R/W Based on Regmap"
992 Select this option to enable accessing system control registers
995 config MFD_DAVINCI_VOICECODEC
1000 config MFD_TI_AM335X_TSCADC
1001 tristate "TI ADC / Touch Screen chip support"
1006 If you say yes here you get support for Texas Instruments series
1007 of Touch Screen /ADC chips.
1008 To compile this driver as a module, choose M here: the
1009 module will be called ti_am335x_tscadc.
1011 config MFD_DM355EVM_MSP
1012 bool "TI DaVinci DM355 EVM microcontroller"
1013 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1015 This driver supports the MSP430 microcontroller used on these
1016 boards. MSP430 firmware manages resets and power sequencing,
1017 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1020 tristate "TI/National Semiconductor LP3943 MFD Driver"
1025 Support for the TI/National Semiconductor LP3943.
1026 This driver consists of GPIO and PWM drivers.
1027 With these functionalities, it can be used for LED string control or
1028 general usage such like a GPIO controller and a PWM controller.
1031 bool "TI LP8788 Power Management Unit Driver"
1037 TI LP8788 PMU supports regulators, battery charger, RTC,
1038 ADC, backlight driver and current sinks.
1040 config MFD_OMAP_USB_HOST
1041 bool "TI OMAP USBHS core and TLL driver"
1042 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1045 This is the core driver for the OAMP EHCI and OHCI drivers.
1046 This MFD driver does the required setup functionalities for
1047 OMAP USB Host drivers.
1050 bool "TI Palmas series chips"
1056 If you say yes here you get support for the Palmas
1057 series of PMIC chips from Texas Instruments.
1060 tristate "TI TPS61050/61052 Boost Converters"
1064 select REGULATOR_FIXED_VOLTAGE
1066 This option enables a driver for the TP61050/TPS61052
1067 high-power "white LED driver". This boost converter is
1068 sometimes used for other things than white LEDs, and
1069 also contains a GPIO pin.
1072 tristate "TI TPS6501x Power Management chips"
1073 depends on I2C && GPIOLIB
1074 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1076 If you say yes here you get support for the TPS6501x series of
1077 Power Management chips. These include voltage regulators,
1078 lithium ion/polymer battery charging, and other features that
1079 are often used in portable devices like cell phones and cameras.
1081 This driver can also be built as a module. If so, the module
1082 will be called tps65010.
1085 tristate "TI TPS6507x Power Management / Touch Screen chips"
1089 If you say yes here you get support for the TPS6507x series of
1090 Power Management / Touch Screen chips. These include voltage
1091 regulators, lithium ion/polymer battery charging, touch screen
1092 and other features that are often used in portable devices.
1093 This driver can also be built as a module. If so, the module
1094 will be called tps6507x.
1096 config TPS65911_COMPARATOR
1100 bool "TI TPS65090 Power Management chips"
1106 If you say yes here you get support for the TPS65090 series of
1107 Power Management chips.
1108 This driver provides common support for accessing the device,
1109 additional drivers must be enabled in order to use the
1110 functionality of the device.
1113 tristate "TI TPS65217 Power Management / White LED chips"
1118 If you say yes here you get support for the TPS65217 series of
1119 Power Management / White LED chips.
1120 These include voltage regulators, lithium ion/polymer battery
1121 charger, wled and other features that are often used in portable
1124 This driver can also be built as a module. If so, the module
1125 will be called tps65217.
1128 tristate "TI TPS65218 Power Management chips"
1134 If you say yes here you get support for the TPS65218 series of
1135 Power Management chips.
1136 These include voltage regulators, gpio and other features
1137 that are often used in portable devices. Only regulator
1138 component is currently supported.
1140 This driver can also be built as a module. If so, the module
1141 will be called tps65218.
1144 bool "TI TPS6586x Power Management chips"
1149 If you say yes here you get support for the TPS6586X series of
1150 Power Management chips.
1151 This driver provides common support for accessing the device,
1152 additional drivers must be enabled in order to use the
1153 functionality of the device.
1155 This driver can also be built as a module. If so, the module
1156 will be called tps6586x.
1159 bool "TI TPS65910 Power Management chip"
1161 depends on GPIOLIB || COMPILE_TEST
1167 if you say yes here you get support for the TPS65910 series of
1168 Power Management chips.
1171 bool "TI TPS65912 Power Management chip"
1175 If you say yes here you get support for the TPS65912 series of
1178 config MFD_TPS65912_I2C
1179 bool "TI TPS65912 Power Management chip with I2C"
1182 depends on I2C=y && GPIOLIB
1184 If you say yes here you get support for the TPS65912 series of
1185 PM chips with I2C interface.
1187 config MFD_TPS65912_SPI
1188 bool "TI TPS65912 Power Management chip with SPI"
1191 depends on SPI_MASTER && GPIOLIB
1193 If you say yes here you get support for the TPS65912 series of
1194 PM chips with SPI interface.
1197 bool "TI TPS80031/TPS80032 Power Management chips"
1203 If you say yes here you get support for the Texas Instruments
1204 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1205 Path and Battery Charger. The device provides five configurable
1206 step-down converters, 11 general purpose LDOs, USB OTG Module,
1207 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1208 Power Path from USB, 32K clock generator.
1211 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1216 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1217 This core driver provides register access and IRQ handling
1218 facilities, and registers devices for the various functions
1219 so that function-specific drivers can bind to them.
1221 These multi-function chips are found on many OMAP2 and OMAP3
1222 boards, providing power management, RTC, GPIO, keypad, a
1223 high speed USB OTG transceiver, an audio codec (on most
1224 versions) and many other features.
1226 config TWL4030_POWER
1227 bool "TI TWL4030 power resources"
1228 depends on TWL4030_CORE && ARM
1230 Say yes here if you want to use the power resources on the
1231 TWL4030 family chips. Most of these resources are regulators,
1232 which have a separate driver; some are control signals, such
1233 as clock request handshaking.
1235 This driver uses board-specific data to initialize the resources
1236 and load scripts controlling which resources are switched off/on
1237 or reset when a sleep, wakeup or warm reset event occurs.
1239 config MFD_TWL4030_AUDIO
1240 bool "TI TWL4030 Audio"
1241 depends on TWL4030_CORE
1246 bool "TI TWL6040 audio codec"
1253 Say yes here if you want support for Texas Instruments TWL6040 audio
1255 This driver provides common support for accessing the device,
1256 additional drivers must be enabled in order to use the
1257 functionality of the device (audio, vibra).
1260 bool "TI TWL92330/Menelaus PM chip"
1261 depends on I2C=y && ARCH_OMAP2
1263 If you say yes here you get support for the Texas Instruments
1264 TWL92330/Menelaus Power Management chip. This include voltage
1265 regulators, Dual slot memory card transceivers, real-time clock
1266 and other features that are often used in portable devices like
1267 cell phones and PDAs.
1269 config MFD_WL1273_CORE
1270 tristate "TI WL1273 FM radio"
1275 This is the core driver for the TI WL1273 FM radio. This MFD
1276 driver connects the radio-wl1273 V4L2 module and the wl1273
1280 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1285 Say yes here to enable support for National Semiconductor / TI
1286 LM3533 Lighting Power chips.
1288 This driver provides common support for accessing the device;
1289 additional drivers must be enabled in order to use the LED,
1290 backlight or ambient-light-sensor functionality of the device.
1292 config MFD_TIMBERDALE
1293 tristate "Timberdale FPGA"
1295 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1297 This is the core driver for the timberdale FPGA. This device is a
1298 multifunction device which exposes numerous platform devices.
1300 The timberdale FPGA can be found on the Intel Atom development board
1301 for in-vehicle infontainment, called Russellville.
1304 bool "Toshiba TC35892 and variants"
1309 Support for the Toshiba TC35892 and variants I/O Expander.
1311 This driver provides common support for accessing the device,
1312 additional drivers must be enabled in order to use the
1313 functionality of the device.
1320 bool "Toshiba T7L66XB"
1321 depends on ARM && HAVE_CLK
1325 Support for Toshiba Mobile IO Controller T7L66XB
1328 bool "Toshiba TC6387XB"
1329 depends on ARM && HAVE_CLK
1333 Support for Toshiba Mobile IO Controller TC6387XB
1336 bool "Toshiba TC6393XB"
1337 depends on ARM && HAVE_CLK
1342 Support for Toshiba Mobile IO Controller TC6393XB
1345 tristate "VIA VX855/VX875 integrated south bridge"
1349 Say yes here to enable support for various functions of the
1350 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1351 and/or vx855_gpio drivers for this to do anything useful.
1359 config MFD_ARIZONA_I2C
1360 tristate "Wolfson Microelectronics Arizona platform with I2C"
1366 Support for the Wolfson Microelectronics Arizona platform audio SoC
1367 core functionality controlled via I2C.
1369 config MFD_ARIZONA_SPI
1370 tristate "Wolfson Microelectronics Arizona platform with SPI"
1374 depends on SPI_MASTER
1376 Support for the Wolfson Microelectronics Arizona platform audio SoC
1377 core functionality controlled via I2C.
1380 bool "Wolfson Microelectronics WM5102"
1381 depends on MFD_ARIZONA
1383 Support for Wolfson Microelectronics WM5102 low power audio SoC
1386 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1387 depends on MFD_ARIZONA
1389 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1393 bool "Wolfson Microelectronics WM8997"
1394 depends on MFD_ARIZONA
1396 Support for Wolfson Microelectronics WM8997 low power audio SoC
1399 bool "Wolfson Microelectronics WM8998"
1400 depends on MFD_ARIZONA
1402 Support for Wolfson Microelectronics WM8998 low power audio SoC
1405 bool "Wolfson Microelectronics WM8400"
1410 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1411 CODEC. This driver provides common support for accessing
1412 the device, additional drivers must be enabled in order to use
1413 the functionality of the device.
1418 config MFD_WM831X_I2C
1419 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1426 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1427 when controlled using I2C. This driver provides common support
1428 for accessing the device, additional drivers must be enabled in
1429 order to use the functionality of the device.
1431 config MFD_WM831X_SPI
1432 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1437 depends on SPI_MASTER
1439 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1440 when controlled using SPI. This driver provides common support
1441 for accessing the device, additional drivers must be enabled in
1442 order to use the functionality of the device.
1447 config MFD_WM8350_I2C
1448 bool "Wolfson Microelectronics WM8350 with I2C"
1452 The WM8350 is an integrated audio and power management
1453 subsystem with watchdog and RTC functionality for embedded
1454 systems. This option enables core support for the WM8350 with
1455 I2C as the control interface. Additional options must be
1456 selected to enable support for the functionality of the chip.
1459 tristate "Wolfson Microelectronics WM8994"
1465 The WM8994 is a highly integrated hi-fi CODEC designed for
1466 smartphone applications. As well as audio functionality it
1467 has on board GPIO and regulator functionality which is
1468 supported via the relevant subsystems. This driver provides
1469 core support for the WM8994, in order to use the actual
1470 functionaltiy of the device other drivers must be enabled.
1473 tristate "Support for ST Microelectronics STw481x"
1474 depends on I2C && ARCH_NOMADIK
1478 Select this option to enable the STw481x chip driver used
1479 in various ST Microelectronics and ST-Ericsson embedded
1482 menu "Multimedia Capabilities Port drivers"
1483 depends on ARCH_SA1100
1490 tristate "Support SA11x0 MCP interface"
1491 depends on ARCH_SA1100
1496 tristate "Support for UCB1200 / UCB1300"
1497 depends on MCP_SA11X0
1500 config MCP_UCB1200_TS
1501 tristate "Touchscreen interface support"
1502 depends on MCP_UCB1200 && INPUT
1506 config MFD_VEXPRESS_SYSREG
1507 bool "Versatile Express System Registers"
1508 depends on VEXPRESS_CONFIG && GPIOLIB
1511 select GPIO_GENERIC_PLATFORM
1515 System Registers are the platform configuration block
1516 on the ARM Ltd. Versatile Express board.