2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
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 and AXP209.
78 This driver include only the core APIs. You have to select individual
79 components like regulators or the PEK (Power Enable Key) under the
83 tristate "ChromeOS Embedded Controller"
86 If you say Y here you get support for the ChromeOS Embedded
87 Controller (EC) providing keyboard, battery and power services.
88 You also need to enable the driver for the bus you are using. The
89 protocol for talking to the EC is defined by the bus driver.
91 config MFD_CROS_EC_I2C
92 tristate "ChromeOS Embedded Controller (I2C)"
93 depends on MFD_CROS_EC && I2C
96 If you say Y here, you get support for talking to the ChromeOS
97 EC through an I2C bus. This uses a simple byte-level protocol with
98 a checksum. Failing accesses will be retried three times to
101 config MFD_CROS_EC_SPI
102 tristate "ChromeOS Embedded Controller (SPI)"
103 depends on MFD_CROS_EC && SPI && OF
106 If you say Y here, you get support for talking to the ChromeOS EC
107 through a SPI bus, using a byte-level protocol. Since the EC's
108 response time cannot be guaranteed, we support ignoring
109 'pre-amble' bytes before the response actually starts.
113 depends on GPIOLIB && ARM
116 This driver supports the ASIC3 multifunction chip found on many
117 PDAs (mainly iPAQ and HTC based ones)
120 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
123 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
124 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
125 usually found on PXA processors-based platforms. This includes
126 the I2C driver and the core APIs _only_, you have to select
127 individual components like LCD backlight, voltage regulators,
128 LEDs and battery-charger under the corresponding menus.
134 config MFD_DA9052_SPI
135 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
139 depends on SPI_MASTER=y
141 Support for the Dialog Semiconductor DA9052 PMIC
142 when controlled using SPI. This driver provides common support
143 for accessing the device, additional drivers must be enabled in
144 order to use the functionality of the device.
146 config MFD_DA9052_I2C
147 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
153 Support for the Dialog Semiconductor DA9052 PMIC
154 when controlled using I2C. 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.
159 bool "Dialog Semiconductor DA9055 PMIC Support"
165 Say yes here for support of Dialog Semiconductor DA9055. This is
166 a Power Management IC. This driver provides common support for
167 accessing the device as well as the I2C interface to the chip itself.
168 Additional drivers must be enabled in order to use the functionality
171 This driver can be built as a module. If built as a module it will be
175 bool "Dialog Semiconductor DA9063 PMIC Support"
181 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
182 This includes the I2C driver and core APIs.
183 Additional drivers must be enabled in order to use the functionality
188 depends on (SPI_MASTER || I2C)
191 Enable support for the Freescale MC13783 and MC13892 PMICs.
192 This driver provides common support for accessing the device,
193 additional drivers must be enabled in order to use the
194 functionality of the device.
196 config MFD_MC13XXX_SPI
197 tristate "Freescale MC13783 and MC13892 SPI interface"
198 depends on SPI_MASTER
202 Select this if your MC13xxx is connected via an SPI bus.
204 config MFD_MC13XXX_I2C
205 tristate "Freescale MC13892 I2C interface"
210 Select this if your MC13xxx is connected via an I2C bus.
213 bool "HTC EGPIO support"
214 depends on GPIOLIB && ARM
216 This driver supports the CPLD egpio chip present on
217 several HTC phones. It provides basic support for input
218 pins, output pins, and irqs.
221 tristate "HTC PASIC3 LED/DS1WM chip support"
224 This core driver provides register access for the LED/DS1WM
225 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
226 HTC Magician devices, respectively. Actual functionality is
227 handled by the leds-pasic3 and ds1wm drivers.
230 bool "HTC I2C PLD chip support"
231 depends on I2C=y && GPIOLIB
233 If you say yes here you get support for the supposed CPLD
234 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
235 This device provides input and output GPIOs through an I2C
236 interface to one or more sub-chips.
239 tristate "Intel ICH LPC"
243 The LPC bridge function of the Intel ICH provides support for
244 many functional units. This driver provides needed support for
245 other drivers to control these functions, currently GPIO and
249 tristate "Intel SCH LPC"
253 LPC bridge function of the Intel SCH provides support for
254 System Management Bus and General Purpose I/O.
256 config INTEL_SOC_PMIC
257 bool "Support for Intel Atom SoC PMIC"
263 Select this option to enable support for the PMIC device
264 on some Intel SoC systems. The PMIC provides ADC, GPIO,
265 thermal, charger and related power management functions
268 config MFD_INTEL_MSIC
270 depends on INTEL_SCU_IPC
273 Select this option to enable access to Intel MSIC (Avatele
274 Passage) chip. This chip embeds audio, battery, GPIO, etc.
275 devices used in Intel Medfield platforms.
277 config MFD_IPAQ_MICRO
278 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
279 depends on SA1100_H3100 || SA1100_H3600
282 Select this to get support for the Microcontroller found in
283 the Compaq iPAQ handheld computers. This is an Atmel
284 AT90LS8535 microcontroller flashed with a special iPAQ
285 firmware using the custom protocol implemented in this driver.
287 config MFD_JANZ_CMODIO
288 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
292 This is the core driver for the Janz CMOD-IO PCI MODULbus
293 carrier board. This device is a PCI to MODULbus bridge which may
294 host many different types of MODULbus daughterboards, including
295 CAN and GPIO controllers.
297 config MFD_JZ4740_ADC
298 bool "Janz JZ4740 ADC core"
300 select GENERIC_IRQ_CHIP
301 depends on MACH_JZ4740
303 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
304 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
307 tristate "Kontron module PLD device"
310 This is the core driver for the PLD (Programmable Logic Device) found
311 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
312 device may provide functions like watchdog, GPIO, UART and I2C bus.
314 The following modules are supported:
317 * COMe-bPC2 (ETXexpress-PC)
318 * COMe-bSC# (ETXexpress-SC T#)
321 * COMe-cDC2 (microETXexpress-DC)
323 * COMe-cPC2 (microETXexpress-PC)
326 * COMe-mTT10 (nanoETXexpress-TT)
329 This driver can also be built as a module. If so, the module
330 will be called kempld-core.
333 tristate "Marvell 88PM800"
339 This supports for Marvell 88PM800 Power Management IC.
340 This includes the I2C driver and the core APIs _only_, you have to
341 select individual components like voltage regulators, RTC and
342 battery-charger under the corresponding menus.
345 tristate "Marvell 88PM805"
351 This supports for Marvell 88PM805 Power Management IC. This includes
352 the I2C driver and the core APIs _only_, you have to select individual
353 components like codec device, headset/Mic device under the
357 bool "Marvell 88PM8606/88PM8607"
362 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
363 This includes the I2C driver and the core APIs _only_, you have to
364 select individual components like voltage regulators, RTC and
365 battery-charger under the corresponding menus.
368 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
375 Say yes here to add support for Maxim Semiconductor MAX14577 and
376 MAX77836 Micro-USB ICs with battery charger.
377 This driver provides common support for accessing the device;
378 additional drivers must be enabled in order to use the functionality
382 bool "Maxim Semiconductor MAX77686 PMIC Support"
388 Say yes here to add support for Maxim Semiconductor MAX77686.
389 This is a Power Management IC with RTC on chip.
390 This driver provides common support for accessing the device;
391 additional drivers must be enabled in order to use the functionality
395 bool "Maxim Semiconductor MAX77693 PMIC Support"
401 Say yes here to add support for Maxim Semiconductor MAX77693.
402 This is a companion Power Management IC with Flash, Haptic, Charger,
403 and MUIC(Micro USB Interface Controller) controls on chip.
404 This driver provides common support for accessing the device;
405 additional drivers must be enabled in order to use the functionality
409 tristate "Maxim Semiconductor MAX8907 PMIC Support"
415 Say yes here to add support for Maxim Semiconductor MAX8907. This is
416 a Power Management IC. This driver provides common support for
417 accessing the device; additional drivers must be enabled in order
418 to use the functionality of the device.
421 bool "Maxim Semiconductor MAX8925 PMIC Support"
425 Say yes here to add support for Maxim Semiconductor MAX8925. This is
426 a Power Management IC. This driver provides common support for
427 accessing the device, additional drivers must be enabled in order
428 to use the functionality of the device.
431 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
436 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
437 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
438 MUIC controls on chip.
439 This driver provides common support for accessing the device;
440 additional drivers must be enabled in order to use the functionality
444 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
449 Say yes here to add support for Maxim Semiconductor MAX8998 and
450 National Semiconductor LP3974. This is a Power Management IC.
451 This driver provides common support for accessing the device,
452 additional drivers must be enabled in order to use the functionality
456 bool "Motorola EZXPCAP Support"
457 depends on SPI_MASTER
459 This enables the PCAP ASIC present on EZX Phones. This is
460 needed for MMC, TouchScreen, Sound, USB, etc..
462 config MFD_VIPERBOARD
463 tristate "Nano River Technologies Viperboard"
468 Say yes here if you want support for Nano River Technologies
470 There are mfd cell drivers available for i2c master, adc and
471 both gpios found on the board. The spi part does not yet
473 You need to select the mfd cell drivers separately.
474 The drivers do not support all features the board exposes.
477 tristate "Nokia Retu and Tahvo multi-function device"
482 Retu and Tahvo are a multi-function devices found on Nokia
483 Internet Tablets (770, N800 and N810).
486 tristate "NXP PCF50633"
490 Say yes here if you have NXP PCF50633 chip on your board.
491 This core driver provides register access and IRQ handling
492 facilities, and registers devices for the various functions
493 so that function-specific drivers can bind to them.
496 tristate "NXP PCF50633 ADC"
497 depends on MFD_PCF50633
499 Say yes here if you want to include support for ADC in the
503 tristate "NXP PCF50633 GPIO"
504 depends on MFD_PCF50633
506 Say yes here if you want to include support GPIO for pins on
510 tristate "Philips UCB1400 Core driver"
514 This enables support for the Philips UCB1400 core functions.
515 The UCB1400 is an AC97 audio codec.
517 To compile this driver as a module, choose M here: the
518 module will be called ucb1400_core.
523 config MFD_PM8921_CORE
524 tristate "Qualcomm PM8921 PMIC chip"
525 depends on (ARM || HEXAGON)
531 If you say yes to this option, support will be included for the
532 built-in PM8921 PMIC chip.
534 This is required if your board has a PM8921 and uses its features,
535 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
537 Say M here if you want to include support for PM8921 chip as a module.
538 This will build a module called "pm8921-core".
541 tristate "RDC R-321x southbridge"
545 Say yes here if you want to have support for the RDC R-321x SoC
546 southbridge which provides access to GPIOs and Watchdog using the
547 southbridge PCI device configuration space.
550 tristate "Realtek PCI-E card reader"
554 This supports for Realtek PCI-Express card reader including rts5209,
555 rts5229, rtl8411, etc. Realtek card reader supports access to many
556 types of memory cards, such as Memory Stick, Memory Stick Pro,
557 Secure Digital and MultiMediaCard.
560 tristate "Realtek USB card reader"
564 Select this option to get support for Realtek USB 2.0 card readers
565 including RTS5129, RTS5139, RTS5179 and RTS5170.
566 Realtek card reader supports access to many types of memory cards,
567 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
570 bool "Ricoh RC5T583 Power Management system device"
575 Select this option to get support for the RICOH583 Power
576 Management system device.
577 This driver provides common support for accessing the device
578 through i2c interface. The device supports multiple sub-devices
579 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
580 Additional drivers must be enabled in order to use the
581 different functionality of the device.
584 bool "SAMSUNG Electronics PMIC Series Support"
590 Support for the Samsung Electronics MFD series.
591 This driver provides common support for accessing the device,
592 additional drivers must be enabled in order to use the functionality
595 config MFD_SI476X_CORE
596 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
601 This is the core driver for the SI476x series of AM/FM
602 radio. This MFD driver connects the radio-si476x V4L2 module
603 and the si476x audio codec.
605 To compile this driver as a module, choose M here: the
606 module will be called si476x-core.
609 tristate "Silicon Motion SM501"
611 This is the core driver for the Silicon Motion SM501 multimedia
612 companion chip. This device is a multifunction device which may
613 provide numerous interfaces including USB host controller, USB gadget,
614 asynchronous serial ports, audio functions, and a dual display video
615 interface. The device may be connected by PCI or local bus with
616 varying functions enabled.
618 config MFD_SM501_GPIO
619 bool "Export GPIO via GPIO layer"
620 depends on MFD_SM501 && GPIOLIB
622 This option uses the gpio library layer to export the 64 GPIO
623 lines on the SM501. The platform data is used to supply the
624 base number for the first GPIO line to register.
627 bool "SMSC ECE1099 series chips"
632 If you say yes here you get support for the
633 ece1099 chips from SMSC.
635 To compile this driver as a module, choose M here: the
636 module will be called smsc.
639 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
640 default y if ARCH_U300 || ARCH_U8500
642 Say yes here if you have the ABX500 Mixed Signal IC family
643 chips. This core driver expose register access functions.
644 Functionality specific drivers using these functions can
645 remain unchanged when IC changes. Binding of the functions to
646 actual register access is done by the IC core driver.
649 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
650 depends on I2C=y && ABX500_CORE
652 default y if ARCH_U300
654 Select this to enable the AB3100 Mixed Signal IC core
655 functionality. This connects to a AB3100 on the I2C bus
656 and expose a number of symbols needed for dependent devices
657 to read and write registers and subscribe to events from
658 this multi-functional IC. This is needed to use other features
659 of the AB3100 such as battery-backed RTC, charging control,
660 LEDs, vibrator, system power and temperature, power management
664 tristate "ST-Ericsson AB3100 OTP functions"
665 depends on AB3100_CORE
666 default y if AB3100_CORE
668 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
669 programmable memory) support. This exposes a sysfs file to read
673 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
674 depends on ABX500_CORE && MFD_DB8500_PRCMU
679 Select this option to enable access to AB8500 power management
680 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
681 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
682 the irq_chip parts for handling the Mixed Signal chip events.
683 This chip embeds various other multimedia funtionalities as well.
686 bool "Enable debug info via debugfs"
687 depends on AB8500_GPADC && DEBUG_FS
688 default y if DEBUG_FS
690 Select this option if you want debug information using the debug
694 bool "ST-Ericsson AB8500 GPADC driver"
695 depends on AB8500_CORE && REGULATOR_AB8500
698 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
700 config MFD_DB8500_PRCMU
701 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
702 depends on UX500_SOC_DB8500
705 Select this option to enable support for the DB8500 Power Reset
706 and Control Management Unit. This is basically an autonomous
707 system controller running an XP70 microprocessor, which is accessed
708 through a register map.
711 bool "STMicroelectronics STMPE"
712 depends on (I2C=y || SPI_MASTER=y)
716 Support for the STMPE family of I/O Expanders from
719 Currently supported devices are:
721 STMPE811: GPIO, Touchscreen
722 STMPE1601: GPIO, Keypad
723 STMPE1801: GPIO, Keypad
724 STMPE2401: GPIO, Keypad
725 STMPE2403: GPIO, Keypad
727 This driver provides common support for accessing the device,
728 additional drivers must be enabled in order to use the functionality
729 of the device. Currently available sub drivers are:
733 Touchscreen: stmpe-ts
735 menu "STMicroelectronics STMPE Interface Drivers"
739 bool "STMicroelectronics STMPE I2C Interface"
743 This is used to enable I2C interface of STMPE
746 bool "STMicroelectronics STMPE SPI Interface"
747 depends on SPI_MASTER
749 This is used to enable SPI interface of STMPE
753 bool "STMicroelectronics STA2X11"
758 config MFD_SUN6I_PRCM
759 bool "Allwinner A31 PRCM controller"
760 depends on ARCH_SUNXI
763 Support for the PRCM (Power/Reset/Clock Management) unit available
767 bool "System Controller Register R/W Based on Regmap"
770 Select this option to enable accessing system control registers
773 config MFD_DAVINCI_VOICECODEC
778 config MFD_TI_AM335X_TSCADC
779 tristate "TI ADC / Touch Screen chip support"
784 If you say yes here you get support for Texas Instruments series
785 of Touch Screen /ADC chips.
786 To compile this driver as a module, choose M here: the
787 module will be called ti_am335x_tscadc.
789 config MFD_DM355EVM_MSP
790 bool "TI DaVinci DM355 EVM microcontroller"
791 depends on I2C=y && MACH_DAVINCI_DM355_EVM
793 This driver supports the MSP430 microcontroller used on these
794 boards. MSP430 firmware manages resets and power sequencing,
795 inputs from buttons and the IR remote, LEDs, an RTC, and more.
798 tristate "TI/National Semiconductor LP3943 MFD Driver"
803 Support for the TI/National Semiconductor LP3943.
804 This driver consists of GPIO and PWM drivers.
805 With these functionalities, it can be used for LED string control or
806 general usage such like a GPIO controller and a PWM controller.
809 bool "TI LP8788 Power Management Unit Driver"
815 TI LP8788 PMU supports regulators, battery charger, RTC,
816 ADC, backlight driver and current sinks.
818 config MFD_OMAP_USB_HOST
819 bool "TI OMAP USBHS core and TLL driver"
820 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
823 This is the core driver for the OAMP EHCI and OHCI drivers.
824 This MFD driver does the required setup functionalities for
825 OMAP USB Host drivers.
828 bool "TI Palmas series chips"
834 If you say yes here you get support for the Palmas
835 series of PMIC chips from Texas Instruments.
838 tristate "TI TPS61050/61052 Boost Converters"
842 select REGULATOR_FIXED_VOLTAGE
844 This option enables a driver for the TP61050/TPS61052
845 high-power "white LED driver". This boost converter is
846 sometimes used for other things than white LEDs, and
847 also contains a GPIO pin.
850 tristate "TI TPS6501x Power Management chips"
851 depends on I2C && GPIOLIB
852 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
854 If you say yes here you get support for the TPS6501x series of
855 Power Management chips. These include voltage regulators,
856 lithium ion/polymer battery charging, and other features that
857 are often used in portable devices like cell phones and cameras.
859 This driver can also be built as a module. If so, the module
860 will be called tps65010.
863 tristate "TI TPS6507x Power Management / Touch Screen chips"
867 If you say yes here you get support for the TPS6507x series of
868 Power Management / Touch Screen chips. These include voltage
869 regulators, lithium ion/polymer battery charging, touch screen
870 and other features that are often used in portable devices.
871 This driver can also be built as a module. If so, the module
872 will be called tps6507x.
874 config TPS65911_COMPARATOR
878 bool "TI TPS65090 Power Management chips"
884 If you say yes here you get support for the TPS65090 series of
885 Power Management chips.
886 This driver provides common support for accessing the device,
887 additional drivers must be enabled in order to use the
888 functionality of the device.
891 tristate "TI TPS65217 Power Management / White LED chips"
896 If you say yes here you get support for the TPS65217 series of
897 Power Management / White LED chips.
898 These include voltage regulators, lithium ion/polymer battery
899 charger, wled and other features that are often used in portable
902 This driver can also be built as a module. If so, the module
903 will be called tps65217.
906 tristate "TI TPS65218 Power Management chips"
912 If you say yes here you get support for the TPS65218 series of
913 Power Management chips.
914 These include voltage regulators, gpio and other features
915 that are often used in portable devices. Only regulator
916 component is currently supported.
918 This driver can also be built as a module. If so, the module
919 will be called tps65218.
922 bool "TI TPS6586x Power Management chips"
927 If you say yes here you get support for the TPS6586X series of
928 Power Management chips.
929 This driver provides common support for accessing the device,
930 additional drivers must be enabled in order to use the
931 functionality of the device.
933 This driver can also be built as a module. If so, the module
934 will be called tps6586x.
937 bool "TI TPS65910 Power Management chip"
938 depends on I2C=y && GPIOLIB
944 if you say yes here you get support for the TPS65910 series of
945 Power Management chips.
948 bool "TI TPS65912 Power Management chip"
952 If you say yes here you get support for the TPS65912 series of
955 config MFD_TPS65912_I2C
956 bool "TI TPS65912 Power Management chip with I2C"
959 depends on I2C=y && GPIOLIB
961 If you say yes here you get support for the TPS65912 series of
962 PM chips with I2C interface.
964 config MFD_TPS65912_SPI
965 bool "TI TPS65912 Power Management chip with SPI"
968 depends on SPI_MASTER && GPIOLIB
970 If you say yes here you get support for the TPS65912 series of
971 PM chips with SPI interface.
974 bool "TI TPS80031/TPS80032 Power Management chips"
980 If you say yes here you get support for the Texas Instruments
981 TPS80031/ TPS80032 Fully Integrated Power Management with Power
982 Path and Battery Charger. The device provides five configurable
983 step-down converters, 11 general purpose LDOs, USB OTG Module,
984 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
985 Power Path from USB, 32K clock generator.
988 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
993 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
994 This core driver provides register access and IRQ handling
995 facilities, and registers devices for the various functions
996 so that function-specific drivers can bind to them.
998 These multi-function chips are found on many OMAP2 and OMAP3
999 boards, providing power management, RTC, GPIO, keypad, a
1000 high speed USB OTG transceiver, an audio codec (on most
1001 versions) and many other features.
1003 config TWL4030_POWER
1004 bool "TI TWL4030 power resources"
1005 depends on TWL4030_CORE && ARM
1007 Say yes here if you want to use the power resources on the
1008 TWL4030 family chips. Most of these resources are regulators,
1009 which have a separate driver; some are control signals, such
1010 as clock request handshaking.
1012 This driver uses board-specific data to initialize the resources
1013 and load scripts controlling which resources are switched off/on
1014 or reset when a sleep, wakeup or warm reset event occurs.
1016 config MFD_TWL4030_AUDIO
1017 bool "TI TWL4030 Audio"
1018 depends on TWL4030_CORE
1023 bool "TI TWL6040 audio codec"
1030 Say yes here if you want support for Texas Instruments TWL6040 audio
1032 This driver provides common support for accessing the device,
1033 additional drivers must be enabled in order to use the
1034 functionality of the device (audio, vibra).
1037 bool "TI TWL92330/Menelaus PM chip"
1038 depends on I2C=y && ARCH_OMAP2
1040 If you say yes here you get support for the Texas Instruments
1041 TWL92330/Menelaus Power Management chip. This include voltage
1042 regulators, Dual slot memory card transceivers, real-time clock
1043 and other features that are often used in portable devices like
1044 cell phones and PDAs.
1046 config MFD_WL1273_CORE
1047 tristate "TI WL1273 FM radio"
1052 This is the core driver for the TI WL1273 FM radio. This MFD
1053 driver connects the radio-wl1273 V4L2 module and the wl1273
1057 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1062 Say yes here to enable support for National Semiconductor / TI
1063 LM3533 Lighting Power chips.
1065 This driver provides common support for accessing the device;
1066 additional drivers must be enabled in order to use the LED,
1067 backlight or ambient-light-sensor functionality of the device.
1069 config MFD_TIMBERDALE
1070 tristate "Timberdale FPGA"
1072 depends on PCI && GPIOLIB
1074 This is the core driver for the timberdale FPGA. This device is a
1075 multifunction device which exposes numerous platform devices.
1077 The timberdale FPGA can be found on the Intel Atom development board
1078 for in-vehicle infontainment, called Russellville.
1081 bool "Toshiba TC35892 and variants"
1085 Support for the Toshiba TC35892 and variants I/O Expander.
1087 This driver provides common support for accessing the device,
1088 additional drivers must be enabled in order to use the
1089 functionality of the device.
1096 bool "Toshiba T7L66XB"
1097 depends on ARM && HAVE_CLK
1101 Support for Toshiba Mobile IO Controller T7L66XB
1104 bool "Toshiba TC6387XB"
1105 depends on ARM && HAVE_CLK
1109 Support for Toshiba Mobile IO Controller TC6387XB
1112 bool "Toshiba TC6393XB"
1113 depends on ARM && HAVE_CLK
1118 Support for Toshiba Mobile IO Controller TC6393XB
1121 tristate "VIA VX855/VX875 integrated south bridge"
1125 Say yes here to enable support for various functions of the
1126 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1127 and/or vx855_gpio drivers for this to do anything useful.
1135 config MFD_ARIZONA_I2C
1136 tristate "Wolfson Microelectronics Arizona platform with I2C"
1142 Support for the Wolfson Microelectronics Arizona platform audio SoC
1143 core functionality controlled via I2C.
1145 config MFD_ARIZONA_SPI
1146 tristate "Wolfson Microelectronics Arizona platform with SPI"
1150 depends on SPI_MASTER
1152 Support for the Wolfson Microelectronics Arizona platform audio SoC
1153 core functionality controlled via I2C.
1156 bool "Wolfson Microelectronics WM5102"
1157 depends on MFD_ARIZONA
1159 Support for Wolfson Microelectronics WM5102 low power audio SoC
1162 bool "Wolfson Microelectronics WM5110"
1163 depends on MFD_ARIZONA
1165 Support for Wolfson Microelectronics WM5110 low power audio SoC
1168 bool "Wolfson Microelectronics WM8997"
1169 depends on MFD_ARIZONA
1171 Support for Wolfson Microelectronics WM8997 low power audio SoC
1174 bool "Wolfson Microelectronics WM8400"
1179 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1180 CODEC. This driver provides common support for accessing
1181 the device, additional drivers must be enabled in order to use
1182 the functionality of the device.
1187 config MFD_WM831X_I2C
1188 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1195 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1196 when controlled using I2C. This driver provides common support
1197 for accessing the device, additional drivers must be enabled in
1198 order to use the functionality of the device.
1200 config MFD_WM831X_SPI
1201 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1206 depends on SPI_MASTER
1208 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1209 when controlled using SPI. This driver provides common support
1210 for accessing the device, additional drivers must be enabled in
1211 order to use the functionality of the device.
1216 config MFD_WM8350_I2C
1217 bool "Wolfson Microelectronics WM8350 with I2C"
1221 The WM8350 is an integrated audio and power management
1222 subsystem with watchdog and RTC functionality for embedded
1223 systems. This option enables core support for the WM8350 with
1224 I2C as the control interface. Additional options must be
1225 selected to enable support for the functionality of the chip.
1228 bool "Wolfson Microelectronics WM8994"
1234 The WM8994 is a highly integrated hi-fi CODEC designed for
1235 smartphone applicatiosn. As well as audio functionality it
1236 has on board GPIO and regulator functionality which is
1237 supported via the relevant subsystems. This driver provides
1238 core support for the WM8994, in order to use the actual
1239 functionaltiy of the device other drivers must be enabled.
1242 tristate "Support for ST Microelectronics STw481x"
1243 depends on I2C && ARCH_NOMADIK
1247 Select this option to enable the STw481x chip driver used
1248 in various ST Microelectronics and ST-Ericsson embedded
1251 menu "Multimedia Capabilities Port drivers"
1252 depends on ARCH_SA1100
1259 tristate "Support SA11x0 MCP interface"
1260 depends on ARCH_SA1100
1265 tristate "Support for UCB1200 / UCB1300"
1266 depends on MCP_SA11X0
1269 config MCP_UCB1200_TS
1270 tristate "Touchscreen interface support"
1271 depends on MCP_UCB1200 && INPUT
1275 config MFD_VEXPRESS_SYSREG
1276 bool "Versatile Express System Registers"
1277 depends on VEXPRESS_CONFIG && GPIOLIB
1280 select GPIO_GENERIC_PLATFORM
1284 System Registers are the platform configuration block
1285 on the ARM Ltd. Versatile Express board.