2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
28 Support for the AS3711 PMIC from AMS
31 bool "ams AS3722 Power Management IC"
35 depends on I2C=y && OF
37 The ams AS3722 is a compact system PMU suitable for mobile phones,
38 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
39 controllers, 11 LDOs, RTC, automatic battery, temperature and
40 over current monitoring, GPIOs, ADC and a watchdog.
43 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
46 Say yes here to add support for Analog Devices AD5520 and ADP5501,
47 Multifunction Power Management IC. This includes
48 the I2C driver and the core APIs _only_, you have to select
49 individual components like LCD backlight, LEDs, GPIOs and Kepad
50 under the corresponding menus.
52 config MFD_AAT2870_CORE
53 bool "AnalogicTech AAT2870"
55 depends on I2C=y && GPIOLIB
57 If you say yes here you get support for the AAT2870.
58 This driver provides common support for accessing the device,
59 additional drivers must be enabled in order to use the
60 functionality of the device.
63 tristate "Broadcom BCM590xx PMUs"
68 Support for the BCM590xx PMUs from Broadcom
71 bool "X-Powers AXP20X"
77 If you say Y here you get support for the X-Powers AXP202 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)
192 Enable support for the Freescale MC13783 and MC13892 PMICs.
193 This driver provides common support for accessing the device,
194 additional drivers must be enabled in order to use the
195 functionality of the device.
197 config MFD_MC13XXX_SPI
198 tristate "Freescale MC13783 and MC13892 SPI interface"
199 depends on SPI_MASTER
203 Select this if your MC13xxx is connected via an SPI bus.
205 config MFD_MC13XXX_I2C
206 tristate "Freescale MC13892 I2C interface"
211 Select this if your MC13xxx is connected via an I2C bus.
214 bool "HTC EGPIO support"
215 depends on GPIOLIB && ARM
217 This driver supports the CPLD egpio chip present on
218 several HTC phones. It provides basic support for input
219 pins, output pins, and irqs.
222 tristate "HTC PASIC3 LED/DS1WM chip support"
225 This core driver provides register access for the LED/DS1WM
226 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
227 HTC Magician devices, respectively. Actual functionality is
228 handled by the leds-pasic3 and ds1wm drivers.
231 bool "HTC I2C PLD chip support"
232 depends on I2C=y && GPIOLIB
234 If you say yes here you get support for the supposed CPLD
235 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
236 This device provides input and output GPIOs through an I2C
237 interface to one or more sub-chips.
240 tristate "Intel ICH LPC"
244 The LPC bridge function of the Intel ICH provides support for
245 many functional units. This driver provides needed support for
246 other drivers to control these functions, currently GPIO and
250 tristate "Intel SCH LPC"
254 LPC bridge function of the Intel SCH provides support for
255 System Management Bus and General Purpose I/O.
257 config INTEL_SOC_PMIC
258 bool "Support for Intel Atom SoC PMIC"
264 Select this option to enable support for the PMIC device
265 on some Intel SoC systems. The PMIC provides ADC, GPIO,
266 thermal, charger and related power management functions
269 config MFD_INTEL_MSIC
271 depends on INTEL_SCU_IPC
274 Select this option to enable access to Intel MSIC (Avatele
275 Passage) chip. This chip embeds audio, battery, GPIO, etc.
276 devices used in Intel Medfield platforms.
278 config MFD_IPAQ_MICRO
279 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
280 depends on SA1100_H3100 || SA1100_H3600
283 Select this to get support for the Microcontroller found in
284 the Compaq iPAQ handheld computers. This is an Atmel
285 AT90LS8535 microcontroller flashed with a special iPAQ
286 firmware using the custom protocol implemented in this driver.
288 config MFD_JANZ_CMODIO
289 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
293 This is the core driver for the Janz CMOD-IO PCI MODULbus
294 carrier board. This device is a PCI to MODULbus bridge which may
295 host many different types of MODULbus daughterboards, including
296 CAN and GPIO controllers.
298 config MFD_JZ4740_ADC
299 bool "Janz JZ4740 ADC core"
301 select GENERIC_IRQ_CHIP
302 depends on MACH_JZ4740
304 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
305 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
308 tristate "Kontron module PLD device"
311 This is the core driver for the PLD (Programmable Logic Device) found
312 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
313 device may provide functions like watchdog, GPIO, UART and I2C bus.
315 The following modules are supported:
318 * COMe-bPC2 (ETXexpress-PC)
319 * COMe-bSC# (ETXexpress-SC T#)
322 * COMe-cDC2 (microETXexpress-DC)
324 * COMe-cPC2 (microETXexpress-PC)
327 * COMe-mTT10 (nanoETXexpress-TT)
330 This driver can also be built as a module. If so, the module
331 will be called kempld-core.
334 tristate "Marvell 88PM800"
340 This supports for Marvell 88PM800 Power Management IC.
341 This includes the I2C driver and the core APIs _only_, you have to
342 select individual components like voltage regulators, RTC and
343 battery-charger under the corresponding menus.
346 tristate "Marvell 88PM805"
352 This supports for Marvell 88PM805 Power Management IC. This includes
353 the I2C driver and the core APIs _only_, you have to select individual
354 components like codec device, headset/Mic device under the
358 bool "Marvell 88PM8606/88PM8607"
363 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
364 This includes the I2C driver and the core APIs _only_, you have to
365 select individual components like voltage regulators, RTC and
366 battery-charger under the corresponding menus.
369 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
376 Say yes here to add support for Maxim Semiconductor MAX14577 and
377 MAX77836 Micro-USB ICs with battery charger.
378 This driver provides common support for accessing the device;
379 additional drivers must be enabled in order to use the functionality
383 bool "Maxim Semiconductor MAX77686 PMIC Support"
389 Say yes here to add support for Maxim Semiconductor MAX77686.
390 This is a Power Management IC with RTC on chip.
391 This driver provides common support for accessing the device;
392 additional drivers must be enabled in order to use the functionality
396 bool "Maxim Semiconductor MAX77693 PMIC Support"
402 Say yes here to add support for Maxim Semiconductor MAX77693.
403 This is a companion Power Management IC with Flash, Haptic, Charger,
404 and MUIC(Micro USB Interface Controller) controls on chip.
405 This driver provides common support for accessing the device;
406 additional drivers must be enabled in order to use the functionality
410 tristate "Maxim Semiconductor MAX8907 PMIC Support"
416 Say yes here to add support for Maxim Semiconductor MAX8907. This is
417 a Power Management IC. This driver provides common support for
418 accessing the device; additional drivers must be enabled in order
419 to use the functionality of the device.
422 bool "Maxim Semiconductor MAX8925 PMIC Support"
426 Say yes here to add support for Maxim Semiconductor MAX8925. This is
427 a Power Management IC. This driver provides common support for
428 accessing the device, additional drivers must be enabled in order
429 to use the functionality of the device.
432 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
437 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
438 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
439 MUIC controls 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 MAX8998/National LP3974 PMIC Support"
450 Say yes here to add support for Maxim Semiconductor MAX8998 and
451 National Semiconductor LP3974. This is a Power Management IC.
452 This driver provides common support for accessing the device,
453 additional drivers must be enabled in order to use the functionality
457 bool "Motorola EZXPCAP Support"
458 depends on SPI_MASTER
460 This enables the PCAP ASIC present on EZX Phones. This is
461 needed for MMC, TouchScreen, Sound, USB, etc..
463 config MFD_VIPERBOARD
464 tristate "Nano River Technologies Viperboard"
469 Say yes here if you want support for Nano River Technologies
471 There are mfd cell drivers available for i2c master, adc and
472 both gpios found on the board. The spi part does not yet
474 You need to select the mfd cell drivers separately.
475 The drivers do not support all features the board exposes.
478 tristate "Nokia Retu and Tahvo multi-function device"
483 Retu and Tahvo are a multi-function devices found on Nokia
484 Internet Tablets (770, N800 and N810).
487 tristate "NXP PCF50633"
491 Say yes here if you have NXP PCF50633 chip on your board.
492 This core driver provides register access and IRQ handling
493 facilities, and registers devices for the various functions
494 so that function-specific drivers can bind to them.
497 tristate "NXP PCF50633 ADC"
498 depends on MFD_PCF50633
500 Say yes here if you want to include support for ADC in the
504 tristate "NXP PCF50633 GPIO"
505 depends on MFD_PCF50633
507 Say yes here if you want to include support GPIO for pins on
511 tristate "Philips UCB1400 Core driver"
515 This enables support for the Philips UCB1400 core functions.
516 The UCB1400 is an AC97 audio codec.
518 To compile this driver as a module, choose M here: the
519 module will be called ucb1400_core.
524 config MFD_PM8921_CORE
525 tristate "Qualcomm PM8921 PMIC chip"
526 depends on (ARM || HEXAGON)
532 If you say yes to this option, support will be included for the
533 built-in PM8921 PMIC chip.
535 This is required if your board has a PM8921 and uses its features,
536 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
538 Say M here if you want to include support for PM8921 chip as a module.
539 This will build a module called "pm8921-core".
542 tristate "RDC R-321x southbridge"
546 Say yes here if you want to have support for the RDC R-321x SoC
547 southbridge which provides access to GPIOs and Watchdog using the
548 southbridge PCI device configuration space.
551 tristate "Realtek PCI-E card reader"
555 This supports for Realtek PCI-Express card reader including rts5209,
556 rts5229, rtl8411, etc. Realtek card reader supports access to many
557 types of memory cards, such as Memory Stick, Memory Stick Pro,
558 Secure Digital and MultiMediaCard.
561 tristate "Realtek USB card reader"
565 Select this option to get support for Realtek USB 2.0 card readers
566 including RTS5129, RTS5139, RTS5179 and RTS5170.
567 Realtek card reader supports access to many types of memory cards,
568 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
571 bool "Ricoh RC5T583 Power Management system device"
576 Select this option to get support for the RICOH583 Power
577 Management system device.
578 This driver provides common support for accessing the device
579 through i2c interface. The device supports multiple sub-devices
580 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
581 Additional drivers must be enabled in order to use the
582 different functionality of the device.
585 bool "SAMSUNG Electronics PMIC Series Support"
592 Support for the Samsung Electronics MFD series.
593 This driver provides common support for accessing the device,
594 additional drivers must be enabled in order to use the functionality
597 config MFD_SI476X_CORE
598 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
603 This is the core driver for the SI476x series of AM/FM
604 radio. This MFD driver connects the radio-si476x V4L2 module
605 and the si476x audio codec.
607 To compile this driver as a module, choose M here: the
608 module will be called si476x-core.
611 tristate "Silicon Motion SM501"
613 This is the core driver for the Silicon Motion SM501 multimedia
614 companion chip. This device is a multifunction device which may
615 provide numerous interfaces including USB host controller, USB gadget,
616 asynchronous serial ports, audio functions, and a dual display video
617 interface. The device may be connected by PCI or local bus with
618 varying functions enabled.
620 config MFD_SM501_GPIO
621 bool "Export GPIO via GPIO layer"
622 depends on MFD_SM501 && GPIOLIB
624 This option uses the gpio library layer to export the 64 GPIO
625 lines on the SM501. The platform data is used to supply the
626 base number for the first GPIO line to register.
629 bool "SMSC ECE1099 series chips"
634 If you say yes here you get support for the
635 ece1099 chips from SMSC.
637 To compile this driver as a module, choose M here: the
638 module will be called smsc.
641 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
642 default y if ARCH_U300 || ARCH_U8500
644 Say yes here if you have the ABX500 Mixed Signal IC family
645 chips. This core driver expose register access functions.
646 Functionality specific drivers using these functions can
647 remain unchanged when IC changes. Binding of the functions to
648 actual register access is done by the IC core driver.
651 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
652 depends on I2C=y && ABX500_CORE
654 default y if ARCH_U300
656 Select this to enable the AB3100 Mixed Signal IC core
657 functionality. This connects to a AB3100 on the I2C bus
658 and expose a number of symbols needed for dependent devices
659 to read and write registers and subscribe to events from
660 this multi-functional IC. This is needed to use other features
661 of the AB3100 such as battery-backed RTC, charging control,
662 LEDs, vibrator, system power and temperature, power management
666 tristate "ST-Ericsson AB3100 OTP functions"
667 depends on AB3100_CORE
668 default y if AB3100_CORE
670 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
671 programmable memory) support. This exposes a sysfs file to read
675 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
676 depends on ABX500_CORE && MFD_DB8500_PRCMU
681 Select this option to enable access to AB8500 power management
682 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
683 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
684 the irq_chip parts for handling the Mixed Signal chip events.
685 This chip embeds various other multimedia funtionalities as well.
688 bool "Enable debug info via debugfs"
689 depends on AB8500_GPADC && DEBUG_FS
690 default y if DEBUG_FS
692 Select this option if you want debug information using the debug
696 bool "ST-Ericsson AB8500 GPADC driver"
697 depends on AB8500_CORE && REGULATOR_AB8500
700 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
702 config MFD_DB8500_PRCMU
703 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
704 depends on UX500_SOC_DB8500
707 Select this option to enable support for the DB8500 Power Reset
708 and Control Management Unit. This is basically an autonomous
709 system controller running an XP70 microprocessor, which is accessed
710 through a register map.
713 bool "STMicroelectronics STMPE"
714 depends on (I2C=y || SPI_MASTER=y)
718 Support for the STMPE family of I/O Expanders from
721 Currently supported devices are:
723 STMPE811: GPIO, Touchscreen
724 STMPE1601: GPIO, Keypad
725 STMPE1801: GPIO, Keypad
726 STMPE2401: GPIO, Keypad
727 STMPE2403: GPIO, Keypad
729 This driver provides common support for accessing the device,
730 additional drivers must be enabled in order to use the functionality
731 of the device. Currently available sub drivers are:
735 Touchscreen: stmpe-ts
737 menu "STMicroelectronics STMPE Interface Drivers"
741 bool "STMicroelectronics STMPE I2C Interface"
745 This is used to enable I2C interface of STMPE
748 bool "STMicroelectronics STMPE SPI Interface"
749 depends on SPI_MASTER
751 This is used to enable SPI interface of STMPE
755 bool "STMicroelectronics STA2X11"
760 config MFD_SUN6I_PRCM
761 bool "Allwinner A31 PRCM controller"
762 depends on ARCH_SUNXI
765 Support for the PRCM (Power/Reset/Clock Management) unit available
769 bool "System Controller Register R/W Based on Regmap"
772 Select this option to enable accessing system control registers
775 config MFD_DAVINCI_VOICECODEC
780 config MFD_TI_AM335X_TSCADC
781 tristate "TI ADC / Touch Screen chip support"
786 If you say yes here you get support for Texas Instruments series
787 of Touch Screen /ADC chips.
788 To compile this driver as a module, choose M here: the
789 module will be called ti_am335x_tscadc.
791 config MFD_DM355EVM_MSP
792 bool "TI DaVinci DM355 EVM microcontroller"
793 depends on I2C=y && MACH_DAVINCI_DM355_EVM
795 This driver supports the MSP430 microcontroller used on these
796 boards. MSP430 firmware manages resets and power sequencing,
797 inputs from buttons and the IR remote, LEDs, an RTC, and more.
800 tristate "TI/National Semiconductor LP3943 MFD Driver"
805 Support for the TI/National Semiconductor LP3943.
806 This driver consists of GPIO and PWM drivers.
807 With these functionalities, it can be used for LED string control or
808 general usage such like a GPIO controller and a PWM controller.
811 bool "TI LP8788 Power Management Unit Driver"
817 TI LP8788 PMU supports regulators, battery charger, RTC,
818 ADC, backlight driver and current sinks.
820 config MFD_OMAP_USB_HOST
821 bool "TI OMAP USBHS core and TLL driver"
822 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
825 This is the core driver for the OAMP EHCI and OHCI drivers.
826 This MFD driver does the required setup functionalities for
827 OMAP USB Host drivers.
830 bool "TI Palmas series chips"
836 If you say yes here you get support for the Palmas
837 series of PMIC chips from Texas Instruments.
840 tristate "TI TPS61050/61052 Boost Converters"
844 select REGULATOR_FIXED_VOLTAGE
846 This option enables a driver for the TP61050/TPS61052
847 high-power "white LED driver". This boost converter is
848 sometimes used for other things than white LEDs, and
849 also contains a GPIO pin.
852 tristate "TI TPS6501x Power Management chips"
853 depends on I2C && GPIOLIB
854 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
856 If you say yes here you get support for the TPS6501x series of
857 Power Management chips. These include voltage regulators,
858 lithium ion/polymer battery charging, and other features that
859 are often used in portable devices like cell phones and cameras.
861 This driver can also be built as a module. If so, the module
862 will be called tps65010.
865 tristate "TI TPS6507x Power Management / Touch Screen chips"
869 If you say yes here you get support for the TPS6507x series of
870 Power Management / Touch Screen chips. These include voltage
871 regulators, lithium ion/polymer battery charging, touch screen
872 and other features that are often used in portable devices.
873 This driver can also be built as a module. If so, the module
874 will be called tps6507x.
876 config TPS65911_COMPARATOR
880 bool "TI TPS65090 Power Management chips"
886 If you say yes here you get support for the TPS65090 series of
887 Power Management chips.
888 This driver provides common support for accessing the device,
889 additional drivers must be enabled in order to use the
890 functionality of the device.
893 tristate "TI TPS65217 Power Management / White LED chips"
898 If you say yes here you get support for the TPS65217 series of
899 Power Management / White LED chips.
900 These include voltage regulators, lithium ion/polymer battery
901 charger, wled and other features that are often used in portable
904 This driver can also be built as a module. If so, the module
905 will be called tps65217.
908 tristate "TI TPS65218 Power Management chips"
914 If you say yes here you get support for the TPS65218 series of
915 Power Management chips.
916 These include voltage regulators, gpio and other features
917 that are often used in portable devices. Only regulator
918 component is currently supported.
920 This driver can also be built as a module. If so, the module
921 will be called tps65218.
924 bool "TI TPS6586x Power Management chips"
929 If you say yes here you get support for the TPS6586X series of
930 Power Management chips.
931 This driver provides common support for accessing the device,
932 additional drivers must be enabled in order to use the
933 functionality of the device.
935 This driver can also be built as a module. If so, the module
936 will be called tps6586x.
939 bool "TI TPS65910 Power Management chip"
940 depends on I2C=y && GPIOLIB
946 if you say yes here you get support for the TPS65910 series of
947 Power Management chips.
950 bool "TI TPS65912 Power Management chip"
954 If you say yes here you get support for the TPS65912 series of
957 config MFD_TPS65912_I2C
958 bool "TI TPS65912 Power Management chip with I2C"
961 depends on I2C=y && GPIOLIB
963 If you say yes here you get support for the TPS65912 series of
964 PM chips with I2C interface.
966 config MFD_TPS65912_SPI
967 bool "TI TPS65912 Power Management chip with SPI"
970 depends on SPI_MASTER && GPIOLIB
972 If you say yes here you get support for the TPS65912 series of
973 PM chips with SPI interface.
976 bool "TI TPS80031/TPS80032 Power Management chips"
982 If you say yes here you get support for the Texas Instruments
983 TPS80031/ TPS80032 Fully Integrated Power Management with Power
984 Path and Battery Charger. The device provides five configurable
985 step-down converters, 11 general purpose LDOs, USB OTG Module,
986 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
987 Power Path from USB, 32K clock generator.
990 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
995 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
996 This core driver provides register access and IRQ handling
997 facilities, and registers devices for the various functions
998 so that function-specific drivers can bind to them.
1000 These multi-function chips are found on many OMAP2 and OMAP3
1001 boards, providing power management, RTC, GPIO, keypad, a
1002 high speed USB OTG transceiver, an audio codec (on most
1003 versions) and many other features.
1005 config TWL4030_POWER
1006 bool "TI TWL4030 power resources"
1007 depends on TWL4030_CORE && ARM
1009 Say yes here if you want to use the power resources on the
1010 TWL4030 family chips. Most of these resources are regulators,
1011 which have a separate driver; some are control signals, such
1012 as clock request handshaking.
1014 This driver uses board-specific data to initialize the resources
1015 and load scripts controlling which resources are switched off/on
1016 or reset when a sleep, wakeup or warm reset event occurs.
1018 config MFD_TWL4030_AUDIO
1019 bool "TI TWL4030 Audio"
1020 depends on TWL4030_CORE
1025 bool "TI TWL6040 audio codec"
1032 Say yes here if you want support for Texas Instruments TWL6040 audio
1034 This driver provides common support for accessing the device,
1035 additional drivers must be enabled in order to use the
1036 functionality of the device (audio, vibra).
1039 bool "TI TWL92330/Menelaus PM chip"
1040 depends on I2C=y && ARCH_OMAP2
1042 If you say yes here you get support for the Texas Instruments
1043 TWL92330/Menelaus Power Management chip. This include voltage
1044 regulators, Dual slot memory card transceivers, real-time clock
1045 and other features that are often used in portable devices like
1046 cell phones and PDAs.
1048 config MFD_WL1273_CORE
1049 tristate "TI WL1273 FM radio"
1054 This is the core driver for the TI WL1273 FM radio. This MFD
1055 driver connects the radio-wl1273 V4L2 module and the wl1273
1059 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1064 Say yes here to enable support for National Semiconductor / TI
1065 LM3533 Lighting Power chips.
1067 This driver provides common support for accessing the device;
1068 additional drivers must be enabled in order to use the LED,
1069 backlight or ambient-light-sensor functionality of the device.
1071 config MFD_TIMBERDALE
1072 tristate "Timberdale FPGA"
1074 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1076 This is the core driver for the timberdale FPGA. This device is a
1077 multifunction device which exposes numerous platform devices.
1079 The timberdale FPGA can be found on the Intel Atom development board
1080 for in-vehicle infontainment, called Russellville.
1083 bool "Toshiba TC35892 and variants"
1087 Support for the Toshiba TC35892 and variants I/O Expander.
1089 This driver provides common support for accessing the device,
1090 additional drivers must be enabled in order to use the
1091 functionality of the device.
1098 bool "Toshiba T7L66XB"
1099 depends on ARM && HAVE_CLK
1103 Support for Toshiba Mobile IO Controller T7L66XB
1106 bool "Toshiba TC6387XB"
1107 depends on ARM && HAVE_CLK
1111 Support for Toshiba Mobile IO Controller TC6387XB
1114 bool "Toshiba TC6393XB"
1115 depends on ARM && HAVE_CLK
1120 Support for Toshiba Mobile IO Controller TC6393XB
1123 tristate "VIA VX855/VX875 integrated south bridge"
1127 Say yes here to enable support for various functions of the
1128 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1129 and/or vx855_gpio drivers for this to do anything useful.
1137 config MFD_ARIZONA_I2C
1138 tristate "Wolfson Microelectronics Arizona platform with I2C"
1144 Support for the Wolfson Microelectronics Arizona platform audio SoC
1145 core functionality controlled via I2C.
1147 config MFD_ARIZONA_SPI
1148 tristate "Wolfson Microelectronics Arizona platform with SPI"
1152 depends on SPI_MASTER
1154 Support for the Wolfson Microelectronics Arizona platform audio SoC
1155 core functionality controlled via I2C.
1158 bool "Wolfson Microelectronics WM5102"
1159 depends on MFD_ARIZONA
1161 Support for Wolfson Microelectronics WM5102 low power audio SoC
1164 bool "Wolfson Microelectronics WM5110"
1165 depends on MFD_ARIZONA
1167 Support for Wolfson Microelectronics WM5110 low power audio SoC
1170 bool "Wolfson Microelectronics WM8997"
1171 depends on MFD_ARIZONA
1173 Support for Wolfson Microelectronics WM8997 low power audio SoC
1176 bool "Wolfson Microelectronics WM8400"
1181 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1182 CODEC. This driver provides common support for accessing
1183 the device, additional drivers must be enabled in order to use
1184 the functionality of the device.
1189 config MFD_WM831X_I2C
1190 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1197 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1198 when controlled using I2C. This driver provides common support
1199 for accessing the device, additional drivers must be enabled in
1200 order to use the functionality of the device.
1202 config MFD_WM831X_SPI
1203 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1208 depends on SPI_MASTER
1210 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1211 when controlled using SPI. This driver provides common support
1212 for accessing the device, additional drivers must be enabled in
1213 order to use the functionality of the device.
1218 config MFD_WM8350_I2C
1219 bool "Wolfson Microelectronics WM8350 with I2C"
1223 The WM8350 is an integrated audio and power management
1224 subsystem with watchdog and RTC functionality for embedded
1225 systems. This option enables core support for the WM8350 with
1226 I2C as the control interface. Additional options must be
1227 selected to enable support for the functionality of the chip.
1230 bool "Wolfson Microelectronics WM8994"
1236 The WM8994 is a highly integrated hi-fi CODEC designed for
1237 smartphone applicatiosn. As well as audio functionality it
1238 has on board GPIO and regulator functionality which is
1239 supported via the relevant subsystems. This driver provides
1240 core support for the WM8994, in order to use the actual
1241 functionaltiy of the device other drivers must be enabled.
1244 tristate "Support for ST Microelectronics STw481x"
1245 depends on I2C && ARCH_NOMADIK
1249 Select this option to enable the STw481x chip driver used
1250 in various ST Microelectronics and ST-Ericsson embedded
1253 menu "Multimedia Capabilities Port drivers"
1254 depends on ARCH_SA1100
1261 tristate "Support SA11x0 MCP interface"
1262 depends on ARCH_SA1100
1267 tristate "Support for UCB1200 / UCB1300"
1268 depends on MCP_SA11X0
1271 config MCP_UCB1200_TS
1272 tristate "Touchscreen interface support"
1273 depends on MCP_UCB1200 && INPUT
1277 config MFD_VEXPRESS_SYSREG
1278 bool "Versatile Express System Registers"
1279 depends on VEXPRESS_CONFIG && GPIOLIB
1282 select GPIO_GENERIC_PLATFORM
1286 System Registers are the platform configuration block
1287 on the ARM Ltd. Versatile Express board.