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
242 if you say yes here you get support for the TPS65910 series of
243 Power Management chips.
249 config MFD_TPS65912_I2C
250 bool "TPS65912 Power Management chip with I2C"
253 depends on I2C=y && GPIOLIB
255 If you say yes here you get support for the TPS65912 series of
256 PM chips with I2C interface.
258 config MFD_TPS65912_SPI
259 bool "TPS65912 Power Management chip with SPI"
262 depends on SPI_MASTER && GPIOLIB
264 If you say yes here you get support for the TPS65912 series of
265 PM chips with SPI interface.
268 bool "TI TPS80031/TPS80032 Power Management chips"
269 depends on I2C=y && GENERIC_HARDIRQS
274 If you say yes here you get support for the Texas Instruments
275 TPS80031/ TPS80032 Fully Integrated Power Management with Power
276 Path and Battery Charger. The device provides five configurable
277 step-down converters, 11 general purpose LDOs, USB OTG Module,
278 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
279 Power Path from USB, 32K clock generator.
282 bool "Texas Instruments TWL92330/Menelaus PM chip"
283 depends on I2C=y && ARCH_OMAP2
285 If you say yes here you get support for the Texas Instruments
286 TWL92330/Menelaus Power Management chip. This include voltage
287 regulators, Dual slot memory card transceivers, real-time clock
288 and other features that are often used in portable devices like
289 cell phones and PDAs.
292 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
293 depends on I2C=y && GENERIC_HARDIRQS
297 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
298 This core driver provides register access and IRQ handling
299 facilities, and registers devices for the various functions
300 so that function-specific drivers can bind to them.
302 These multi-function chips are found on many OMAP2 and OMAP3
303 boards, providing power management, RTC, GPIO, keypad, a
304 high speed USB OTG transceiver, an audio codec (on most
305 versions) and many other features.
308 tristate "Texas Instruments TWL4030 MADC"
309 depends on TWL4030_CORE
311 This driver provides support for triton TWL4030-MADC. The
312 driver supports both RT and SW conversion methods.
314 This driver can be built as a module. If so it will be
318 bool "Support power resources on TWL4030 family chips"
319 depends on TWL4030_CORE && ARM
321 Say yes here if you want to use the power resources on the
322 TWL4030 family chips. Most of these resources are regulators,
323 which have a separate driver; some are control signals, such
324 as clock request handshaking.
326 This driver uses board-specific data to initialize the resources
327 and load scripts controlling which resources are switched off/on
328 or reset when a sleep, wakeup or warm reset event occurs.
330 config MFD_TWL4030_AUDIO
332 depends on TWL4030_CORE
337 bool "Support for TWL6040 audio codec"
344 Say yes here if you want support for Texas Instruments TWL6040 audio
346 This driver provides common support for accessing the device,
347 additional drivers must be enabled in order to use the
348 functionality of the device (audio, vibra).
351 bool "Support STMicroelectronics STMPE"
352 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
355 Support for the STMPE family of I/O Expanders from
358 Currently supported devices are:
360 STMPE811: GPIO, Touchscreen
361 STMPE1601: GPIO, Keypad
362 STMPE2401: GPIO, Keypad
363 STMPE2403: GPIO, Keypad
365 This driver provides common support for accessing the device,
366 additional drivers must be enabled in order to use the functionality
367 of the device. Currently available sub drivers are:
371 Touchscreen: stmpe-ts
373 menu "STMPE Interface Drivers"
377 bool "STMPE I2C Inteface"
381 This is used to enable I2C interface of STMPE
384 bool "STMPE SPI Inteface"
385 depends on SPI_MASTER
387 This is used to enable SPI interface of STMPE
391 bool "Support Toshiba TC35892 and variants"
392 depends on I2C=y && GENERIC_HARDIRQS
395 Support for the Toshiba TC35892 and variants I/O Expander.
397 This driver provides common support for accessing the device,
398 additional drivers must be enabled in order to use the
399 functionality of the device.
406 bool "Support Toshiba T7L66XB"
407 depends on ARM && HAVE_CLK
411 Support for Toshiba Mobile IO Controller T7L66XB
414 bool "Support for the SMSC ECE1099 series chips"
419 If you say yes here you get support for the
420 ece1099 chips from SMSC.
422 To compile this driver as a module, choose M here: the
423 module will be called smsc.
426 bool "Support Toshiba TC6387XB"
427 depends on ARM && HAVE_CLK
431 Support for Toshiba Mobile IO Controller TC6387XB
434 bool "Support Toshiba TC6393XB"
435 depends on ARM && HAVE_CLK
440 Support for Toshiba Mobile IO Controller TC6393XB
443 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
446 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
447 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
448 usually found on PXA processors-based platforms. This includes
449 the I2C driver and the core APIs _only_, you have to select
450 individual components like LCD backlight, voltage regulators,
451 LEDs and battery-charger under the corresponding menus.
457 config MFD_DA9052_SPI
458 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
462 depends on SPI_MASTER=y
464 Support for the Dialog Semiconductor DA9052 PMIC
465 when controlled using SPI. This driver provides common support
466 for accessing the device, additional drivers must be enabled in
467 order to use the functionality of the device.
469 config MFD_DA9052_I2C
470 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
476 Support for the Dialog Semiconductor DA9052 PMIC
477 when controlled using I2C. This driver provides common support
478 for accessing the device, additional drivers must be enabled in
479 order to use the functionality of the device.
482 bool "Dialog Semiconductor DA9055 PMIC Support"
489 Say yes here for support of Dialog Semiconductor DA9055. This is
490 a Power Management IC. This driver provides common support for
491 accessing the device as well as the I2C interface to the chip itself.
492 Additional drivers must be enabled in order to use the functionality
495 This driver can be built as a module. If built as a module it will be
499 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
502 Say yes here to add support for Analog Devices AD5520 and ADP5501,
503 Multifunction Power Management IC. This includes
504 the I2C driver and the core APIs _only_, you have to select
505 individual components like LCD backlight, LEDs, GPIOs and Kepad
506 under the corresponding menus.
509 bool "Texas Instruments LP8788 Power Management Unit Driver"
515 TI LP8788 PMU supports regulators, battery charger, RTC,
516 ADC, backlight driver and current sinks.
519 bool "Maxim Semiconductor MAX77686 PMIC Support"
520 depends on I2C=y && GENERIC_HARDIRQS
525 Say yes here to support for Maxim Semiconductor MAX77686.
526 This is a Power Management IC with RTC on chip.
527 This driver provides common support for accessing the device;
528 additional drivers must be enabled in order to use the functionality
532 bool "Maxim Semiconductor MAX77693 PMIC Support"
533 depends on I2C=y && GENERIC_HARDIRQS
537 Say yes here to support for Maxim Semiconductor MAX77693.
538 This is a companion Power Management IC with Flash, Haptic, Charger,
539 and MUIC(Micro USB Interface Controller) controls on chip.
540 This driver provides common support for accessing the device;
541 additional drivers must be enabled in order to use the functionality
545 tristate "Maxim Semiconductor MAX8907 PMIC Support"
547 depends on I2C=y && GENERIC_HARDIRQS
551 Say yes here to support for Maxim Semiconductor MAX8907. This is
552 a Power Management IC. This driver provides common support for
553 accessing the device; additional drivers must be enabled in order
554 to use the functionality of the device.
557 bool "Maxim Semiconductor MAX8925 PMIC Support"
558 depends on I2C=y && GENERIC_HARDIRQS
561 Say yes here to support for Maxim Semiconductor MAX8925. This is
562 a Power Management IC. This driver provides common support for
563 accessing the device, additional drivers must be enabled in order
564 to use the functionality of the device.
567 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
568 depends on I2C=y && GENERIC_HARDIRQS
572 Say yes here to support for Maxim Semiconductor MAX8997/8966.
573 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
574 MUIC controls on chip.
575 This driver provides common support for accessing the device;
576 additional drivers must be enabled in order to use the functionality
580 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
581 depends on I2C=y && GENERIC_HARDIRQS
584 Say yes here to support for Maxim Semiconductor MAX8998 and
585 National Semiconductor LP3974. This is a Power Management IC.
586 This driver provides common support for accessing the device,
587 additional drivers must be enabled in order to use the functionality
591 bool "SAMSUNG Electronics PMIC Series Support"
592 depends on I2C=y && GENERIC_HARDIRQS
597 Support for the Samsung Electronics MFD series.
598 This driver provides common support for accessing the device,
599 additional drivers must be enabled in order to use the functionality
608 config MFD_ARIZONA_I2C
609 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
615 Support for the Wolfson Microelectronics Arizona platform audio SoC
616 core functionality controlled via I2C.
618 config MFD_ARIZONA_SPI
619 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
623 depends on SPI_MASTER
625 Support for the Wolfson Microelectronics Arizona platform audio SoC
626 core functionality controlled via I2C.
629 bool "Support Wolfson Microelectronics WM5102"
630 depends on MFD_ARIZONA
632 Support for Wolfson Microelectronics WM5102 low power audio SoC
635 bool "Support Wolfson Microelectronics WM5110"
636 depends on MFD_ARIZONA
638 Support for Wolfson Microelectronics WM5110 low power audio SoC
641 bool "Support Wolfson Microelectronics WM8400"
646 Support for the Wolfson Microelecronics WM8400 PMIC and audio
647 CODEC. This driver provides common support for accessing
648 the device, additional drivers must be enabled in order to use
649 the functionality of the device.
653 depends on GENERIC_HARDIRQS
655 config MFD_WM831X_I2C
656 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
661 depends on I2C=y && GENERIC_HARDIRQS
663 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
664 when controlled using I2C. This driver provides common support
665 for accessing the device, additional drivers must be enabled in
666 order to use the functionality of the device.
668 config MFD_WM831X_SPI
669 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
674 depends on SPI_MASTER && GENERIC_HARDIRQS
676 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
677 when controlled using SPI. This driver provides common support
678 for accessing the device, additional drivers must be enabled in
679 order to use the functionality of the device.
683 depends on GENERIC_HARDIRQS
685 config MFD_WM8350_CONFIG_MODE_0
687 depends on MFD_WM8350
689 config MFD_WM8350_CONFIG_MODE_1
691 depends on MFD_WM8350
693 config MFD_WM8350_CONFIG_MODE_2
695 depends on MFD_WM8350
697 config MFD_WM8350_CONFIG_MODE_3
699 depends on MFD_WM8350
701 config MFD_WM8351_CONFIG_MODE_0
703 depends on MFD_WM8350
705 config MFD_WM8351_CONFIG_MODE_1
707 depends on MFD_WM8350
709 config MFD_WM8351_CONFIG_MODE_2
711 depends on MFD_WM8350
713 config MFD_WM8351_CONFIG_MODE_3
715 depends on MFD_WM8350
717 config MFD_WM8352_CONFIG_MODE_0
719 depends on MFD_WM8350
721 config MFD_WM8352_CONFIG_MODE_1
723 depends on MFD_WM8350
725 config MFD_WM8352_CONFIG_MODE_2
727 depends on MFD_WM8350
729 config MFD_WM8352_CONFIG_MODE_3
731 depends on MFD_WM8350
733 config MFD_WM8350_I2C
734 bool "Support Wolfson Microelectronics WM8350 with I2C"
736 depends on I2C=y && GENERIC_HARDIRQS
738 The WM8350 is an integrated audio and power management
739 subsystem with watchdog and RTC functionality for embedded
740 systems. This option enables core support for the WM8350 with
741 I2C as the control interface. Additional options must be
742 selected to enable support for the functionality of the chip.
745 bool "Support Wolfson Microelectronics WM8994"
749 depends on I2C=y && GENERIC_HARDIRQS
751 The WM8994 is a highly integrated hi-fi CODEC designed for
752 smartphone applicatiosn. As well as audio functionality it
753 has on board GPIO and regulator functionality which is
754 supported via the relevant subsystems. This driver provides
755 core support for the WM8994, in order to use the actual
756 functionaltiy of the device other drivers must be enabled.
759 tristate "Support for NXP PCF50633"
763 Say yes here if you have NXP PCF50633 chip on your board.
764 This core driver provides register access and IRQ handling
765 facilities, and registers devices for the various functions
766 so that function-specific drivers can bind to them.
769 tristate "Support for NXP PCF50633 ADC"
770 depends on MFD_PCF50633
772 Say yes here if you want to include support for ADC in the
776 tristate "Support for NXP PCF50633 GPIO"
777 depends on MFD_PCF50633
779 Say yes here if you want to include support GPIO for pins on
787 depends on SPI_MASTER || I2C
791 Enable support for the Freescale MC13783 and MC13892 PMICs.
792 This driver provides common support for accessing the device,
793 additional drivers must be enabled in order to use the
794 functionality of the device.
796 config MFD_MC13XXX_SPI
797 tristate "Freescale MC13783 and MC13892 SPI interface"
798 depends on SPI_MASTER
802 Select this if your MC13xxx is connected via an SPI bus.
804 config MFD_MC13XXX_I2C
805 tristate "Freescale MC13892 I2C interface"
810 Select this if your MC13xxx is connected via an I2C bus.
813 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
814 default y if ARCH_U300 || ARCH_U8500
816 Say yes here if you have the ABX500 Mixed Signal IC family
817 chips. This core driver expose register access functions.
818 Functionality specific drivers using these functions can
819 remain unchanged when IC changes. Binding of the functions to
820 actual register access is done by the IC core driver.
823 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
824 depends on I2C=y && ABX500_CORE
826 default y if ARCH_U300
828 Select this to enable the AB3100 Mixed Signal IC core
829 functionality. This connects to a AB3100 on the I2C bus
830 and expose a number of symbols needed for dependent devices
831 to read and write registers and subscribe to events from
832 this multi-functional IC. This is needed to use other features
833 of the AB3100 such as battery-backed RTC, charging control,
834 LEDs, vibrator, system power and temperature, power management
838 tristate "ST-Ericsson AB3100 OTP functions"
839 depends on AB3100_CORE
840 default y if AB3100_CORE
842 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
843 programmable memory) support. This exposes a sysfs file to read
848 depends on GENERIC_HARDIRQS && SPI_MASTER
850 This enables the PCAP ASIC present on EZX Phones. This is
851 needed for MMC, TouchScreen, Sound, USB, etc..
854 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
855 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
859 Select this option to enable access to AB8500 power management
860 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
861 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
862 the irq_chip parts for handling the Mixed Signal chip events.
863 This chip embeds various other multimedia funtionalities as well.
866 bool "Enable debug info via debugfs"
867 depends on AB8500_CORE && DEBUG_FS
868 default y if DEBUG_FS
870 Select this option if you want debug information using the debug
874 bool "AB8500 GPADC driver"
875 depends on AB8500_CORE && REGULATOR_AB8500
878 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
880 config MFD_DB8500_PRCMU
881 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
882 depends on UX500_SOC_DB8500
885 Select this option to enable support for the DB8500 Power Reset
886 and Control Management Unit. This is basically an autonomous
887 system controller running an XP70 microprocessor, which is accessed
888 through a register map.
891 tristate "Support for CS5535 and CS5536 southbridge core functions"
893 depends on PCI && X86
895 This is the core driver for CS5535/CS5536 MFD functions. This is
896 necessary for using the board's GPIO and MFGPT functionality.
898 config MFD_TIMBERDALE
899 tristate "Support for the Timberdale FPGA"
901 depends on PCI && GPIOLIB
903 This is the core driver for the timberdale FPGA. This device is a
904 multifunction device which exposes numerous platform devices.
906 The timberdale FPGA can be found on the Intel Atom development board
907 for in-vehicle infontainment, called Russellville.
910 tristate "Intel SCH LPC"
914 LPC bridge function of the Intel SCH provides support for
915 System Management Bus and General Purpose I/O.
918 tristate "Intel ICH LPC"
922 The LPC bridge function of the Intel ICH provides support for
923 many functional units. This driver provides needed support for
924 other drivers to control these functions, currently GPIO and
928 tristate "Support for RDC-R321x southbridge"
932 Say yes here if you want to have support for the RDC R-321x SoC
933 southbridge which provides access to GPIOs and Watchdog using the
934 southbridge PCI device configuration space.
936 config MFD_JANZ_CMODIO
937 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
941 This is the core driver for the Janz CMOD-IO PCI MODULbus
942 carrier board. This device is a PCI to MODULbus bridge which may
943 host many different types of MODULbus daughterboards, including
944 CAN and GPIO controllers.
946 config MFD_JZ4740_ADC
947 bool "Support for the JZ4740 SoC ADC core"
949 select GENERIC_IRQ_CHIP
950 depends on MACH_JZ4740
952 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
953 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
956 tristate "Support for VIA VX855/VX875 integrated south bridge"
960 Say yes here to enable support for various functions of the
961 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
962 and/or vx855_gpio drivers for this to do anything useful.
964 config MFD_WL1273_CORE
965 tristate "Support for TI WL1273 FM radio."
970 This is the core driver for the TI WL1273 FM radio. This MFD
971 driver connects the radio-wl1273 V4L2 module and the wl1273
974 config MFD_OMAP_USB_HOST
975 bool "Support OMAP USBHS core and TLL driver"
976 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
979 This is the core driver for the OAMP EHCI and OHCI drivers.
980 This MFD driver does the required setup functionalities for
981 OMAP USB Host drivers.
986 config MFD_PM8921_CORE
987 tristate "Qualcomm PM8921 PMIC chip"
992 If you say yes to this option, support will be included for the
993 built-in PM8921 PMIC chip.
995 This is required if your board has a PM8921 and uses its features,
996 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
998 Say M here if you want to include support for PM8921 chip as a module.
999 This will build a module called "pm8921-core".
1001 config MFD_PM8XXX_IRQ
1002 bool "Support for Qualcomm PM8xxx IRQ features"
1003 depends on MFD_PM8XXX
1004 default y if MFD_PM8XXX
1006 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
1008 This is required to use certain other PM 8xxx features, such as GPIO
1011 config TPS65911_COMPARATOR
1015 bool "TPS65090 Power Management chips"
1016 depends on I2C=y && GENERIC_HARDIRQS
1021 If you say yes here you get support for the TPS65090 series of
1022 Power Management chips.
1023 This driver provides common support for accessing the device,
1024 additional drivers must be enabled in order to use the
1025 functionality of the device.
1027 config MFD_AAT2870_CORE
1028 bool "Support for the AnalogicTech AAT2870"
1030 depends on I2C=y && GPIOLIB
1032 If you say yes here you get support for the AAT2870.
1033 This driver provides common support for accessing the device,
1034 additional drivers must be enabled in order to use the
1035 functionality of the device.
1037 config MFD_INTEL_MSIC
1038 bool "Support for Intel MSIC"
1039 depends on INTEL_SCU_IPC
1042 Select this option to enable access to Intel MSIC (Avatele
1043 Passage) chip. This chip embeds audio, battery, GPIO, etc.
1044 devices used in Intel Medfield platforms.
1047 bool "Ricoh RC5T583 Power Management system device"
1048 depends on I2C=y && GENERIC_HARDIRQS
1052 Select this option to get support for the RICOH583 Power
1053 Management system device.
1054 This driver provides common support for accessing the device
1055 through i2c interface. The device supports multiple sub-devices
1056 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1057 Additional drivers must be enabled in order to use the
1058 different functionality of the device.
1061 bool "STA2X11 multi function device support"
1067 bool "System Controller Register R/W Based on Regmap"
1071 Select this option to enable accessing system control registers
1075 bool "Support for the TI Palmas series chips"
1081 If you say yes here you get support for the Palmas
1082 series of PMIC chips from Texas Instruments.
1084 config MFD_VIPERBOARD
1085 tristate "Support for Nano River Technologies Viperboard"
1090 Say yes here if you want support for Nano River Technologies
1092 There are mfd cell drivers available for i2c master, adc and
1093 both gpios found on the board. The spi part does not yet
1095 You need to select the mfd cell drivers separately.
1096 The drivers do not support all features the board exposes.
1099 tristate "Support for Retu multi-function device"
1104 Retu is a multi-function device found on Nokia Internet Tablets
1105 (770, N800 and N810).
1108 bool "Support for AS3711"
1114 Support for the AS3711 PMIC from AMS
1119 menu "Multimedia Capabilities Port drivers"
1120 depends on ARCH_SA1100
1127 tristate "Support SA11x0 MCP interface"
1128 depends on ARCH_SA1100
1133 bool "Support for UCB1200 / UCB1300"
1134 depends on MCP_SA11X0
1137 config MCP_UCB1200_TS
1138 tristate "Touchscreen interface support"
1139 depends on MCP_UCB1200 && INPUT
1143 config VEXPRESS_CONFIG
1146 Platform configuration infrastructure for the ARM Ltd.