2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 bool "Support Marvell 88PM8606/88PM8607"
15 depends on I2C=y && GENERIC_HARDIRQS
19 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
20 This includes the I2C driver and the core APIs _only_, you have to
21 select individual components like voltage regulators, RTC and
22 battery-charger under the corresponding menus.
25 tristate "Support Marvell 88PM800"
26 depends on I2C=y && GENERIC_HARDIRQS
31 This supports for Marvell 88PM800 Power Management IC.
32 This includes the I2C driver and the core APIs _only_, you have to
33 select individual components like voltage regulators, RTC and
34 battery-charger under the corresponding menus.
37 tristate "Support Marvell 88PM805"
38 depends on I2C=y && GENERIC_HARDIRQS
43 This supports for Marvell 88PM805 Power Management IC. This includes
44 the I2C driver and the core APIs _only_, you have to select individual
45 components like codec device, headset/Mic device under the
49 tristate "Support for Silicon Motion SM501"
51 This is the core driver for the Silicon Motion SM501 multimedia
52 companion chip. This device is a multifunction device which may
53 provide numerous interfaces including USB host controller, USB gadget,
54 asynchronous serial ports, audio functions, and a dual display video
55 interface. The device may be connected by PCI or local bus with
56 varying functions enabled.
59 bool "Export GPIO via GPIO layer"
60 depends on MFD_SM501 && GPIOLIB
62 This option uses the gpio library layer to export the 64 GPIO
63 lines on the SM501. The platform data is used to supply the
64 base number for the first GPIO line to register.
67 tristate "Support for Realtek PCI-E card reader"
71 This supports for Realtek PCI-Express card reader including rts5209,
72 rts5229, rtl8411, etc. Realtek card reader supports access to many
73 types of memory cards, such as Memory Stick, Memory Stick Pro,
74 Secure Digital and MultiMediaCard.
77 bool "Support for Compaq ASIC3"
78 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
81 This driver supports the ASIC3 multifunction chip found on many
82 PDAs (mainly iPAQ and HTC based ones)
84 config MFD_DAVINCI_VOICECODEC
88 config MFD_DM355EVM_MSP
89 bool "DaVinci DM355 EVM microcontroller"
90 depends on I2C=y && MACH_DAVINCI_DM355_EVM
92 This driver supports the MSP430 microcontroller used on these
93 boards. MSP430 firmware manages resets and power sequencing,
94 inputs from buttons and the IR remote, LEDs, an RTC, and more.
97 tristate "TI Sequencer Serial Port support"
98 depends on ARCH_DAVINCI_TNETV107X
101 Say Y here if you want support for the Sequencer Serial Port
102 in a Texas Instruments TNETV107X SoC.
104 To compile this driver as a module, choose M here: the
105 module will be called ti-ssp.
107 config MFD_TI_AM335X_TSCADC
108 tristate "TI ADC / Touch Screen chip support"
113 If you say yes here you get support for Texas Instruments series
114 of Touch Screen /ADC chips.
115 To compile this driver as a module, choose M here: the
116 module will be called ti_am335x_tscadc.
119 bool "HTC EGPIO support"
120 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
122 This driver supports the CPLD egpio chip present on
123 several HTC phones. It provides basic support for input
124 pins, output pins, and irqs.
127 tristate "HTC PASIC3 LED/DS1WM chip support"
130 This core driver provides register access for the LED/DS1WM
131 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
132 HTC Magician devices, respectively. Actual functionality is
133 handled by the leds-pasic3 and ds1wm drivers.
136 bool "HTC I2C PLD chip support"
137 depends on I2C=y && GPIOLIB
139 If you say yes here you get support for the supposed CPLD
140 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
141 This device provides input and output GPIOs through an I2C
142 interface to one or more sub-chips.
145 tristate "Philips UCB1400 Core driver"
149 This enables support for the Philips UCB1400 core functions.
150 The UCB1400 is an AC97 audio codec.
152 To compile this driver as a module, choose M here: the
153 module will be called ucb1400_core.
156 tristate "LM3533 Lighting Power chip"
161 Say yes here to enable support for National Semiconductor / TI
162 LM3533 Lighting Power chips.
164 This driver provides common support for accessing the device;
165 additional drivers must be enabled in order to use the LED,
166 backlight or ambient-light-sensor functionality of the device.
169 tristate "TPS61050/61052 Boost Converters"
173 select REGULATOR_FIXED_VOLTAGE
175 This option enables a driver for the TP61050/TPS61052
176 high-power "white LED driver". This boost converter is
177 sometimes used for other things than white LEDs, and
178 also contains a GPIO pin.
181 tristate "TPS6501x Power Management chips"
182 depends on I2C && GPIOLIB
183 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
185 If you say yes here you get support for the TPS6501x series of
186 Power Management chips. These include voltage regulators,
187 lithium ion/polymer battery charging, and other features that
188 are often used in portable devices like cell phones and cameras.
190 This driver can also be built as a module. If so, the module
191 will be called tps65010.
194 tristate "TPS6507x Power Management / Touch Screen chips"
198 If you say yes here you get support for the TPS6507x series of
199 Power Management / Touch Screen chips. These include voltage
200 regulators, lithium ion/polymer battery charging, touch screen
201 and other features that are often used in portable devices.
202 This driver can also be built as a module. If so, the module
203 will be called tps6507x.
206 tristate "TPS65217 Power Management / White LED chips"
211 If you say yes here you get support for the TPS65217 series of
212 Power Management / White LED chips.
213 These include voltage regulators, lithium ion/polymer battery
214 charger, wled and other features that are often used in portable
217 This driver can also be built as a module. If so, the module
218 will be called tps65217.
221 bool "TPS6586x Power Management chips"
222 depends on I2C=y && GENERIC_HARDIRQS
226 If you say yes here you get support for the TPS6586X series of
227 Power Management chips.
228 This driver provides common support for accessing the device,
229 additional drivers must be enabled in order to use the
230 functionality of the device.
232 This driver can also be built as a module. If so, the module
233 will be called tps6586x.
236 bool "TPS65910 Power Management chip"
237 depends on I2C=y && GPIOLIB
243 if you say yes here you get support for the TPS65910 series of
244 Power Management chips.
250 config MFD_TPS65912_I2C
251 bool "TPS65912 Power Management chip with I2C"
254 depends on I2C=y && GPIOLIB
256 If you say yes here you get support for the TPS65912 series of
257 PM chips with I2C interface.
259 config MFD_TPS65912_SPI
260 bool "TPS65912 Power Management chip with SPI"
263 depends on SPI_MASTER && GPIOLIB
265 If you say yes here you get support for the TPS65912 series of
266 PM chips with SPI interface.
269 bool "TI TPS80031/TPS80032 Power Management chips"
270 depends on I2C=y && GENERIC_HARDIRQS
275 If you say yes here you get support for the Texas Instruments
276 TPS80031/ TPS80032 Fully Integrated Power Management with Power
277 Path and Battery Charger. The device provides five configurable
278 step-down converters, 11 general purpose LDOs, USB OTG Module,
279 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
280 Power Path from USB, 32K clock generator.
283 bool "Texas Instruments TWL92330/Menelaus PM chip"
284 depends on I2C=y && ARCH_OMAP2
286 If you say yes here you get support for the Texas Instruments
287 TWL92330/Menelaus Power Management chip. This include voltage
288 regulators, Dual slot memory card transceivers, real-time clock
289 and other features that are often used in portable devices like
290 cell phones and PDAs.
293 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
294 depends on I2C=y && GENERIC_HARDIRQS
298 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
299 This core driver provides register access and IRQ handling
300 facilities, and registers devices for the various functions
301 so that function-specific drivers can bind to them.
303 These multi-function chips are found on many OMAP2 and OMAP3
304 boards, providing power management, RTC, GPIO, keypad, a
305 high speed USB OTG transceiver, an audio codec (on most
306 versions) and many other features.
309 tristate "Texas Instruments TWL4030 MADC"
310 depends on TWL4030_CORE
312 This driver provides support for triton TWL4030-MADC. The
313 driver supports both RT and SW conversion methods.
315 This driver can be built as a module. If so it will be
319 bool "Support power resources on TWL4030 family chips"
320 depends on TWL4030_CORE && ARM
322 Say yes here if you want to use the power resources on the
323 TWL4030 family chips. Most of these resources are regulators,
324 which have a separate driver; some are control signals, such
325 as clock request handshaking.
327 This driver uses board-specific data to initialize the resources
328 and load scripts controlling which resources are switched off/on
329 or reset when a sleep, wakeup or warm reset event occurs.
331 config MFD_TWL4030_AUDIO
333 depends on TWL4030_CORE
338 bool "Support for TWL6040 audio codec"
345 Say yes here if you want support for Texas Instruments TWL6040 audio
347 This driver provides common support for accessing the device,
348 additional drivers must be enabled in order to use the
349 functionality of the device (audio, vibra).
352 bool "Support STMicroelectronics STMPE"
353 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
356 Support for the STMPE family of I/O Expanders from
359 Currently supported devices are:
361 STMPE811: GPIO, Touchscreen
362 STMPE1601: GPIO, Keypad
363 STMPE2401: GPIO, Keypad
364 STMPE2403: GPIO, Keypad
366 This driver provides common support for accessing the device,
367 additional drivers must be enabled in order to use the functionality
368 of the device. Currently available sub drivers are:
372 Touchscreen: stmpe-ts
374 menu "STMPE Interface Drivers"
378 bool "STMPE I2C Inteface"
382 This is used to enable I2C interface of STMPE
385 bool "STMPE SPI Inteface"
386 depends on SPI_MASTER
388 This is used to enable SPI interface of STMPE
392 bool "Support Toshiba TC35892 and variants"
393 depends on I2C=y && GENERIC_HARDIRQS
396 Support for the Toshiba TC35892 and variants I/O Expander.
398 This driver provides common support for accessing the device,
399 additional drivers must be enabled in order to use the
400 functionality of the device.
407 bool "Support Toshiba T7L66XB"
408 depends on ARM && HAVE_CLK
412 Support for Toshiba Mobile IO Controller T7L66XB
415 bool "Support for the SMSC ECE1099 series chips"
420 If you say yes here you get support for the
421 ece1099 chips from SMSC.
423 To compile this driver as a module, choose M here: the
424 module will be called smsc.
427 bool "Support Toshiba TC6387XB"
428 depends on ARM && HAVE_CLK
432 Support for Toshiba Mobile IO Controller TC6387XB
435 bool "Support Toshiba TC6393XB"
436 depends on ARM && HAVE_CLK
441 Support for Toshiba Mobile IO Controller TC6393XB
444 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
447 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
448 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
449 usually found on PXA processors-based platforms. This includes
450 the I2C driver and the core APIs _only_, you have to select
451 individual components like LCD backlight, voltage regulators,
452 LEDs and battery-charger under the corresponding menus.
458 config MFD_DA9052_SPI
459 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
463 depends on SPI_MASTER=y
465 Support for the Dialog Semiconductor DA9052 PMIC
466 when controlled using SPI. This driver provides common support
467 for accessing the device, additional drivers must be enabled in
468 order to use the functionality of the device.
470 config MFD_DA9052_I2C
471 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
477 Support for the Dialog Semiconductor DA9052 PMIC
478 when controlled using I2C. This driver provides common support
479 for accessing the device, additional drivers must be enabled in
480 order to use the functionality of the device.
483 bool "Dialog Semiconductor DA9055 PMIC Support"
490 Say yes here for support of Dialog Semiconductor DA9055. This is
491 a Power Management IC. This driver provides common support for
492 accessing the device as well as the I2C interface to the chip itself.
493 Additional drivers must be enabled in order to use the functionality
496 This driver can be built as a module. If built as a module it will be
500 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
503 Say yes here to add support for Analog Devices AD5520 and ADP5501,
504 Multifunction Power Management IC. This includes
505 the I2C driver and the core APIs _only_, you have to select
506 individual components like LCD backlight, LEDs, GPIOs and Kepad
507 under the corresponding menus.
510 bool "Texas Instruments LP8788 Power Management Unit Driver"
516 TI LP8788 PMU supports regulators, battery charger, RTC,
517 ADC, backlight driver and current sinks.
520 bool "Maxim Semiconductor MAX77686 PMIC Support"
521 depends on I2C=y && GENERIC_HARDIRQS
526 Say yes here to support for Maxim Semiconductor MAX77686.
527 This is a Power Management IC with RTC on chip.
528 This driver provides common support for accessing the device;
529 additional drivers must be enabled in order to use the functionality
533 bool "Maxim Semiconductor MAX77693 PMIC Support"
534 depends on I2C=y && GENERIC_HARDIRQS
538 Say yes here to support for Maxim Semiconductor MAX77693.
539 This is a companion Power Management IC with Flash, Haptic, Charger,
540 and MUIC(Micro USB Interface Controller) controls on chip.
541 This driver provides common support for accessing the device;
542 additional drivers must be enabled in order to use the functionality
546 tristate "Maxim Semiconductor MAX8907 PMIC Support"
548 depends on I2C=y && GENERIC_HARDIRQS
552 Say yes here to support for Maxim Semiconductor MAX8907. This is
553 a Power Management IC. This driver provides common support for
554 accessing the device; additional drivers must be enabled in order
555 to use the functionality of the device.
558 bool "Maxim Semiconductor MAX8925 PMIC Support"
559 depends on I2C=y && GENERIC_HARDIRQS
562 Say yes here to support for Maxim Semiconductor MAX8925. This is
563 a Power Management IC. This driver provides common support for
564 accessing the device, additional drivers must be enabled in order
565 to use the functionality of the device.
568 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
569 depends on I2C=y && GENERIC_HARDIRQS
573 Say yes here to support for Maxim Semiconductor MAX8997/8966.
574 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
575 MUIC controls on chip.
576 This driver provides common support for accessing the device;
577 additional drivers must be enabled in order to use the functionality
581 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
582 depends on I2C=y && GENERIC_HARDIRQS
585 Say yes here to support for Maxim Semiconductor MAX8998 and
586 National Semiconductor LP3974. This is a Power Management IC.
587 This driver provides common support for accessing the device,
588 additional drivers must be enabled in order to use the functionality
592 bool "SAMSUNG Electronics PMIC Series Support"
593 depends on I2C=y && GENERIC_HARDIRQS
598 Support for the Samsung Electronics MFD series.
599 This driver provides common support for accessing the device,
600 additional drivers must be enabled in order to use the functionality
609 config MFD_ARIZONA_I2C
610 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
616 Support for the Wolfson Microelectronics Arizona platform audio SoC
617 core functionality controlled via I2C.
619 config MFD_ARIZONA_SPI
620 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
624 depends on SPI_MASTER
626 Support for the Wolfson Microelectronics Arizona platform audio SoC
627 core functionality controlled via I2C.
630 bool "Support Wolfson Microelectronics WM5102"
631 depends on MFD_ARIZONA
633 Support for Wolfson Microelectronics WM5102 low power audio SoC
636 bool "Support Wolfson Microelectronics WM5110"
637 depends on MFD_ARIZONA
639 Support for Wolfson Microelectronics WM5110 low power audio SoC
642 bool "Support Wolfson Microelectronics WM8400"
647 Support for the Wolfson Microelecronics WM8400 PMIC and audio
648 CODEC. This driver provides common support for accessing
649 the device, additional drivers must be enabled in order to use
650 the functionality of the device.
654 depends on GENERIC_HARDIRQS
656 config MFD_WM831X_I2C
657 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
662 depends on I2C=y && GENERIC_HARDIRQS
664 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
665 when controlled using I2C. This driver provides common support
666 for accessing the device, additional drivers must be enabled in
667 order to use the functionality of the device.
669 config MFD_WM831X_SPI
670 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
675 depends on SPI_MASTER && GENERIC_HARDIRQS
677 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
678 when controlled using SPI. This driver provides common support
679 for accessing the device, additional drivers must be enabled in
680 order to use the functionality of the device.
684 depends on GENERIC_HARDIRQS
686 config MFD_WM8350_CONFIG_MODE_0
688 depends on MFD_WM8350
690 config MFD_WM8350_CONFIG_MODE_1
692 depends on MFD_WM8350
694 config MFD_WM8350_CONFIG_MODE_2
696 depends on MFD_WM8350
698 config MFD_WM8350_CONFIG_MODE_3
700 depends on MFD_WM8350
702 config MFD_WM8351_CONFIG_MODE_0
704 depends on MFD_WM8350
706 config MFD_WM8351_CONFIG_MODE_1
708 depends on MFD_WM8350
710 config MFD_WM8351_CONFIG_MODE_2
712 depends on MFD_WM8350
714 config MFD_WM8351_CONFIG_MODE_3
716 depends on MFD_WM8350
718 config MFD_WM8352_CONFIG_MODE_0
720 depends on MFD_WM8350
722 config MFD_WM8352_CONFIG_MODE_1
724 depends on MFD_WM8350
726 config MFD_WM8352_CONFIG_MODE_2
728 depends on MFD_WM8350
730 config MFD_WM8352_CONFIG_MODE_3
732 depends on MFD_WM8350
734 config MFD_WM8350_I2C
735 bool "Support Wolfson Microelectronics WM8350 with I2C"
737 depends on I2C=y && GENERIC_HARDIRQS
739 The WM8350 is an integrated audio and power management
740 subsystem with watchdog and RTC functionality for embedded
741 systems. This option enables core support for the WM8350 with
742 I2C as the control interface. Additional options must be
743 selected to enable support for the functionality of the chip.
746 bool "Support Wolfson Microelectronics WM8994"
750 depends on I2C=y && GENERIC_HARDIRQS
752 The WM8994 is a highly integrated hi-fi CODEC designed for
753 smartphone applicatiosn. As well as audio functionality it
754 has on board GPIO and regulator functionality which is
755 supported via the relevant subsystems. This driver provides
756 core support for the WM8994, in order to use the actual
757 functionaltiy of the device other drivers must be enabled.
760 tristate "Support for NXP PCF50633"
764 Say yes here if you have NXP PCF50633 chip on your board.
765 This core driver provides register access and IRQ handling
766 facilities, and registers devices for the various functions
767 so that function-specific drivers can bind to them.
770 tristate "Support for NXP PCF50633 ADC"
771 depends on MFD_PCF50633
773 Say yes here if you want to include support for ADC in the
777 tristate "Support for NXP PCF50633 GPIO"
778 depends on MFD_PCF50633
780 Say yes here if you want to include support GPIO for pins on
788 depends on SPI_MASTER || I2C
792 Enable support for the Freescale MC13783 and MC13892 PMICs.
793 This driver provides common support for accessing the device,
794 additional drivers must be enabled in order to use the
795 functionality of the device.
797 config MFD_MC13XXX_SPI
798 tristate "Freescale MC13783 and MC13892 SPI interface"
799 depends on SPI_MASTER
803 Select this if your MC13xxx is connected via an SPI bus.
805 config MFD_MC13XXX_I2C
806 tristate "Freescale MC13892 I2C interface"
811 Select this if your MC13xxx is connected via an I2C bus.
814 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
815 default y if ARCH_U300 || ARCH_U8500
817 Say yes here if you have the ABX500 Mixed Signal IC family
818 chips. This core driver expose register access functions.
819 Functionality specific drivers using these functions can
820 remain unchanged when IC changes. Binding of the functions to
821 actual register access is done by the IC core driver.
824 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
825 depends on I2C=y && ABX500_CORE
827 default y if ARCH_U300
829 Select this to enable the AB3100 Mixed Signal IC core
830 functionality. This connects to a AB3100 on the I2C bus
831 and expose a number of symbols needed for dependent devices
832 to read and write registers and subscribe to events from
833 this multi-functional IC. This is needed to use other features
834 of the AB3100 such as battery-backed RTC, charging control,
835 LEDs, vibrator, system power and temperature, power management
839 tristate "ST-Ericsson AB3100 OTP functions"
840 depends on AB3100_CORE
841 default y if AB3100_CORE
843 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
844 programmable memory) support. This exposes a sysfs file to read
849 depends on GENERIC_HARDIRQS && SPI_MASTER
851 This enables the PCAP ASIC present on EZX Phones. This is
852 needed for MMC, TouchScreen, Sound, USB, etc..
855 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
856 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
860 Select this option to enable access to AB8500 power management
861 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
862 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
863 the irq_chip parts for handling the Mixed Signal chip events.
864 This chip embeds various other multimedia funtionalities as well.
867 bool "Enable debug info via debugfs"
868 depends on AB8500_CORE && DEBUG_FS
869 default y if DEBUG_FS
871 Select this option if you want debug information using the debug
875 bool "AB8500 GPADC driver"
876 depends on AB8500_CORE && REGULATOR_AB8500
879 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
881 config MFD_DB8500_PRCMU
882 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
883 depends on UX500_SOC_DB8500
886 Select this option to enable support for the DB8500 Power Reset
887 and Control Management Unit. This is basically an autonomous
888 system controller running an XP70 microprocessor, which is accessed
889 through a register map.
892 tristate "Support for CS5535 and CS5536 southbridge core functions"
894 depends on PCI && X86
896 This is the core driver for CS5535/CS5536 MFD functions. This is
897 necessary for using the board's GPIO and MFGPT functionality.
899 config MFD_TIMBERDALE
900 tristate "Support for the Timberdale FPGA"
902 depends on PCI && GPIOLIB
904 This is the core driver for the timberdale FPGA. This device is a
905 multifunction device which exposes numerous platform devices.
907 The timberdale FPGA can be found on the Intel Atom development board
908 for in-vehicle infontainment, called Russellville.
911 tristate "Intel SCH LPC"
915 LPC bridge function of the Intel SCH provides support for
916 System Management Bus and General Purpose I/O.
919 tristate "Intel ICH LPC"
923 The LPC bridge function of the Intel ICH provides support for
924 many functional units. This driver provides needed support for
925 other drivers to control these functions, currently GPIO and
929 tristate "Support for RDC-R321x southbridge"
933 Say yes here if you want to have support for the RDC R-321x SoC
934 southbridge which provides access to GPIOs and Watchdog using the
935 southbridge PCI device configuration space.
937 config MFD_JANZ_CMODIO
938 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
942 This is the core driver for the Janz CMOD-IO PCI MODULbus
943 carrier board. This device is a PCI to MODULbus bridge which may
944 host many different types of MODULbus daughterboards, including
945 CAN and GPIO controllers.
947 config MFD_JZ4740_ADC
948 bool "Support for the JZ4740 SoC ADC core"
950 select GENERIC_IRQ_CHIP
951 depends on MACH_JZ4740
953 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
954 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
957 tristate "Support for VIA VX855/VX875 integrated south bridge"
961 Say yes here to enable support for various functions of the
962 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
963 and/or vx855_gpio drivers for this to do anything useful.
965 config MFD_WL1273_CORE
966 tristate "Support for TI WL1273 FM radio."
971 This is the core driver for the TI WL1273 FM radio. This MFD
972 driver connects the radio-wl1273 V4L2 module and the wl1273
975 config MFD_OMAP_USB_HOST
976 bool "Support OMAP USBHS core and TLL driver"
977 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
980 This is the core driver for the OAMP EHCI and OHCI drivers.
981 This MFD driver does the required setup functionalities for
982 OMAP USB Host drivers.
987 config MFD_PM8921_CORE
988 tristate "Qualcomm PM8921 PMIC chip"
993 If you say yes to this option, support will be included for the
994 built-in PM8921 PMIC chip.
996 This is required if your board has a PM8921 and uses its features,
997 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
999 Say M here if you want to include support for PM8921 chip as a module.
1000 This will build a module called "pm8921-core".
1002 config MFD_PM8XXX_IRQ
1003 bool "Support for Qualcomm PM8xxx IRQ features"
1004 depends on MFD_PM8XXX
1005 default y if MFD_PM8XXX
1007 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
1009 This is required to use certain other PM 8xxx features, such as GPIO
1012 config TPS65911_COMPARATOR
1016 bool "TPS65090 Power Management chips"
1017 depends on I2C=y && GENERIC_HARDIRQS
1022 If you say yes here you get support for the TPS65090 series of
1023 Power Management chips.
1024 This driver provides common support for accessing the device,
1025 additional drivers must be enabled in order to use the
1026 functionality of the device.
1028 config MFD_AAT2870_CORE
1029 bool "Support for the AnalogicTech AAT2870"
1031 depends on I2C=y && GPIOLIB
1033 If you say yes here you get support for the AAT2870.
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.
1038 config MFD_INTEL_MSIC
1039 bool "Support for Intel MSIC"
1040 depends on INTEL_SCU_IPC
1043 Select this option to enable access to Intel MSIC (Avatele
1044 Passage) chip. This chip embeds audio, battery, GPIO, etc.
1045 devices used in Intel Medfield platforms.
1048 bool "Ricoh RC5T583 Power Management system device"
1049 depends on I2C=y && GENERIC_HARDIRQS
1053 Select this option to get support for the RICOH583 Power
1054 Management system device.
1055 This driver provides common support for accessing the device
1056 through i2c interface. The device supports multiple sub-devices
1057 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1058 Additional drivers must be enabled in order to use the
1059 different functionality of the device.
1062 bool "STA2X11 multi function device support"
1068 bool "System Controller Register R/W Based on Regmap"
1072 Select this option to enable accessing system control registers
1076 bool "Support for the TI Palmas series chips"
1082 If you say yes here you get support for the Palmas
1083 series of PMIC chips from Texas Instruments.
1085 config MFD_VIPERBOARD
1086 tristate "Support for Nano River Technologies Viperboard"
1091 Say yes here if you want support for Nano River Technologies
1093 There are mfd cell drivers available for i2c master, adc and
1094 both gpios found on the board. The spi part does not yet
1096 You need to select the mfd cell drivers separately.
1097 The drivers do not support all features the board exposes.
1100 tristate "Support for Retu multi-function device"
1105 Retu is a multi-function device found on Nokia Internet Tablets
1106 (770, N800 and N810).
1109 bool "Support for AS3711"
1115 Support for the AS3711 PMIC from AMS
1120 menu "Multimedia Capabilities Port drivers"
1121 depends on ARCH_SA1100
1128 tristate "Support SA11x0 MCP interface"
1129 depends on ARCH_SA1100
1134 bool "Support for UCB1200 / UCB1300"
1135 depends on MCP_SA11X0
1138 config MCP_UCB1200_TS
1139 tristate "Touchscreen interface support"
1140 depends on MCP_UCB1200 && INPUT
1144 config VEXPRESS_CONFIG
1147 Platform configuration infrastructure for the ARM Ltd.