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#)
369 * COMe-cDC2 (microETXexpress-DC)
371 * COMe-cPC2 (microETXexpress-PC)
374 * COMe-mTT10 (nanoETXexpress-TT)
377 This driver can also be built as a module. If so, the module
378 will be called kempld-core.
381 tristate "Marvell 88PM800"
387 This supports for Marvell 88PM800 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 tristate "Marvell 88PM805"
399 This supports for Marvell 88PM805 Power Management IC. This includes
400 the I2C driver and the core APIs _only_, you have to select individual
401 components like codec device, headset/Mic device under the
405 bool "Marvell 88PM8606/88PM8607"
410 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
411 This includes the I2C driver and the core APIs _only_, you have to
412 select individual components like voltage regulators, RTC and
413 battery-charger under the corresponding menus.
416 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
423 Say yes here to add support for Maxim Semiconductor MAX14577 and
424 MAX77836 Micro-USB ICs with battery charger.
425 This driver provides common support for accessing the device;
426 additional drivers must be enabled in order to use the functionality
430 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
438 Say yes here to add support for Maxim Semiconductor MAX77686 and
439 MAX77802 which are Power Management IC with an RTC on chip.
440 This driver provides common support for accessing the device;
441 additional drivers must be enabled in order to use the functionality
445 bool "Maxim Semiconductor MAX77693 PMIC Support"
451 Say yes here to add support for Maxim Semiconductor MAX77693.
452 This is a companion Power Management IC with Flash, Haptic, Charger,
453 and MUIC(Micro USB Interface Controller) controls on chip.
454 This driver provides common support for accessing the device;
455 additional drivers must be enabled in order to use the functionality
459 tristate "Maxim Semiconductor MAX8907 PMIC Support"
465 Say yes here to add support for Maxim Semiconductor MAX8907. This is
466 a Power Management IC. This driver provides common support for
467 accessing the device; additional drivers must be enabled in order
468 to use the functionality of the device.
471 bool "Maxim Semiconductor MAX8925 PMIC Support"
475 Say yes here to add support for Maxim Semiconductor MAX8925. This is
476 a Power Management IC. This driver provides common support for
477 accessing the device, additional drivers must be enabled in order
478 to use the functionality of the device.
481 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
486 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
487 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
488 MUIC controls on chip.
489 This driver provides common support for accessing the device;
490 additional drivers must be enabled in order to use the functionality
494 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
499 Say yes here to add support for Maxim Semiconductor MAX8998 and
500 National Semiconductor LP3974. This is a Power Management IC.
501 This driver provides common support for accessing the device,
502 additional drivers must be enabled in order to use the functionality
506 tristate "MEN 14F021P00 Board Management Controller Support"
510 Say yes here to add support for the MEN 14F021P00 BMC
511 which is a Board Management Controller connected to the I2C bus.
512 The device supports multiple sub-devices like LED, HWMON and WDT.
513 This driver provides common support for accessing the devices;
514 additional drivers must be enabled in order to use the
515 functionality of the BMC device.
517 This driver can also be built as a module. If so the module
518 will be called menf21bmc.
521 bool "Motorola EZXPCAP Support"
522 depends on SPI_MASTER
524 This enables the PCAP ASIC present on EZX Phones. This is
525 needed for MMC, TouchScreen, Sound, USB, etc..
527 config MFD_VIPERBOARD
528 tristate "Nano River Technologies Viperboard"
533 Say yes here if you want support for Nano River Technologies
535 There are mfd cell drivers available for i2c master, adc and
536 both gpios found on the board. The spi part does not yet
538 You need to select the mfd cell drivers separately.
539 The drivers do not support all features the board exposes.
542 tristate "Nokia Retu and Tahvo multi-function device"
547 Retu and Tahvo are a multi-function devices found on Nokia
548 Internet Tablets (770, N800 and N810).
551 tristate "NXP PCF50633"
555 Say yes here if you have NXP PCF50633 chip on your board.
556 This core driver provides register access and IRQ handling
557 facilities, and registers devices for the various functions
558 so that function-specific drivers can bind to them.
561 tristate "NXP PCF50633 ADC"
562 depends on MFD_PCF50633
564 Say yes here if you want to include support for ADC in the
568 tristate "NXP PCF50633 GPIO"
569 depends on MFD_PCF50633
571 Say yes here if you want to include support GPIO for pins on
575 tristate "Philips UCB1400 Core driver"
579 This enables support for the Philips UCB1400 core functions.
580 The UCB1400 is an AC97 audio codec.
582 To compile this driver as a module, choose M here: the
583 module will be called ucb1400_core.
588 config MFD_PM8921_CORE
589 tristate "Qualcomm PM8921 PMIC chip"
590 depends on (ARM || HEXAGON)
596 If you say yes to this option, support will be included for the
597 built-in PM8921 PMIC chip.
599 This is required if your board has a PM8921 and uses its features,
600 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
602 Say M here if you want to include support for PM8921 chip as a module.
603 This will build a module called "pm8921-core".
606 tristate "Qualcomm Resource Power Manager (RPM)"
607 depends on ARCH_QCOM && OF
609 If you say yes to this option, support will be included for the
610 Resource Power Manager system found in the Qualcomm 8660, 8960 and
613 This is required to access many regulators, clocks and bus
614 frequencies controlled by the RPM on these devices.
616 Say M here if you want to include support for the Qualcomm RPM as a
617 module. This will build a module called "qcom_rpm".
620 tristate "Qualcomm SPMI PMICs"
621 depends on ARCH_QCOM || COMPILE_TEST
626 This enables support for the Qualcomm SPMI PMICs.
627 These PMICs are currently used with the Snapdragon 800 series of
628 SoCs. Note, that this will only be useful paired with descriptions
629 of the independent functions as children nodes in the device tree.
631 Say M here if you want to include support for the SPMI PMIC
632 series as a module. The module will be called "qcom-spmi-pmic".
635 tristate "RDC R-321x southbridge"
639 Say yes here if you want to have support for the RDC R-321x SoC
640 southbridge which provides access to GPIOs and Watchdog using the
641 southbridge PCI device configuration space.
644 tristate "Realtek PCI-E card reader"
648 This supports for Realtek PCI-Express card reader including rts5209,
649 rts5229, rtl8411, etc. Realtek card reader supports access to many
650 types of memory cards, such as Memory Stick, Memory Stick Pro,
651 Secure Digital and MultiMediaCard.
654 tristate "Richtek RT5033 Power Management IC"
659 This driver provides for the Richtek RT5033 Power Management IC,
660 which includes the I2C driver and the Core APIs. This driver provides
661 common support for accessing the device. The device supports multiple
662 sub-devices like charger, fuel gauge, flash LED, current source,
666 tristate "Realtek USB card reader"
670 Select this option to get support for Realtek USB 2.0 card readers
671 including RTS5129, RTS5139, RTS5179 and RTS5170.
672 Realtek card reader supports access to many types of memory cards,
673 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
676 bool "Ricoh RC5T583 Power Management system device"
681 Select this option to get support for the RICOH583 Power
682 Management system device.
683 This driver provides common support for accessing the device
684 through i2c interface. The device supports multiple sub-devices
685 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
686 Additional drivers must be enabled in order to use the
687 different functionality of the device.
690 tristate "Rockchip RK808 Power Management chip"
696 If you say yes here you get support for the RK808
697 Power Management chips.
698 This driver provides common support for accessing the device
699 through I2C interface. The device supports multiple sub-devices
700 including interrupts, RTC, LDO & DCDC regulators, and onkey.
703 tristate "Ricoh RN5T5618 PMIC"
708 Say yes here to add support for the Ricoh RN5T618 PMIC. This
709 driver provides common support for accessing the device,
710 additional drivers must be enabled in order to use the
711 functionality of the device.
714 bool "SAMSUNG Electronics PMIC Series Support"
720 Support for the Samsung Electronics MFD series.
721 This driver provides common support for accessing the device,
722 additional drivers must be enabled in order to use the functionality
725 config MFD_SI476X_CORE
726 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
731 This is the core driver for the SI476x series of AM/FM
732 radio. This MFD driver connects the radio-si476x V4L2 module
733 and the si476x audio codec.
735 To compile this driver as a module, choose M here: the
736 module will be called si476x-core.
739 tristate "Silicon Motion SM501"
741 This is the core driver for the Silicon Motion SM501 multimedia
742 companion chip. This device is a multifunction device which may
743 provide numerous interfaces including USB host controller, USB gadget,
744 asynchronous serial ports, audio functions, and a dual display video
745 interface. The device may be connected by PCI or local bus with
746 varying functions enabled.
748 config MFD_SM501_GPIO
749 bool "Export GPIO via GPIO layer"
750 depends on MFD_SM501 && GPIOLIB
752 This option uses the gpio library layer to export the 64 GPIO
753 lines on the SM501. The platform data is used to supply the
754 base number for the first GPIO line to register.
757 bool "SMSC ECE1099 series chips"
762 If you say yes here you get support for the
763 ece1099 chips from SMSC.
765 To compile this driver as a module, choose M here: the
766 module will be called smsc.
769 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
770 default y if ARCH_U300 || ARCH_U8500
772 Say yes here if you have the ABX500 Mixed Signal IC family
773 chips. This core driver expose register access functions.
774 Functionality specific drivers using these functions can
775 remain unchanged when IC changes. Binding of the functions to
776 actual register access is done by the IC core driver.
779 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
780 depends on I2C=y && ABX500_CORE
782 default y if ARCH_U300
784 Select this to enable the AB3100 Mixed Signal IC core
785 functionality. This connects to a AB3100 on the I2C bus
786 and expose a number of symbols needed for dependent devices
787 to read and write registers and subscribe to events from
788 this multi-functional IC. This is needed to use other features
789 of the AB3100 such as battery-backed RTC, charging control,
790 LEDs, vibrator, system power and temperature, power management
794 tristate "ST-Ericsson AB3100 OTP functions"
795 depends on AB3100_CORE
796 default y if AB3100_CORE
798 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
799 programmable memory) support. This exposes a sysfs file to read
803 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
804 depends on ABX500_CORE && MFD_DB8500_PRCMU
809 Select this option to enable access to AB8500 power management
810 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
811 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
812 the irq_chip parts for handling the Mixed Signal chip events.
813 This chip embeds various other multimedia funtionalities as well.
816 bool "Enable debug info via debugfs"
817 depends on AB8500_GPADC && DEBUG_FS
818 default y if DEBUG_FS
820 Select this option if you want debug information using the debug
824 bool "ST-Ericsson AB8500 GPADC driver"
825 depends on AB8500_CORE && REGULATOR_AB8500
828 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
830 config MFD_DB8500_PRCMU
831 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
832 depends on UX500_SOC_DB8500
835 Select this option to enable support for the DB8500 Power Reset
836 and Control Management Unit. This is basically an autonomous
837 system controller running an XP70 microprocessor, which is accessed
838 through a register map.
841 bool "STMicroelectronics STMPE"
842 depends on (I2C=y || SPI_MASTER=y)
846 Support for the STMPE family of I/O Expanders from
849 Currently supported devices are:
851 STMPE811: GPIO, Touchscreen
852 STMPE1601: GPIO, Keypad
853 STMPE1801: GPIO, Keypad
854 STMPE2401: GPIO, Keypad
855 STMPE2403: GPIO, Keypad
857 This driver provides common support for accessing the device,
858 additional drivers must be enabled in order to use the functionality
859 of the device. Currently available sub drivers are:
863 Touchscreen: stmpe-ts
865 menu "STMicroelectronics STMPE Interface Drivers"
869 bool "STMicroelectronics STMPE I2C Interface"
873 This is used to enable I2C interface of STMPE
876 bool "STMicroelectronics STMPE SPI Interface"
877 depends on SPI_MASTER
879 This is used to enable SPI interface of STMPE
883 bool "STMicroelectronics STA2X11"
888 config MFD_SUN6I_PRCM
889 bool "Allwinner A31 PRCM controller"
890 depends on ARCH_SUNXI
893 Support for the PRCM (Power/Reset/Clock Management) unit available
897 bool "System Controller Register R/W Based on Regmap"
900 Select this option to enable accessing system control registers
903 config MFD_DAVINCI_VOICECODEC
908 config MFD_TI_AM335X_TSCADC
909 tristate "TI ADC / Touch Screen chip support"
914 If you say yes here you get support for Texas Instruments series
915 of Touch Screen /ADC chips.
916 To compile this driver as a module, choose M here: the
917 module will be called ti_am335x_tscadc.
919 config MFD_DM355EVM_MSP
920 bool "TI DaVinci DM355 EVM microcontroller"
921 depends on I2C=y && MACH_DAVINCI_DM355_EVM
923 This driver supports the MSP430 microcontroller used on these
924 boards. MSP430 firmware manages resets and power sequencing,
925 inputs from buttons and the IR remote, LEDs, an RTC, and more.
928 tristate "TI/National Semiconductor LP3943 MFD Driver"
933 Support for the TI/National Semiconductor LP3943.
934 This driver consists of GPIO and PWM drivers.
935 With these functionalities, it can be used for LED string control or
936 general usage such like a GPIO controller and a PWM controller.
939 bool "TI LP8788 Power Management Unit Driver"
945 TI LP8788 PMU supports regulators, battery charger, RTC,
946 ADC, backlight driver and current sinks.
948 config MFD_OMAP_USB_HOST
949 bool "TI OMAP USBHS core and TLL driver"
950 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
953 This is the core driver for the OAMP EHCI and OHCI drivers.
954 This MFD driver does the required setup functionalities for
955 OMAP USB Host drivers.
958 bool "TI Palmas series chips"
964 If you say yes here you get support for the Palmas
965 series of PMIC chips from Texas Instruments.
968 tristate "TI TPS61050/61052 Boost Converters"
972 select REGULATOR_FIXED_VOLTAGE
974 This option enables a driver for the TP61050/TPS61052
975 high-power "white LED driver". This boost converter is
976 sometimes used for other things than white LEDs, and
977 also contains a GPIO pin.
980 tristate "TI TPS6501x Power Management chips"
981 depends on I2C && GPIOLIB
982 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
984 If you say yes here you get support for the TPS6501x series of
985 Power Management chips. These include voltage regulators,
986 lithium ion/polymer battery charging, and other features that
987 are often used in portable devices like cell phones and cameras.
989 This driver can also be built as a module. If so, the module
990 will be called tps65010.
993 tristate "TI TPS6507x Power Management / Touch Screen chips"
997 If you say yes here you get support for the TPS6507x series of
998 Power Management / Touch Screen chips. These include voltage
999 regulators, lithium ion/polymer battery charging, touch screen
1000 and other features that are often used in portable devices.
1001 This driver can also be built as a module. If so, the module
1002 will be called tps6507x.
1004 config TPS65911_COMPARATOR
1008 bool "TI TPS65090 Power Management chips"
1014 If you say yes here you get support for the TPS65090 series of
1015 Power Management chips.
1016 This driver provides common support for accessing the device,
1017 additional drivers must be enabled in order to use the
1018 functionality of the device.
1021 tristate "TI TPS65217 Power Management / White LED chips"
1026 If you say yes here you get support for the TPS65217 series of
1027 Power Management / White LED chips.
1028 These include voltage regulators, lithium ion/polymer battery
1029 charger, wled and other features that are often used in portable
1032 This driver can also be built as a module. If so, the module
1033 will be called tps65217.
1036 tristate "TI TPS65218 Power Management chips"
1042 If you say yes here you get support for the TPS65218 series of
1043 Power Management chips.
1044 These include voltage regulators, gpio and other features
1045 that are often used in portable devices. Only regulator
1046 component is currently supported.
1048 This driver can also be built as a module. If so, the module
1049 will be called tps65218.
1052 bool "TI TPS6586x Power Management chips"
1057 If you say yes here you get support for the TPS6586X series of
1058 Power Management chips.
1059 This driver provides common support for accessing the device,
1060 additional drivers must be enabled in order to use the
1061 functionality of the device.
1063 This driver can also be built as a module. If so, the module
1064 will be called tps6586x.
1067 bool "TI TPS65910 Power Management chip"
1068 depends on I2C=y && GPIOLIB
1074 if you say yes here you get support for the TPS65910 series of
1075 Power Management chips.
1078 bool "TI TPS65912 Power Management chip"
1082 If you say yes here you get support for the TPS65912 series of
1085 config MFD_TPS65912_I2C
1086 bool "TI TPS65912 Power Management chip with I2C"
1089 depends on I2C=y && GPIOLIB
1091 If you say yes here you get support for the TPS65912 series of
1092 PM chips with I2C interface.
1094 config MFD_TPS65912_SPI
1095 bool "TI TPS65912 Power Management chip with SPI"
1098 depends on SPI_MASTER && GPIOLIB
1100 If you say yes here you get support for the TPS65912 series of
1101 PM chips with SPI interface.
1104 bool "TI TPS80031/TPS80032 Power Management chips"
1110 If you say yes here you get support for the Texas Instruments
1111 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1112 Path and Battery Charger. The device provides five configurable
1113 step-down converters, 11 general purpose LDOs, USB OTG Module,
1114 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1115 Power Path from USB, 32K clock generator.
1118 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1123 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1124 This core driver provides register access and IRQ handling
1125 facilities, and registers devices for the various functions
1126 so that function-specific drivers can bind to them.
1128 These multi-function chips are found on many OMAP2 and OMAP3
1129 boards, providing power management, RTC, GPIO, keypad, a
1130 high speed USB OTG transceiver, an audio codec (on most
1131 versions) and many other features.
1133 config TWL4030_POWER
1134 bool "TI TWL4030 power resources"
1135 depends on TWL4030_CORE && ARM
1137 Say yes here if you want to use the power resources on the
1138 TWL4030 family chips. Most of these resources are regulators,
1139 which have a separate driver; some are control signals, such
1140 as clock request handshaking.
1142 This driver uses board-specific data to initialize the resources
1143 and load scripts controlling which resources are switched off/on
1144 or reset when a sleep, wakeup or warm reset event occurs.
1146 config MFD_TWL4030_AUDIO
1147 bool "TI TWL4030 Audio"
1148 depends on TWL4030_CORE
1153 bool "TI TWL6040 audio codec"
1160 Say yes here if you want support for Texas Instruments TWL6040 audio
1162 This driver provides common support for accessing the device,
1163 additional drivers must be enabled in order to use the
1164 functionality of the device (audio, vibra).
1167 bool "TI TWL92330/Menelaus PM chip"
1168 depends on I2C=y && ARCH_OMAP2
1170 If you say yes here you get support for the Texas Instruments
1171 TWL92330/Menelaus Power Management chip. This include voltage
1172 regulators, Dual slot memory card transceivers, real-time clock
1173 and other features that are often used in portable devices like
1174 cell phones and PDAs.
1176 config MFD_WL1273_CORE
1177 tristate "TI WL1273 FM radio"
1182 This is the core driver for the TI WL1273 FM radio. This MFD
1183 driver connects the radio-wl1273 V4L2 module and the wl1273
1187 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1192 Say yes here to enable support for National Semiconductor / TI
1193 LM3533 Lighting Power chips.
1195 This driver provides common support for accessing the device;
1196 additional drivers must be enabled in order to use the LED,
1197 backlight or ambient-light-sensor functionality of the device.
1199 config MFD_TIMBERDALE
1200 tristate "Timberdale FPGA"
1202 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1204 This is the core driver for the timberdale FPGA. This device is a
1205 multifunction device which exposes numerous platform devices.
1207 The timberdale FPGA can be found on the Intel Atom development board
1208 for in-vehicle infontainment, called Russellville.
1211 bool "Toshiba TC35892 and variants"
1215 Support for the Toshiba TC35892 and variants I/O Expander.
1217 This driver provides common support for accessing the device,
1218 additional drivers must be enabled in order to use the
1219 functionality of the device.
1226 bool "Toshiba T7L66XB"
1227 depends on ARM && HAVE_CLK
1231 Support for Toshiba Mobile IO Controller T7L66XB
1234 bool "Toshiba TC6387XB"
1235 depends on ARM && HAVE_CLK
1239 Support for Toshiba Mobile IO Controller TC6387XB
1242 bool "Toshiba TC6393XB"
1243 depends on ARM && HAVE_CLK
1248 Support for Toshiba Mobile IO Controller TC6393XB
1251 tristate "VIA VX855/VX875 integrated south bridge"
1255 Say yes here to enable support for various functions of the
1256 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1257 and/or vx855_gpio drivers for this to do anything useful.
1265 config MFD_ARIZONA_I2C
1266 tristate "Wolfson Microelectronics Arizona platform with I2C"
1272 Support for the Wolfson Microelectronics Arizona platform audio SoC
1273 core functionality controlled via I2C.
1275 config MFD_ARIZONA_SPI
1276 tristate "Wolfson Microelectronics Arizona platform with SPI"
1280 depends on SPI_MASTER
1282 Support for the Wolfson Microelectronics Arizona platform audio SoC
1283 core functionality controlled via I2C.
1286 bool "Wolfson Microelectronics WM5102"
1287 depends on MFD_ARIZONA
1289 Support for Wolfson Microelectronics WM5102 low power audio SoC
1292 bool "Wolfson Microelectronics WM5110"
1293 depends on MFD_ARIZONA
1295 Support for Wolfson Microelectronics WM5110 low power audio SoC
1298 bool "Wolfson Microelectronics WM8997"
1299 depends on MFD_ARIZONA
1301 Support for Wolfson Microelectronics WM8997 low power audio SoC
1304 bool "Wolfson Microelectronics WM8400"
1309 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1310 CODEC. This driver provides common support for accessing
1311 the device, additional drivers must be enabled in order to use
1312 the functionality of the device.
1317 config MFD_WM831X_I2C
1318 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1325 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1326 when controlled using I2C. This driver provides common support
1327 for accessing the device, additional drivers must be enabled in
1328 order to use the functionality of the device.
1330 config MFD_WM831X_SPI
1331 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1336 depends on SPI_MASTER
1338 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1339 when controlled using SPI. This driver provides common support
1340 for accessing the device, additional drivers must be enabled in
1341 order to use the functionality of the device.
1346 config MFD_WM8350_I2C
1347 bool "Wolfson Microelectronics WM8350 with I2C"
1351 The WM8350 is an integrated audio and power management
1352 subsystem with watchdog and RTC functionality for embedded
1353 systems. This option enables core support for the WM8350 with
1354 I2C as the control interface. Additional options must be
1355 selected to enable support for the functionality of the chip.
1358 tristate "Wolfson Microelectronics WM8994"
1364 The WM8994 is a highly integrated hi-fi CODEC designed for
1365 smartphone applicatiosn. As well as audio functionality it
1366 has on board GPIO and regulator functionality which is
1367 supported via the relevant subsystems. This driver provides
1368 core support for the WM8994, in order to use the actual
1369 functionaltiy of the device other drivers must be enabled.
1372 tristate "Support for ST Microelectronics STw481x"
1373 depends on I2C && ARCH_NOMADIK
1377 Select this option to enable the STw481x chip driver used
1378 in various ST Microelectronics and ST-Ericsson embedded
1381 menu "Multimedia Capabilities Port drivers"
1382 depends on ARCH_SA1100
1389 tristate "Support SA11x0 MCP interface"
1390 depends on ARCH_SA1100
1395 tristate "Support for UCB1200 / UCB1300"
1396 depends on MCP_SA11X0
1399 config MCP_UCB1200_TS
1400 tristate "Touchscreen interface support"
1401 depends on MCP_UCB1200 && INPUT
1405 config MFD_VEXPRESS_SYSREG
1406 bool "Versatile Express System Registers"
1407 depends on VEXPRESS_CONFIG && GPIOLIB
1410 select GPIO_GENERIC_PLATFORM
1414 System Registers are the platform configuration block
1415 on the ARM Ltd. Versatile Express board.