2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
18 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
19 This includes the I2C driver and the core APIs _only_, you have to
20 select individual components like voltage regulators, RTC and
21 battery-charger under the corresponding menus.
24 tristate "Support for Silicon Motion SM501"
26 This is the core driver for the Silicon Motion SM501 multimedia
27 companion chip. This device is a multifunction device which may
28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
34 bool "Export GPIO via GPIO layer"
35 depends on MFD_SM501 && GPIOLIB
37 This option uses the gpio library layer to export the 64 GPIO
38 lines on the SM501. The platform data is used to supply the
39 base number for the first GPIO line to register.
42 bool "Support for Compaq ASIC3"
43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
49 config MFD_DAVINCI_VOICECODEC
53 config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
57 This driver supports the MSP430 microcontroller used on these
58 boards. MSP430 firmware manages resets and power sequencing,
59 inputs from buttons and the IR remote, LEDs, an RTC, and more.
62 tristate "TI Sequencer Serial Port support"
63 depends on ARCH_DAVINCI_TNETV107X
66 Say Y here if you want support for the Sequencer Serial Port
67 in a Texas Instruments TNETV107X SoC.
69 To compile this driver as a module, choose M here: the
70 module will be called ti-ssp.
73 bool "HTC EGPIO support"
74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
76 This driver supports the CPLD egpio chip present on
77 several HTC phones. It provides basic support for input
78 pins, output pins, and irqs.
81 tristate "HTC PASIC3 LED/DS1WM chip support"
84 This core driver provides register access for the LED/DS1WM
85 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
86 HTC Magician devices, respectively. Actual functionality is
87 handled by the leds-pasic3 and ds1wm drivers.
90 bool "HTC I2C PLD chip support"
91 depends on I2C=y && GPIOLIB
93 If you say yes here you get support for the supposed CPLD
94 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
95 This device provides input and output GPIOs through an I2C
96 interface to one or more sub-chips.
99 tristate "Philips UCB1400 Core driver"
103 This enables support for the Philips UCB1400 core functions.
104 The UCB1400 is an AC97 audio codec.
106 To compile this driver as a module, choose M here: the
107 module will be called ucb1400_core.
110 tristate "LM3533 Lighting Power chip"
115 Say yes here to enable support for National Semiconductor / TI
116 LM3533 Lighting Power chips.
118 This driver provides common support for accessing the device;
119 additional drivers must be enabled in order to use the LED,
120 backlight or ambient-light-sensor functionality of the device.
123 tristate "TPS61050/61052 Boost Converters"
127 select REGULATOR_FIXED_VOLTAGE
129 This option enables a driver for the TP61050/TPS61052
130 high-power "white LED driver". This boost converter is
131 sometimes used for other things than white LEDs, and
132 also contains a GPIO pin.
135 tristate "TPS6501x Power Management chips"
136 depends on I2C && GPIOLIB
137 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
139 If you say yes here you get support for the TPS6501x series of
140 Power Management chips. These include voltage regulators,
141 lithium ion/polymer battery charging, and other features that
142 are often used in portable devices like cell phones and cameras.
144 This driver can also be built as a module. If so, the module
145 will be called tps65010.
148 tristate "TPS6507x Power Management / Touch Screen chips"
152 If you say yes here you get support for the TPS6507x series of
153 Power Management / Touch Screen chips. These include voltage
154 regulators, lithium ion/polymer battery charging, touch screen
155 and other features that are often used in portable devices.
156 This driver can also be built as a module. If so, the module
157 will be called tps6507x.
160 tristate "TPS65217 Power Management / White LED chips"
165 If you say yes here you get support for the TPS65217 series of
166 Power Management / White LED chips.
167 These include voltage regulators, lithium ion/polymer battery
168 charger, wled and other features that are often used in portable
171 This driver can also be built as a module. If so, the module
172 will be called tps65217.
175 bool "TPS6586x Power Management chips"
176 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
179 If you say yes here you get support for the TPS6586X series of
180 Power Management chips.
181 This driver provides common support for accessing the device,
182 additional drivers must be enabled in order to use the
183 functionality of the device.
185 This driver can also be built as a module. If so, the module
186 will be called tps6586x.
189 bool "TPS65910 Power Management chip"
190 depends on I2C=y && GPIOLIB
195 if you say yes here you get support for the TPS65910 series of
196 Power Management chips.
202 config MFD_TPS65912_I2C
203 bool "TPS65912 Power Management chip with I2C"
206 depends on I2C=y && GPIOLIB
208 If you say yes here you get support for the TPS65912 series of
209 PM chips with I2C interface.
211 config MFD_TPS65912_SPI
212 bool "TPS65912 Power Management chip with SPI"
215 depends on SPI_MASTER && GPIOLIB
217 If you say yes here you get support for the TPS65912 series of
218 PM chips with SPI interface.
221 bool "Texas Instruments TWL92330/Menelaus PM chip"
222 depends on I2C=y && ARCH_OMAP2
224 If you say yes here you get support for the Texas Instruments
225 TWL92330/Menelaus Power Management chip. This include voltage
226 regulators, Dual slot memory card transceivers, real-time clock
227 and other features that are often used in portable devices like
228 cell phones and PDAs.
231 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
232 depends on I2C=y && GENERIC_HARDIRQS
235 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
236 This core driver provides register access and IRQ handling
237 facilities, and registers devices for the various functions
238 so that function-specific drivers can bind to them.
240 These multi-function chips are found on many OMAP2 and OMAP3
241 boards, providing power management, RTC, GPIO, keypad, a
242 high speed USB OTG transceiver, an audio codec (on most
243 versions) and many other features.
246 tristate "Texas Instruments TWL4030 MADC"
247 depends on TWL4030_CORE
249 This driver provides support for triton TWL4030-MADC. The
250 driver supports both RT and SW conversion methods.
252 This driver can be built as a module. If so it will be
256 bool "Support power resources on TWL4030 family chips"
257 depends on TWL4030_CORE && ARM
259 Say yes here if you want to use the power resources on the
260 TWL4030 family chips. Most of these resources are regulators,
261 which have a separate driver; some are control signals, such
262 as clock request handshaking.
264 This driver uses board-specific data to initialize the resources
265 and load scripts controlling which resources are switched off/on
266 or reset when a sleep, wakeup or warm reset event occurs.
268 config MFD_TWL4030_AUDIO
270 depends on TWL4030_CORE
275 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
276 depends on TWL4030_CORE
280 Say yes here if you want support for TWL6030 PWM.
281 This is used to control charging LED brightness.
284 bool "Support for TWL6040 audio codec"
285 depends on I2C=y && GENERIC_HARDIRQS
290 Say yes here if you want support for Texas Instruments TWL6040 audio
292 This driver provides common support for accessing the device,
293 additional drivers must be enabled in order to use the
294 functionality of the device (audio, vibra).
297 bool "Support STMicroelectronics STMPE"
298 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
301 Support for the STMPE family of I/O Expanders from
304 Currently supported devices are:
306 STMPE811: GPIO, Touchscreen
307 STMPE1601: GPIO, Keypad
308 STMPE2401: GPIO, Keypad
309 STMPE2403: GPIO, Keypad
311 This driver provides common support for accessing the device,
312 additional drivers must be enabled in order to use the functionality
313 of the device. Currently available sub drivers are:
317 Touchscreen: stmpe-ts
319 menu "STMPE Interface Drivers"
323 bool "STMPE I2C Inteface"
327 This is used to enable I2C interface of STMPE
330 bool "STMPE SPI Inteface"
331 depends on SPI_MASTER
333 This is used to enable SPI interface of STMPE
337 bool "Support Toshiba TC35892 and variants"
338 depends on I2C=y && GENERIC_HARDIRQS
341 Support for the Toshiba TC35892 and variants I/O Expander.
343 This driver provides common support for accessing the device,
344 additional drivers must be enabled in order to use the
345 functionality of the device.
352 bool "Support Toshiba T7L66XB"
353 depends on ARM && HAVE_CLK
357 Support for Toshiba Mobile IO Controller T7L66XB
360 bool "Support Toshiba TC6387XB"
361 depends on ARM && HAVE_CLK
365 Support for Toshiba Mobile IO Controller TC6387XB
368 bool "Support Toshiba TC6393XB"
369 depends on GPIOLIB && ARM && HAVE_CLK
373 Support for Toshiba Mobile IO Controller TC6393XB
376 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
379 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
380 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
381 usually found on PXA processors-based platforms. This includes
382 the I2C driver and the core APIs _only_, you have to select
383 individual components like LCD backlight, voltage regulators,
384 LEDs and battery-charger under the corresponding menus.
390 config MFD_DA9052_SPI
391 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
395 depends on SPI_MASTER=y
397 Support for the Dialog Semiconductor DA9052 PMIC
398 when controlled using SPI. This driver provides common support
399 for accessing the device, additional drivers must be enabled in
400 order to use the functionality of the device.
402 config MFD_DA9052_I2C
403 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
409 Support for the Dialog Semiconductor DA9052 PMIC
410 when controlled using I2C. This driver provides common support
411 for accessing the device, additional drivers must be enabled in
412 order to use the functionality of the device.
415 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
418 Say yes here to add support for Analog Devices AD5520 and ADP5501,
419 Multifunction Power Management IC. This includes
420 the I2C driver and the core APIs _only_, you have to select
421 individual components like LCD backlight, LEDs, GPIOs and Kepad
422 under the corresponding menus.
425 bool "Maxim Semiconductor MAX77693 PMIC Support"
426 depends on I2C=y && GENERIC_HARDIRQS
430 Say yes here to support for Maxim Semiconductor MAX77693.
431 This is a companion Power Management IC with Flash, Haptic, Charger,
432 and MUIC(Micro USB Interface Controller) controls on chip.
433 This driver provides common support for accessing the device;
434 additional drivers must be enabled in order to use the functionality
438 bool "Maxim Semiconductor MAX8925 PMIC Support"
439 depends on I2C=y && GENERIC_HARDIRQS
442 Say yes here to support for Maxim Semiconductor MAX8925. This is
443 a Power Management IC. This driver provies common support for
444 accessing the device, additional drivers must be enabled in order
445 to use the functionality of the device.
448 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
449 depends on I2C=y && GENERIC_HARDIRQS
452 Say yes here to support for Maxim Semiconductor MAX8997/8966.
453 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
454 MUIC controls on chip.
455 This driver provides common support for accessing the device;
456 additional drivers must be enabled in order to use the functionality
460 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
461 depends on I2C=y && GENERIC_HARDIRQS
464 Say yes here to support for Maxim Semiconductor MAX8998 and
465 National Semiconductor LP3974. This is a Power Management IC.
466 This driver provies common support for accessing the device,
467 additional drivers must be enabled in order to use the functionality
471 bool "SAMSUNG S5M Series Support"
472 depends on I2C=y && GENERIC_HARDIRQS
476 Support for the Samsung Electronics S5M MFD series.
477 This driver provies common support for accessing the device,
478 additional drivers must be enabled in order to use the functionality
482 bool "Support Wolfson Microelectronics WM8400"
487 Support for the Wolfson Microelecronics WM8400 PMIC and audio
488 CODEC. This driver provides common support for accessing
489 the device, additional drivers must be enabled in order to use
490 the functionality of the device.
494 depends on GENERIC_HARDIRQS
496 config MFD_WM831X_I2C
497 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
502 depends on I2C=y && GENERIC_HARDIRQS
504 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
505 when controlled using I2C. This driver provides common support
506 for accessing the device, additional drivers must be enabled in
507 order to use the functionality of the device.
509 config MFD_WM831X_SPI
510 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
515 depends on SPI_MASTER && GENERIC_HARDIRQS
517 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
518 when controlled using SPI. This driver provides common support
519 for accessing the device, additional drivers must be enabled in
520 order to use the functionality of the device.
524 depends on GENERIC_HARDIRQS
526 config MFD_WM8350_CONFIG_MODE_0
528 depends on MFD_WM8350
530 config MFD_WM8350_CONFIG_MODE_1
532 depends on MFD_WM8350
534 config MFD_WM8350_CONFIG_MODE_2
536 depends on MFD_WM8350
538 config MFD_WM8350_CONFIG_MODE_3
540 depends on MFD_WM8350
542 config MFD_WM8351_CONFIG_MODE_0
544 depends on MFD_WM8350
546 config MFD_WM8351_CONFIG_MODE_1
548 depends on MFD_WM8350
550 config MFD_WM8351_CONFIG_MODE_2
552 depends on MFD_WM8350
554 config MFD_WM8351_CONFIG_MODE_3
556 depends on MFD_WM8350
558 config MFD_WM8352_CONFIG_MODE_0
560 depends on MFD_WM8350
562 config MFD_WM8352_CONFIG_MODE_1
564 depends on MFD_WM8350
566 config MFD_WM8352_CONFIG_MODE_2
568 depends on MFD_WM8350
570 config MFD_WM8352_CONFIG_MODE_3
572 depends on MFD_WM8350
574 config MFD_WM8350_I2C
575 bool "Support Wolfson Microelectronics WM8350 with I2C"
577 depends on I2C=y && GENERIC_HARDIRQS
579 The WM8350 is an integrated audio and power management
580 subsystem with watchdog and RTC functionality for embedded
581 systems. This option enables core support for the WM8350 with
582 I2C as the control interface. Additional options must be
583 selected to enable support for the functionality of the chip.
586 bool "Support Wolfson Microelectronics WM8994"
590 depends on I2C=y && GENERIC_HARDIRQS
592 The WM8994 is a highly integrated hi-fi CODEC designed for
593 smartphone applicatiosn. As well as audio functionality it
594 has on board GPIO and regulator functionality which is
595 supported via the relevant subsystems. This driver provides
596 core support for the WM8994, in order to use the actual
597 functionaltiy of the device other drivers must be enabled.
600 tristate "Support for NXP PCF50633"
604 Say yes here if you have NXP PCF50633 chip on your board.
605 This core driver provides register access and IRQ handling
606 facilities, and registers devices for the various functions
607 so that function-specific drivers can bind to them.
610 tristate "Support for NXP PCF50633 ADC"
611 depends on MFD_PCF50633
613 Say yes here if you want to include support for ADC in the
617 tristate "Support for NXP PCF50633 GPIO"
618 depends on MFD_PCF50633
620 Say yes here if you want to include support GPIO for pins on
628 depends on SPI_MASTER || I2C
632 Enable support for the Freescale MC13783 and MC13892 PMICs.
633 This driver provides common support for accessing the device,
634 additional drivers must be enabled in order to use the
635 functionality of the device.
637 config MFD_MC13XXX_SPI
638 tristate "Freescale MC13783 and MC13892 SPI interface"
639 depends on SPI_MASTER
643 Select this if your MC13xxx is connected via an SPI bus.
645 config MFD_MC13XXX_I2C
646 tristate "Freescale MC13892 I2C interface"
651 Select this if your MC13xxx is connected via an I2C bus.
654 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
655 default y if ARCH_U300 || ARCH_U8500
657 Say yes here if you have the ABX500 Mixed Signal IC family
658 chips. This core driver expose register access functions.
659 Functionality specific drivers using these functions can
660 remain unchanged when IC changes. Binding of the functions to
661 actual register access is done by the IC core driver.
664 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
665 depends on I2C=y && ABX500_CORE
667 default y if ARCH_U300
669 Select this to enable the AB3100 Mixed Signal IC core
670 functionality. This connects to a AB3100 on the I2C bus
671 and expose a number of symbols needed for dependent devices
672 to read and write registers and subscribe to events from
673 this multi-functional IC. This is needed to use other features
674 of the AB3100 such as battery-backed RTC, charging control,
675 LEDs, vibrator, system power and temperature, power management
679 tristate "ST-Ericsson AB3100 OTP functions"
680 depends on AB3100_CORE
681 default y if AB3100_CORE
683 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
684 programmable memory) support. This exposes a sysfs file to read
689 depends on GENERIC_HARDIRQS && SPI_MASTER
691 This enables the PCAP ASIC present on EZX Phones. This is
692 needed for MMC, TouchScreen, Sound, USB, etc..
695 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
696 depends on ABX500_CORE && MFD_DB5500_PRCMU
699 Select this option to enable access to AB5500 power management
700 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
701 This chip embeds various other multimedia funtionalities as well.
704 bool "Enable debug info via debugfs"
705 depends on AB5500_CORE && DEBUG_FS
706 default y if DEBUG_FS
708 Select this option if you want debug information from the AB5500
709 using the debug filesystem, debugfs.
712 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
713 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
716 Select this option to enable access to AB8500 power management
717 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
718 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
719 the irq_chip parts for handling the Mixed Signal chip events.
720 This chip embeds various other multimedia funtionalities as well.
722 config AB8500_I2C_CORE
723 bool "AB8500 register access via PRCMU I2C"
724 depends on AB8500_CORE && MFD_DB8500_PRCMU
727 This enables register access to the AB8500 chip via PRCMU I2C.
728 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
729 the I2C bus is connected to the Power Reset
730 and Mangagement Unit, PRCMU.
733 bool "Enable debug info via debugfs"
734 depends on AB8500_CORE && DEBUG_FS
735 default y if DEBUG_FS
737 Select this option if you want debug information using the debug
741 bool "AB8500 GPADC driver"
742 depends on AB8500_CORE && REGULATOR_AB8500
745 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
747 config MFD_DB8500_PRCMU
748 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
749 depends on UX500_SOC_DB8500
752 Select this option to enable support for the DB8500 Power Reset
753 and Control Management Unit. This is basically an autonomous
754 system controller running an XP70 microprocessor, which is accessed
755 through a register map.
757 config MFD_DB5500_PRCMU
758 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
759 depends on UX500_SOC_DB5500
762 Select this option to enable support for the DB5500 Power Reset
763 and Control Management Unit. This is basically an autonomous
764 system controller running an XP70 microprocessor, which is accessed
765 through a register map.
768 tristate "Support for CS5535 and CS5536 southbridge core functions"
770 depends on PCI && X86
772 This is the core driver for CS5535/CS5536 MFD functions. This is
773 necessary for using the board's GPIO and MFGPT functionality.
775 config MFD_TIMBERDALE
776 tristate "Support for the Timberdale FPGA"
778 depends on PCI && GPIOLIB
780 This is the core driver for the timberdale FPGA. This device is a
781 multifunction device which exposes numerous platform devices.
783 The timberdale FPGA can be found on the Intel Atom development board
784 for in-vehicle infontainment, called Russellville.
787 tristate "Intel SCH LPC"
791 LPC bridge function of the Intel SCH provides support for
792 System Management Bus and General Purpose I/O.
795 tristate "Intel ICH LPC"
799 The LPC bridge function of the Intel ICH provides support for
800 many functional units. This driver provides needed support for
801 other drivers to control these functions, currently GPIO and
805 tristate "Support for RDC-R321x southbridge"
809 Say yes here if you want to have support for the RDC R-321x SoC
810 southbridge which provides access to GPIOs and Watchdog using the
811 southbridge PCI device configuration space.
813 config MFD_JANZ_CMODIO
814 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
818 This is the core driver for the Janz CMOD-IO PCI MODULbus
819 carrier board. This device is a PCI to MODULbus bridge which may
820 host many different types of MODULbus daughterboards, including
821 CAN and GPIO controllers.
823 config MFD_JZ4740_ADC
824 bool "Support for the JZ4740 SoC ADC core"
826 select GENERIC_IRQ_CHIP
827 depends on MACH_JZ4740
829 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
830 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
833 tristate "Support for VIA VX855/VX875 integrated south bridge"
837 Say yes here to enable support for various functions of the
838 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
839 and/or vx855_gpio drivers for this to do anything useful.
841 config MFD_WL1273_CORE
842 tristate "Support for TI WL1273 FM radio."
847 This is the core driver for the TI WL1273 FM radio. This MFD
848 driver connects the radio-wl1273 V4L2 module and the wl1273
851 config MFD_OMAP_USB_HOST
852 bool "Support OMAP USBHS core driver"
853 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
856 This is the core driver for the OAMP EHCI and OHCI drivers.
857 This MFD driver does the required setup functionalities for
858 OMAP USB Host drivers.
863 config MFD_PM8921_CORE
864 tristate "Qualcomm PM8921 PMIC chip"
869 If you say yes to this option, support will be included for the
870 built-in PM8921 PMIC chip.
872 This is required if your board has a PM8921 and uses its features,
873 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
875 Say M here if you want to include support for PM8921 chip as a module.
876 This will build a module called "pm8921-core".
878 config MFD_PM8XXX_IRQ
879 bool "Support for Qualcomm PM8xxx IRQ features"
880 depends on MFD_PM8XXX
881 default y if MFD_PM8XXX
883 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
885 This is required to use certain other PM 8xxx features, such as GPIO
888 config TPS65911_COMPARATOR
892 bool "TPS65090 Power Management chips"
893 depends on I2C=y && GENERIC_HARDIRQS
897 If you say yes here you get support for the TPS65090 series of
898 Power Management chips.
899 This driver provides common support for accessing the device,
900 additional drivers must be enabled in order to use the
901 functionality of the device.
903 config MFD_AAT2870_CORE
904 bool "Support for the AnalogicTech AAT2870"
906 depends on I2C=y && GPIOLIB
908 If you say yes here you get support for the AAT2870.
909 This driver provides common support for accessing the device,
910 additional drivers must be enabled in order to use the
911 functionality of the device.
913 config MFD_INTEL_MSIC
914 bool "Support for Intel MSIC"
915 depends on INTEL_SCU_IPC
918 Select this option to enable access to Intel MSIC (Avatele
919 Passage) chip. This chip embeds audio, battery, GPIO, etc.
920 devices used in Intel Medfield platforms.
923 bool "Ricoh RC5T583 Power Management system device"
924 depends on I2C=y && GENERIC_HARDIRQS
928 Select this option to get support for the RICOH583 Power
929 Management system device.
930 This driver provides common support for accessing the device
931 through i2c interface. The device supports multiple sub-devices
932 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
933 Additional drivers must be enabled in order to use the
934 different functionality of the device.
937 bool "STA2X11 multi function device support"
942 bool "Support for Freescale i.MX on-chip ANATOP controller"
945 Select this option to enable Freescale i.MX on-chip ANATOP
946 MFD controller. This controller embeds regulator and
947 thermal devices for Freescale i.MX platforms.
952 menu "Multimedia Capabilities Port drivers"
953 depends on ARCH_SA1100
960 tristate "Support SA11x0 MCP interface"
961 depends on ARCH_SA1100
966 bool "Support for UCB1200 / UCB1300"
967 depends on MCP_SA11X0
970 config MCP_UCB1200_TS
971 tristate "Touchscreen interface support"
972 depends on MCP_UCB1200 && INPUT