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.
63 tristate "Broadcom BCM590xx PMUs"
68 Support for the BCM590xx PMUs from Broadcom
71 bool "X-Powers AXP20X"
77 If you say Y here you get support for the X-Powers AXP202, AXP209 and
78 AXP288 power management IC (PMIC).
79 This driver include only the core APIs. You have to select individual
80 components like regulators or the PEK (Power Enable Key) under the
84 tristate "ChromeOS Embedded Controller"
87 If you say Y here you get support for the ChromeOS Embedded
88 Controller (EC) providing keyboard, battery and power services.
89 You also need to enable the driver for the bus you are using. The
90 protocol for talking to the EC is defined by the bus driver.
92 config MFD_CROS_EC_I2C
93 tristate "ChromeOS Embedded Controller (I2C)"
94 depends on MFD_CROS_EC && I2C
97 If you say Y here, you get support for talking to the ChromeOS
98 EC through an I2C bus. This uses a simple byte-level protocol with
99 a checksum. Failing accesses will be retried three times to
102 config MFD_CROS_EC_SPI
103 tristate "ChromeOS Embedded Controller (SPI)"
104 depends on MFD_CROS_EC && SPI && OF
107 If you say Y here, you get support for talking to the ChromeOS EC
108 through a SPI bus, using a byte-level protocol. Since the EC's
109 response time cannot be guaranteed, we support ignoring
110 'pre-amble' bytes before the response actually starts.
114 depends on GPIOLIB && ARM
117 This driver supports the ASIC3 multifunction chip found on many
118 PDAs (mainly iPAQ and HTC based ones)
121 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
124 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
125 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
126 usually found on PXA processors-based platforms. This includes
127 the I2C driver and the core APIs _only_, you have to select
128 individual components like LCD backlight, voltage regulators,
129 LEDs and battery-charger under the corresponding menus.
135 config MFD_DA9052_SPI
136 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
140 depends on SPI_MASTER=y
142 Support for the Dialog Semiconductor DA9052 PMIC
143 when controlled using SPI. This driver provides common support
144 for accessing the device, additional drivers must be enabled in
145 order to use the functionality of the device.
147 config MFD_DA9052_I2C
148 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
154 Support for the Dialog Semiconductor DA9052 PMIC
155 when controlled using I2C. This driver provides common support
156 for accessing the device, additional drivers must be enabled in
157 order to use the functionality of the device.
160 bool "Dialog Semiconductor DA9055 PMIC Support"
166 Say yes here for support of Dialog Semiconductor DA9055. This is
167 a Power Management IC. This driver provides common support for
168 accessing the device as well as the I2C interface to the chip itself.
169 Additional drivers must be enabled in order to use the functionality
172 This driver can be built as a module. If built as a module it will be
176 bool "Dialog Semiconductor DA9063 PMIC Support"
182 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
183 This includes the I2C driver and core APIs.
184 Additional drivers must be enabled in order to use the functionality
188 tristate "Diolan DLN2 support"
192 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
193 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
194 etc. must be enabled in order to use the functionality of
199 depends on (SPI_MASTER || I2C)
203 Enable support for the Freescale MC13783 and MC13892 PMICs.
204 This driver provides common support for accessing the device,
205 additional drivers must be enabled in order to use the
206 functionality of the device.
208 config MFD_MC13XXX_SPI
209 tristate "Freescale MC13783 and MC13892 SPI interface"
210 depends on SPI_MASTER
214 Select this if your MC13xxx is connected via an SPI bus.
216 config MFD_MC13XXX_I2C
217 tristate "Freescale MC13892 I2C interface"
222 Select this if your MC13xxx is connected via an I2C bus.
224 config MFD_HI6421_PMIC
225 tristate "HiSilicon Hi6421 PMU/Codec IC"
230 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
231 functions, such as regulators, RTC, codec, Coulomb counter, etc.
232 This driver includes core APIs _only_. You have to select
233 individul components like voltage regulators under corresponding
234 menus in order to enable them.
235 We communicate with the Hi6421 via memory-mapped I/O.
238 bool "HTC EGPIO support"
239 depends on GPIOLIB && ARM
241 This driver supports the CPLD egpio chip present on
242 several HTC phones. It provides basic support for input
243 pins, output pins, and irqs.
246 tristate "HTC PASIC3 LED/DS1WM chip support"
249 This core driver provides register access for the LED/DS1WM
250 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
251 HTC Magician devices, respectively. Actual functionality is
252 handled by the leds-pasic3 and ds1wm drivers.
255 bool "HTC I2C PLD chip support"
256 depends on I2C=y && GPIOLIB
258 If you say yes here you get support for the supposed CPLD
259 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
260 This device provides input and output GPIOs through an I2C
261 interface to one or more sub-chips.
264 tristate "Intel ICH LPC"
268 The LPC bridge function of the Intel ICH provides support for
269 many functional units. This driver provides needed support for
270 other drivers to control these functions, currently GPIO and
274 tristate "Intel SCH LPC"
278 LPC bridge function of the Intel SCH provides support for
279 System Management Bus and General Purpose I/O.
281 config INTEL_SOC_PMIC
282 bool "Support for Intel Atom SoC PMIC"
288 Select this option to enable support for the PMIC device
289 on some Intel SoC systems. The PMIC provides ADC, GPIO,
290 thermal, charger and related power management functions
293 config MFD_INTEL_MSIC
295 depends on INTEL_SCU_IPC
298 Select this option to enable access to Intel MSIC (Avatele
299 Passage) chip. This chip embeds audio, battery, GPIO, etc.
300 devices used in Intel Medfield platforms.
302 config MFD_IPAQ_MICRO
303 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
304 depends on SA1100_H3100 || SA1100_H3600
307 Select this to get support for the Microcontroller found in
308 the Compaq iPAQ handheld computers. This is an Atmel
309 AT90LS8535 microcontroller flashed with a special iPAQ
310 firmware using the custom protocol implemented in this driver.
312 config MFD_JANZ_CMODIO
313 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
317 This is the core driver for the Janz CMOD-IO PCI MODULbus
318 carrier board. This device is a PCI to MODULbus bridge which may
319 host many different types of MODULbus daughterboards, including
320 CAN and GPIO controllers.
322 config MFD_JZ4740_ADC
323 bool "Janz JZ4740 ADC core"
325 select GENERIC_IRQ_CHIP
326 depends on MACH_JZ4740
328 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
329 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
332 tristate "Kontron module PLD device"
335 This is the core driver for the PLD (Programmable Logic Device) found
336 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
337 device may provide functions like watchdog, GPIO, UART and I2C bus.
339 The following modules are supported:
342 * COMe-bPC2 (ETXexpress-PC)
343 * COMe-bSC# (ETXexpress-SC T#)
346 * COMe-cDC2 (microETXexpress-DC)
348 * COMe-cPC2 (microETXexpress-PC)
351 * COMe-mTT10 (nanoETXexpress-TT)
354 This driver can also be built as a module. If so, the module
355 will be called kempld-core.
358 tristate "Marvell 88PM800"
364 This supports for Marvell 88PM800 Power Management IC.
365 This includes the I2C driver and the core APIs _only_, you have to
366 select individual components like voltage regulators, RTC and
367 battery-charger under the corresponding menus.
370 tristate "Marvell 88PM805"
376 This supports for Marvell 88PM805 Power Management IC. This includes
377 the I2C driver and the core APIs _only_, you have to select individual
378 components like codec device, headset/Mic device under the
382 bool "Marvell 88PM8606/88PM8607"
387 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
388 This includes the I2C driver and the core APIs _only_, you have to
389 select individual components like voltage regulators, RTC and
390 battery-charger under the corresponding menus.
393 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
400 Say yes here to add support for Maxim Semiconductor MAX14577 and
401 MAX77836 Micro-USB ICs with battery charger.
402 This driver provides common support for accessing the device;
403 additional drivers must be enabled in order to use the functionality
407 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
414 Say yes here to add support for Maxim Semiconductor MAX77686 and
415 MAX77802 which are Power Management IC with an RTC on chip.
416 This driver provides common support for accessing the device;
417 additional drivers must be enabled in order to use the functionality
421 bool "Maxim Semiconductor MAX77693 PMIC Support"
427 Say yes here to add support for Maxim Semiconductor MAX77693.
428 This is a companion Power Management IC with Flash, Haptic, Charger,
429 and MUIC(Micro USB Interface Controller) controls on chip.
430 This driver provides common support for accessing the device;
431 additional drivers must be enabled in order to use the functionality
435 tristate "Maxim Semiconductor MAX8907 PMIC Support"
441 Say yes here to add support for Maxim Semiconductor MAX8907. This is
442 a Power Management IC. This driver provides common support for
443 accessing the device; additional drivers must be enabled in order
444 to use the functionality of the device.
447 bool "Maxim Semiconductor MAX8925 PMIC Support"
451 Say yes here to add support for Maxim Semiconductor MAX8925. This is
452 a Power Management IC. This driver provides common support for
453 accessing the device, additional drivers must be enabled in order
454 to use the functionality of the device.
457 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
462 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
463 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
464 MUIC controls on chip.
465 This driver provides common support for accessing the device;
466 additional drivers must be enabled in order to use the functionality
470 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
475 Say yes here to add support for Maxim Semiconductor MAX8998 and
476 National Semiconductor LP3974. This is a Power Management IC.
477 This driver provides common support for accessing the device,
478 additional drivers must be enabled in order to use the functionality
482 tristate "MEN 14F021P00 Board Management Controller Support"
486 Say yes here to add support for the MEN 14F021P00 BMC
487 which is a Board Management Controller connected to the I2C bus.
488 The device supports multiple sub-devices like LED, HWMON and WDT.
489 This driver provides common support for accessing the devices;
490 additional drivers must be enabled in order to use the
491 functionality of the BMC device.
493 This driver can also be built as a module. If so the module
494 will be called menf21bmc.
497 bool "Motorola EZXPCAP Support"
498 depends on SPI_MASTER
500 This enables the PCAP ASIC present on EZX Phones. This is
501 needed for MMC, TouchScreen, Sound, USB, etc..
503 config MFD_VIPERBOARD
504 tristate "Nano River Technologies Viperboard"
509 Say yes here if you want support for Nano River Technologies
511 There are mfd cell drivers available for i2c master, adc and
512 both gpios found on the board. The spi part does not yet
514 You need to select the mfd cell drivers separately.
515 The drivers do not support all features the board exposes.
518 tristate "Nokia Retu and Tahvo multi-function device"
523 Retu and Tahvo are a multi-function devices found on Nokia
524 Internet Tablets (770, N800 and N810).
527 tristate "NXP PCF50633"
531 Say yes here if you have NXP PCF50633 chip on your board.
532 This core driver provides register access and IRQ handling
533 facilities, and registers devices for the various functions
534 so that function-specific drivers can bind to them.
537 tristate "NXP PCF50633 ADC"
538 depends on MFD_PCF50633
540 Say yes here if you want to include support for ADC in the
544 tristate "NXP PCF50633 GPIO"
545 depends on MFD_PCF50633
547 Say yes here if you want to include support GPIO for pins on
551 tristate "Philips UCB1400 Core driver"
555 This enables support for the Philips UCB1400 core functions.
556 The UCB1400 is an AC97 audio codec.
558 To compile this driver as a module, choose M here: the
559 module will be called ucb1400_core.
564 config MFD_PM8921_CORE
565 tristate "Qualcomm PM8921 PMIC chip"
566 depends on (ARM || HEXAGON)
572 If you say yes to this option, support will be included for the
573 built-in PM8921 PMIC chip.
575 This is required if your board has a PM8921 and uses its features,
576 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
578 Say M here if you want to include support for PM8921 chip as a module.
579 This will build a module called "pm8921-core".
582 tristate "Qualcomm SPMI PMICs"
583 depends on ARCH_QCOM || COMPILE_TEST
588 This enables support for the Qualcomm SPMI PMICs.
589 These PMICs are currently used with the Snapdragon 800 series of
590 SoCs. Note, that this will only be useful paired with descriptions
591 of the independent functions as children nodes in the device tree.
593 Say M here if you want to include support for the SPMI PMIC
594 series as a module. The module will be called "qcom-spmi-pmic".
597 tristate "RDC R-321x southbridge"
601 Say yes here if you want to have support for the RDC R-321x SoC
602 southbridge which provides access to GPIOs and Watchdog using the
603 southbridge PCI device configuration space.
606 tristate "Realtek PCI-E card reader"
610 This supports for Realtek PCI-Express card reader including rts5209,
611 rts5229, rtl8411, etc. Realtek card reader supports access to many
612 types of memory cards, such as Memory Stick, Memory Stick Pro,
613 Secure Digital and MultiMediaCard.
616 tristate "Realtek USB card reader"
620 Select this option to get support for Realtek USB 2.0 card readers
621 including RTS5129, RTS5139, RTS5179 and RTS5170.
622 Realtek card reader supports access to many types of memory cards,
623 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
626 bool "Ricoh RC5T583 Power Management system device"
631 Select this option to get support for the RICOH583 Power
632 Management system device.
633 This driver provides common support for accessing the device
634 through i2c interface. The device supports multiple sub-devices
635 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
636 Additional drivers must be enabled in order to use the
637 different functionality of the device.
640 tristate "Rockchip RK808 Power Management chip"
646 If you say yes here you get support for the RK808
647 Power Management chips.
648 This driver provides common support for accessing the device
649 through I2C interface. The device supports multiple sub-devices
650 including interrupts, RTC, LDO & DCDC regulators, and onkey.
653 tristate "Ricoh RN5T5618 PMIC"
658 Say yes here to add support for the Ricoh RN5T618 PMIC. This
659 driver provides common support for accessing the device,
660 additional drivers must be enabled in order to use the
661 functionality of the device.
664 bool "SAMSUNG Electronics PMIC Series Support"
671 Support for the Samsung Electronics MFD series.
672 This driver provides common support for accessing the device,
673 additional drivers must be enabled in order to use the functionality
676 config MFD_SI476X_CORE
677 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
682 This is the core driver for the SI476x series of AM/FM
683 radio. This MFD driver connects the radio-si476x V4L2 module
684 and the si476x audio codec.
686 To compile this driver as a module, choose M here: the
687 module will be called si476x-core.
690 tristate "Silicon Motion SM501"
692 This is the core driver for the Silicon Motion SM501 multimedia
693 companion chip. This device is a multifunction device which may
694 provide numerous interfaces including USB host controller, USB gadget,
695 asynchronous serial ports, audio functions, and a dual display video
696 interface. The device may be connected by PCI or local bus with
697 varying functions enabled.
699 config MFD_SM501_GPIO
700 bool "Export GPIO via GPIO layer"
701 depends on MFD_SM501 && GPIOLIB
703 This option uses the gpio library layer to export the 64 GPIO
704 lines on the SM501. The platform data is used to supply the
705 base number for the first GPIO line to register.
708 bool "SMSC ECE1099 series chips"
713 If you say yes here you get support for the
714 ece1099 chips from SMSC.
716 To compile this driver as a module, choose M here: the
717 module will be called smsc.
720 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
721 default y if ARCH_U300 || ARCH_U8500
723 Say yes here if you have the ABX500 Mixed Signal IC family
724 chips. This core driver expose register access functions.
725 Functionality specific drivers using these functions can
726 remain unchanged when IC changes. Binding of the functions to
727 actual register access is done by the IC core driver.
730 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
731 depends on I2C=y && ABX500_CORE
733 default y if ARCH_U300
735 Select this to enable the AB3100 Mixed Signal IC core
736 functionality. This connects to a AB3100 on the I2C bus
737 and expose a number of symbols needed for dependent devices
738 to read and write registers and subscribe to events from
739 this multi-functional IC. This is needed to use other features
740 of the AB3100 such as battery-backed RTC, charging control,
741 LEDs, vibrator, system power and temperature, power management
745 tristate "ST-Ericsson AB3100 OTP functions"
746 depends on AB3100_CORE
747 default y if AB3100_CORE
749 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
750 programmable memory) support. This exposes a sysfs file to read
754 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
755 depends on ABX500_CORE && MFD_DB8500_PRCMU
760 Select this option to enable access to AB8500 power management
761 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
762 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
763 the irq_chip parts for handling the Mixed Signal chip events.
764 This chip embeds various other multimedia funtionalities as well.
767 bool "Enable debug info via debugfs"
768 depends on AB8500_GPADC && DEBUG_FS
769 default y if DEBUG_FS
771 Select this option if you want debug information using the debug
775 bool "ST-Ericsson AB8500 GPADC driver"
776 depends on AB8500_CORE && REGULATOR_AB8500
779 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
781 config MFD_DB8500_PRCMU
782 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
783 depends on UX500_SOC_DB8500
786 Select this option to enable support for the DB8500 Power Reset
787 and Control Management Unit. This is basically an autonomous
788 system controller running an XP70 microprocessor, which is accessed
789 through a register map.
792 bool "STMicroelectronics STMPE"
793 depends on (I2C=y || SPI_MASTER=y)
797 Support for the STMPE family of I/O Expanders from
800 Currently supported devices are:
802 STMPE811: GPIO, Touchscreen
803 STMPE1601: GPIO, Keypad
804 STMPE1801: GPIO, Keypad
805 STMPE2401: GPIO, Keypad
806 STMPE2403: GPIO, Keypad
808 This driver provides common support for accessing the device,
809 additional drivers must be enabled in order to use the functionality
810 of the device. Currently available sub drivers are:
814 Touchscreen: stmpe-ts
816 menu "STMicroelectronics STMPE Interface Drivers"
820 bool "STMicroelectronics STMPE I2C Interface"
824 This is used to enable I2C interface of STMPE
827 bool "STMicroelectronics STMPE SPI Interface"
828 depends on SPI_MASTER
830 This is used to enable SPI interface of STMPE
834 bool "STMicroelectronics STA2X11"
839 config MFD_SUN6I_PRCM
840 bool "Allwinner A31 PRCM controller"
841 depends on ARCH_SUNXI
844 Support for the PRCM (Power/Reset/Clock Management) unit available
848 bool "System Controller Register R/W Based on Regmap"
851 Select this option to enable accessing system control registers
854 config MFD_DAVINCI_VOICECODEC
859 config MFD_TI_AM335X_TSCADC
860 tristate "TI ADC / Touch Screen chip support"
865 If you say yes here you get support for Texas Instruments series
866 of Touch Screen /ADC chips.
867 To compile this driver as a module, choose M here: the
868 module will be called ti_am335x_tscadc.
870 config MFD_DM355EVM_MSP
871 bool "TI DaVinci DM355 EVM microcontroller"
872 depends on I2C=y && MACH_DAVINCI_DM355_EVM
874 This driver supports the MSP430 microcontroller used on these
875 boards. MSP430 firmware manages resets and power sequencing,
876 inputs from buttons and the IR remote, LEDs, an RTC, and more.
879 tristate "TI/National Semiconductor LP3943 MFD Driver"
884 Support for the TI/National Semiconductor LP3943.
885 This driver consists of GPIO and PWM drivers.
886 With these functionalities, it can be used for LED string control or
887 general usage such like a GPIO controller and a PWM controller.
890 bool "TI LP8788 Power Management Unit Driver"
896 TI LP8788 PMU supports regulators, battery charger, RTC,
897 ADC, backlight driver and current sinks.
899 config MFD_OMAP_USB_HOST
900 bool "TI OMAP USBHS core and TLL driver"
901 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
904 This is the core driver for the OAMP EHCI and OHCI drivers.
905 This MFD driver does the required setup functionalities for
906 OMAP USB Host drivers.
909 bool "TI Palmas series chips"
915 If you say yes here you get support for the Palmas
916 series of PMIC chips from Texas Instruments.
919 tristate "TI TPS61050/61052 Boost Converters"
923 select REGULATOR_FIXED_VOLTAGE
925 This option enables a driver for the TP61050/TPS61052
926 high-power "white LED driver". This boost converter is
927 sometimes used for other things than white LEDs, and
928 also contains a GPIO pin.
931 tristate "TI TPS6501x Power Management chips"
932 depends on I2C && GPIOLIB
933 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
935 If you say yes here you get support for the TPS6501x series of
936 Power Management chips. These include voltage regulators,
937 lithium ion/polymer battery charging, and other features that
938 are often used in portable devices like cell phones and cameras.
940 This driver can also be built as a module. If so, the module
941 will be called tps65010.
944 tristate "TI TPS6507x Power Management / Touch Screen chips"
948 If you say yes here you get support for the TPS6507x series of
949 Power Management / Touch Screen chips. These include voltage
950 regulators, lithium ion/polymer battery charging, touch screen
951 and other features that are often used in portable devices.
952 This driver can also be built as a module. If so, the module
953 will be called tps6507x.
955 config TPS65911_COMPARATOR
959 bool "TI TPS65090 Power Management chips"
965 If you say yes here you get support for the TPS65090 series of
966 Power Management chips.
967 This driver provides common support for accessing the device,
968 additional drivers must be enabled in order to use the
969 functionality of the device.
972 tristate "TI TPS65217 Power Management / White LED chips"
977 If you say yes here you get support for the TPS65217 series of
978 Power Management / White LED chips.
979 These include voltage regulators, lithium ion/polymer battery
980 charger, wled and other features that are often used in portable
983 This driver can also be built as a module. If so, the module
984 will be called tps65217.
987 tristate "TI TPS65218 Power Management chips"
993 If you say yes here you get support for the TPS65218 series of
994 Power Management chips.
995 These include voltage regulators, gpio and other features
996 that are often used in portable devices. Only regulator
997 component is currently supported.
999 This driver can also be built as a module. If so, the module
1000 will be called tps65218.
1003 bool "TI TPS6586x Power Management chips"
1008 If you say yes here you get support for the TPS6586X series of
1009 Power Management chips.
1010 This driver provides common support for accessing the device,
1011 additional drivers must be enabled in order to use the
1012 functionality of the device.
1014 This driver can also be built as a module. If so, the module
1015 will be called tps6586x.
1018 bool "TI TPS65910 Power Management chip"
1019 depends on I2C=y && GPIOLIB
1025 if you say yes here you get support for the TPS65910 series of
1026 Power Management chips.
1029 bool "TI TPS65912 Power Management chip"
1033 If you say yes here you get support for the TPS65912 series of
1036 config MFD_TPS65912_I2C
1037 bool "TI TPS65912 Power Management chip with I2C"
1040 depends on I2C=y && GPIOLIB
1042 If you say yes here you get support for the TPS65912 series of
1043 PM chips with I2C interface.
1045 config MFD_TPS65912_SPI
1046 bool "TI TPS65912 Power Management chip with SPI"
1049 depends on SPI_MASTER && GPIOLIB
1051 If you say yes here you get support for the TPS65912 series of
1052 PM chips with SPI interface.
1055 bool "TI TPS80031/TPS80032 Power Management chips"
1061 If you say yes here you get support for the Texas Instruments
1062 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1063 Path and Battery Charger. The device provides five configurable
1064 step-down converters, 11 general purpose LDOs, USB OTG Module,
1065 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1066 Power Path from USB, 32K clock generator.
1069 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1074 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1075 This core driver provides register access and IRQ handling
1076 facilities, and registers devices for the various functions
1077 so that function-specific drivers can bind to them.
1079 These multi-function chips are found on many OMAP2 and OMAP3
1080 boards, providing power management, RTC, GPIO, keypad, a
1081 high speed USB OTG transceiver, an audio codec (on most
1082 versions) and many other features.
1084 config TWL4030_POWER
1085 bool "TI TWL4030 power resources"
1086 depends on TWL4030_CORE && ARM
1088 Say yes here if you want to use the power resources on the
1089 TWL4030 family chips. Most of these resources are regulators,
1090 which have a separate driver; some are control signals, such
1091 as clock request handshaking.
1093 This driver uses board-specific data to initialize the resources
1094 and load scripts controlling which resources are switched off/on
1095 or reset when a sleep, wakeup or warm reset event occurs.
1097 config MFD_TWL4030_AUDIO
1098 bool "TI TWL4030 Audio"
1099 depends on TWL4030_CORE
1104 bool "TI TWL6040 audio codec"
1111 Say yes here if you want support for Texas Instruments TWL6040 audio
1113 This driver provides common support for accessing the device,
1114 additional drivers must be enabled in order to use the
1115 functionality of the device (audio, vibra).
1118 bool "TI TWL92330/Menelaus PM chip"
1119 depends on I2C=y && ARCH_OMAP2
1121 If you say yes here you get support for the Texas Instruments
1122 TWL92330/Menelaus Power Management chip. This include voltage
1123 regulators, Dual slot memory card transceivers, real-time clock
1124 and other features that are often used in portable devices like
1125 cell phones and PDAs.
1127 config MFD_WL1273_CORE
1128 tristate "TI WL1273 FM radio"
1133 This is the core driver for the TI WL1273 FM radio. This MFD
1134 driver connects the radio-wl1273 V4L2 module and the wl1273
1138 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1143 Say yes here to enable support for National Semiconductor / TI
1144 LM3533 Lighting Power chips.
1146 This driver provides common support for accessing the device;
1147 additional drivers must be enabled in order to use the LED,
1148 backlight or ambient-light-sensor functionality of the device.
1150 config MFD_TIMBERDALE
1151 tristate "Timberdale FPGA"
1153 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1155 This is the core driver for the timberdale FPGA. This device is a
1156 multifunction device which exposes numerous platform devices.
1158 The timberdale FPGA can be found on the Intel Atom development board
1159 for in-vehicle infontainment, called Russellville.
1162 bool "Toshiba TC35892 and variants"
1166 Support for the Toshiba TC35892 and variants I/O Expander.
1168 This driver provides common support for accessing the device,
1169 additional drivers must be enabled in order to use the
1170 functionality of the device.
1177 bool "Toshiba T7L66XB"
1178 depends on ARM && HAVE_CLK
1182 Support for Toshiba Mobile IO Controller T7L66XB
1185 bool "Toshiba TC6387XB"
1186 depends on ARM && HAVE_CLK
1190 Support for Toshiba Mobile IO Controller TC6387XB
1193 bool "Toshiba TC6393XB"
1194 depends on ARM && HAVE_CLK
1199 Support for Toshiba Mobile IO Controller TC6393XB
1202 tristate "VIA VX855/VX875 integrated south bridge"
1206 Say yes here to enable support for various functions of the
1207 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1208 and/or vx855_gpio drivers for this to do anything useful.
1216 config MFD_ARIZONA_I2C
1217 tristate "Wolfson Microelectronics Arizona platform with I2C"
1223 Support for the Wolfson Microelectronics Arizona platform audio SoC
1224 core functionality controlled via I2C.
1226 config MFD_ARIZONA_SPI
1227 tristate "Wolfson Microelectronics Arizona platform with SPI"
1231 depends on SPI_MASTER
1233 Support for the Wolfson Microelectronics Arizona platform audio SoC
1234 core functionality controlled via I2C.
1237 bool "Wolfson Microelectronics WM5102"
1238 depends on MFD_ARIZONA
1240 Support for Wolfson Microelectronics WM5102 low power audio SoC
1243 bool "Wolfson Microelectronics WM5110"
1244 depends on MFD_ARIZONA
1246 Support for Wolfson Microelectronics WM5110 low power audio SoC
1249 bool "Wolfson Microelectronics WM8997"
1250 depends on MFD_ARIZONA
1252 Support for Wolfson Microelectronics WM8997 low power audio SoC
1255 bool "Wolfson Microelectronics WM8400"
1260 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1261 CODEC. This driver provides common support for accessing
1262 the device, additional drivers must be enabled in order to use
1263 the functionality of the device.
1268 config MFD_WM831X_I2C
1269 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1276 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1277 when controlled using I2C. This driver provides common support
1278 for accessing the device, additional drivers must be enabled in
1279 order to use the functionality of the device.
1281 config MFD_WM831X_SPI
1282 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1287 depends on SPI_MASTER
1289 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1290 when controlled using SPI. This driver provides common support
1291 for accessing the device, additional drivers must be enabled in
1292 order to use the functionality of the device.
1297 config MFD_WM8350_I2C
1298 bool "Wolfson Microelectronics WM8350 with I2C"
1302 The WM8350 is an integrated audio and power management
1303 subsystem with watchdog and RTC functionality for embedded
1304 systems. This option enables core support for the WM8350 with
1305 I2C as the control interface. Additional options must be
1306 selected to enable support for the functionality of the chip.
1309 tristate "Wolfson Microelectronics WM8994"
1315 The WM8994 is a highly integrated hi-fi CODEC designed for
1316 smartphone applicatiosn. As well as audio functionality it
1317 has on board GPIO and regulator functionality which is
1318 supported via the relevant subsystems. This driver provides
1319 core support for the WM8994, in order to use the actual
1320 functionaltiy of the device other drivers must be enabled.
1323 tristate "Support for ST Microelectronics STw481x"
1324 depends on I2C && ARCH_NOMADIK
1328 Select this option to enable the STw481x chip driver used
1329 in various ST Microelectronics and ST-Ericsson embedded
1332 menu "Multimedia Capabilities Port drivers"
1333 depends on ARCH_SA1100
1340 tristate "Support SA11x0 MCP interface"
1341 depends on ARCH_SA1100
1346 tristate "Support for UCB1200 / UCB1300"
1347 depends on MCP_SA11X0
1350 config MCP_UCB1200_TS
1351 tristate "Touchscreen interface support"
1352 depends on MCP_UCB1200 && INPUT
1356 config MFD_VEXPRESS_SYSREG
1357 bool "Versatile Express System Registers"
1358 depends on VEXPRESS_CONFIG && GPIOLIB
1361 select GPIO_GENERIC_PLATFORM
1365 System Registers are the platform configuration block
1366 on the ARM Ltd. Versatile Express board.