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.
213 config MFD_HI6421_PMIC
214 tristate "HiSilicon Hi6421 PMU/Codec IC"
219 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
220 functions, such as regulators, RTC, codec, Coulomb counter, etc.
221 This driver includes core APIs _only_. You have to select
222 individul components like voltage regulators under corresponding
223 menus in order to enable them.
224 We communicate with the Hi6421 via memory-mapped I/O.
227 bool "HTC EGPIO support"
228 depends on GPIOLIB && ARM
230 This driver supports the CPLD egpio chip present on
231 several HTC phones. It provides basic support for input
232 pins, output pins, and irqs.
235 tristate "HTC PASIC3 LED/DS1WM chip support"
238 This core driver provides register access for the LED/DS1WM
239 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
240 HTC Magician devices, respectively. Actual functionality is
241 handled by the leds-pasic3 and ds1wm drivers.
244 bool "HTC I2C PLD chip support"
245 depends on I2C=y && GPIOLIB
247 If you say yes here you get support for the supposed CPLD
248 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
249 This device provides input and output GPIOs through an I2C
250 interface to one or more sub-chips.
253 tristate "Intel ICH LPC"
257 The LPC bridge function of the Intel ICH provides support for
258 many functional units. This driver provides needed support for
259 other drivers to control these functions, currently GPIO and
263 tristate "Intel SCH LPC"
267 LPC bridge function of the Intel SCH provides support for
268 System Management Bus and General Purpose I/O.
270 config INTEL_SOC_PMIC
271 bool "Support for Intel Atom SoC PMIC"
277 Select this option to enable support for the PMIC device
278 on some Intel SoC systems. The PMIC provides ADC, GPIO,
279 thermal, charger and related power management functions
282 config MFD_INTEL_MSIC
284 depends on INTEL_SCU_IPC
287 Select this option to enable access to Intel MSIC (Avatele
288 Passage) chip. This chip embeds audio, battery, GPIO, etc.
289 devices used in Intel Medfield platforms.
291 config MFD_IPAQ_MICRO
292 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
293 depends on SA1100_H3100 || SA1100_H3600
296 Select this to get support for the Microcontroller found in
297 the Compaq iPAQ handheld computers. This is an Atmel
298 AT90LS8535 microcontroller flashed with a special iPAQ
299 firmware using the custom protocol implemented in this driver.
301 config MFD_JANZ_CMODIO
302 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
306 This is the core driver for the Janz CMOD-IO PCI MODULbus
307 carrier board. This device is a PCI to MODULbus bridge which may
308 host many different types of MODULbus daughterboards, including
309 CAN and GPIO controllers.
311 config MFD_JZ4740_ADC
312 bool "Janz JZ4740 ADC core"
314 select GENERIC_IRQ_CHIP
315 depends on MACH_JZ4740
317 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
318 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
321 tristate "Kontron module PLD device"
324 This is the core driver for the PLD (Programmable Logic Device) found
325 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
326 device may provide functions like watchdog, GPIO, UART and I2C bus.
328 The following modules are supported:
331 * COMe-bPC2 (ETXexpress-PC)
332 * COMe-bSC# (ETXexpress-SC T#)
335 * COMe-cDC2 (microETXexpress-DC)
337 * COMe-cPC2 (microETXexpress-PC)
340 * COMe-mTT10 (nanoETXexpress-TT)
343 This driver can also be built as a module. If so, the module
344 will be called kempld-core.
347 tristate "Marvell 88PM800"
353 This supports for Marvell 88PM800 Power Management IC.
354 This includes the I2C driver and the core APIs _only_, you have to
355 select individual components like voltage regulators, RTC and
356 battery-charger under the corresponding menus.
359 tristate "Marvell 88PM805"
365 This supports for Marvell 88PM805 Power Management IC. This includes
366 the I2C driver and the core APIs _only_, you have to select individual
367 components like codec device, headset/Mic device under the
371 bool "Marvell 88PM8606/88PM8607"
376 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
377 This includes the I2C driver and the core APIs _only_, you have to
378 select individual components like voltage regulators, RTC and
379 battery-charger under the corresponding menus.
382 bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
389 Say yes here to add support for Maxim Semiconductor MAX14577 and
390 MAX77836 Micro-USB ICs with battery charger.
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 MAX77686/802 PMIC Support"
403 Say yes here to add support for Maxim Semiconductor MAX77686 and
404 MAX77802 which are Power Management IC with an RTC 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 bool "Maxim Semiconductor MAX77693 PMIC Support"
416 Say yes here to add support for Maxim Semiconductor MAX77693.
417 This is a companion Power Management IC with Flash, Haptic, Charger,
418 and MUIC(Micro USB Interface Controller) controls on chip.
419 This driver provides common support for accessing the device;
420 additional drivers must be enabled in order to use the functionality
424 tristate "Maxim Semiconductor MAX8907 PMIC Support"
430 Say yes here to add support for Maxim Semiconductor MAX8907. This is
431 a Power Management IC. This driver provides common support for
432 accessing the device; additional drivers must be enabled in order
433 to use the functionality of the device.
436 bool "Maxim Semiconductor MAX8925 PMIC Support"
440 Say yes here to add support for Maxim Semiconductor MAX8925. This is
441 a Power Management IC. This driver provides common support for
442 accessing the device, additional drivers must be enabled in order
443 to use the functionality of the device.
446 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
451 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
452 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
453 MUIC controls on chip.
454 This driver provides common support for accessing the device;
455 additional drivers must be enabled in order to use the functionality
459 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
464 Say yes here to add support for Maxim Semiconductor MAX8998 and
465 National Semiconductor LP3974. This is a Power Management IC.
466 This driver provides common support for accessing the device,
467 additional drivers must be enabled in order to use the functionality
471 tristate "MEN 14F021P00 Board Management Controller Support"
475 Say yes here to add support for the MEN 14F021P00 BMC
476 which is a Board Management Controller connected to the I2C bus.
477 The device supports multiple sub-devices like LED, HWMON and WDT.
478 This driver provides common support for accessing the devices;
479 additional drivers must be enabled in order to use the
480 functionality of the BMC device.
482 This driver can also be built as a module. If so the module
483 will be called menf21bmc.
486 bool "Motorola EZXPCAP Support"
487 depends on SPI_MASTER
489 This enables the PCAP ASIC present on EZX Phones. This is
490 needed for MMC, TouchScreen, Sound, USB, etc..
492 config MFD_VIPERBOARD
493 tristate "Nano River Technologies Viperboard"
498 Say yes here if you want support for Nano River Technologies
500 There are mfd cell drivers available for i2c master, adc and
501 both gpios found on the board. The spi part does not yet
503 You need to select the mfd cell drivers separately.
504 The drivers do not support all features the board exposes.
507 tristate "Nokia Retu and Tahvo multi-function device"
512 Retu and Tahvo are a multi-function devices found on Nokia
513 Internet Tablets (770, N800 and N810).
516 tristate "NXP PCF50633"
520 Say yes here if you have NXP PCF50633 chip on your board.
521 This core driver provides register access and IRQ handling
522 facilities, and registers devices for the various functions
523 so that function-specific drivers can bind to them.
526 tristate "NXP PCF50633 ADC"
527 depends on MFD_PCF50633
529 Say yes here if you want to include support for ADC in the
533 tristate "NXP PCF50633 GPIO"
534 depends on MFD_PCF50633
536 Say yes here if you want to include support GPIO for pins on
540 tristate "Philips UCB1400 Core driver"
544 This enables support for the Philips UCB1400 core functions.
545 The UCB1400 is an AC97 audio codec.
547 To compile this driver as a module, choose M here: the
548 module will be called ucb1400_core.
553 config MFD_PM8921_CORE
554 tristate "Qualcomm PM8921 PMIC chip"
555 depends on (ARM || HEXAGON)
561 If you say yes to this option, support will be included for the
562 built-in PM8921 PMIC chip.
564 This is required if your board has a PM8921 and uses its features,
565 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
567 Say M here if you want to include support for PM8921 chip as a module.
568 This will build a module called "pm8921-core".
571 tristate "Qualcomm SPMI PMICs"
572 depends on ARCH_QCOM || COMPILE_TEST
577 This enables support for the Qualcomm SPMI PMICs.
578 These PMICs are currently used with the Snapdragon 800 series of
579 SoCs. Note, that this will only be useful paired with descriptions
580 of the independent functions as children nodes in the device tree.
582 Say M here if you want to include support for the SPMI PMIC
583 series as a module. The module will be called "qcom-spmi-pmic".
586 tristate "RDC R-321x southbridge"
590 Say yes here if you want to have support for the RDC R-321x SoC
591 southbridge which provides access to GPIOs and Watchdog using the
592 southbridge PCI device configuration space.
595 tristate "Realtek PCI-E card reader"
599 This supports for Realtek PCI-Express card reader including rts5209,
600 rts5229, rtl8411, etc. Realtek card reader supports access to many
601 types of memory cards, such as Memory Stick, Memory Stick Pro,
602 Secure Digital and MultiMediaCard.
605 tristate "Realtek USB card reader"
609 Select this option to get support for Realtek USB 2.0 card readers
610 including RTS5129, RTS5139, RTS5179 and RTS5170.
611 Realtek card reader supports access to many types of memory cards,
612 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
615 bool "Ricoh RC5T583 Power Management system device"
620 Select this option to get support for the RICOH583 Power
621 Management system device.
622 This driver provides common support for accessing the device
623 through i2c interface. The device supports multiple sub-devices
624 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
625 Additional drivers must be enabled in order to use the
626 different functionality of the device.
629 tristate "Rockchip RK808 Power Management chip"
635 If you say yes here you get support for the RK808
636 Power Management chips.
637 This driver provides common support for accessing the device
638 through I2C interface. The device supports multiple sub-devices
639 including interrupts, RTC, LDO & DCDC regulators, and onkey.
642 tristate "Ricoh RN5T5618 PMIC"
647 Say yes here to add support for the Ricoh RN5T618 PMIC. This
648 driver provides common support for accessing the device,
649 additional drivers must be enabled in order to use the
650 functionality of the device.
653 bool "SAMSUNG Electronics PMIC Series Support"
660 Support for the Samsung Electronics MFD series.
661 This driver provides common support for accessing the device,
662 additional drivers must be enabled in order to use the functionality
665 config MFD_SI476X_CORE
666 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
671 This is the core driver for the SI476x series of AM/FM
672 radio. This MFD driver connects the radio-si476x V4L2 module
673 and the si476x audio codec.
675 To compile this driver as a module, choose M here: the
676 module will be called si476x-core.
679 tristate "Silicon Motion SM501"
681 This is the core driver for the Silicon Motion SM501 multimedia
682 companion chip. This device is a multifunction device which may
683 provide numerous interfaces including USB host controller, USB gadget,
684 asynchronous serial ports, audio functions, and a dual display video
685 interface. The device may be connected by PCI or local bus with
686 varying functions enabled.
688 config MFD_SM501_GPIO
689 bool "Export GPIO via GPIO layer"
690 depends on MFD_SM501 && GPIOLIB
692 This option uses the gpio library layer to export the 64 GPIO
693 lines on the SM501. The platform data is used to supply the
694 base number for the first GPIO line to register.
697 bool "SMSC ECE1099 series chips"
702 If you say yes here you get support for the
703 ece1099 chips from SMSC.
705 To compile this driver as a module, choose M here: the
706 module will be called smsc.
709 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
710 default y if ARCH_U300 || ARCH_U8500
712 Say yes here if you have the ABX500 Mixed Signal IC family
713 chips. This core driver expose register access functions.
714 Functionality specific drivers using these functions can
715 remain unchanged when IC changes. Binding of the functions to
716 actual register access is done by the IC core driver.
719 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
720 depends on I2C=y && ABX500_CORE
722 default y if ARCH_U300
724 Select this to enable the AB3100 Mixed Signal IC core
725 functionality. This connects to a AB3100 on the I2C bus
726 and expose a number of symbols needed for dependent devices
727 to read and write registers and subscribe to events from
728 this multi-functional IC. This is needed to use other features
729 of the AB3100 such as battery-backed RTC, charging control,
730 LEDs, vibrator, system power and temperature, power management
734 tristate "ST-Ericsson AB3100 OTP functions"
735 depends on AB3100_CORE
736 default y if AB3100_CORE
738 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
739 programmable memory) support. This exposes a sysfs file to read
743 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
744 depends on ABX500_CORE && MFD_DB8500_PRCMU
749 Select this option to enable access to AB8500 power management
750 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
751 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
752 the irq_chip parts for handling the Mixed Signal chip events.
753 This chip embeds various other multimedia funtionalities as well.
756 bool "Enable debug info via debugfs"
757 depends on AB8500_GPADC && DEBUG_FS
758 default y if DEBUG_FS
760 Select this option if you want debug information using the debug
764 bool "ST-Ericsson AB8500 GPADC driver"
765 depends on AB8500_CORE && REGULATOR_AB8500
768 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
770 config MFD_DB8500_PRCMU
771 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
772 depends on UX500_SOC_DB8500
775 Select this option to enable support for the DB8500 Power Reset
776 and Control Management Unit. This is basically an autonomous
777 system controller running an XP70 microprocessor, which is accessed
778 through a register map.
781 bool "STMicroelectronics STMPE"
782 depends on (I2C=y || SPI_MASTER=y)
786 Support for the STMPE family of I/O Expanders from
789 Currently supported devices are:
791 STMPE811: GPIO, Touchscreen
792 STMPE1601: GPIO, Keypad
793 STMPE1801: GPIO, Keypad
794 STMPE2401: GPIO, Keypad
795 STMPE2403: GPIO, Keypad
797 This driver provides common support for accessing the device,
798 additional drivers must be enabled in order to use the functionality
799 of the device. Currently available sub drivers are:
803 Touchscreen: stmpe-ts
805 menu "STMicroelectronics STMPE Interface Drivers"
809 bool "STMicroelectronics STMPE I2C Interface"
813 This is used to enable I2C interface of STMPE
816 bool "STMicroelectronics STMPE SPI Interface"
817 depends on SPI_MASTER
819 This is used to enable SPI interface of STMPE
823 bool "STMicroelectronics STA2X11"
828 config MFD_SUN6I_PRCM
829 bool "Allwinner A31 PRCM controller"
830 depends on ARCH_SUNXI
833 Support for the PRCM (Power/Reset/Clock Management) unit available
837 bool "System Controller Register R/W Based on Regmap"
840 Select this option to enable accessing system control registers
843 config MFD_DAVINCI_VOICECODEC
848 config MFD_TI_AM335X_TSCADC
849 tristate "TI ADC / Touch Screen chip support"
854 If you say yes here you get support for Texas Instruments series
855 of Touch Screen /ADC chips.
856 To compile this driver as a module, choose M here: the
857 module will be called ti_am335x_tscadc.
859 config MFD_DM355EVM_MSP
860 bool "TI DaVinci DM355 EVM microcontroller"
861 depends on I2C=y && MACH_DAVINCI_DM355_EVM
863 This driver supports the MSP430 microcontroller used on these
864 boards. MSP430 firmware manages resets and power sequencing,
865 inputs from buttons and the IR remote, LEDs, an RTC, and more.
868 tristate "TI/National Semiconductor LP3943 MFD Driver"
873 Support for the TI/National Semiconductor LP3943.
874 This driver consists of GPIO and PWM drivers.
875 With these functionalities, it can be used for LED string control or
876 general usage such like a GPIO controller and a PWM controller.
879 bool "TI LP8788 Power Management Unit Driver"
885 TI LP8788 PMU supports regulators, battery charger, RTC,
886 ADC, backlight driver and current sinks.
888 config MFD_OMAP_USB_HOST
889 bool "TI OMAP USBHS core and TLL driver"
890 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
893 This is the core driver for the OAMP EHCI and OHCI drivers.
894 This MFD driver does the required setup functionalities for
895 OMAP USB Host drivers.
898 bool "TI Palmas series chips"
904 If you say yes here you get support for the Palmas
905 series of PMIC chips from Texas Instruments.
908 tristate "TI TPS61050/61052 Boost Converters"
912 select REGULATOR_FIXED_VOLTAGE
914 This option enables a driver for the TP61050/TPS61052
915 high-power "white LED driver". This boost converter is
916 sometimes used for other things than white LEDs, and
917 also contains a GPIO pin.
920 tristate "TI TPS6501x Power Management chips"
921 depends on I2C && GPIOLIB
922 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
924 If you say yes here you get support for the TPS6501x series of
925 Power Management chips. These include voltage regulators,
926 lithium ion/polymer battery charging, and other features that
927 are often used in portable devices like cell phones and cameras.
929 This driver can also be built as a module. If so, the module
930 will be called tps65010.
933 tristate "TI TPS6507x Power Management / Touch Screen chips"
937 If you say yes here you get support for the TPS6507x series of
938 Power Management / Touch Screen chips. These include voltage
939 regulators, lithium ion/polymer battery charging, touch screen
940 and other features that are often used in portable devices.
941 This driver can also be built as a module. If so, the module
942 will be called tps6507x.
944 config TPS65911_COMPARATOR
948 bool "TI TPS65090 Power Management chips"
954 If you say yes here you get support for the TPS65090 series of
955 Power Management chips.
956 This driver provides common support for accessing the device,
957 additional drivers must be enabled in order to use the
958 functionality of the device.
961 tristate "TI TPS65217 Power Management / White LED chips"
966 If you say yes here you get support for the TPS65217 series of
967 Power Management / White LED chips.
968 These include voltage regulators, lithium ion/polymer battery
969 charger, wled and other features that are often used in portable
972 This driver can also be built as a module. If so, the module
973 will be called tps65217.
976 tristate "TI TPS65218 Power Management chips"
982 If you say yes here you get support for the TPS65218 series of
983 Power Management chips.
984 These include voltage regulators, gpio and other features
985 that are often used in portable devices. Only regulator
986 component is currently supported.
988 This driver can also be built as a module. If so, the module
989 will be called tps65218.
992 bool "TI TPS6586x Power Management chips"
997 If you say yes here you get support for the TPS6586X series of
998 Power Management chips.
999 This driver provides common support for accessing the device,
1000 additional drivers must be enabled in order to use the
1001 functionality of the device.
1003 This driver can also be built as a module. If so, the module
1004 will be called tps6586x.
1007 bool "TI TPS65910 Power Management chip"
1008 depends on I2C=y && GPIOLIB
1014 if you say yes here you get support for the TPS65910 series of
1015 Power Management chips.
1018 bool "TI TPS65912 Power Management chip"
1022 If you say yes here you get support for the TPS65912 series of
1025 config MFD_TPS65912_I2C
1026 bool "TI TPS65912 Power Management chip with I2C"
1029 depends on I2C=y && GPIOLIB
1031 If you say yes here you get support for the TPS65912 series of
1032 PM chips with I2C interface.
1034 config MFD_TPS65912_SPI
1035 bool "TI TPS65912 Power Management chip with SPI"
1038 depends on SPI_MASTER && GPIOLIB
1040 If you say yes here you get support for the TPS65912 series of
1041 PM chips with SPI interface.
1044 bool "TI TPS80031/TPS80032 Power Management chips"
1050 If you say yes here you get support for the Texas Instruments
1051 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1052 Path and Battery Charger. The device provides five configurable
1053 step-down converters, 11 general purpose LDOs, USB OTG Module,
1054 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1055 Power Path from USB, 32K clock generator.
1058 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1063 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1064 This core driver provides register access and IRQ handling
1065 facilities, and registers devices for the various functions
1066 so that function-specific drivers can bind to them.
1068 These multi-function chips are found on many OMAP2 and OMAP3
1069 boards, providing power management, RTC, GPIO, keypad, a
1070 high speed USB OTG transceiver, an audio codec (on most
1071 versions) and many other features.
1073 config TWL4030_POWER
1074 bool "TI TWL4030 power resources"
1075 depends on TWL4030_CORE && ARM
1077 Say yes here if you want to use the power resources on the
1078 TWL4030 family chips. Most of these resources are regulators,
1079 which have a separate driver; some are control signals, such
1080 as clock request handshaking.
1082 This driver uses board-specific data to initialize the resources
1083 and load scripts controlling which resources are switched off/on
1084 or reset when a sleep, wakeup or warm reset event occurs.
1086 config MFD_TWL4030_AUDIO
1087 bool "TI TWL4030 Audio"
1088 depends on TWL4030_CORE
1093 bool "TI TWL6040 audio codec"
1100 Say yes here if you want support for Texas Instruments TWL6040 audio
1102 This driver provides common support for accessing the device,
1103 additional drivers must be enabled in order to use the
1104 functionality of the device (audio, vibra).
1107 bool "TI TWL92330/Menelaus PM chip"
1108 depends on I2C=y && ARCH_OMAP2
1110 If you say yes here you get support for the Texas Instruments
1111 TWL92330/Menelaus Power Management chip. This include voltage
1112 regulators, Dual slot memory card transceivers, real-time clock
1113 and other features that are often used in portable devices like
1114 cell phones and PDAs.
1116 config MFD_WL1273_CORE
1117 tristate "TI WL1273 FM radio"
1122 This is the core driver for the TI WL1273 FM radio. This MFD
1123 driver connects the radio-wl1273 V4L2 module and the wl1273
1127 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1132 Say yes here to enable support for National Semiconductor / TI
1133 LM3533 Lighting Power chips.
1135 This driver provides common support for accessing the device;
1136 additional drivers must be enabled in order to use the LED,
1137 backlight or ambient-light-sensor functionality of the device.
1139 config MFD_TIMBERDALE
1140 tristate "Timberdale FPGA"
1142 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1144 This is the core driver for the timberdale FPGA. This device is a
1145 multifunction device which exposes numerous platform devices.
1147 The timberdale FPGA can be found on the Intel Atom development board
1148 for in-vehicle infontainment, called Russellville.
1151 bool "Toshiba TC35892 and variants"
1155 Support for the Toshiba TC35892 and variants I/O Expander.
1157 This driver provides common support for accessing the device,
1158 additional drivers must be enabled in order to use the
1159 functionality of the device.
1166 bool "Toshiba T7L66XB"
1167 depends on ARM && HAVE_CLK
1171 Support for Toshiba Mobile IO Controller T7L66XB
1174 bool "Toshiba TC6387XB"
1175 depends on ARM && HAVE_CLK
1179 Support for Toshiba Mobile IO Controller TC6387XB
1182 bool "Toshiba TC6393XB"
1183 depends on ARM && HAVE_CLK
1188 Support for Toshiba Mobile IO Controller TC6393XB
1191 tristate "VIA VX855/VX875 integrated south bridge"
1195 Say yes here to enable support for various functions of the
1196 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1197 and/or vx855_gpio drivers for this to do anything useful.
1205 config MFD_ARIZONA_I2C
1206 tristate "Wolfson Microelectronics Arizona platform with I2C"
1212 Support for the Wolfson Microelectronics Arizona platform audio SoC
1213 core functionality controlled via I2C.
1215 config MFD_ARIZONA_SPI
1216 tristate "Wolfson Microelectronics Arizona platform with SPI"
1220 depends on SPI_MASTER
1222 Support for the Wolfson Microelectronics Arizona platform audio SoC
1223 core functionality controlled via I2C.
1226 bool "Wolfson Microelectronics WM5102"
1227 depends on MFD_ARIZONA
1229 Support for Wolfson Microelectronics WM5102 low power audio SoC
1232 bool "Wolfson Microelectronics WM5110"
1233 depends on MFD_ARIZONA
1235 Support for Wolfson Microelectronics WM5110 low power audio SoC
1238 bool "Wolfson Microelectronics WM8997"
1239 depends on MFD_ARIZONA
1241 Support for Wolfson Microelectronics WM8997 low power audio SoC
1244 bool "Wolfson Microelectronics WM8400"
1249 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1250 CODEC. This driver provides common support for accessing
1251 the device, additional drivers must be enabled in order to use
1252 the functionality of the device.
1257 config MFD_WM831X_I2C
1258 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1265 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1266 when controlled using I2C. This driver provides common support
1267 for accessing the device, additional drivers must be enabled in
1268 order to use the functionality of the device.
1270 config MFD_WM831X_SPI
1271 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1276 depends on SPI_MASTER
1278 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1279 when controlled using SPI. This driver provides common support
1280 for accessing the device, additional drivers must be enabled in
1281 order to use the functionality of the device.
1286 config MFD_WM8350_I2C
1287 bool "Wolfson Microelectronics WM8350 with I2C"
1291 The WM8350 is an integrated audio and power management
1292 subsystem with watchdog and RTC functionality for embedded
1293 systems. This option enables core support for the WM8350 with
1294 I2C as the control interface. Additional options must be
1295 selected to enable support for the functionality of the chip.
1298 tristate "Wolfson Microelectronics WM8994"
1304 The WM8994 is a highly integrated hi-fi CODEC designed for
1305 smartphone applicatiosn. As well as audio functionality it
1306 has on board GPIO and regulator functionality which is
1307 supported via the relevant subsystems. This driver provides
1308 core support for the WM8994, in order to use the actual
1309 functionaltiy of the device other drivers must be enabled.
1312 tristate "Support for ST Microelectronics STw481x"
1313 depends on I2C && ARCH_NOMADIK
1317 Select this option to enable the STw481x chip driver used
1318 in various ST Microelectronics and ST-Ericsson embedded
1321 menu "Multimedia Capabilities Port drivers"
1322 depends on ARCH_SA1100
1329 tristate "Support SA11x0 MCP interface"
1330 depends on ARCH_SA1100
1335 tristate "Support for UCB1200 / UCB1300"
1336 depends on MCP_SA11X0
1339 config MCP_UCB1200_TS
1340 tristate "Touchscreen interface support"
1341 depends on MCP_UCB1200 && INPUT
1345 config MFD_VEXPRESS_SYSREG
1346 bool "Versatile Express System Registers"
1347 depends on VEXPRESS_CONFIG && GPIOLIB
1350 select GPIO_GENERIC_PLATFORM
1354 System Registers are the platform configuration block
1355 on the ARM Ltd. Versatile Express board.