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
429 Say yes here to support for Maxim Semiconductor MAX77693.
430 This is a companion Power Management IC with Flash, Haptic, Charger,
431 and MUIC(Micro USB Interface Controller) controls on chip.
432 This driver provides common support for accessing the device;
433 additional drivers must be enabled in order to use the functionality
437 bool "Maxim Semiconductor MAX8925 PMIC Support"
438 depends on I2C=y && GENERIC_HARDIRQS
441 Say yes here to support for Maxim Semiconductor MAX8925. This is
442 a Power Management IC. This driver provies common support for
443 accessing the device, additional drivers must be enabled in order
444 to use the functionality of the device.
447 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
448 depends on I2C=y && GENERIC_HARDIRQS
451 Say yes here to support for Maxim Semiconductor MAX8997/8966.
452 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
453 MUIC controls on chip.
454 This driver provides common support for accessing the device;
455 additional drivers must be enabled in order to use the functionality
459 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
460 depends on I2C=y && GENERIC_HARDIRQS
463 Say yes here to support for Maxim Semiconductor MAX8998 and
464 National Semiconductor LP3974. This is a Power Management IC.
465 This driver provies common support for accessing the device,
466 additional drivers must be enabled in order to use the functionality
470 bool "SAMSUNG S5M Series Support"
471 depends on I2C=y && GENERIC_HARDIRQS
475 Support for the Samsung Electronics S5M MFD series.
476 This driver provies common support for accessing the device,
477 additional drivers must be enabled in order to use the functionality
481 bool "Support Wolfson Microelectronics WM8400"
486 Support for the Wolfson Microelecronics WM8400 PMIC and audio
487 CODEC. This driver provides common support for accessing
488 the device, additional drivers must be enabled in order to use
489 the functionality of the device.
493 depends on GENERIC_HARDIRQS
495 config MFD_WM831X_I2C
496 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
501 depends on I2C=y && GENERIC_HARDIRQS
503 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
504 when controlled using I2C. This driver provides common support
505 for accessing the device, additional drivers must be enabled in
506 order to use the functionality of the device.
508 config MFD_WM831X_SPI
509 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
514 depends on SPI_MASTER && GENERIC_HARDIRQS
516 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
517 when controlled using SPI. This driver provides common support
518 for accessing the device, additional drivers must be enabled in
519 order to use the functionality of the device.
523 depends on GENERIC_HARDIRQS
525 config MFD_WM8350_CONFIG_MODE_0
527 depends on MFD_WM8350
529 config MFD_WM8350_CONFIG_MODE_1
531 depends on MFD_WM8350
533 config MFD_WM8350_CONFIG_MODE_2
535 depends on MFD_WM8350
537 config MFD_WM8350_CONFIG_MODE_3
539 depends on MFD_WM8350
541 config MFD_WM8351_CONFIG_MODE_0
543 depends on MFD_WM8350
545 config MFD_WM8351_CONFIG_MODE_1
547 depends on MFD_WM8350
549 config MFD_WM8351_CONFIG_MODE_2
551 depends on MFD_WM8350
553 config MFD_WM8351_CONFIG_MODE_3
555 depends on MFD_WM8350
557 config MFD_WM8352_CONFIG_MODE_0
559 depends on MFD_WM8350
561 config MFD_WM8352_CONFIG_MODE_1
563 depends on MFD_WM8350
565 config MFD_WM8352_CONFIG_MODE_2
567 depends on MFD_WM8350
569 config MFD_WM8352_CONFIG_MODE_3
571 depends on MFD_WM8350
573 config MFD_WM8350_I2C
574 bool "Support Wolfson Microelectronics WM8350 with I2C"
576 depends on I2C=y && GENERIC_HARDIRQS
578 The WM8350 is an integrated audio and power management
579 subsystem with watchdog and RTC functionality for embedded
580 systems. This option enables core support for the WM8350 with
581 I2C as the control interface. Additional options must be
582 selected to enable support for the functionality of the chip.
585 bool "Support Wolfson Microelectronics WM8994"
589 depends on I2C=y && GENERIC_HARDIRQS
591 The WM8994 is a highly integrated hi-fi CODEC designed for
592 smartphone applicatiosn. As well as audio functionality it
593 has on board GPIO and regulator functionality which is
594 supported via the relevant subsystems. This driver provides
595 core support for the WM8994, in order to use the actual
596 functionaltiy of the device other drivers must be enabled.
599 tristate "Support for NXP PCF50633"
603 Say yes here if you have NXP PCF50633 chip on your board.
604 This core driver provides register access and IRQ handling
605 facilities, and registers devices for the various functions
606 so that function-specific drivers can bind to them.
609 tristate "Support for NXP PCF50633 ADC"
610 depends on MFD_PCF50633
612 Say yes here if you want to include support for ADC in the
616 tristate "Support for NXP PCF50633 GPIO"
617 depends on MFD_PCF50633
619 Say yes here if you want to include support GPIO for pins on
626 tristate "Support Freescale MC13783 and MC13892"
627 depends on SPI_MASTER || I2C
631 Enable support for the Freescale MC13783 and MC13892 PMICs.
632 This driver provides common support for accessing the device,
633 additional drivers must be enabled in order to use the
634 functionality of the device.
638 config MFD_MC13XXX_SPI
639 tristate "MC13xxx SPI interface" if SPI_MASTER
643 Select this if your MC13xxx is connected via an SPI bus.
645 config MFD_MC13XXX_I2C
646 tristate "MC13xxx I2C interface" if I2C
650 Select this if your MC13xxx is connected via an I2C bus.
655 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
656 default y if ARCH_U300 || ARCH_U8500
658 Say yes here if you have the ABX500 Mixed Signal IC family
659 chips. This core driver expose register access functions.
660 Functionality specific drivers using these functions can
661 remain unchanged when IC changes. Binding of the functions to
662 actual register access is done by the IC core driver.
665 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
666 depends on I2C=y && ABX500_CORE
668 default y if ARCH_U300
670 Select this to enable the AB3100 Mixed Signal IC core
671 functionality. This connects to a AB3100 on the I2C bus
672 and expose a number of symbols needed for dependent devices
673 to read and write registers and subscribe to events from
674 this multi-functional IC. This is needed to use other features
675 of the AB3100 such as battery-backed RTC, charging control,
676 LEDs, vibrator, system power and temperature, power management
680 tristate "ST-Ericsson AB3100 OTP functions"
681 depends on AB3100_CORE
682 default y if AB3100_CORE
684 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
685 programmable memory) support. This exposes a sysfs file to read
690 depends on GENERIC_HARDIRQS && SPI_MASTER
692 This enables the PCAP ASIC present on EZX Phones. This is
693 needed for MMC, TouchScreen, Sound, USB, etc..
696 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
697 depends on ABX500_CORE && MFD_DB5500_PRCMU
700 Select this option to enable access to AB5500 power management
701 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
702 This chip embeds various other multimedia funtionalities as well.
705 bool "Enable debug info via debugfs"
706 depends on AB5500_CORE && DEBUG_FS
707 default y if DEBUG_FS
709 Select this option if you want debug information from the AB5500
710 using the debug filesystem, debugfs.
713 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
714 depends on GENERIC_HARDIRQS && ABX500_CORE
717 Select this option to enable access to AB8500 power management
718 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
719 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
720 the irq_chip parts for handling the Mixed Signal chip events.
721 This chip embeds various other multimedia funtionalities as well.
723 config AB8500_I2C_CORE
724 bool "AB8500 register access via PRCMU I2C"
725 depends on AB8500_CORE && MFD_DB8500_PRCMU
728 This enables register access to the AB8500 chip via PRCMU I2C.
729 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
730 the I2C bus is connected to the Power Reset
731 and Mangagement Unit, PRCMU.
734 bool "Enable debug info via debugfs"
735 depends on AB8500_CORE && DEBUG_FS
736 default y if DEBUG_FS
738 Select this option if you want debug information using the debug
742 bool "AB8500 GPADC driver"
743 depends on AB8500_CORE && REGULATOR_AB8500
746 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
748 config MFD_DB8500_PRCMU
749 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
750 depends on UX500_SOC_DB8500
753 Select this option to enable support for the DB8500 Power Reset
754 and Control Management Unit. This is basically an autonomous
755 system controller running an XP70 microprocessor, which is accessed
756 through a register map.
758 config MFD_DB5500_PRCMU
759 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
760 depends on UX500_SOC_DB5500
763 Select this option to enable support for the DB5500 Power Reset
764 and Control Management Unit. This is basically an autonomous
765 system controller running an XP70 microprocessor, which is accessed
766 through a register map.
769 tristate "Support for CS5535 and CS5536 southbridge core functions"
771 depends on PCI && X86
773 This is the core driver for CS5535/CS5536 MFD functions. This is
774 necessary for using the board's GPIO and MFGPT functionality.
776 config MFD_TIMBERDALE
777 tristate "Support for the Timberdale FPGA"
779 depends on PCI && GPIOLIB
781 This is the core driver for the timberdale FPGA. This device is a
782 multifunction device which exposes numerous platform devices.
784 The timberdale FPGA can be found on the Intel Atom development board
785 for in-vehicle infontainment, called Russellville.
788 tristate "Intel SCH LPC"
792 LPC bridge function of the Intel SCH provides support for
793 System Management Bus and General Purpose I/O.
796 tristate "Intel ICH LPC"
800 The LPC bridge function of the Intel ICH provides support for
801 many functional units. This driver provides needed support for
802 other drivers to control these functions, currently GPIO and
806 tristate "Support for RDC-R321x southbridge"
810 Say yes here if you want to have support for the RDC R-321x SoC
811 southbridge which provides access to GPIOs and Watchdog using the
812 southbridge PCI device configuration space.
814 config MFD_JANZ_CMODIO
815 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
819 This is the core driver for the Janz CMOD-IO PCI MODULbus
820 carrier board. This device is a PCI to MODULbus bridge which may
821 host many different types of MODULbus daughterboards, including
822 CAN and GPIO controllers.
824 config MFD_JZ4740_ADC
825 bool "Support for the JZ4740 SoC ADC core"
827 select GENERIC_IRQ_CHIP
828 depends on MACH_JZ4740
830 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
831 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
834 tristate "Support for VIA VX855/VX875 integrated south bridge"
838 Say yes here to enable support for various functions of the
839 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
840 and/or vx855_gpio drivers for this to do anything useful.
842 config MFD_WL1273_CORE
843 tristate "Support for TI WL1273 FM radio."
848 This is the core driver for the TI WL1273 FM radio. This MFD
849 driver connects the radio-wl1273 V4L2 module and the wl1273
852 config MFD_OMAP_USB_HOST
853 bool "Support OMAP USBHS core driver"
854 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
857 This is the core driver for the OAMP EHCI and OHCI drivers.
858 This MFD driver does the required setup functionalities for
859 OMAP USB Host drivers.
864 config MFD_PM8921_CORE
865 tristate "Qualcomm PM8921 PMIC chip"
870 If you say yes to this option, support will be included for the
871 built-in PM8921 PMIC chip.
873 This is required if your board has a PM8921 and uses its features,
874 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
876 Say M here if you want to include support for PM8921 chip as a module.
877 This will build a module called "pm8921-core".
879 config MFD_PM8XXX_IRQ
880 bool "Support for Qualcomm PM8xxx IRQ features"
881 depends on MFD_PM8XXX
882 default y if MFD_PM8XXX
884 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
886 This is required to use certain other PM 8xxx features, such as GPIO
889 config TPS65911_COMPARATOR
893 bool "TPS65090 Power Management chips"
894 depends on I2C=y && GENERIC_HARDIRQS
898 If you say yes here you get support for the TPS65090 series of
899 Power Management chips.
900 This driver provides common support for accessing the device,
901 additional drivers must be enabled in order to use the
902 functionality of the device.
904 config MFD_AAT2870_CORE
905 bool "Support for the AnalogicTech AAT2870"
907 depends on I2C=y && GPIOLIB
909 If you say yes here you get support for the AAT2870.
910 This driver provides common support for accessing the device,
911 additional drivers must be enabled in order to use the
912 functionality of the device.
914 config MFD_INTEL_MSIC
915 bool "Support for Intel MSIC"
916 depends on INTEL_SCU_IPC
919 Select this option to enable access to Intel MSIC (Avatele
920 Passage) chip. This chip embeds audio, battery, GPIO, etc.
921 devices used in Intel Medfield platforms.
924 bool "Ricoh RC5T583 Power Management system device"
925 depends on I2C=y && GENERIC_HARDIRQS
929 Select this option to get support for the RICOH583 Power
930 Management system device.
931 This driver provides common support for accessing the device
932 through i2c interface. The device supports multiple sub-devices
933 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
934 Additional drivers must be enabled in order to use the
935 different functionality of the device.
938 bool "STA2X11 multi function device support"
943 bool "Support for Freescale i.MX on-chip ANATOP controller"
946 Select this option to enable Freescale i.MX on-chip ANATOP
947 MFD controller. This controller embeds regulator and
948 thermal devices for Freescale i.MX platforms.
953 menu "Multimedia Capabilities Port drivers"
954 depends on ARCH_SA1100
961 tristate "Support SA11x0 MCP interface"
962 depends on ARCH_SA1100
967 bool "Support for UCB1200 / UCB1300"
968 depends on MCP_SA11X0
971 config MCP_UCB1200_TS
972 tristate "Touchscreen interface support"
973 depends on MCP_UCB1200 && INPUT