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"
55 depends on I2C=y && GPIOLIB
57 If you say yes here you get support for the AAT2870.
58 This driver provides common support for accessing the device,
59 additional drivers must be enabled in order to use the
60 functionality of the device.
62 config MFD_ATMEL_HLCDC
63 tristate "Atmel HLCDC (High-end LCD Controller)"
68 If you say yes here you get support for the HLCDC block.
69 This driver provides common support for accessing the device,
70 additional drivers must be enabled in order to use the
71 functionality of the device.
74 tristate "Broadcom BCM590xx PMUs"
79 Support for the BCM590xx PMUs from Broadcom
82 bool "X-Powers AXP20X"
88 If you say Y here you get support for the X-Powers AXP202, AXP209 and
89 AXP288 power management IC (PMIC).
90 This driver include only the core APIs. You have to select individual
91 components like regulators or the PEK (Power Enable Key) under the
95 tristate "ChromeOS Embedded Controller"
98 If you say Y here you get support for the ChromeOS Embedded
99 Controller (EC) providing keyboard, battery and power services.
100 You also need to enable the driver for the bus you are using. The
101 protocol for talking to the EC is defined by the bus driver.
103 config MFD_CROS_EC_I2C
104 tristate "ChromeOS Embedded Controller (I2C)"
105 depends on MFD_CROS_EC && I2C
108 If you say Y here, you get support for talking to the ChromeOS
109 EC through an I2C bus. This uses a simple byte-level protocol with
110 a checksum. Failing accesses will be retried three times to
113 config MFD_CROS_EC_SPI
114 tristate "ChromeOS Embedded Controller (SPI)"
115 depends on MFD_CROS_EC && SPI && OF
118 If you say Y here, you get support for talking to the ChromeOS EC
119 through a SPI bus, using a byte-level protocol. Since the EC's
120 response time cannot be guaranteed, we support ignoring
121 'pre-amble' bytes before the response actually starts.
125 depends on GPIOLIB && ARM
128 This driver supports the ASIC3 multifunction chip found on many
129 PDAs (mainly iPAQ and HTC based ones)
132 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
135 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
136 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
137 usually found on PXA processors-based platforms. This includes
138 the I2C driver and the core APIs _only_, you have to select
139 individual components like LCD backlight, voltage regulators,
140 LEDs and battery-charger under the corresponding menus.
146 config MFD_DA9052_SPI
147 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
151 depends on SPI_MASTER=y
153 Support for the Dialog Semiconductor DA9052 PMIC
154 when controlled using SPI. This driver provides common support
155 for accessing the device, additional drivers must be enabled in
156 order to use the functionality of the device.
158 config MFD_DA9052_I2C
159 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
165 Support for the Dialog Semiconductor DA9052 PMIC
166 when controlled using I2C. This driver provides common support
167 for accessing the device, additional drivers must be enabled in
168 order to use the functionality of the device.
171 bool "Dialog Semiconductor DA9055 PMIC Support"
177 Say yes here for support of Dialog Semiconductor DA9055. This is
178 a Power Management IC. This driver provides common support for
179 accessing the device as well as the I2C interface to the chip itself.
180 Additional drivers must be enabled in order to use the functionality
183 This driver can be built as a module. If built as a module it will be
187 bool "Dialog Semiconductor DA9063 PMIC Support"
193 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
194 This includes the I2C driver and core APIs.
195 Additional drivers must be enabled in order to use the functionality
199 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
205 This adds support for the DA9150 integrated charger and fuel-gauge
206 chip. This driver provides common support for accessing the device.
207 Additional drivers must be enabled in order to use the specific
208 features of the device.
211 tristate "Diolan DLN2 support"
215 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
216 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
217 etc. must be enabled in order to use the functionality of
222 depends on (SPI_MASTER || I2C)
226 Enable support for the Freescale MC13783 and MC13892 PMICs.
227 This driver provides common support for accessing the device,
228 additional drivers must be enabled in order to use the
229 functionality of the device.
231 config MFD_MC13XXX_SPI
232 tristate "Freescale MC13783 and MC13892 SPI interface"
233 depends on SPI_MASTER
237 Select this if your MC13xxx is connected via an SPI bus.
239 config MFD_MC13XXX_I2C
240 tristate "Freescale MC13892 I2C interface"
245 Select this if your MC13xxx is connected via an I2C bus.
247 config MFD_HI6421_PMIC
248 tristate "HiSilicon Hi6421 PMU/Codec IC"
253 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
254 functions, such as regulators, RTC, codec, Coulomb counter, etc.
255 This driver includes core APIs _only_. You have to select
256 individul components like voltage regulators under corresponding
257 menus in order to enable them.
258 We communicate with the Hi6421 via memory-mapped I/O.
261 bool "HTC EGPIO support"
262 depends on GPIOLIB && ARM
264 This driver supports the CPLD egpio chip present on
265 several HTC phones. It provides basic support for input
266 pins, output pins, and irqs.
269 tristate "HTC PASIC3 LED/DS1WM chip support"
272 This core driver provides register access for the LED/DS1WM
273 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
274 HTC Magician devices, respectively. Actual functionality is
275 handled by the leds-pasic3 and ds1wm drivers.
278 bool "HTC I2C PLD chip support"
279 depends on I2C=y && GPIOLIB
281 If you say yes here you get support for the supposed CPLD
282 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
283 This device provides input and output GPIOs through an I2C
284 interface to one or more sub-chips.
287 tristate "Intel ICH LPC"
291 The LPC bridge function of the Intel ICH provides support for
292 many functional units. This driver provides needed support for
293 other drivers to control these functions, currently GPIO and
297 tristate "Intel SCH LPC"
301 LPC bridge function of the Intel SCH provides support for
302 System Management Bus and General Purpose I/O.
304 config INTEL_SOC_PMIC
305 bool "Support for Intel Atom SoC PMIC"
311 Select this option to enable support for the PMIC device
312 on some Intel SoC systems. The PMIC provides ADC, GPIO,
313 thermal, charger and related power management functions
316 config MFD_INTEL_MSIC
318 depends on INTEL_SCU_IPC
321 Select this option to enable access to Intel MSIC (Avatele
322 Passage) chip. This chip embeds audio, battery, GPIO, etc.
323 devices used in Intel Medfield platforms.
325 config MFD_IPAQ_MICRO
326 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
327 depends on SA1100_H3100 || SA1100_H3600
330 Select this to get support for the Microcontroller found in
331 the Compaq iPAQ handheld computers. This is an Atmel
332 AT90LS8535 microcontroller flashed with a special iPAQ
333 firmware using the custom protocol implemented in this driver.
335 config MFD_JANZ_CMODIO
336 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
340 This is the core driver for the Janz CMOD-IO PCI MODULbus
341 carrier board. This device is a PCI to MODULbus bridge which may
342 host many different types of MODULbus daughterboards, including
343 CAN and GPIO controllers.
345 config MFD_JZ4740_ADC
346 bool "Janz JZ4740 ADC core"
348 select GENERIC_IRQ_CHIP
349 depends on MACH_JZ4740
351 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
352 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
355 tristate "Kontron module PLD device"
358 This is the core driver for the PLD (Programmable Logic Device) found
359 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
360 device may provide functions like watchdog, GPIO, UART and I2C bus.
362 The following modules are supported:
365 * COMe-bPC2 (ETXexpress-PC)
366 * COMe-bSC# (ETXexpress-SC T#)
370 * COMe-cDC2 (microETXexpress-DC)
372 * COMe-cPC2 (microETXexpress-PC)
375 * COMe-mTT10 (nanoETXexpress-TT)
378 This driver can also be built as a module. If so, the module
379 will be called kempld-core.
382 tristate "Marvell 88PM800"
388 This supports for Marvell 88PM800 Power Management IC.
389 This includes the I2C driver and the core APIs _only_, you have to
390 select individual components like voltage regulators, RTC and
391 battery-charger under the corresponding menus.
394 tristate "Marvell 88PM805"
400 This supports for Marvell 88PM805 Power Management IC. This includes
401 the I2C driver and the core APIs _only_, you have to select individual
402 components like codec device, headset/Mic device under the
406 bool "Marvell 88PM8606/88PM8607"
411 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
412 This includes the I2C driver and the core APIs _only_, you have to
413 select individual components like voltage regulators, RTC and
414 battery-charger under the corresponding menus.
417 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
424 Say yes here to add support for Maxim Semiconductor MAX14577 and
425 MAX77836 Micro-USB ICs with battery charger.
426 This driver provides common support for accessing the device;
427 additional drivers must be enabled in order to use the functionality
431 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
439 Say yes here to add support for Maxim Semiconductor MAX77686 and
440 MAX77802 which are Power Management IC with an RTC on chip.
441 This driver provides common support for accessing the device;
442 additional drivers must be enabled in order to use the functionality
446 bool "Maxim Semiconductor MAX77693 PMIC Support"
452 Say yes here to add support for Maxim Semiconductor MAX77693.
453 This is a companion Power Management IC with Flash, Haptic, Charger,
454 and MUIC(Micro USB Interface Controller) controls on chip.
455 This driver provides common support for accessing the device;
456 additional drivers must be enabled in order to use the functionality
460 bool "Maxim Semiconductor MAX77843 PMIC Support"
466 Say yes here to add support for Maxim Semiconductor MAX77843.
467 This is companion Power Management IC with LEDs, Haptic, Charger,
468 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
469 This driver provides common support for accessing the device;
470 additional drivers must be enabled in order to use the functionality
474 tristate "Maxim Semiconductor MAX8907 PMIC Support"
480 Say yes here to add support for Maxim Semiconductor MAX8907. This is
481 a Power Management IC. This driver provides common support for
482 accessing the device; additional drivers must be enabled in order
483 to use the functionality of the device.
486 bool "Maxim Semiconductor MAX8925 PMIC Support"
490 Say yes here to add support for Maxim Semiconductor MAX8925. This is
491 a Power Management IC. This driver provides common support for
492 accessing the device, additional drivers must be enabled in order
493 to use the functionality of the device.
496 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
501 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
502 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
503 MUIC controls on chip.
504 This driver provides common support for accessing the device;
505 additional drivers must be enabled in order to use the functionality
509 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
514 Say yes here to add support for Maxim Semiconductor MAX8998 and
515 National Semiconductor LP3974. This is a Power Management IC.
516 This driver provides common support for accessing the device,
517 additional drivers must be enabled in order to use the functionality
521 tristate "MediaTek MT6397 PMIC Support"
525 Say yes here to add support for MediaTek MT6397 PMIC. This is
526 a Power Management IC. This driver provides common support for
527 accessing the device; additional drivers must be enabled in order
528 to use the functionality of the device.
531 tristate "MEN 14F021P00 Board Management Controller Support"
535 Say yes here to add support for the MEN 14F021P00 BMC
536 which is a Board Management Controller connected to the I2C bus.
537 The device supports multiple sub-devices like LED, HWMON and WDT.
538 This driver provides common support for accessing the devices;
539 additional drivers must be enabled in order to use the
540 functionality of the BMC device.
542 This driver can also be built as a module. If so the module
543 will be called menf21bmc.
546 bool "Motorola EZXPCAP Support"
547 depends on SPI_MASTER
549 This enables the PCAP ASIC present on EZX Phones. This is
550 needed for MMC, TouchScreen, Sound, USB, etc..
552 config MFD_VIPERBOARD
553 tristate "Nano River Technologies Viperboard"
558 Say yes here if you want support for Nano River Technologies
560 There are mfd cell drivers available for i2c master, adc and
561 both gpios found on the board. The spi part does not yet
563 You need to select the mfd cell drivers separately.
564 The drivers do not support all features the board exposes.
567 tristate "Nokia Retu and Tahvo multi-function device"
572 Retu and Tahvo are a multi-function devices found on Nokia
573 Internet Tablets (770, N800 and N810).
576 tristate "NXP PCF50633"
580 Say yes here if you have NXP PCF50633 chip on your board.
581 This core driver provides register access and IRQ handling
582 facilities, and registers devices for the various functions
583 so that function-specific drivers can bind to them.
586 tristate "NXP PCF50633 ADC"
587 depends on MFD_PCF50633
589 Say yes here if you want to include support for ADC in the
593 tristate "NXP PCF50633 GPIO"
594 depends on MFD_PCF50633
596 Say yes here if you want to include support GPIO for pins on
600 tristate "Philips UCB1400 Core driver"
604 This enables support for the Philips UCB1400 core functions.
605 The UCB1400 is an AC97 audio codec.
607 To compile this driver as a module, choose M here: the
608 module will be called ucb1400_core.
613 config MFD_PM8921_CORE
614 tristate "Qualcomm PM8921 PMIC chip"
615 depends on (ARM || HEXAGON)
621 If you say yes to this option, support will be included for the
622 built-in PM8921 PMIC chip.
624 This is required if your board has a PM8921 and uses its features,
625 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
627 Say M here if you want to include support for PM8921 chip as a module.
628 This will build a module called "pm8921-core".
631 tristate "Qualcomm Resource Power Manager (RPM)"
632 depends on ARCH_QCOM && OF
634 If you say yes to this option, support will be included for the
635 Resource Power Manager system found in the Qualcomm 8660, 8960 and
638 This is required to access many regulators, clocks and bus
639 frequencies controlled by the RPM on these devices.
641 Say M here if you want to include support for the Qualcomm RPM as a
642 module. This will build a module called "qcom_rpm".
645 tristate "Qualcomm SPMI PMICs"
646 depends on ARCH_QCOM || COMPILE_TEST
651 This enables support for the Qualcomm SPMI PMICs.
652 These PMICs are currently used with the Snapdragon 800 series of
653 SoCs. Note, that this will only be useful paired with descriptions
654 of the independent functions as children nodes in the device tree.
656 Say M here if you want to include support for the SPMI PMIC
657 series as a module. The module will be called "qcom-spmi-pmic".
660 tristate "RDC R-321x southbridge"
664 Say yes here if you want to have support for the RDC R-321x SoC
665 southbridge which provides access to GPIOs and Watchdog using the
666 southbridge PCI device configuration space.
669 tristate "Realtek PCI-E card reader"
673 This supports for Realtek PCI-Express card reader including rts5209,
674 rts5229, rtl8411, etc. Realtek card reader supports access to many
675 types of memory cards, such as Memory Stick, Memory Stick Pro,
676 Secure Digital and MultiMediaCard.
679 tristate "Richtek RT5033 Power Management IC"
685 This driver provides for the Richtek RT5033 Power Management IC,
686 which includes the I2C driver and the Core APIs. This driver provides
687 common support for accessing the device. The device supports multiple
688 sub-devices like charger, fuel gauge, flash LED, current source,
692 tristate "Realtek USB card reader"
696 Select this option to get support for Realtek USB 2.0 card readers
697 including RTS5129, RTS5139, RTS5179 and RTS5170.
698 Realtek card reader supports access to many types of memory cards,
699 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
702 bool "Ricoh RC5T583 Power Management system device"
707 Select this option to get support for the RICOH583 Power
708 Management system device.
709 This driver provides common support for accessing the device
710 through i2c interface. The device supports multiple sub-devices
711 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
712 Additional drivers must be enabled in order to use the
713 different functionality of the device.
716 tristate "Rockchip RK808 Power Management chip"
722 If you say yes here you get support for the RK808
723 Power Management chips.
724 This driver provides common support for accessing the device
725 through I2C interface. The device supports multiple sub-devices
726 including interrupts, RTC, LDO & DCDC regulators, and onkey.
729 tristate "Ricoh RN5T5618 PMIC"
734 Say yes here to add support for the Ricoh RN5T618 PMIC. This
735 driver provides common support for accessing the device,
736 additional drivers must be enabled in order to use the
737 functionality of the device.
740 bool "SAMSUNG Electronics PMIC Series Support"
746 Support for the Samsung Electronics MFD series.
747 This driver provides common support for accessing the device,
748 additional drivers must be enabled in order to use the functionality
751 config MFD_SI476X_CORE
752 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
757 This is the core driver for the SI476x series of AM/FM
758 radio. This MFD driver connects the radio-si476x V4L2 module
759 and the si476x audio codec.
761 To compile this driver as a module, choose M here: the
762 module will be called si476x-core.
765 tristate "Silicon Motion SM501"
767 This is the core driver for the Silicon Motion SM501 multimedia
768 companion chip. This device is a multifunction device which may
769 provide numerous interfaces including USB host controller, USB gadget,
770 asynchronous serial ports, audio functions, and a dual display video
771 interface. The device may be connected by PCI or local bus with
772 varying functions enabled.
774 config MFD_SM501_GPIO
775 bool "Export GPIO via GPIO layer"
776 depends on MFD_SM501 && GPIOLIB
778 This option uses the gpio library layer to export the 64 GPIO
779 lines on the SM501. The platform data is used to supply the
780 base number for the first GPIO line to register.
783 bool "SMSC ECE1099 series chips"
788 If you say yes here you get support for the
789 ece1099 chips from SMSC.
791 To compile this driver as a module, choose M here: the
792 module will be called smsc.
795 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
796 default y if ARCH_U300 || ARCH_U8500
798 Say yes here if you have the ABX500 Mixed Signal IC family
799 chips. This core driver expose register access functions.
800 Functionality specific drivers using these functions can
801 remain unchanged when IC changes. Binding of the functions to
802 actual register access is done by the IC core driver.
805 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
806 depends on I2C=y && ABX500_CORE
808 default y if ARCH_U300
810 Select this to enable the AB3100 Mixed Signal IC core
811 functionality. This connects to a AB3100 on the I2C bus
812 and expose a number of symbols needed for dependent devices
813 to read and write registers and subscribe to events from
814 this multi-functional IC. This is needed to use other features
815 of the AB3100 such as battery-backed RTC, charging control,
816 LEDs, vibrator, system power and temperature, power management
820 tristate "ST-Ericsson AB3100 OTP functions"
821 depends on AB3100_CORE
822 default y if AB3100_CORE
824 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
825 programmable memory) support. This exposes a sysfs file to read
829 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
830 depends on ABX500_CORE && MFD_DB8500_PRCMU
835 Select this option to enable access to AB8500 power management
836 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
837 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
838 the irq_chip parts for handling the Mixed Signal chip events.
839 This chip embeds various other multimedia funtionalities as well.
842 bool "Enable debug info via debugfs"
843 depends on AB8500_GPADC && DEBUG_FS
844 default y if DEBUG_FS
846 Select this option if you want debug information using the debug
850 bool "ST-Ericsson AB8500 GPADC driver"
851 depends on AB8500_CORE && REGULATOR_AB8500
854 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
856 config MFD_DB8500_PRCMU
857 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
858 depends on UX500_SOC_DB8500
861 Select this option to enable support for the DB8500 Power Reset
862 and Control Management Unit. This is basically an autonomous
863 system controller running an XP70 microprocessor, which is accessed
864 through a register map.
867 bool "STMicroelectronics STMPE"
868 depends on (I2C=y || SPI_MASTER=y)
872 Support for the STMPE family of I/O Expanders from
875 Currently supported devices are:
877 STMPE811: GPIO, Touchscreen
878 STMPE1601: GPIO, Keypad
879 STMPE1801: GPIO, Keypad
880 STMPE2401: GPIO, Keypad
881 STMPE2403: GPIO, Keypad
883 This driver provides common support for accessing the device,
884 additional drivers must be enabled in order to use the functionality
885 of the device. Currently available sub drivers are:
889 Touchscreen: stmpe-ts
891 menu "STMicroelectronics STMPE Interface Drivers"
895 bool "STMicroelectronics STMPE I2C Interface"
899 This is used to enable I2C interface of STMPE
902 bool "STMicroelectronics STMPE SPI Interface"
903 depends on SPI_MASTER
905 This is used to enable SPI interface of STMPE
909 bool "STMicroelectronics STA2X11"
914 config MFD_SUN6I_PRCM
915 bool "Allwinner A31 PRCM controller"
916 depends on ARCH_SUNXI
919 Support for the PRCM (Power/Reset/Clock Management) unit available
923 bool "System Controller Register R/W Based on Regmap"
926 Select this option to enable accessing system control registers
929 config MFD_DAVINCI_VOICECODEC
934 config MFD_TI_AM335X_TSCADC
935 tristate "TI ADC / Touch Screen chip support"
940 If you say yes here you get support for Texas Instruments series
941 of Touch Screen /ADC chips.
942 To compile this driver as a module, choose M here: the
943 module will be called ti_am335x_tscadc.
945 config MFD_DM355EVM_MSP
946 bool "TI DaVinci DM355 EVM microcontroller"
947 depends on I2C=y && MACH_DAVINCI_DM355_EVM
949 This driver supports the MSP430 microcontroller used on these
950 boards. MSP430 firmware manages resets and power sequencing,
951 inputs from buttons and the IR remote, LEDs, an RTC, and more.
954 tristate "TI/National Semiconductor LP3943 MFD Driver"
959 Support for the TI/National Semiconductor LP3943.
960 This driver consists of GPIO and PWM drivers.
961 With these functionalities, it can be used for LED string control or
962 general usage such like a GPIO controller and a PWM controller.
965 bool "TI LP8788 Power Management Unit Driver"
971 TI LP8788 PMU supports regulators, battery charger, RTC,
972 ADC, backlight driver and current sinks.
974 config MFD_OMAP_USB_HOST
975 bool "TI OMAP USBHS core and TLL driver"
976 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
979 This is the core driver for the OAMP EHCI and OHCI drivers.
980 This MFD driver does the required setup functionalities for
981 OMAP USB Host drivers.
984 bool "TI Palmas series chips"
990 If you say yes here you get support for the Palmas
991 series of PMIC chips from Texas Instruments.
994 tristate "TI TPS61050/61052 Boost Converters"
998 select REGULATOR_FIXED_VOLTAGE
1000 This option enables a driver for the TP61050/TPS61052
1001 high-power "white LED driver". This boost converter is
1002 sometimes used for other things than white LEDs, and
1003 also contains a GPIO pin.
1006 tristate "TI TPS6501x Power Management chips"
1007 depends on I2C && GPIOLIB
1008 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1010 If you say yes here you get support for the TPS6501x series of
1011 Power Management chips. These include voltage regulators,
1012 lithium ion/polymer battery charging, and other features that
1013 are often used in portable devices like cell phones and cameras.
1015 This driver can also be built as a module. If so, the module
1016 will be called tps65010.
1019 tristate "TI TPS6507x Power Management / Touch Screen chips"
1023 If you say yes here you get support for the TPS6507x series of
1024 Power Management / Touch Screen chips. These include voltage
1025 regulators, lithium ion/polymer battery charging, touch screen
1026 and other features that are often used in portable devices.
1027 This driver can also be built as a module. If so, the module
1028 will be called tps6507x.
1030 config TPS65911_COMPARATOR
1034 bool "TI TPS65090 Power Management chips"
1040 If you say yes here you get support for the TPS65090 series of
1041 Power Management chips.
1042 This driver provides common support for accessing the device,
1043 additional drivers must be enabled in order to use the
1044 functionality of the device.
1047 tristate "TI TPS65217 Power Management / White LED chips"
1052 If you say yes here you get support for the TPS65217 series of
1053 Power Management / White LED chips.
1054 These include voltage regulators, lithium ion/polymer battery
1055 charger, wled and other features that are often used in portable
1058 This driver can also be built as a module. If so, the module
1059 will be called tps65217.
1062 tristate "TI TPS65218 Power Management chips"
1068 If you say yes here you get support for the TPS65218 series of
1069 Power Management chips.
1070 These include voltage regulators, gpio and other features
1071 that are often used in portable devices. Only regulator
1072 component is currently supported.
1074 This driver can also be built as a module. If so, the module
1075 will be called tps65218.
1078 bool "TI TPS6586x Power Management chips"
1083 If you say yes here you get support for the TPS6586X series of
1084 Power Management chips.
1085 This driver provides common support for accessing the device,
1086 additional drivers must be enabled in order to use the
1087 functionality of the device.
1089 This driver can also be built as a module. If so, the module
1090 will be called tps6586x.
1093 bool "TI TPS65910 Power Management chip"
1094 depends on I2C=y && GPIOLIB
1100 if you say yes here you get support for the TPS65910 series of
1101 Power Management chips.
1104 bool "TI TPS65912 Power Management chip"
1108 If you say yes here you get support for the TPS65912 series of
1111 config MFD_TPS65912_I2C
1112 bool "TI TPS65912 Power Management chip with I2C"
1115 depends on I2C=y && GPIOLIB
1117 If you say yes here you get support for the TPS65912 series of
1118 PM chips with I2C interface.
1120 config MFD_TPS65912_SPI
1121 bool "TI TPS65912 Power Management chip with SPI"
1124 depends on SPI_MASTER && GPIOLIB
1126 If you say yes here you get support for the TPS65912 series of
1127 PM chips with SPI interface.
1130 bool "TI TPS80031/TPS80032 Power Management chips"
1136 If you say yes here you get support for the Texas Instruments
1137 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1138 Path and Battery Charger. The device provides five configurable
1139 step-down converters, 11 general purpose LDOs, USB OTG Module,
1140 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1141 Power Path from USB, 32K clock generator.
1144 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1149 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1150 This core driver provides register access and IRQ handling
1151 facilities, and registers devices for the various functions
1152 so that function-specific drivers can bind to them.
1154 These multi-function chips are found on many OMAP2 and OMAP3
1155 boards, providing power management, RTC, GPIO, keypad, a
1156 high speed USB OTG transceiver, an audio codec (on most
1157 versions) and many other features.
1159 config TWL4030_POWER
1160 bool "TI TWL4030 power resources"
1161 depends on TWL4030_CORE && ARM
1163 Say yes here if you want to use the power resources on the
1164 TWL4030 family chips. Most of these resources are regulators,
1165 which have a separate driver; some are control signals, such
1166 as clock request handshaking.
1168 This driver uses board-specific data to initialize the resources
1169 and load scripts controlling which resources are switched off/on
1170 or reset when a sleep, wakeup or warm reset event occurs.
1172 config MFD_TWL4030_AUDIO
1173 bool "TI TWL4030 Audio"
1174 depends on TWL4030_CORE
1179 bool "TI TWL6040 audio codec"
1186 Say yes here if you want support for Texas Instruments TWL6040 audio
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 (audio, vibra).
1193 bool "TI TWL92330/Menelaus PM chip"
1194 depends on I2C=y && ARCH_OMAP2
1196 If you say yes here you get support for the Texas Instruments
1197 TWL92330/Menelaus Power Management chip. This include voltage
1198 regulators, Dual slot memory card transceivers, real-time clock
1199 and other features that are often used in portable devices like
1200 cell phones and PDAs.
1202 config MFD_WL1273_CORE
1203 tristate "TI WL1273 FM radio"
1208 This is the core driver for the TI WL1273 FM radio. This MFD
1209 driver connects the radio-wl1273 V4L2 module and the wl1273
1213 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1218 Say yes here to enable support for National Semiconductor / TI
1219 LM3533 Lighting Power chips.
1221 This driver provides common support for accessing the device;
1222 additional drivers must be enabled in order to use the LED,
1223 backlight or ambient-light-sensor functionality of the device.
1225 config MFD_TIMBERDALE
1226 tristate "Timberdale FPGA"
1228 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1230 This is the core driver for the timberdale FPGA. This device is a
1231 multifunction device which exposes numerous platform devices.
1233 The timberdale FPGA can be found on the Intel Atom development board
1234 for in-vehicle infontainment, called Russellville.
1237 bool "Toshiba TC35892 and variants"
1241 Support for the Toshiba TC35892 and variants I/O Expander.
1243 This driver provides common support for accessing the device,
1244 additional drivers must be enabled in order to use the
1245 functionality of the device.
1252 bool "Toshiba T7L66XB"
1253 depends on ARM && HAVE_CLK
1257 Support for Toshiba Mobile IO Controller T7L66XB
1260 bool "Toshiba TC6387XB"
1261 depends on ARM && HAVE_CLK
1265 Support for Toshiba Mobile IO Controller TC6387XB
1268 bool "Toshiba TC6393XB"
1269 depends on ARM && HAVE_CLK
1274 Support for Toshiba Mobile IO Controller TC6393XB
1277 tristate "VIA VX855/VX875 integrated south bridge"
1281 Say yes here to enable support for various functions of the
1282 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1283 and/or vx855_gpio drivers for this to do anything useful.
1291 config MFD_ARIZONA_I2C
1292 tristate "Wolfson Microelectronics Arizona platform with I2C"
1298 Support for the Wolfson Microelectronics Arizona platform audio SoC
1299 core functionality controlled via I2C.
1301 config MFD_ARIZONA_SPI
1302 tristate "Wolfson Microelectronics Arizona platform with SPI"
1306 depends on SPI_MASTER
1308 Support for the Wolfson Microelectronics Arizona platform audio SoC
1309 core functionality controlled via I2C.
1312 bool "Wolfson Microelectronics WM5102"
1313 depends on MFD_ARIZONA
1315 Support for Wolfson Microelectronics WM5102 low power audio SoC
1318 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1319 depends on MFD_ARIZONA
1321 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1325 bool "Wolfson Microelectronics WM8997"
1326 depends on MFD_ARIZONA
1328 Support for Wolfson Microelectronics WM8997 low power audio SoC
1331 bool "Wolfson Microelectronics WM8400"
1336 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1337 CODEC. This driver provides common support for accessing
1338 the device, additional drivers must be enabled in order to use
1339 the functionality of the device.
1344 config MFD_WM831X_I2C
1345 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1352 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1353 when controlled using I2C. This driver provides common support
1354 for accessing the device, additional drivers must be enabled in
1355 order to use the functionality of the device.
1357 config MFD_WM831X_SPI
1358 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1363 depends on SPI_MASTER
1365 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1366 when controlled using SPI. This driver provides common support
1367 for accessing the device, additional drivers must be enabled in
1368 order to use the functionality of the device.
1373 config MFD_WM8350_I2C
1374 bool "Wolfson Microelectronics WM8350 with I2C"
1378 The WM8350 is an integrated audio and power management
1379 subsystem with watchdog and RTC functionality for embedded
1380 systems. This option enables core support for the WM8350 with
1381 I2C as the control interface. Additional options must be
1382 selected to enable support for the functionality of the chip.
1385 tristate "Wolfson Microelectronics WM8994"
1391 The WM8994 is a highly integrated hi-fi CODEC designed for
1392 smartphone applicatiosn. As well as audio functionality it
1393 has on board GPIO and regulator functionality which is
1394 supported via the relevant subsystems. This driver provides
1395 core support for the WM8994, in order to use the actual
1396 functionaltiy of the device other drivers must be enabled.
1399 tristate "Support for ST Microelectronics STw481x"
1400 depends on I2C && ARCH_NOMADIK
1404 Select this option to enable the STw481x chip driver used
1405 in various ST Microelectronics and ST-Ericsson embedded
1408 menu "Multimedia Capabilities Port drivers"
1409 depends on ARCH_SA1100
1416 tristate "Support SA11x0 MCP interface"
1417 depends on ARCH_SA1100
1422 tristate "Support for UCB1200 / UCB1300"
1423 depends on MCP_SA11X0
1426 config MCP_UCB1200_TS
1427 tristate "Touchscreen interface support"
1428 depends on MCP_UCB1200 && INPUT
1432 config MFD_VEXPRESS_SYSREG
1433 bool "Versatile Express System Registers"
1434 depends on VEXPRESS_CONFIG && GPIOLIB
1437 select GPIO_GENERIC_PLATFORM
1441 System Registers are the platform configuration block
1442 on the ARM Ltd. Versatile Express board.