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 bool "Support for Compaq ASIC3"
68 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
71 This driver supports the ASIC3 multifunction chip found on many
72 PDAs (mainly iPAQ and HTC based ones)
74 config MFD_DAVINCI_VOICECODEC
78 config MFD_DM355EVM_MSP
79 bool "DaVinci DM355 EVM microcontroller"
80 depends on I2C=y && MACH_DAVINCI_DM355_EVM
82 This driver supports the MSP430 microcontroller used on these
83 boards. MSP430 firmware manages resets and power sequencing,
84 inputs from buttons and the IR remote, LEDs, an RTC, and more.
87 tristate "TI Sequencer Serial Port support"
88 depends on ARCH_DAVINCI_TNETV107X
91 Say Y here if you want support for the Sequencer Serial Port
92 in a Texas Instruments TNETV107X SoC.
94 To compile this driver as a module, choose M here: the
95 module will be called ti-ssp.
98 bool "HTC EGPIO support"
99 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
101 This driver supports the CPLD egpio chip present on
102 several HTC phones. It provides basic support for input
103 pins, output pins, and irqs.
106 tristate "HTC PASIC3 LED/DS1WM chip support"
109 This core driver provides register access for the LED/DS1WM
110 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
111 HTC Magician devices, respectively. Actual functionality is
112 handled by the leds-pasic3 and ds1wm drivers.
115 bool "HTC I2C PLD chip support"
116 depends on I2C=y && GPIOLIB
118 If you say yes here you get support for the supposed CPLD
119 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
120 This device provides input and output GPIOs through an I2C
121 interface to one or more sub-chips.
124 tristate "Philips UCB1400 Core driver"
128 This enables support for the Philips UCB1400 core functions.
129 The UCB1400 is an AC97 audio codec.
131 To compile this driver as a module, choose M here: the
132 module will be called ucb1400_core.
135 tristate "LM3533 Lighting Power chip"
140 Say yes here to enable support for National Semiconductor / TI
141 LM3533 Lighting Power chips.
143 This driver provides common support for accessing the device;
144 additional drivers must be enabled in order to use the LED,
145 backlight or ambient-light-sensor functionality of the device.
148 tristate "TPS61050/61052 Boost Converters"
152 select REGULATOR_FIXED_VOLTAGE
154 This option enables a driver for the TP61050/TPS61052
155 high-power "white LED driver". This boost converter is
156 sometimes used for other things than white LEDs, and
157 also contains a GPIO pin.
160 tristate "TPS6501x Power Management chips"
161 depends on I2C && GPIOLIB
162 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
164 If you say yes here you get support for the TPS6501x series of
165 Power Management chips. These include voltage regulators,
166 lithium ion/polymer battery charging, and other features that
167 are often used in portable devices like cell phones and cameras.
169 This driver can also be built as a module. If so, the module
170 will be called tps65010.
173 tristate "TPS6507x Power Management / Touch Screen chips"
177 If you say yes here you get support for the TPS6507x series of
178 Power Management / Touch Screen chips. These include voltage
179 regulators, lithium ion/polymer battery charging, touch screen
180 and other features that are often used in portable devices.
181 This driver can also be built as a module. If so, the module
182 will be called tps6507x.
185 tristate "TPS65217 Power Management / White LED chips"
190 If you say yes here you get support for the TPS65217 series of
191 Power Management / White LED chips.
192 These include voltage regulators, lithium ion/polymer battery
193 charger, wled and other features that are often used in portable
196 This driver can also be built as a module. If so, the module
197 will be called tps65217.
200 bool "TPS6586x Power Management chips"
201 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
205 If you say yes here you get support for the TPS6586X series of
206 Power Management chips.
207 This driver provides common support for accessing the device,
208 additional drivers must be enabled in order to use the
209 functionality of the device.
211 This driver can also be built as a module. If so, the module
212 will be called tps6586x.
215 bool "TPS65910 Power Management chip"
216 depends on I2C=y && GPIOLIB
221 if you say yes here you get support for the TPS65910 series of
222 Power Management chips.
228 config MFD_TPS65912_I2C
229 bool "TPS65912 Power Management chip with I2C"
232 depends on I2C=y && GPIOLIB
234 If you say yes here you get support for the TPS65912 series of
235 PM chips with I2C interface.
237 config MFD_TPS65912_SPI
238 bool "TPS65912 Power Management chip with SPI"
241 depends on SPI_MASTER && GPIOLIB
243 If you say yes here you get support for the TPS65912 series of
244 PM chips with SPI interface.
247 bool "Texas Instruments TWL92330/Menelaus PM chip"
248 depends on I2C=y && ARCH_OMAP2
250 If you say yes here you get support for the Texas Instruments
251 TWL92330/Menelaus Power Management chip. This include voltage
252 regulators, Dual slot memory card transceivers, real-time clock
253 and other features that are often used in portable devices like
254 cell phones and PDAs.
257 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
258 depends on I2C=y && GENERIC_HARDIRQS
261 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
262 This core driver provides register access and IRQ handling
263 facilities, and registers devices for the various functions
264 so that function-specific drivers can bind to them.
266 These multi-function chips are found on many OMAP2 and OMAP3
267 boards, providing power management, RTC, GPIO, keypad, a
268 high speed USB OTG transceiver, an audio codec (on most
269 versions) and many other features.
272 tristate "Texas Instruments TWL4030 MADC"
273 depends on TWL4030_CORE
275 This driver provides support for triton TWL4030-MADC. The
276 driver supports both RT and SW conversion methods.
278 This driver can be built as a module. If so it will be
282 bool "Support power resources on TWL4030 family chips"
283 depends on TWL4030_CORE && ARM
285 Say yes here if you want to use the power resources on the
286 TWL4030 family chips. Most of these resources are regulators,
287 which have a separate driver; some are control signals, such
288 as clock request handshaking.
290 This driver uses board-specific data to initialize the resources
291 and load scripts controlling which resources are switched off/on
292 or reset when a sleep, wakeup or warm reset event occurs.
294 config MFD_TWL4030_AUDIO
296 depends on TWL4030_CORE
301 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
302 depends on TWL4030_CORE
306 Say yes here if you want support for TWL6030 PWM.
307 This is used to control charging LED brightness.
310 bool "Support for TWL6040 audio codec"
311 depends on I2C=y && GENERIC_HARDIRQS
317 Say yes here if you want support for Texas Instruments TWL6040 audio
319 This driver provides common support for accessing the device,
320 additional drivers must be enabled in order to use the
321 functionality of the device (audio, vibra).
324 bool "Support STMicroelectronics STMPE"
325 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
328 Support for the STMPE family of I/O Expanders from
331 Currently supported devices are:
333 STMPE811: GPIO, Touchscreen
334 STMPE1601: GPIO, Keypad
335 STMPE2401: GPIO, Keypad
336 STMPE2403: GPIO, Keypad
338 This driver provides common support for accessing the device,
339 additional drivers must be enabled in order to use the functionality
340 of the device. Currently available sub drivers are:
344 Touchscreen: stmpe-ts
346 menu "STMPE Interface Drivers"
350 bool "STMPE I2C Inteface"
354 This is used to enable I2C interface of STMPE
357 bool "STMPE SPI Inteface"
358 depends on SPI_MASTER
360 This is used to enable SPI interface of STMPE
364 bool "Support Toshiba TC35892 and variants"
365 depends on I2C=y && GENERIC_HARDIRQS
368 Support for the Toshiba TC35892 and variants I/O Expander.
370 This driver provides common support for accessing the device,
371 additional drivers must be enabled in order to use the
372 functionality of the device.
379 bool "Support Toshiba T7L66XB"
380 depends on ARM && HAVE_CLK
384 Support for Toshiba Mobile IO Controller T7L66XB
387 bool "Support Toshiba TC6387XB"
388 depends on ARM && HAVE_CLK
392 Support for Toshiba Mobile IO Controller TC6387XB
395 bool "Support Toshiba TC6393XB"
396 depends on GPIOLIB && ARM && HAVE_CLK
400 Support for Toshiba Mobile IO Controller TC6393XB
403 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
406 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
407 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
408 usually found on PXA processors-based platforms. This includes
409 the I2C driver and the core APIs _only_, you have to select
410 individual components like LCD backlight, voltage regulators,
411 LEDs and battery-charger under the corresponding menus.
417 config MFD_DA9052_SPI
418 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
422 depends on SPI_MASTER=y
424 Support for the Dialog Semiconductor DA9052 PMIC
425 when controlled using SPI. This driver provides common support
426 for accessing the device, additional drivers must be enabled in
427 order to use the functionality of the device.
429 config MFD_DA9052_I2C
430 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
436 Support for the Dialog Semiconductor DA9052 PMIC
437 when controlled using I2C. This driver provides common support
438 for accessing the device, additional drivers must be enabled in
439 order to use the functionality of the device.
442 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
445 Say yes here to add support for Analog Devices AD5520 and ADP5501,
446 Multifunction Power Management IC. This includes
447 the I2C driver and the core APIs _only_, you have to select
448 individual components like LCD backlight, LEDs, GPIOs and Kepad
449 under the corresponding menus.
452 bool "Maxim Semiconductor MAX77686 PMIC Support"
453 depends on I2C=y && GENERIC_HARDIRQS
458 Say yes here to support for Maxim Semiconductor MAX77686.
459 This is a Power Management IC with RTC on chip.
460 This driver provides common support for accessing the device;
461 additional drivers must be enabled in order to use the functionality
465 bool "Maxim Semiconductor MAX77693 PMIC Support"
466 depends on I2C=y && GENERIC_HARDIRQS
470 Say yes here to support for Maxim Semiconductor MAX77693.
471 This is a companion Power Management IC with Flash, Haptic, Charger,
472 and MUIC(Micro USB Interface Controller) controls on chip.
473 This driver provides common support for accessing the device;
474 additional drivers must be enabled in order to use the functionality
478 bool "Maxim Semiconductor MAX8925 PMIC Support"
479 depends on I2C=y && GENERIC_HARDIRQS
482 Say yes here to support for Maxim Semiconductor MAX8925. This is
483 a Power Management IC. This driver provides common support for
484 accessing the device, additional drivers must be enabled in order
485 to use the functionality of the device.
488 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
489 depends on I2C=y && GENERIC_HARDIRQS
493 Say yes here to support for Maxim Semiconductor MAX8997/8966.
494 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
495 MUIC controls on chip.
496 This driver provides common support for accessing the device;
497 additional drivers must be enabled in order to use the functionality
501 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
502 depends on I2C=y && GENERIC_HARDIRQS
505 Say yes here to support for Maxim Semiconductor MAX8998 and
506 National Semiconductor LP3974. This is a Power Management IC.
507 This driver provides common support for accessing the device,
508 additional drivers must be enabled in order to use the functionality
512 bool "SAMSUNG S5M Series Support"
513 depends on I2C=y && GENERIC_HARDIRQS
517 Support for the Samsung Electronics S5M MFD series.
518 This driver provides common support for accessing the device,
519 additional drivers must be enabled in order to use the functionality
526 config MFD_ARIZONA_I2C
527 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
533 Support for the Wolfson Microelectronics Arizona platform audio SoC
534 core functionality controlled via I2C.
536 config MFD_ARIZONA_SPI
537 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
541 depends on SPI_MASTER
543 Support for the Wolfson Microelectronics Arizona platform audio SoC
544 core functionality controlled via I2C.
547 bool "Support Wolfson Microelectronics WM5102"
548 depends on MFD_ARIZONA
550 Support for Wolfson Microelectronics WM5102 low power audio SoC
553 bool "Support Wolfson Microelectronics WM8400"
558 Support for the Wolfson Microelecronics WM8400 PMIC and audio
559 CODEC. This driver provides common support for accessing
560 the device, additional drivers must be enabled in order to use
561 the functionality of the device.
565 depends on GENERIC_HARDIRQS
567 config MFD_WM831X_I2C
568 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
573 depends on I2C=y && GENERIC_HARDIRQS
575 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
576 when controlled using I2C. This driver provides common support
577 for accessing the device, additional drivers must be enabled in
578 order to use the functionality of the device.
580 config MFD_WM831X_SPI
581 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
586 depends on SPI_MASTER && GENERIC_HARDIRQS
588 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
589 when controlled using SPI. This driver provides common support
590 for accessing the device, additional drivers must be enabled in
591 order to use the functionality of the device.
595 depends on GENERIC_HARDIRQS
597 config MFD_WM8350_CONFIG_MODE_0
599 depends on MFD_WM8350
601 config MFD_WM8350_CONFIG_MODE_1
603 depends on MFD_WM8350
605 config MFD_WM8350_CONFIG_MODE_2
607 depends on MFD_WM8350
609 config MFD_WM8350_CONFIG_MODE_3
611 depends on MFD_WM8350
613 config MFD_WM8351_CONFIG_MODE_0
615 depends on MFD_WM8350
617 config MFD_WM8351_CONFIG_MODE_1
619 depends on MFD_WM8350
621 config MFD_WM8351_CONFIG_MODE_2
623 depends on MFD_WM8350
625 config MFD_WM8351_CONFIG_MODE_3
627 depends on MFD_WM8350
629 config MFD_WM8352_CONFIG_MODE_0
631 depends on MFD_WM8350
633 config MFD_WM8352_CONFIG_MODE_1
635 depends on MFD_WM8350
637 config MFD_WM8352_CONFIG_MODE_2
639 depends on MFD_WM8350
641 config MFD_WM8352_CONFIG_MODE_3
643 depends on MFD_WM8350
645 config MFD_WM8350_I2C
646 bool "Support Wolfson Microelectronics WM8350 with I2C"
648 depends on I2C=y && GENERIC_HARDIRQS
650 The WM8350 is an integrated audio and power management
651 subsystem with watchdog and RTC functionality for embedded
652 systems. This option enables core support for the WM8350 with
653 I2C as the control interface. Additional options must be
654 selected to enable support for the functionality of the chip.
657 bool "Support Wolfson Microelectronics WM8994"
661 depends on I2C=y && GENERIC_HARDIRQS
663 The WM8994 is a highly integrated hi-fi CODEC designed for
664 smartphone applicatiosn. As well as audio functionality it
665 has on board GPIO and regulator functionality which is
666 supported via the relevant subsystems. This driver provides
667 core support for the WM8994, in order to use the actual
668 functionaltiy of the device other drivers must be enabled.
671 tristate "Support for NXP PCF50633"
675 Say yes here if you have NXP PCF50633 chip on your board.
676 This core driver provides register access and IRQ handling
677 facilities, and registers devices for the various functions
678 so that function-specific drivers can bind to them.
681 tristate "Support for NXP PCF50633 ADC"
682 depends on MFD_PCF50633
684 Say yes here if you want to include support for ADC in the
688 tristate "Support for NXP PCF50633 GPIO"
689 depends on MFD_PCF50633
691 Say yes here if you want to include support GPIO for pins on
699 depends on SPI_MASTER || I2C
703 Enable support for the Freescale MC13783 and MC13892 PMICs.
704 This driver provides common support for accessing the device,
705 additional drivers must be enabled in order to use the
706 functionality of the device.
708 config MFD_MC13XXX_SPI
709 tristate "Freescale MC13783 and MC13892 SPI interface"
710 depends on SPI_MASTER
714 Select this if your MC13xxx is connected via an SPI bus.
716 config MFD_MC13XXX_I2C
717 tristate "Freescale MC13892 I2C interface"
722 Select this if your MC13xxx is connected via an I2C bus.
725 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
726 default y if ARCH_U300 || ARCH_U8500
728 Say yes here if you have the ABX500 Mixed Signal IC family
729 chips. This core driver expose register access functions.
730 Functionality specific drivers using these functions can
731 remain unchanged when IC changes. Binding of the functions to
732 actual register access is done by the IC core driver.
735 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
736 depends on I2C=y && ABX500_CORE
738 default y if ARCH_U300
740 Select this to enable the AB3100 Mixed Signal IC core
741 functionality. This connects to a AB3100 on the I2C bus
742 and expose a number of symbols needed for dependent devices
743 to read and write registers and subscribe to events from
744 this multi-functional IC. This is needed to use other features
745 of the AB3100 such as battery-backed RTC, charging control,
746 LEDs, vibrator, system power and temperature, power management
750 tristate "ST-Ericsson AB3100 OTP functions"
751 depends on AB3100_CORE
752 default y if AB3100_CORE
754 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
755 programmable memory) support. This exposes a sysfs file to read
760 depends on GENERIC_HARDIRQS && SPI_MASTER
762 This enables the PCAP ASIC present on EZX Phones. This is
763 needed for MMC, TouchScreen, Sound, USB, etc..
766 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
767 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
771 Select this option to enable access to AB8500 power management
772 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
773 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
774 the irq_chip parts for handling the Mixed Signal chip events.
775 This chip embeds various other multimedia funtionalities as well.
778 bool "Enable debug info via debugfs"
779 depends on AB8500_CORE && DEBUG_FS
780 default y if DEBUG_FS
782 Select this option if you want debug information using the debug
786 bool "AB8500 GPADC driver"
787 depends on AB8500_CORE && REGULATOR_AB8500
790 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
792 config MFD_DB8500_PRCMU
793 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
794 depends on UX500_SOC_DB8500
797 Select this option to enable support for the DB8500 Power Reset
798 and Control Management Unit. This is basically an autonomous
799 system controller running an XP70 microprocessor, which is accessed
800 through a register map.
803 tristate "Support for CS5535 and CS5536 southbridge core functions"
805 depends on PCI && X86
807 This is the core driver for CS5535/CS5536 MFD functions. This is
808 necessary for using the board's GPIO and MFGPT functionality.
810 config MFD_TIMBERDALE
811 tristate "Support for the Timberdale FPGA"
813 depends on PCI && GPIOLIB
815 This is the core driver for the timberdale FPGA. This device is a
816 multifunction device which exposes numerous platform devices.
818 The timberdale FPGA can be found on the Intel Atom development board
819 for in-vehicle infontainment, called Russellville.
822 tristate "Intel SCH LPC"
826 LPC bridge function of the Intel SCH provides support for
827 System Management Bus and General Purpose I/O.
830 tristate "Intel ICH LPC"
834 The LPC bridge function of the Intel ICH provides support for
835 many functional units. This driver provides needed support for
836 other drivers to control these functions, currently GPIO and
840 tristate "Support for RDC-R321x southbridge"
844 Say yes here if you want to have support for the RDC R-321x SoC
845 southbridge which provides access to GPIOs and Watchdog using the
846 southbridge PCI device configuration space.
848 config MFD_JANZ_CMODIO
849 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
853 This is the core driver for the Janz CMOD-IO PCI MODULbus
854 carrier board. This device is a PCI to MODULbus bridge which may
855 host many different types of MODULbus daughterboards, including
856 CAN and GPIO controllers.
858 config MFD_JZ4740_ADC
859 bool "Support for the JZ4740 SoC ADC core"
861 select GENERIC_IRQ_CHIP
862 depends on MACH_JZ4740
864 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
865 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
868 tristate "Support for VIA VX855/VX875 integrated south bridge"
872 Say yes here to enable support for various functions of the
873 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
874 and/or vx855_gpio drivers for this to do anything useful.
876 config MFD_WL1273_CORE
877 tristate "Support for TI WL1273 FM radio."
882 This is the core driver for the TI WL1273 FM radio. This MFD
883 driver connects the radio-wl1273 V4L2 module and the wl1273
886 config MFD_OMAP_USB_HOST
887 bool "Support OMAP USBHS core driver"
888 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
891 This is the core driver for the OAMP EHCI and OHCI drivers.
892 This MFD driver does the required setup functionalities for
893 OMAP USB Host drivers.
898 config MFD_PM8921_CORE
899 tristate "Qualcomm PM8921 PMIC chip"
904 If you say yes to this option, support will be included for the
905 built-in PM8921 PMIC chip.
907 This is required if your board has a PM8921 and uses its features,
908 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
910 Say M here if you want to include support for PM8921 chip as a module.
911 This will build a module called "pm8921-core".
913 config MFD_PM8XXX_IRQ
914 bool "Support for Qualcomm PM8xxx IRQ features"
915 depends on MFD_PM8XXX
916 default y if MFD_PM8XXX
918 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
920 This is required to use certain other PM 8xxx features, such as GPIO
923 config TPS65911_COMPARATOR
927 bool "TPS65090 Power Management chips"
928 depends on I2C=y && GENERIC_HARDIRQS
932 If you say yes here you get support for the TPS65090 series of
933 Power Management chips.
934 This driver provides common support for accessing the device,
935 additional drivers must be enabled in order to use the
936 functionality of the device.
938 config MFD_AAT2870_CORE
939 bool "Support for the AnalogicTech AAT2870"
941 depends on I2C=y && GPIOLIB
943 If you say yes here you get support for the AAT2870.
944 This driver provides common support for accessing the device,
945 additional drivers must be enabled in order to use the
946 functionality of the device.
948 config MFD_INTEL_MSIC
949 bool "Support for Intel MSIC"
950 depends on INTEL_SCU_IPC
953 Select this option to enable access to Intel MSIC (Avatele
954 Passage) chip. This chip embeds audio, battery, GPIO, etc.
955 devices used in Intel Medfield platforms.
958 bool "Ricoh RC5T583 Power Management system device"
959 depends on I2C=y && GENERIC_HARDIRQS
963 Select this option to get support for the RICOH583 Power
964 Management system device.
965 This driver provides common support for accessing the device
966 through i2c interface. The device supports multiple sub-devices
967 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
968 Additional drivers must be enabled in order to use the
969 different functionality of the device.
972 bool "STA2X11 multi function device support"
977 bool "Support for Freescale i.MX on-chip ANATOP controller"
980 Select this option to enable Freescale i.MX on-chip ANATOP
981 MFD controller. This controller embeds regulator and
982 thermal devices for Freescale i.MX platforms.
985 bool "Support for the TI Palmas series chips"
991 If you say yes here you get support for the Palmas
992 series of PMIC chips from Texas Instruments.
997 menu "Multimedia Capabilities Port drivers"
998 depends on ARCH_SA1100
1005 tristate "Support SA11x0 MCP interface"
1006 depends on ARCH_SA1100
1011 bool "Support for UCB1200 / UCB1300"
1012 depends on MCP_SA11X0
1015 config MCP_UCB1200_TS
1016 tristate "Touchscreen interface support"
1017 depends on MCP_UCB1200 && INPUT