2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
28 Support for the AS3711 PMIC from AMS
31 bool "ams AS3722 Power Management IC"
35 depends on I2C=y && OF
37 The ams AS3722 is a compact system PMU suitable for mobile phones,
38 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
39 controllers, 11 LDOs, RTC, automatic battery, temperature and
40 over current monitoring, GPIOs, ADC and a watchdog.
43 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
46 Say yes here to add support for Analog Devices AD5520 and ADP5501,
47 Multifunction Power Management IC. This includes
48 the I2C driver and the core APIs _only_, you have to select
49 individual components like LCD backlight, LEDs, GPIOs and Kepad
50 under the corresponding menus.
52 config MFD_AAT2870_CORE
53 bool "AnalogicTech AAT2870"
56 depends on GPIOLIB || COMPILE_TEST
58 If you say yes here you get support for the AAT2870.
59 This driver provides common support for accessing the device,
60 additional drivers must be enabled in order to use the
61 functionality of the device.
63 config MFD_ATMEL_HLCDC
64 tristate "Atmel HLCDC (High-end LCD Controller)"
69 If you say yes here you get support for the HLCDC block.
70 This driver provides common support for accessing the device,
71 additional drivers must be enabled in order to use the
72 functionality of the device.
75 tristate "Broadcom BCM590xx PMUs"
80 Support for the BCM590xx PMUs from Broadcom
83 bool "X-Powers AXP20X"
89 If you say Y here you get support for the X-Powers AXP202, AXP209 and
90 AXP288 power management IC (PMIC).
91 This driver include only the core APIs. You have to select individual
92 components like regulators or the PEK (Power Enable Key) under the
96 tristate "ChromeOS Embedded Controller"
98 select CHROME_PLATFORMS
101 If you say Y here you get support for the ChromeOS Embedded
102 Controller (EC) providing keyboard, battery and power services.
103 You also need to enable the driver for the bus you are using. The
104 protocol for talking to the EC is defined by the bus driver.
106 config MFD_CROS_EC_I2C
107 tristate "ChromeOS Embedded Controller (I2C)"
108 depends on MFD_CROS_EC && CROS_EC_PROTO && I2C
111 If you say Y here, you get support for talking to the ChromeOS
112 EC through an I2C bus. This uses a simple byte-level protocol with
113 a checksum. Failing accesses will be retried three times to
116 config MFD_CROS_EC_SPI
117 tristate "ChromeOS Embedded Controller (SPI)"
118 depends on MFD_CROS_EC && CROS_EC_PROTO && SPI && OF
121 If you say Y here, you get support for talking to the ChromeOS EC
122 through a SPI bus, using a byte-level protocol. Since the EC's
123 response time cannot be guaranteed, we support ignoring
124 'pre-amble' bytes before the response actually starts.
128 depends on GPIOLIB && ARM
131 This driver supports the ASIC3 multifunction chip found on many
132 PDAs (mainly iPAQ and HTC based ones)
135 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
138 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
139 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
140 usually found on PXA processors-based platforms. This includes
141 the I2C driver and the core APIs _only_, you have to select
142 individual components like LCD backlight, voltage regulators,
143 LEDs and battery-charger under the corresponding menus.
149 config MFD_DA9052_SPI
150 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
154 depends on SPI_MASTER=y
156 Support for the Dialog Semiconductor DA9052 PMIC
157 when controlled using SPI. This driver provides common support
158 for accessing the device, additional drivers must be enabled in
159 order to use the functionality of the device.
161 config MFD_DA9052_I2C
162 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
168 Support for the Dialog Semiconductor DA9052 PMIC
169 when controlled using I2C. This driver provides common support
170 for accessing the device, additional drivers must be enabled in
171 order to use the functionality of the device.
174 bool "Dialog Semiconductor DA9055 PMIC Support"
180 Say yes here for support of Dialog Semiconductor DA9055. This is
181 a Power Management IC. This driver provides common support for
182 accessing the device as well as the I2C interface to the chip itself.
183 Additional drivers must be enabled in order to use the functionality
186 This driver can be built as a module. If built as a module it will be
190 bool "Dialog Semiconductor DA9063 PMIC Support"
196 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
197 This includes the I2C driver and core APIs.
198 Additional drivers must be enabled in order to use the functionality
202 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
208 This adds support for the DA9150 integrated charger and fuel-gauge
209 chip. This driver provides common support for accessing the device.
210 Additional drivers must be enabled in order to use the specific
211 features of the device.
214 tristate "Diolan DLN2 support"
218 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
219 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
220 etc. must be enabled in order to use the functionality of
225 depends on (SPI_MASTER || I2C)
229 Enable support for the Freescale MC13783 and MC13892 PMICs.
230 This driver provides common support for accessing the device,
231 additional drivers must be enabled in order to use the
232 functionality of the device.
234 config MFD_MC13XXX_SPI
235 tristate "Freescale MC13783 and MC13892 SPI interface"
236 depends on SPI_MASTER
240 Select this if your MC13xxx is connected via an SPI bus.
242 config MFD_MC13XXX_I2C
243 tristate "Freescale MC13892 I2C interface"
248 Select this if your MC13xxx is connected via an I2C bus.
250 config MFD_HI6421_PMIC
251 tristate "HiSilicon Hi6421 PMU/Codec IC"
256 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
257 functions, such as regulators, RTC, codec, Coulomb counter, etc.
258 This driver includes core APIs _only_. You have to select
259 individul components like voltage regulators under corresponding
260 menus in order to enable them.
261 We communicate with the Hi6421 via memory-mapped I/O.
264 bool "HTC EGPIO support"
265 depends on GPIOLIB && ARM
267 This driver supports the CPLD egpio chip present on
268 several HTC phones. It provides basic support for input
269 pins, output pins, and irqs.
272 tristate "HTC PASIC3 LED/DS1WM chip support"
275 This core driver provides register access for the LED/DS1WM
276 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
277 HTC Magician devices, respectively. Actual functionality is
278 handled by the leds-pasic3 and ds1wm drivers.
281 bool "HTC I2C PLD chip support"
282 depends on I2C=y && GPIOLIB
284 If you say yes here you get support for the supposed CPLD
285 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
286 This device provides input and output GPIOs through an I2C
287 interface to one or more sub-chips.
289 config MFD_INTEL_QUARK_I2C_GPIO
290 tristate "Intel Quark MFD I2C GPIO"
293 depends on COMMON_CLK
296 This MFD provides support for I2C and GPIO that exist only
297 in a single PCI device. It splits the 2 IO devices to
298 their respective IO driver.
299 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
302 tristate "Intel ICH LPC"
306 The LPC bridge function of the Intel ICH provides support for
307 many functional units. This driver provides needed support for
308 other drivers to control these functions, currently GPIO and
312 tristate "Intel SCH LPC"
316 LPC bridge function of the Intel SCH provides support for
317 System Management Bus and General Purpose I/O.
319 config INTEL_SOC_PMIC
320 bool "Support for Intel Atom SoC PMIC"
327 Select this option to enable support for the PMIC device
328 on some Intel SoC systems. The PMIC provides ADC, GPIO,
329 thermal, charger and related power management functions
332 config MFD_INTEL_MSIC
334 depends on INTEL_SCU_IPC
337 Select this option to enable access to Intel MSIC (Avatele
338 Passage) chip. This chip embeds audio, battery, GPIO, etc.
339 devices used in Intel Medfield platforms.
341 config MFD_IPAQ_MICRO
342 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
343 depends on SA1100_H3100 || SA1100_H3600
346 Select this to get support for the Microcontroller found in
347 the Compaq iPAQ handheld computers. This is an Atmel
348 AT90LS8535 microcontroller flashed with a special iPAQ
349 firmware using the custom protocol implemented in this driver.
351 config MFD_JANZ_CMODIO
352 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
356 This is the core driver for the Janz CMOD-IO PCI MODULbus
357 carrier board. This device is a PCI to MODULbus bridge which may
358 host many different types of MODULbus daughterboards, including
359 CAN and GPIO controllers.
361 config MFD_JZ4740_ADC
362 bool "Janz JZ4740 ADC core"
364 select GENERIC_IRQ_CHIP
365 depends on MACH_JZ4740
367 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
368 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
371 tristate "Kontron module PLD device"
374 This is the core driver for the PLD (Programmable Logic Device) found
375 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
376 device may provide functions like watchdog, GPIO, UART and I2C bus.
378 The following modules are supported:
381 * COMe-bPC2 (ETXexpress-PC)
382 * COMe-bSC# (ETXexpress-SC T#)
386 * COMe-cDC2 (microETXexpress-DC)
388 * COMe-cPC2 (microETXexpress-PC)
391 * COMe-mTT10 (nanoETXexpress-TT)
394 This driver can also be built as a module. If so, the module
395 will be called kempld-core.
398 tristate "Marvell 88PM800"
404 This supports for Marvell 88PM800 Power Management IC.
405 This includes the I2C driver and the core APIs _only_, you have to
406 select individual components like voltage regulators, RTC and
407 battery-charger under the corresponding menus.
410 tristate "Marvell 88PM805"
416 This supports for Marvell 88PM805 Power Management IC. This includes
417 the I2C driver and the core APIs _only_, you have to select individual
418 components like codec device, headset/Mic device under the
422 bool "Marvell 88PM8606/88PM8607"
427 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
428 This includes the I2C driver and the core APIs _only_, you have to
429 select individual components like voltage regulators, RTC and
430 battery-charger under the corresponding menus.
433 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
440 Say yes here to add support for Maxim Semiconductor MAX14577 and
441 MAX77836 Micro-USB ICs with battery charger.
442 This driver provides common support for accessing the device;
443 additional drivers must be enabled in order to use the functionality
447 bool "Maxim Semiconductor MAX77686/802 PMIC Support"
455 Say yes here to add support for Maxim Semiconductor MAX77686 and
456 MAX77802 which are Power Management IC with an RTC on chip.
457 This driver provides common support for accessing the device;
458 additional drivers must be enabled in order to use the functionality
462 bool "Maxim Semiconductor MAX77693 PMIC Support"
468 Say yes here to add support for Maxim Semiconductor MAX77693.
469 This is a companion Power Management IC with Flash, Haptic, Charger,
470 and MUIC(Micro USB Interface Controller) controls on chip.
471 This driver provides common support for accessing the device;
472 additional drivers must be enabled in order to use the functionality
476 bool "Maxim Semiconductor MAX77843 PMIC Support"
482 Say yes here to add support for Maxim Semiconductor MAX77843.
483 This is companion Power Management IC with LEDs, Haptic, Charger,
484 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
485 This driver provides common support for accessing the device;
486 additional drivers must be enabled in order to use the functionality
490 tristate "Maxim Semiconductor MAX8907 PMIC Support"
496 Say yes here to add support for Maxim Semiconductor MAX8907. This is
497 a Power Management IC. This driver provides common support for
498 accessing the device; additional drivers must be enabled in order
499 to use the functionality of the device.
502 bool "Maxim Semiconductor MAX8925 PMIC Support"
506 Say yes here to add support for Maxim Semiconductor MAX8925. This is
507 a Power Management IC. This driver provides common support for
508 accessing the device, additional drivers must be enabled in order
509 to use the functionality of the device.
512 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
517 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
518 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
519 MUIC controls on chip.
520 This driver provides common support for accessing the device;
521 additional drivers must be enabled in order to use the functionality
525 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
530 Say yes here to add support for Maxim Semiconductor MAX8998 and
531 National Semiconductor LP3974. This is a Power Management IC.
532 This driver provides common support for accessing the device,
533 additional drivers must be enabled in order to use the functionality
537 tristate "MediaTek MT6397 PMIC Support"
541 Say yes here to add support for MediaTek MT6397 PMIC. This is
542 a Power Management IC. This driver provides common support for
543 accessing the device; additional drivers must be enabled in order
544 to use the functionality of the device.
547 tristate "MEN 14F021P00 Board Management Controller Support"
551 Say yes here to add support for the MEN 14F021P00 BMC
552 which is a Board Management Controller connected to the I2C bus.
553 The device supports multiple sub-devices like LED, HWMON and WDT.
554 This driver provides common support for accessing the devices;
555 additional drivers must be enabled in order to use the
556 functionality of the BMC device.
558 This driver can also be built as a module. If so the module
559 will be called menf21bmc.
562 bool "Motorola EZXPCAP Support"
563 depends on SPI_MASTER
565 This enables the PCAP ASIC present on EZX Phones. This is
566 needed for MMC, TouchScreen, Sound, USB, etc..
568 config MFD_VIPERBOARD
569 tristate "Nano River Technologies Viperboard"
574 Say yes here if you want support for Nano River Technologies
576 There are mfd cell drivers available for i2c master, adc and
577 both gpios found on the board. The spi part does not yet
579 You need to select the mfd cell drivers separately.
580 The drivers do not support all features the board exposes.
583 tristate "Nokia Retu and Tahvo multi-function device"
588 Retu and Tahvo are a multi-function devices found on Nokia
589 Internet Tablets (770, N800 and N810).
592 tristate "NXP PCF50633"
596 Say yes here if you have NXP PCF50633 chip on your board.
597 This core driver provides register access and IRQ handling
598 facilities, and registers devices for the various functions
599 so that function-specific drivers can bind to them.
602 tristate "NXP PCF50633 ADC"
603 depends on MFD_PCF50633
605 Say yes here if you want to include support for ADC in the
609 tristate "NXP PCF50633 GPIO"
610 depends on MFD_PCF50633
612 Say yes here if you want to include support GPIO for pins on
616 tristate "Philips UCB1400 Core driver"
620 This enables support for the Philips UCB1400 core functions.
621 The UCB1400 is an AC97 audio codec.
623 To compile this driver as a module, choose M here: the
624 module will be called ucb1400_core.
629 config MFD_PM8921_CORE
630 tristate "Qualcomm PM8921 PMIC chip"
631 depends on (ARM || HEXAGON)
637 If you say yes to this option, support will be included for the
638 built-in PM8921 PMIC chip.
640 This is required if your board has a PM8921 and uses its features,
641 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
643 Say M here if you want to include support for PM8921 chip as a module.
644 This will build a module called "pm8921-core".
647 tristate "Qualcomm Resource Power Manager (RPM)"
648 depends on ARCH_QCOM && OF
650 If you say yes to this option, support will be included for the
651 Resource Power Manager system found in the Qualcomm 8660, 8960 and
654 This is required to access many regulators, clocks and bus
655 frequencies controlled by the RPM on these devices.
657 Say M here if you want to include support for the Qualcomm RPM as a
658 module. This will build a module called "qcom_rpm".
661 tristate "Qualcomm SPMI PMICs"
662 depends on ARCH_QCOM || COMPILE_TEST
667 This enables support for the Qualcomm SPMI PMICs.
668 These PMICs are currently used with the Snapdragon 800 series of
669 SoCs. Note, that this will only be useful paired with descriptions
670 of the independent functions as children nodes in the device tree.
672 Say M here if you want to include support for the SPMI PMIC
673 series as a module. The module will be called "qcom-spmi-pmic".
676 tristate "RDC R-321x southbridge"
680 Say yes here if you want to have support for the RDC R-321x SoC
681 southbridge which provides access to GPIOs and Watchdog using the
682 southbridge PCI device configuration space.
685 tristate "Realtek PCI-E card reader"
689 This supports for Realtek PCI-Express card reader including rts5209,
690 rts5229, rtl8411, etc. Realtek card reader supports access to many
691 types of memory cards, such as Memory Stick, Memory Stick Pro,
692 Secure Digital and MultiMediaCard.
695 tristate "Richtek RT5033 Power Management IC"
701 This driver provides for the Richtek RT5033 Power Management IC,
702 which includes the I2C driver and the Core APIs. This driver provides
703 common support for accessing the device. The device supports multiple
704 sub-devices like charger, fuel gauge, flash LED, current source,
708 tristate "Realtek USB card reader"
712 Select this option to get support for Realtek USB 2.0 card readers
713 including RTS5129, RTS5139, RTS5179 and RTS5170.
714 Realtek card reader supports access to many types of memory cards,
715 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
718 bool "Ricoh RC5T583 Power Management system device"
723 Select this option to get support for the RICOH583 Power
724 Management system device.
725 This driver provides common support for accessing the device
726 through i2c interface. The device supports multiple sub-devices
727 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
728 Additional drivers must be enabled in order to use the
729 different functionality of the device.
732 tristate "Rockchip RK808 Power Management chip"
738 If you say yes here you get support for the RK808
739 Power Management chips.
740 This driver provides common support for accessing the device
741 through I2C interface. The device supports multiple sub-devices
742 including interrupts, RTC, LDO & DCDC regulators, and onkey.
745 tristate "Ricoh RN5T5618 PMIC"
750 Say yes here to add support for the Ricoh RN5T618 PMIC. This
751 driver provides common support for accessing the device,
752 additional drivers must be enabled in order to use the
753 functionality of the device.
756 bool "SAMSUNG Electronics PMIC Series Support"
762 Support for the Samsung Electronics MFD series.
763 This driver provides common support for accessing the device,
764 additional drivers must be enabled in order to use the functionality
767 config MFD_SI476X_CORE
768 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
773 This is the core driver for the SI476x series of AM/FM
774 radio. This MFD driver connects the radio-si476x V4L2 module
775 and the si476x audio codec.
777 To compile this driver as a module, choose M here: the
778 module will be called si476x-core.
781 tristate "Silicon Motion SM501"
783 This is the core driver for the Silicon Motion SM501 multimedia
784 companion chip. This device is a multifunction device which may
785 provide numerous interfaces including USB host controller, USB gadget,
786 asynchronous serial ports, audio functions, and a dual display video
787 interface. The device may be connected by PCI or local bus with
788 varying functions enabled.
790 config MFD_SM501_GPIO
791 bool "Export GPIO via GPIO layer"
792 depends on MFD_SM501 && GPIOLIB
794 This option uses the gpio library layer to export the 64 GPIO
795 lines on the SM501. The platform data is used to supply the
796 base number for the first GPIO line to register.
799 tristate "Skyworks Solutions SKY81452"
804 This is the core driver for the Skyworks SKY81452 backlight and
805 voltage regulator device.
807 This driver can also be built as a module. If so, the module
808 will be called sky81452.
811 bool "SMSC ECE1099 series chips"
816 If you say yes here you get support for the
817 ece1099 chips from SMSC.
819 To compile this driver as a module, choose M here: the
820 module will be called smsc.
823 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
824 default y if ARCH_U300 || ARCH_U8500
826 Say yes here if you have the ABX500 Mixed Signal IC family
827 chips. This core driver expose register access functions.
828 Functionality specific drivers using these functions can
829 remain unchanged when IC changes. Binding of the functions to
830 actual register access is done by the IC core driver.
833 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
834 depends on I2C=y && ABX500_CORE
836 default y if ARCH_U300
838 Select this to enable the AB3100 Mixed Signal IC core
839 functionality. This connects to a AB3100 on the I2C bus
840 and expose a number of symbols needed for dependent devices
841 to read and write registers and subscribe to events from
842 this multi-functional IC. This is needed to use other features
843 of the AB3100 such as battery-backed RTC, charging control,
844 LEDs, vibrator, system power and temperature, power management
848 tristate "ST-Ericsson AB3100 OTP functions"
849 depends on AB3100_CORE
850 default y if AB3100_CORE
852 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
853 programmable memory) support. This exposes a sysfs file to read
857 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
858 depends on ABX500_CORE && MFD_DB8500_PRCMU
863 Select this option to enable access to AB8500 power management
864 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
865 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
866 the irq_chip parts for handling the Mixed Signal chip events.
867 This chip embeds various other multimedia funtionalities as well.
870 bool "Enable debug info via debugfs"
871 depends on AB8500_GPADC && DEBUG_FS
872 default y if DEBUG_FS
874 Select this option if you want debug information using the debug
878 bool "ST-Ericsson AB8500 GPADC driver"
879 depends on AB8500_CORE && REGULATOR_AB8500
882 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
884 config MFD_DB8500_PRCMU
885 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
886 depends on UX500_SOC_DB8500
889 Select this option to enable support for the DB8500 Power Reset
890 and Control Management Unit. This is basically an autonomous
891 system controller running an XP70 microprocessor, which is accessed
892 through a register map.
895 bool "STMicroelectronics STMPE"
896 depends on (I2C=y || SPI_MASTER=y)
900 Support for the STMPE family of I/O Expanders from
903 Currently supported devices are:
905 STMPE811: GPIO, Touchscreen
906 STMPE1601: GPIO, Keypad
907 STMPE1801: GPIO, Keypad
908 STMPE2401: GPIO, Keypad
909 STMPE2403: GPIO, Keypad
911 This driver provides common support for accessing the device,
912 additional drivers must be enabled in order to use the functionality
913 of the device. Currently available sub drivers are:
917 Touchscreen: stmpe-ts
919 menu "STMicroelectronics STMPE Interface Drivers"
923 bool "STMicroelectronics STMPE I2C Interface"
927 This is used to enable I2C interface of STMPE
930 bool "STMicroelectronics STMPE SPI Interface"
931 depends on SPI_MASTER
933 This is used to enable SPI interface of STMPE
937 bool "STMicroelectronics STA2X11"
942 config MFD_SUN6I_PRCM
943 bool "Allwinner A31 PRCM controller"
944 depends on ARCH_SUNXI
947 Support for the PRCM (Power/Reset/Clock Management) unit available
951 bool "System Controller Register R/W Based on Regmap"
954 Select this option to enable accessing system control registers
957 config MFD_DAVINCI_VOICECODEC
962 config MFD_TI_AM335X_TSCADC
963 tristate "TI ADC / Touch Screen chip support"
968 If you say yes here you get support for Texas Instruments series
969 of Touch Screen /ADC chips.
970 To compile this driver as a module, choose M here: the
971 module will be called ti_am335x_tscadc.
973 config MFD_DM355EVM_MSP
974 bool "TI DaVinci DM355 EVM microcontroller"
975 depends on I2C=y && MACH_DAVINCI_DM355_EVM
977 This driver supports the MSP430 microcontroller used on these
978 boards. MSP430 firmware manages resets and power sequencing,
979 inputs from buttons and the IR remote, LEDs, an RTC, and more.
982 tristate "TI/National Semiconductor LP3943 MFD Driver"
987 Support for the TI/National Semiconductor LP3943.
988 This driver consists of GPIO and PWM drivers.
989 With these functionalities, it can be used for LED string control or
990 general usage such like a GPIO controller and a PWM controller.
993 bool "TI LP8788 Power Management Unit Driver"
999 TI LP8788 PMU supports regulators, battery charger, RTC,
1000 ADC, backlight driver and current sinks.
1002 config MFD_OMAP_USB_HOST
1003 bool "TI OMAP USBHS core and TLL driver"
1004 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1007 This is the core driver for the OAMP EHCI and OHCI drivers.
1008 This MFD driver does the required setup functionalities for
1009 OMAP USB Host drivers.
1012 bool "TI Palmas series chips"
1018 If you say yes here you get support for the Palmas
1019 series of PMIC chips from Texas Instruments.
1022 tristate "TI TPS61050/61052 Boost Converters"
1026 select REGULATOR_FIXED_VOLTAGE
1028 This option enables a driver for the TP61050/TPS61052
1029 high-power "white LED driver". This boost converter is
1030 sometimes used for other things than white LEDs, and
1031 also contains a GPIO pin.
1034 tristate "TI TPS6501x Power Management chips"
1035 depends on I2C && GPIOLIB
1036 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1038 If you say yes here you get support for the TPS6501x series of
1039 Power Management chips. These include voltage regulators,
1040 lithium ion/polymer battery charging, and other features that
1041 are often used in portable devices like cell phones and cameras.
1043 This driver can also be built as a module. If so, the module
1044 will be called tps65010.
1047 tristate "TI TPS6507x Power Management / Touch Screen chips"
1051 If you say yes here you get support for the TPS6507x series of
1052 Power Management / Touch Screen chips. These include voltage
1053 regulators, lithium ion/polymer battery charging, touch screen
1054 and other features that are often used in portable devices.
1055 This driver can also be built as a module. If so, the module
1056 will be called tps6507x.
1058 config TPS65911_COMPARATOR
1062 bool "TI TPS65090 Power Management chips"
1068 If you say yes here you get support for the TPS65090 series of
1069 Power Management chips.
1070 This driver provides common support for accessing the device,
1071 additional drivers must be enabled in order to use the
1072 functionality of the device.
1075 tristate "TI TPS65217 Power Management / White LED chips"
1080 If you say yes here you get support for the TPS65217 series of
1081 Power Management / White LED chips.
1082 These include voltage regulators, lithium ion/polymer battery
1083 charger, wled and other features that are often used in portable
1086 This driver can also be built as a module. If so, the module
1087 will be called tps65217.
1090 tristate "TI TPS65218 Power Management chips"
1096 If you say yes here you get support for the TPS65218 series of
1097 Power Management chips.
1098 These include voltage regulators, gpio and other features
1099 that are often used in portable devices. Only regulator
1100 component is currently supported.
1102 This driver can also be built as a module. If so, the module
1103 will be called tps65218.
1106 bool "TI TPS6586x Power Management chips"
1111 If you say yes here you get support for the TPS6586X series of
1112 Power Management chips.
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.
1117 This driver can also be built as a module. If so, the module
1118 will be called tps6586x.
1121 bool "TI TPS65910 Power Management chip"
1123 depends on GPIOLIB || COMPILE_TEST
1129 if you say yes here you get support for the TPS65910 series of
1130 Power Management chips.
1133 bool "TI TPS65912 Power Management chip"
1137 If you say yes here you get support for the TPS65912 series of
1140 config MFD_TPS65912_I2C
1141 bool "TI TPS65912 Power Management chip with I2C"
1144 depends on I2C=y && GPIOLIB
1146 If you say yes here you get support for the TPS65912 series of
1147 PM chips with I2C interface.
1149 config MFD_TPS65912_SPI
1150 bool "TI TPS65912 Power Management chip with SPI"
1153 depends on SPI_MASTER && GPIOLIB
1155 If you say yes here you get support for the TPS65912 series of
1156 PM chips with SPI interface.
1159 bool "TI TPS80031/TPS80032 Power Management chips"
1165 If you say yes here you get support for the Texas Instruments
1166 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1167 Path and Battery Charger. The device provides five configurable
1168 step-down converters, 11 general purpose LDOs, USB OTG Module,
1169 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1170 Power Path from USB, 32K clock generator.
1173 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1178 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1179 This core driver provides register access and IRQ handling
1180 facilities, and registers devices for the various functions
1181 so that function-specific drivers can bind to them.
1183 These multi-function chips are found on many OMAP2 and OMAP3
1184 boards, providing power management, RTC, GPIO, keypad, a
1185 high speed USB OTG transceiver, an audio codec (on most
1186 versions) and many other features.
1188 config TWL4030_POWER
1189 bool "TI TWL4030 power resources"
1190 depends on TWL4030_CORE && ARM
1192 Say yes here if you want to use the power resources on the
1193 TWL4030 family chips. Most of these resources are regulators,
1194 which have a separate driver; some are control signals, such
1195 as clock request handshaking.
1197 This driver uses board-specific data to initialize the resources
1198 and load scripts controlling which resources are switched off/on
1199 or reset when a sleep, wakeup or warm reset event occurs.
1201 config MFD_TWL4030_AUDIO
1202 bool "TI TWL4030 Audio"
1203 depends on TWL4030_CORE
1208 bool "TI TWL6040 audio codec"
1215 Say yes here if you want support for Texas Instruments TWL6040 audio
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 (audio, vibra).
1222 bool "TI TWL92330/Menelaus PM chip"
1223 depends on I2C=y && ARCH_OMAP2
1225 If you say yes here you get support for the Texas Instruments
1226 TWL92330/Menelaus Power Management chip. This include voltage
1227 regulators, Dual slot memory card transceivers, real-time clock
1228 and other features that are often used in portable devices like
1229 cell phones and PDAs.
1231 config MFD_WL1273_CORE
1232 tristate "TI WL1273 FM radio"
1237 This is the core driver for the TI WL1273 FM radio. This MFD
1238 driver connects the radio-wl1273 V4L2 module and the wl1273
1242 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1247 Say yes here to enable support for National Semiconductor / TI
1248 LM3533 Lighting Power chips.
1250 This driver provides common support for accessing the device;
1251 additional drivers must be enabled in order to use the LED,
1252 backlight or ambient-light-sensor functionality of the device.
1254 config MFD_TIMBERDALE
1255 tristate "Timberdale FPGA"
1257 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1259 This is the core driver for the timberdale FPGA. This device is a
1260 multifunction device which exposes numerous platform devices.
1262 The timberdale FPGA can be found on the Intel Atom development board
1263 for in-vehicle infontainment, called Russellville.
1266 bool "Toshiba TC35892 and variants"
1271 Support for the Toshiba TC35892 and variants I/O Expander.
1273 This driver provides common support for accessing the device,
1274 additional drivers must be enabled in order to use the
1275 functionality of the device.
1282 bool "Toshiba T7L66XB"
1283 depends on ARM && HAVE_CLK
1287 Support for Toshiba Mobile IO Controller T7L66XB
1290 bool "Toshiba TC6387XB"
1291 depends on ARM && HAVE_CLK
1295 Support for Toshiba Mobile IO Controller TC6387XB
1298 bool "Toshiba TC6393XB"
1299 depends on ARM && HAVE_CLK
1304 Support for Toshiba Mobile IO Controller TC6393XB
1307 tristate "VIA VX855/VX875 integrated south bridge"
1311 Say yes here to enable support for various functions of the
1312 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1313 and/or vx855_gpio drivers for this to do anything useful.
1321 config MFD_ARIZONA_I2C
1322 tristate "Wolfson Microelectronics Arizona platform with I2C"
1328 Support for the Wolfson Microelectronics Arizona platform audio SoC
1329 core functionality controlled via I2C.
1331 config MFD_ARIZONA_SPI
1332 tristate "Wolfson Microelectronics Arizona platform with SPI"
1336 depends on SPI_MASTER
1338 Support for the Wolfson Microelectronics Arizona platform audio SoC
1339 core functionality controlled via I2C.
1342 bool "Wolfson Microelectronics WM5102"
1343 depends on MFD_ARIZONA
1345 Support for Wolfson Microelectronics WM5102 low power audio SoC
1348 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1349 depends on MFD_ARIZONA
1351 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1355 bool "Wolfson Microelectronics WM8997"
1356 depends on MFD_ARIZONA
1358 Support for Wolfson Microelectronics WM8997 low power audio SoC
1361 bool "Wolfson Microelectronics WM8400"
1366 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1367 CODEC. This driver provides common support for accessing
1368 the device, additional drivers must be enabled in order to use
1369 the functionality of the device.
1374 config MFD_WM831X_I2C
1375 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1382 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1383 when controlled using I2C. This driver provides common support
1384 for accessing the device, additional drivers must be enabled in
1385 order to use the functionality of the device.
1387 config MFD_WM831X_SPI
1388 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1393 depends on SPI_MASTER
1395 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1396 when controlled using SPI. This driver provides common support
1397 for accessing the device, additional drivers must be enabled in
1398 order to use the functionality of the device.
1403 config MFD_WM8350_I2C
1404 bool "Wolfson Microelectronics WM8350 with I2C"
1408 The WM8350 is an integrated audio and power management
1409 subsystem with watchdog and RTC functionality for embedded
1410 systems. This option enables core support for the WM8350 with
1411 I2C as the control interface. Additional options must be
1412 selected to enable support for the functionality of the chip.
1415 tristate "Wolfson Microelectronics WM8994"
1421 The WM8994 is a highly integrated hi-fi CODEC designed for
1422 smartphone applications. As well as audio functionality it
1423 has on board GPIO and regulator functionality which is
1424 supported via the relevant subsystems. This driver provides
1425 core support for the WM8994, in order to use the actual
1426 functionaltiy of the device other drivers must be enabled.
1429 tristate "Support for ST Microelectronics STw481x"
1430 depends on I2C && ARCH_NOMADIK
1434 Select this option to enable the STw481x chip driver used
1435 in various ST Microelectronics and ST-Ericsson embedded
1438 menu "Multimedia Capabilities Port drivers"
1439 depends on ARCH_SA1100
1446 tristate "Support SA11x0 MCP interface"
1447 depends on ARCH_SA1100
1452 tristate "Support for UCB1200 / UCB1300"
1453 depends on MCP_SA11X0
1456 config MCP_UCB1200_TS
1457 tristate "Touchscreen interface support"
1458 depends on MCP_UCB1200 && INPUT
1462 config MFD_VEXPRESS_SYSREG
1463 bool "Versatile Express System Registers"
1464 depends on VEXPRESS_CONFIG && GPIOLIB
1467 select GPIO_GENERIC_PLATFORM
1471 System Registers are the platform configuration block
1472 on the ARM Ltd. Versatile Express board.