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/802 PMIC Support"
390 Say yes here to add support for Maxim Semiconductor MAX77686 and
391 MAX77802 which are Power Management IC with an RTC on chip.
392 This driver provides common support for accessing the device;
393 additional drivers must be enabled in order to use the functionality
397 bool "Maxim Semiconductor MAX77693 PMIC Support"
403 Say yes here to add support for Maxim Semiconductor MAX77693.
404 This is a companion Power Management IC with Flash, Haptic, Charger,
405 and MUIC(Micro USB Interface Controller) controls on chip.
406 This driver provides common support for accessing the device;
407 additional drivers must be enabled in order to use the functionality
411 tristate "Maxim Semiconductor MAX8907 PMIC Support"
417 Say yes here to add support for Maxim Semiconductor MAX8907. This is
418 a Power Management IC. This driver provides common support for
419 accessing the device; additional drivers must be enabled in order
420 to use the functionality of the device.
423 bool "Maxim Semiconductor MAX8925 PMIC Support"
427 Say yes here to add support for Maxim Semiconductor MAX8925. This is
428 a Power Management IC. This driver provides common support for
429 accessing the device, additional drivers must be enabled in order
430 to use the functionality of the device.
433 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
438 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
439 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
440 MUIC controls on chip.
441 This driver provides common support for accessing the device;
442 additional drivers must be enabled in order to use the functionality
446 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
451 Say yes here to add support for Maxim Semiconductor MAX8998 and
452 National Semiconductor LP3974. This is a Power Management IC.
453 This driver provides common support for accessing the device,
454 additional drivers must be enabled in order to use the functionality
458 tristate "MEN 14F021P00 Board Management Controller Support"
462 Say yes here to add support for the MEN 14F021P00 BMC
463 which is a Board Management Controller connected to the I2C bus.
464 The device supports multiple sub-devices like LED, HWMON and WDT.
465 This driver provides common support for accessing the devices;
466 additional drivers must be enabled in order to use the
467 functionality of the BMC device.
469 This driver can also be built as a module. If so the module
470 will be called menf21bmc.
473 bool "Motorola EZXPCAP Support"
474 depends on SPI_MASTER
476 This enables the PCAP ASIC present on EZX Phones. This is
477 needed for MMC, TouchScreen, Sound, USB, etc..
479 config MFD_VIPERBOARD
480 tristate "Nano River Technologies Viperboard"
485 Say yes here if you want support for Nano River Technologies
487 There are mfd cell drivers available for i2c master, adc and
488 both gpios found on the board. The spi part does not yet
490 You need to select the mfd cell drivers separately.
491 The drivers do not support all features the board exposes.
494 tristate "Nokia Retu and Tahvo multi-function device"
499 Retu and Tahvo are a multi-function devices found on Nokia
500 Internet Tablets (770, N800 and N810).
503 tristate "NXP PCF50633"
507 Say yes here if you have NXP PCF50633 chip on your board.
508 This core driver provides register access and IRQ handling
509 facilities, and registers devices for the various functions
510 so that function-specific drivers can bind to them.
513 tristate "NXP PCF50633 ADC"
514 depends on MFD_PCF50633
516 Say yes here if you want to include support for ADC in the
520 tristate "NXP PCF50633 GPIO"
521 depends on MFD_PCF50633
523 Say yes here if you want to include support GPIO for pins on
527 tristate "Philips UCB1400 Core driver"
531 This enables support for the Philips UCB1400 core functions.
532 The UCB1400 is an AC97 audio codec.
534 To compile this driver as a module, choose M here: the
535 module will be called ucb1400_core.
540 config MFD_PM8921_CORE
541 tristate "Qualcomm PM8921 PMIC chip"
542 depends on (ARM || HEXAGON)
548 If you say yes to this option, support will be included for the
549 built-in PM8921 PMIC chip.
551 This is required if your board has a PM8921 and uses its features,
552 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
554 Say M here if you want to include support for PM8921 chip as a module.
555 This will build a module called "pm8921-core".
558 tristate "RDC R-321x southbridge"
562 Say yes here if you want to have support for the RDC R-321x SoC
563 southbridge which provides access to GPIOs and Watchdog using the
564 southbridge PCI device configuration space.
567 tristate "Realtek PCI-E card reader"
571 This supports for Realtek PCI-Express card reader including rts5209,
572 rts5229, rtl8411, etc. Realtek card reader supports access to many
573 types of memory cards, such as Memory Stick, Memory Stick Pro,
574 Secure Digital and MultiMediaCard.
577 tristate "Realtek USB card reader"
581 Select this option to get support for Realtek USB 2.0 card readers
582 including RTS5129, RTS5139, RTS5179 and RTS5170.
583 Realtek card reader supports access to many types of memory cards,
584 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
587 bool "Ricoh RC5T583 Power Management system device"
592 Select this option to get support for the RICOH583 Power
593 Management system device.
594 This driver provides common support for accessing the device
595 through i2c interface. The device supports multiple sub-devices
596 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
597 Additional drivers must be enabled in order to use the
598 different functionality of the device.
601 bool "SAMSUNG Electronics PMIC Series Support"
608 Support for the Samsung Electronics MFD series.
609 This driver provides common support for accessing the device,
610 additional drivers must be enabled in order to use the functionality
613 config MFD_SI476X_CORE
614 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
619 This is the core driver for the SI476x series of AM/FM
620 radio. This MFD driver connects the radio-si476x V4L2 module
621 and the si476x audio codec.
623 To compile this driver as a module, choose M here: the
624 module will be called si476x-core.
627 tristate "Silicon Motion SM501"
629 This is the core driver for the Silicon Motion SM501 multimedia
630 companion chip. This device is a multifunction device which may
631 provide numerous interfaces including USB host controller, USB gadget,
632 asynchronous serial ports, audio functions, and a dual display video
633 interface. The device may be connected by PCI or local bus with
634 varying functions enabled.
636 config MFD_SM501_GPIO
637 bool "Export GPIO via GPIO layer"
638 depends on MFD_SM501 && GPIOLIB
640 This option uses the gpio library layer to export the 64 GPIO
641 lines on the SM501. The platform data is used to supply the
642 base number for the first GPIO line to register.
645 bool "SMSC ECE1099 series chips"
650 If you say yes here you get support for the
651 ece1099 chips from SMSC.
653 To compile this driver as a module, choose M here: the
654 module will be called smsc.
657 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
658 default y if ARCH_U300 || ARCH_U8500
660 Say yes here if you have the ABX500 Mixed Signal IC family
661 chips. This core driver expose register access functions.
662 Functionality specific drivers using these functions can
663 remain unchanged when IC changes. Binding of the functions to
664 actual register access is done by the IC core driver.
667 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
668 depends on I2C=y && ABX500_CORE
670 default y if ARCH_U300
672 Select this to enable the AB3100 Mixed Signal IC core
673 functionality. This connects to a AB3100 on the I2C bus
674 and expose a number of symbols needed for dependent devices
675 to read and write registers and subscribe to events from
676 this multi-functional IC. This is needed to use other features
677 of the AB3100 such as battery-backed RTC, charging control,
678 LEDs, vibrator, system power and temperature, power management
682 tristate "ST-Ericsson AB3100 OTP functions"
683 depends on AB3100_CORE
684 default y if AB3100_CORE
686 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
687 programmable memory) support. This exposes a sysfs file to read
691 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
692 depends on ABX500_CORE && MFD_DB8500_PRCMU
697 Select this option to enable access to AB8500 power management
698 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
699 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
700 the irq_chip parts for handling the Mixed Signal chip events.
701 This chip embeds various other multimedia funtionalities as well.
704 bool "Enable debug info via debugfs"
705 depends on AB8500_GPADC && DEBUG_FS
706 default y if DEBUG_FS
708 Select this option if you want debug information using the debug
712 bool "ST-Ericsson AB8500 GPADC driver"
713 depends on AB8500_CORE && REGULATOR_AB8500
716 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
718 config MFD_DB8500_PRCMU
719 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
720 depends on UX500_SOC_DB8500
723 Select this option to enable support for the DB8500 Power Reset
724 and Control Management Unit. This is basically an autonomous
725 system controller running an XP70 microprocessor, which is accessed
726 through a register map.
729 bool "STMicroelectronics STMPE"
730 depends on (I2C=y || SPI_MASTER=y)
734 Support for the STMPE family of I/O Expanders from
737 Currently supported devices are:
739 STMPE811: GPIO, Touchscreen
740 STMPE1601: GPIO, Keypad
741 STMPE1801: GPIO, Keypad
742 STMPE2401: GPIO, Keypad
743 STMPE2403: GPIO, Keypad
745 This driver provides common support for accessing the device,
746 additional drivers must be enabled in order to use the functionality
747 of the device. Currently available sub drivers are:
751 Touchscreen: stmpe-ts
753 menu "STMicroelectronics STMPE Interface Drivers"
757 bool "STMicroelectronics STMPE I2C Interface"
761 This is used to enable I2C interface of STMPE
764 bool "STMicroelectronics STMPE SPI Interface"
765 depends on SPI_MASTER
767 This is used to enable SPI interface of STMPE
771 bool "STMicroelectronics STA2X11"
776 config MFD_SUN6I_PRCM
777 bool "Allwinner A31 PRCM controller"
778 depends on ARCH_SUNXI
781 Support for the PRCM (Power/Reset/Clock Management) unit available
785 bool "System Controller Register R/W Based on Regmap"
788 Select this option to enable accessing system control registers
791 config MFD_DAVINCI_VOICECODEC
796 config MFD_TI_AM335X_TSCADC
797 tristate "TI ADC / Touch Screen chip support"
802 If you say yes here you get support for Texas Instruments series
803 of Touch Screen /ADC chips.
804 To compile this driver as a module, choose M here: the
805 module will be called ti_am335x_tscadc.
807 config MFD_DM355EVM_MSP
808 bool "TI DaVinci DM355 EVM microcontroller"
809 depends on I2C=y && MACH_DAVINCI_DM355_EVM
811 This driver supports the MSP430 microcontroller used on these
812 boards. MSP430 firmware manages resets and power sequencing,
813 inputs from buttons and the IR remote, LEDs, an RTC, and more.
816 tristate "TI/National Semiconductor LP3943 MFD Driver"
821 Support for the TI/National Semiconductor LP3943.
822 This driver consists of GPIO and PWM drivers.
823 With these functionalities, it can be used for LED string control or
824 general usage such like a GPIO controller and a PWM controller.
827 bool "TI LP8788 Power Management Unit Driver"
833 TI LP8788 PMU supports regulators, battery charger, RTC,
834 ADC, backlight driver and current sinks.
836 config MFD_OMAP_USB_HOST
837 bool "TI OMAP USBHS core and TLL driver"
838 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
841 This is the core driver for the OAMP EHCI and OHCI drivers.
842 This MFD driver does the required setup functionalities for
843 OMAP USB Host drivers.
846 bool "TI Palmas series chips"
852 If you say yes here you get support for the Palmas
853 series of PMIC chips from Texas Instruments.
856 tristate "TI TPS61050/61052 Boost Converters"
860 select REGULATOR_FIXED_VOLTAGE
862 This option enables a driver for the TP61050/TPS61052
863 high-power "white LED driver". This boost converter is
864 sometimes used for other things than white LEDs, and
865 also contains a GPIO pin.
868 tristate "TI TPS6501x Power Management chips"
869 depends on I2C && GPIOLIB
870 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
872 If you say yes here you get support for the TPS6501x series of
873 Power Management chips. These include voltage regulators,
874 lithium ion/polymer battery charging, and other features that
875 are often used in portable devices like cell phones and cameras.
877 This driver can also be built as a module. If so, the module
878 will be called tps65010.
881 tristate "TI TPS6507x Power Management / Touch Screen chips"
885 If you say yes here you get support for the TPS6507x series of
886 Power Management / Touch Screen chips. These include voltage
887 regulators, lithium ion/polymer battery charging, touch screen
888 and other features that are often used in portable devices.
889 This driver can also be built as a module. If so, the module
890 will be called tps6507x.
892 config TPS65911_COMPARATOR
896 bool "TI TPS65090 Power Management chips"
902 If you say yes here you get support for the TPS65090 series of
903 Power Management chips.
904 This driver provides common support for accessing the device,
905 additional drivers must be enabled in order to use the
906 functionality of the device.
909 tristate "TI TPS65217 Power Management / White LED chips"
914 If you say yes here you get support for the TPS65217 series of
915 Power Management / White LED chips.
916 These include voltage regulators, lithium ion/polymer battery
917 charger, wled and other features that are often used in portable
920 This driver can also be built as a module. If so, the module
921 will be called tps65217.
924 tristate "TI TPS65218 Power Management chips"
930 If you say yes here you get support for the TPS65218 series of
931 Power Management chips.
932 These include voltage regulators, gpio and other features
933 that are often used in portable devices. Only regulator
934 component is currently supported.
936 This driver can also be built as a module. If so, the module
937 will be called tps65218.
940 bool "TI TPS6586x Power Management chips"
945 If you say yes here you get support for the TPS6586X series of
946 Power Management chips.
947 This driver provides common support for accessing the device,
948 additional drivers must be enabled in order to use the
949 functionality of the device.
951 This driver can also be built as a module. If so, the module
952 will be called tps6586x.
955 bool "TI TPS65910 Power Management chip"
956 depends on I2C=y && GPIOLIB
962 if you say yes here you get support for the TPS65910 series of
963 Power Management chips.
966 bool "TI TPS65912 Power Management chip"
970 If you say yes here you get support for the TPS65912 series of
973 config MFD_TPS65912_I2C
974 bool "TI TPS65912 Power Management chip with I2C"
977 depends on I2C=y && GPIOLIB
979 If you say yes here you get support for the TPS65912 series of
980 PM chips with I2C interface.
982 config MFD_TPS65912_SPI
983 bool "TI TPS65912 Power Management chip with SPI"
986 depends on SPI_MASTER && GPIOLIB
988 If you say yes here you get support for the TPS65912 series of
989 PM chips with SPI interface.
992 bool "TI TPS80031/TPS80032 Power Management chips"
998 If you say yes here you get support for the Texas Instruments
999 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1000 Path and Battery Charger. The device provides five configurable
1001 step-down converters, 11 general purpose LDOs, USB OTG Module,
1002 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1003 Power Path from USB, 32K clock generator.
1006 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1011 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1012 This core driver provides register access and IRQ handling
1013 facilities, and registers devices for the various functions
1014 so that function-specific drivers can bind to them.
1016 These multi-function chips are found on many OMAP2 and OMAP3
1017 boards, providing power management, RTC, GPIO, keypad, a
1018 high speed USB OTG transceiver, an audio codec (on most
1019 versions) and many other features.
1021 config TWL4030_POWER
1022 bool "TI TWL4030 power resources"
1023 depends on TWL4030_CORE && ARM
1025 Say yes here if you want to use the power resources on the
1026 TWL4030 family chips. Most of these resources are regulators,
1027 which have a separate driver; some are control signals, such
1028 as clock request handshaking.
1030 This driver uses board-specific data to initialize the resources
1031 and load scripts controlling which resources are switched off/on
1032 or reset when a sleep, wakeup or warm reset event occurs.
1034 config MFD_TWL4030_AUDIO
1035 bool "TI TWL4030 Audio"
1036 depends on TWL4030_CORE
1041 bool "TI TWL6040 audio codec"
1048 Say yes here if you want support for Texas Instruments TWL6040 audio
1050 This driver provides common support for accessing the device,
1051 additional drivers must be enabled in order to use the
1052 functionality of the device (audio, vibra).
1055 bool "TI TWL92330/Menelaus PM chip"
1056 depends on I2C=y && ARCH_OMAP2
1058 If you say yes here you get support for the Texas Instruments
1059 TWL92330/Menelaus Power Management chip. This include voltage
1060 regulators, Dual slot memory card transceivers, real-time clock
1061 and other features that are often used in portable devices like
1062 cell phones and PDAs.
1064 config MFD_WL1273_CORE
1065 tristate "TI WL1273 FM radio"
1070 This is the core driver for the TI WL1273 FM radio. This MFD
1071 driver connects the radio-wl1273 V4L2 module and the wl1273
1075 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1080 Say yes here to enable support for National Semiconductor / TI
1081 LM3533 Lighting Power chips.
1083 This driver provides common support for accessing the device;
1084 additional drivers must be enabled in order to use the LED,
1085 backlight or ambient-light-sensor functionality of the device.
1087 config MFD_TIMBERDALE
1088 tristate "Timberdale FPGA"
1090 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1092 This is the core driver for the timberdale FPGA. This device is a
1093 multifunction device which exposes numerous platform devices.
1095 The timberdale FPGA can be found on the Intel Atom development board
1096 for in-vehicle infontainment, called Russellville.
1099 bool "Toshiba TC35892 and variants"
1103 Support for the Toshiba TC35892 and variants I/O Expander.
1105 This driver provides common support for accessing the device,
1106 additional drivers must be enabled in order to use the
1107 functionality of the device.
1114 bool "Toshiba T7L66XB"
1115 depends on ARM && HAVE_CLK
1119 Support for Toshiba Mobile IO Controller T7L66XB
1122 bool "Toshiba TC6387XB"
1123 depends on ARM && HAVE_CLK
1127 Support for Toshiba Mobile IO Controller TC6387XB
1130 bool "Toshiba TC6393XB"
1131 depends on ARM && HAVE_CLK
1136 Support for Toshiba Mobile IO Controller TC6393XB
1139 tristate "VIA VX855/VX875 integrated south bridge"
1143 Say yes here to enable support for various functions of the
1144 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1145 and/or vx855_gpio drivers for this to do anything useful.
1153 config MFD_ARIZONA_I2C
1154 tristate "Wolfson Microelectronics Arizona platform with I2C"
1160 Support for the Wolfson Microelectronics Arizona platform audio SoC
1161 core functionality controlled via I2C.
1163 config MFD_ARIZONA_SPI
1164 tristate "Wolfson Microelectronics Arizona platform with SPI"
1168 depends on SPI_MASTER
1170 Support for the Wolfson Microelectronics Arizona platform audio SoC
1171 core functionality controlled via I2C.
1174 bool "Wolfson Microelectronics WM5102"
1175 depends on MFD_ARIZONA
1177 Support for Wolfson Microelectronics WM5102 low power audio SoC
1180 bool "Wolfson Microelectronics WM5110"
1181 depends on MFD_ARIZONA
1183 Support for Wolfson Microelectronics WM5110 low power audio SoC
1186 bool "Wolfson Microelectronics WM8997"
1187 depends on MFD_ARIZONA
1189 Support for Wolfson Microelectronics WM8997 low power audio SoC
1192 bool "Wolfson Microelectronics WM8400"
1197 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1198 CODEC. This driver provides common support for accessing
1199 the device, additional drivers must be enabled in order to use
1200 the functionality of the device.
1205 config MFD_WM831X_I2C
1206 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1213 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1214 when controlled using I2C. This driver provides common support
1215 for accessing the device, additional drivers must be enabled in
1216 order to use the functionality of the device.
1218 config MFD_WM831X_SPI
1219 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1224 depends on SPI_MASTER
1226 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1227 when controlled using SPI. This driver provides common support
1228 for accessing the device, additional drivers must be enabled in
1229 order to use the functionality of the device.
1234 config MFD_WM8350_I2C
1235 bool "Wolfson Microelectronics WM8350 with I2C"
1239 The WM8350 is an integrated audio and power management
1240 subsystem with watchdog and RTC functionality for embedded
1241 systems. This option enables core support for the WM8350 with
1242 I2C as the control interface. Additional options must be
1243 selected to enable support for the functionality of the chip.
1246 bool "Wolfson Microelectronics WM8994"
1252 The WM8994 is a highly integrated hi-fi CODEC designed for
1253 smartphone applicatiosn. As well as audio functionality it
1254 has on board GPIO and regulator functionality which is
1255 supported via the relevant subsystems. This driver provides
1256 core support for the WM8994, in order to use the actual
1257 functionaltiy of the device other drivers must be enabled.
1260 tristate "Support for ST Microelectronics STw481x"
1261 depends on I2C && ARCH_NOMADIK
1265 Select this option to enable the STw481x chip driver used
1266 in various ST Microelectronics and ST-Ericsson embedded
1269 menu "Multimedia Capabilities Port drivers"
1270 depends on ARCH_SA1100
1277 tristate "Support SA11x0 MCP interface"
1278 depends on ARCH_SA1100
1283 tristate "Support for UCB1200 / UCB1300"
1284 depends on MCP_SA11X0
1287 config MCP_UCB1200_TS
1288 tristate "Touchscreen interface support"
1289 depends on MCP_UCB1200 && INPUT
1293 config MFD_VEXPRESS_SYSREG
1294 bool "Versatile Express System Registers"
1295 depends on VEXPRESS_CONFIG && GPIOLIB
1298 select GPIO_GENERIC_PLATFORM
1302 System Registers are the platform configuration block
1303 on the ARM Ltd. Versatile Express board.