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.
286 config MFD_INTEL_QUARK_I2C_GPIO
287 tristate "Intel Quark MFD I2C GPIO"
290 depends on COMMON_CLK
293 This MFD provides support for I2C and GPIO that exist only
294 in a single PCI device. It splits the 2 IO devices to
295 their respective IO driver.
296 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
299 tristate "Intel ICH LPC"
303 The LPC bridge function of the Intel ICH provides support for
304 many functional units. This driver provides needed support for
305 other drivers to control these functions, currently GPIO and
309 tristate "Intel SCH LPC"
313 LPC bridge function of the Intel SCH provides support for
314 System Management Bus and General Purpose I/O.
316 config INTEL_SOC_PMIC
317 bool "Support for Intel Atom SoC PMIC"
323 Select this option to enable support for the PMIC device
324 on some Intel SoC systems. The PMIC provides ADC, GPIO,
325 thermal, charger and related power management functions
328 config MFD_INTEL_MSIC
330 depends on INTEL_SCU_IPC
333 Select this option to enable access to Intel MSIC (Avatele
334 Passage) chip. This chip embeds audio, battery, GPIO, etc.
335 devices used in Intel Medfield platforms.
337 config MFD_IPAQ_MICRO
338 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
339 depends on SA1100_H3100 || SA1100_H3600
342 Select this to get support for the Microcontroller found in
343 the Compaq iPAQ handheld computers. This is an Atmel
344 AT90LS8535 microcontroller flashed with a special iPAQ
345 firmware using the custom protocol implemented in this driver.
347 config MFD_JANZ_CMODIO
348 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
352 This is the core driver for the Janz CMOD-IO PCI MODULbus
353 carrier board. This device is a PCI to MODULbus bridge which may
354 host many different types of MODULbus daughterboards, including
355 CAN and GPIO controllers.
357 config MFD_JZ4740_ADC
358 bool "Janz JZ4740 ADC core"
360 select GENERIC_IRQ_CHIP
361 depends on MACH_JZ4740
363 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
364 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
367 tristate "Kontron module PLD device"
370 This is the core driver for the PLD (Programmable Logic Device) found
371 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
372 device may provide functions like watchdog, GPIO, UART and I2C bus.
374 The following modules are supported:
377 * COMe-bPC2 (ETXexpress-PC)
378 * COMe-bSC# (ETXexpress-SC T#)
382 * COMe-cDC2 (microETXexpress-DC)
384 * COMe-cPC2 (microETXexpress-PC)
387 * COMe-mTT10 (nanoETXexpress-TT)
390 This driver can also be built as a module. If so, the module
391 will be called kempld-core.
394 tristate "Marvell 88PM800"
400 This supports for Marvell 88PM800 Power Management IC.
401 This includes the I2C driver and the core APIs _only_, you have to
402 select individual components like voltage regulators, RTC and
403 battery-charger under the corresponding menus.
406 tristate "Marvell 88PM805"
412 This supports for Marvell 88PM805 Power Management IC. This includes
413 the I2C driver and the core APIs _only_, you have to select individual
414 components like codec device, headset/Mic device under the
418 bool "Marvell 88PM8606/88PM8607"
423 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
424 This includes the I2C driver and the core APIs _only_, you have to
425 select individual components like voltage regulators, RTC and
426 battery-charger under the corresponding menus.
429 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
436 Say yes here to add support for Maxim Semiconductor MAX14577 and
437 MAX77836 Micro-USB ICs with battery charger.
438 This driver provides common support for accessing the device;
439 additional drivers must be enabled in order to use the functionality
443 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
451 Say yes here to add support for Maxim Semiconductor MAX77686 and
452 MAX77802 which are Power Management IC with an RTC on chip.
453 This driver provides common support for accessing the device;
454 additional drivers must be enabled in order to use the functionality
458 bool "Maxim Semiconductor MAX77693 PMIC Support"
464 Say yes here to add support for Maxim Semiconductor MAX77693.
465 This is a companion Power Management IC with Flash, Haptic, Charger,
466 and MUIC(Micro USB Interface Controller) controls on chip.
467 This driver provides common support for accessing the device;
468 additional drivers must be enabled in order to use the functionality
472 bool "Maxim Semiconductor MAX77843 PMIC Support"
478 Say yes here to add support for Maxim Semiconductor MAX77843.
479 This is companion Power Management IC with LEDs, Haptic, Charger,
480 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
481 This driver provides common support for accessing the device;
482 additional drivers must be enabled in order to use the functionality
486 tristate "Maxim Semiconductor MAX8907 PMIC Support"
492 Say yes here to add support for Maxim Semiconductor MAX8907. This is
493 a Power Management IC. This driver provides common support for
494 accessing the device; additional drivers must be enabled in order
495 to use the functionality of the device.
498 bool "Maxim Semiconductor MAX8925 PMIC Support"
502 Say yes here to add support for Maxim Semiconductor MAX8925. This is
503 a Power Management IC. This driver provides common support for
504 accessing the device, additional drivers must be enabled in order
505 to use the functionality of the device.
508 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
513 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
514 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
515 MUIC controls on chip.
516 This driver provides common support for accessing the device;
517 additional drivers must be enabled in order to use the functionality
521 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
526 Say yes here to add support for Maxim Semiconductor MAX8998 and
527 National Semiconductor LP3974. This is a Power Management IC.
528 This driver provides common support for accessing the device,
529 additional drivers must be enabled in order to use the functionality
533 tristate "MediaTek MT6397 PMIC Support"
537 Say yes here to add support for MediaTek MT6397 PMIC. This is
538 a Power Management IC. This driver provides common support for
539 accessing the device; additional drivers must be enabled in order
540 to use the functionality of the device.
543 tristate "MEN 14F021P00 Board Management Controller Support"
547 Say yes here to add support for the MEN 14F021P00 BMC
548 which is a Board Management Controller connected to the I2C bus.
549 The device supports multiple sub-devices like LED, HWMON and WDT.
550 This driver provides common support for accessing the devices;
551 additional drivers must be enabled in order to use the
552 functionality of the BMC device.
554 This driver can also be built as a module. If so the module
555 will be called menf21bmc.
558 bool "Motorola EZXPCAP Support"
559 depends on SPI_MASTER
561 This enables the PCAP ASIC present on EZX Phones. This is
562 needed for MMC, TouchScreen, Sound, USB, etc..
564 config MFD_VIPERBOARD
565 tristate "Nano River Technologies Viperboard"
570 Say yes here if you want support for Nano River Technologies
572 There are mfd cell drivers available for i2c master, adc and
573 both gpios found on the board. The spi part does not yet
575 You need to select the mfd cell drivers separately.
576 The drivers do not support all features the board exposes.
579 tristate "Nokia Retu and Tahvo multi-function device"
584 Retu and Tahvo are a multi-function devices found on Nokia
585 Internet Tablets (770, N800 and N810).
588 tristate "NXP PCF50633"
592 Say yes here if you have NXP PCF50633 chip on your board.
593 This core driver provides register access and IRQ handling
594 facilities, and registers devices for the various functions
595 so that function-specific drivers can bind to them.
598 tristate "NXP PCF50633 ADC"
599 depends on MFD_PCF50633
601 Say yes here if you want to include support for ADC in the
605 tristate "NXP PCF50633 GPIO"
606 depends on MFD_PCF50633
608 Say yes here if you want to include support GPIO for pins on
612 tristate "Philips UCB1400 Core driver"
616 This enables support for the Philips UCB1400 core functions.
617 The UCB1400 is an AC97 audio codec.
619 To compile this driver as a module, choose M here: the
620 module will be called ucb1400_core.
625 config MFD_PM8921_CORE
626 tristate "Qualcomm PM8921 PMIC chip"
627 depends on (ARM || HEXAGON)
633 If you say yes to this option, support will be included for the
634 built-in PM8921 PMIC chip.
636 This is required if your board has a PM8921 and uses its features,
637 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
639 Say M here if you want to include support for PM8921 chip as a module.
640 This will build a module called "pm8921-core".
643 tristate "Qualcomm Resource Power Manager (RPM)"
644 depends on ARCH_QCOM && OF
646 If you say yes to this option, support will be included for the
647 Resource Power Manager system found in the Qualcomm 8660, 8960 and
650 This is required to access many regulators, clocks and bus
651 frequencies controlled by the RPM on these devices.
653 Say M here if you want to include support for the Qualcomm RPM as a
654 module. This will build a module called "qcom_rpm".
657 tristate "Qualcomm SPMI PMICs"
658 depends on ARCH_QCOM || COMPILE_TEST
663 This enables support for the Qualcomm SPMI PMICs.
664 These PMICs are currently used with the Snapdragon 800 series of
665 SoCs. Note, that this will only be useful paired with descriptions
666 of the independent functions as children nodes in the device tree.
668 Say M here if you want to include support for the SPMI PMIC
669 series as a module. The module will be called "qcom-spmi-pmic".
672 tristate "RDC R-321x southbridge"
676 Say yes here if you want to have support for the RDC R-321x SoC
677 southbridge which provides access to GPIOs and Watchdog using the
678 southbridge PCI device configuration space.
681 tristate "Realtek PCI-E card reader"
685 This supports for Realtek PCI-Express card reader including rts5209,
686 rts5229, rtl8411, etc. Realtek card reader supports access to many
687 types of memory cards, such as Memory Stick, Memory Stick Pro,
688 Secure Digital and MultiMediaCard.
691 tristate "Richtek RT5033 Power Management IC"
697 This driver provides for the Richtek RT5033 Power Management IC,
698 which includes the I2C driver and the Core APIs. This driver provides
699 common support for accessing the device. The device supports multiple
700 sub-devices like charger, fuel gauge, flash LED, current source,
704 tristate "Realtek USB card reader"
708 Select this option to get support for Realtek USB 2.0 card readers
709 including RTS5129, RTS5139, RTS5179 and RTS5170.
710 Realtek card reader supports access to many types of memory cards,
711 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
714 bool "Ricoh RC5T583 Power Management system device"
719 Select this option to get support for the RICOH583 Power
720 Management system device.
721 This driver provides common support for accessing the device
722 through i2c interface. The device supports multiple sub-devices
723 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
724 Additional drivers must be enabled in order to use the
725 different functionality of the device.
728 tristate "Rockchip RK808 Power Management chip"
734 If you say yes here you get support for the RK808
735 Power Management chips.
736 This driver provides common support for accessing the device
737 through I2C interface. The device supports multiple sub-devices
738 including interrupts, RTC, LDO & DCDC regulators, and onkey.
741 tristate "Ricoh RN5T5618 PMIC"
746 Say yes here to add support for the Ricoh RN5T618 PMIC. This
747 driver provides common support for accessing the device,
748 additional drivers must be enabled in order to use the
749 functionality of the device.
752 bool "SAMSUNG Electronics PMIC Series Support"
758 Support for the Samsung Electronics MFD series.
759 This driver provides common support for accessing the device,
760 additional drivers must be enabled in order to use the functionality
763 config MFD_SI476X_CORE
764 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
769 This is the core driver for the SI476x series of AM/FM
770 radio. This MFD driver connects the radio-si476x V4L2 module
771 and the si476x audio codec.
773 To compile this driver as a module, choose M here: the
774 module will be called si476x-core.
777 tristate "Silicon Motion SM501"
779 This is the core driver for the Silicon Motion SM501 multimedia
780 companion chip. This device is a multifunction device which may
781 provide numerous interfaces including USB host controller, USB gadget,
782 asynchronous serial ports, audio functions, and a dual display video
783 interface. The device may be connected by PCI or local bus with
784 varying functions enabled.
786 config MFD_SM501_GPIO
787 bool "Export GPIO via GPIO layer"
788 depends on MFD_SM501 && GPIOLIB
790 This option uses the gpio library layer to export the 64 GPIO
791 lines on the SM501. The platform data is used to supply the
792 base number for the first GPIO line to register.
795 bool "SMSC ECE1099 series chips"
800 If you say yes here you get support for the
801 ece1099 chips from SMSC.
803 To compile this driver as a module, choose M here: the
804 module will be called smsc.
807 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
808 default y if ARCH_U300 || ARCH_U8500
810 Say yes here if you have the ABX500 Mixed Signal IC family
811 chips. This core driver expose register access functions.
812 Functionality specific drivers using these functions can
813 remain unchanged when IC changes. Binding of the functions to
814 actual register access is done by the IC core driver.
817 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
818 depends on I2C=y && ABX500_CORE
820 default y if ARCH_U300
822 Select this to enable the AB3100 Mixed Signal IC core
823 functionality. This connects to a AB3100 on the I2C bus
824 and expose a number of symbols needed for dependent devices
825 to read and write registers and subscribe to events from
826 this multi-functional IC. This is needed to use other features
827 of the AB3100 such as battery-backed RTC, charging control,
828 LEDs, vibrator, system power and temperature, power management
832 tristate "ST-Ericsson AB3100 OTP functions"
833 depends on AB3100_CORE
834 default y if AB3100_CORE
836 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
837 programmable memory) support. This exposes a sysfs file to read
841 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
842 depends on ABX500_CORE && MFD_DB8500_PRCMU
847 Select this option to enable access to AB8500 power management
848 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
849 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
850 the irq_chip parts for handling the Mixed Signal chip events.
851 This chip embeds various other multimedia funtionalities as well.
854 bool "Enable debug info via debugfs"
855 depends on AB8500_GPADC && DEBUG_FS
856 default y if DEBUG_FS
858 Select this option if you want debug information using the debug
862 bool "ST-Ericsson AB8500 GPADC driver"
863 depends on AB8500_CORE && REGULATOR_AB8500
866 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
868 config MFD_DB8500_PRCMU
869 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
870 depends on UX500_SOC_DB8500
873 Select this option to enable support for the DB8500 Power Reset
874 and Control Management Unit. This is basically an autonomous
875 system controller running an XP70 microprocessor, which is accessed
876 through a register map.
879 bool "STMicroelectronics STMPE"
880 depends on (I2C=y || SPI_MASTER=y)
884 Support for the STMPE family of I/O Expanders from
887 Currently supported devices are:
889 STMPE811: GPIO, Touchscreen
890 STMPE1601: GPIO, Keypad
891 STMPE1801: GPIO, Keypad
892 STMPE2401: GPIO, Keypad
893 STMPE2403: GPIO, Keypad
895 This driver provides common support for accessing the device,
896 additional drivers must be enabled in order to use the functionality
897 of the device. Currently available sub drivers are:
901 Touchscreen: stmpe-ts
903 menu "STMicroelectronics STMPE Interface Drivers"
907 bool "STMicroelectronics STMPE I2C Interface"
911 This is used to enable I2C interface of STMPE
914 bool "STMicroelectronics STMPE SPI Interface"
915 depends on SPI_MASTER
917 This is used to enable SPI interface of STMPE
921 bool "STMicroelectronics STA2X11"
926 config MFD_SUN6I_PRCM
927 bool "Allwinner A31 PRCM controller"
928 depends on ARCH_SUNXI
931 Support for the PRCM (Power/Reset/Clock Management) unit available
935 bool "System Controller Register R/W Based on Regmap"
938 Select this option to enable accessing system control registers
941 config MFD_DAVINCI_VOICECODEC
946 config MFD_TI_AM335X_TSCADC
947 tristate "TI ADC / Touch Screen chip support"
952 If you say yes here you get support for Texas Instruments series
953 of Touch Screen /ADC chips.
954 To compile this driver as a module, choose M here: the
955 module will be called ti_am335x_tscadc.
957 config MFD_DM355EVM_MSP
958 bool "TI DaVinci DM355 EVM microcontroller"
959 depends on I2C=y && MACH_DAVINCI_DM355_EVM
961 This driver supports the MSP430 microcontroller used on these
962 boards. MSP430 firmware manages resets and power sequencing,
963 inputs from buttons and the IR remote, LEDs, an RTC, and more.
966 tristate "TI/National Semiconductor LP3943 MFD Driver"
971 Support for the TI/National Semiconductor LP3943.
972 This driver consists of GPIO and PWM drivers.
973 With these functionalities, it can be used for LED string control or
974 general usage such like a GPIO controller and a PWM controller.
977 bool "TI LP8788 Power Management Unit Driver"
983 TI LP8788 PMU supports regulators, battery charger, RTC,
984 ADC, backlight driver and current sinks.
986 config MFD_OMAP_USB_HOST
987 bool "TI OMAP USBHS core and TLL driver"
988 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
991 This is the core driver for the OAMP EHCI and OHCI drivers.
992 This MFD driver does the required setup functionalities for
993 OMAP USB Host drivers.
996 bool "TI Palmas series chips"
1002 If you say yes here you get support for the Palmas
1003 series of PMIC chips from Texas Instruments.
1006 tristate "TI TPS61050/61052 Boost Converters"
1010 select REGULATOR_FIXED_VOLTAGE
1012 This option enables a driver for the TP61050/TPS61052
1013 high-power "white LED driver". This boost converter is
1014 sometimes used for other things than white LEDs, and
1015 also contains a GPIO pin.
1018 tristate "TI TPS6501x Power Management chips"
1019 depends on I2C && GPIOLIB
1020 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1022 If you say yes here you get support for the TPS6501x series of
1023 Power Management chips. These include voltage regulators,
1024 lithium ion/polymer battery charging, and other features that
1025 are often used in portable devices like cell phones and cameras.
1027 This driver can also be built as a module. If so, the module
1028 will be called tps65010.
1031 tristate "TI TPS6507x Power Management / Touch Screen chips"
1035 If you say yes here you get support for the TPS6507x series of
1036 Power Management / Touch Screen chips. These include voltage
1037 regulators, lithium ion/polymer battery charging, touch screen
1038 and other features that are often used in portable devices.
1039 This driver can also be built as a module. If so, the module
1040 will be called tps6507x.
1042 config TPS65911_COMPARATOR
1046 bool "TI TPS65090 Power Management chips"
1052 If you say yes here you get support for the TPS65090 series of
1053 Power Management chips.
1054 This driver provides common support for accessing the device,
1055 additional drivers must be enabled in order to use the
1056 functionality of the device.
1059 tristate "TI TPS65217 Power Management / White LED chips"
1064 If you say yes here you get support for the TPS65217 series of
1065 Power Management / White LED chips.
1066 These include voltage regulators, lithium ion/polymer battery
1067 charger, wled and other features that are often used in portable
1070 This driver can also be built as a module. If so, the module
1071 will be called tps65217.
1074 tristate "TI TPS65218 Power Management chips"
1080 If you say yes here you get support for the TPS65218 series of
1081 Power Management chips.
1082 These include voltage regulators, gpio and other features
1083 that are often used in portable devices. Only regulator
1084 component is currently supported.
1086 This driver can also be built as a module. If so, the module
1087 will be called tps65218.
1090 bool "TI TPS6586x Power Management chips"
1095 If you say yes here you get support for the TPS6586X series of
1096 Power Management chips.
1097 This driver provides common support for accessing the device,
1098 additional drivers must be enabled in order to use the
1099 functionality of the device.
1101 This driver can also be built as a module. If so, the module
1102 will be called tps6586x.
1105 bool "TI TPS65910 Power Management chip"
1106 depends on I2C=y && GPIOLIB
1112 if you say yes here you get support for the TPS65910 series of
1113 Power Management chips.
1116 bool "TI TPS65912 Power Management chip"
1120 If you say yes here you get support for the TPS65912 series of
1123 config MFD_TPS65912_I2C
1124 bool "TI TPS65912 Power Management chip with I2C"
1127 depends on I2C=y && GPIOLIB
1129 If you say yes here you get support for the TPS65912 series of
1130 PM chips with I2C interface.
1132 config MFD_TPS65912_SPI
1133 bool "TI TPS65912 Power Management chip with SPI"
1136 depends on SPI_MASTER && GPIOLIB
1138 If you say yes here you get support for the TPS65912 series of
1139 PM chips with SPI interface.
1142 bool "TI TPS80031/TPS80032 Power Management chips"
1148 If you say yes here you get support for the Texas Instruments
1149 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1150 Path and Battery Charger. The device provides five configurable
1151 step-down converters, 11 general purpose LDOs, USB OTG Module,
1152 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1153 Power Path from USB, 32K clock generator.
1156 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1161 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1162 This core driver provides register access and IRQ handling
1163 facilities, and registers devices for the various functions
1164 so that function-specific drivers can bind to them.
1166 These multi-function chips are found on many OMAP2 and OMAP3
1167 boards, providing power management, RTC, GPIO, keypad, a
1168 high speed USB OTG transceiver, an audio codec (on most
1169 versions) and many other features.
1171 config TWL4030_POWER
1172 bool "TI TWL4030 power resources"
1173 depends on TWL4030_CORE && ARM
1175 Say yes here if you want to use the power resources on the
1176 TWL4030 family chips. Most of these resources are regulators,
1177 which have a separate driver; some are control signals, such
1178 as clock request handshaking.
1180 This driver uses board-specific data to initialize the resources
1181 and load scripts controlling which resources are switched off/on
1182 or reset when a sleep, wakeup or warm reset event occurs.
1184 config MFD_TWL4030_AUDIO
1185 bool "TI TWL4030 Audio"
1186 depends on TWL4030_CORE
1191 bool "TI TWL6040 audio codec"
1198 Say yes here if you want support for Texas Instruments TWL6040 audio
1200 This driver provides common support for accessing the device,
1201 additional drivers must be enabled in order to use the
1202 functionality of the device (audio, vibra).
1205 bool "TI TWL92330/Menelaus PM chip"
1206 depends on I2C=y && ARCH_OMAP2
1208 If you say yes here you get support for the Texas Instruments
1209 TWL92330/Menelaus Power Management chip. This include voltage
1210 regulators, Dual slot memory card transceivers, real-time clock
1211 and other features that are often used in portable devices like
1212 cell phones and PDAs.
1214 config MFD_WL1273_CORE
1215 tristate "TI WL1273 FM radio"
1220 This is the core driver for the TI WL1273 FM radio. This MFD
1221 driver connects the radio-wl1273 V4L2 module and the wl1273
1225 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1230 Say yes here to enable support for National Semiconductor / TI
1231 LM3533 Lighting Power chips.
1233 This driver provides common support for accessing the device;
1234 additional drivers must be enabled in order to use the LED,
1235 backlight or ambient-light-sensor functionality of the device.
1237 config MFD_TIMBERDALE
1238 tristate "Timberdale FPGA"
1240 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1242 This is the core driver for the timberdale FPGA. This device is a
1243 multifunction device which exposes numerous platform devices.
1245 The timberdale FPGA can be found on the Intel Atom development board
1246 for in-vehicle infontainment, called Russellville.
1249 bool "Toshiba TC35892 and variants"
1253 Support for the Toshiba TC35892 and variants I/O Expander.
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.
1264 bool "Toshiba T7L66XB"
1265 depends on ARM && HAVE_CLK
1269 Support for Toshiba Mobile IO Controller T7L66XB
1272 bool "Toshiba TC6387XB"
1273 depends on ARM && HAVE_CLK
1277 Support for Toshiba Mobile IO Controller TC6387XB
1280 bool "Toshiba TC6393XB"
1281 depends on ARM && HAVE_CLK
1286 Support for Toshiba Mobile IO Controller TC6393XB
1289 tristate "VIA VX855/VX875 integrated south bridge"
1293 Say yes here to enable support for various functions of the
1294 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1295 and/or vx855_gpio drivers for this to do anything useful.
1303 config MFD_ARIZONA_I2C
1304 tristate "Wolfson Microelectronics Arizona platform with I2C"
1310 Support for the Wolfson Microelectronics Arizona platform audio SoC
1311 core functionality controlled via I2C.
1313 config MFD_ARIZONA_SPI
1314 tristate "Wolfson Microelectronics Arizona platform with SPI"
1318 depends on SPI_MASTER
1320 Support for the Wolfson Microelectronics Arizona platform audio SoC
1321 core functionality controlled via I2C.
1324 bool "Wolfson Microelectronics WM5102"
1325 depends on MFD_ARIZONA
1327 Support for Wolfson Microelectronics WM5102 low power audio SoC
1330 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1331 depends on MFD_ARIZONA
1333 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1337 bool "Wolfson Microelectronics WM8997"
1338 depends on MFD_ARIZONA
1340 Support for Wolfson Microelectronics WM8997 low power audio SoC
1343 bool "Wolfson Microelectronics WM8400"
1348 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1349 CODEC. This driver provides common support for accessing
1350 the device, additional drivers must be enabled in order to use
1351 the functionality of the device.
1356 config MFD_WM831X_I2C
1357 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1364 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1365 when controlled using I2C. This driver provides common support
1366 for accessing the device, additional drivers must be enabled in
1367 order to use the functionality of the device.
1369 config MFD_WM831X_SPI
1370 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1375 depends on SPI_MASTER
1377 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1378 when controlled using SPI. This driver provides common support
1379 for accessing the device, additional drivers must be enabled in
1380 order to use the functionality of the device.
1385 config MFD_WM8350_I2C
1386 bool "Wolfson Microelectronics WM8350 with I2C"
1390 The WM8350 is an integrated audio and power management
1391 subsystem with watchdog and RTC functionality for embedded
1392 systems. This option enables core support for the WM8350 with
1393 I2C as the control interface. Additional options must be
1394 selected to enable support for the functionality of the chip.
1397 tristate "Wolfson Microelectronics WM8994"
1403 The WM8994 is a highly integrated hi-fi CODEC designed for
1404 smartphone applicatiosn. As well as audio functionality it
1405 has on board GPIO and regulator functionality which is
1406 supported via the relevant subsystems. This driver provides
1407 core support for the WM8994, in order to use the actual
1408 functionaltiy of the device other drivers must be enabled.
1411 tristate "Support for ST Microelectronics STw481x"
1412 depends on I2C && ARCH_NOMADIK
1416 Select this option to enable the STw481x chip driver used
1417 in various ST Microelectronics and ST-Ericsson embedded
1420 menu "Multimedia Capabilities Port drivers"
1421 depends on ARCH_SA1100
1428 tristate "Support SA11x0 MCP interface"
1429 depends on ARCH_SA1100
1434 tristate "Support for UCB1200 / UCB1300"
1435 depends on MCP_SA11X0
1438 config MCP_UCB1200_TS
1439 tristate "Touchscreen interface support"
1440 depends on MCP_UCB1200 && INPUT
1444 config MFD_VEXPRESS_SYSREG
1445 bool "Versatile Express System Registers"
1446 depends on VEXPRESS_CONFIG && GPIOLIB
1449 select GPIO_GENERIC_PLATFORM
1453 System Registers are the platform configuration block
1454 on the ARM Ltd. Versatile Express board.