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 && GENERIC_HARDIRQS
206 If you say yes here you get support for the TPS6586X series of
207 Power Management chips.
208 This driver provides common support for accessing the device,
209 additional drivers must be enabled in order to use the
210 functionality of the device.
212 This driver can also be built as a module. If so, the module
213 will be called tps6586x.
216 bool "TPS65910 Power Management chip"
217 depends on I2C=y && GPIOLIB
222 if you say yes here you get support for the TPS65910 series of
223 Power Management chips.
229 config MFD_TPS65912_I2C
230 bool "TPS65912 Power Management chip with I2C"
233 depends on I2C=y && GPIOLIB
235 If you say yes here you get support for the TPS65912 series of
236 PM chips with I2C interface.
238 config MFD_TPS65912_SPI
239 bool "TPS65912 Power Management chip with SPI"
242 depends on SPI_MASTER && GPIOLIB
244 If you say yes here you get support for the TPS65912 series of
245 PM chips with SPI interface.
248 bool "Texas Instruments TWL92330/Menelaus PM chip"
249 depends on I2C=y && ARCH_OMAP2
251 If you say yes here you get support for the Texas Instruments
252 TWL92330/Menelaus Power Management chip. This include voltage
253 regulators, Dual slot memory card transceivers, real-time clock
254 and other features that are often used in portable devices like
255 cell phones and PDAs.
258 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
259 depends on I2C=y && GENERIC_HARDIRQS
262 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
263 This core driver provides register access and IRQ handling
264 facilities, and registers devices for the various functions
265 so that function-specific drivers can bind to them.
267 These multi-function chips are found on many OMAP2 and OMAP3
268 boards, providing power management, RTC, GPIO, keypad, a
269 high speed USB OTG transceiver, an audio codec (on most
270 versions) and many other features.
273 tristate "Texas Instruments TWL4030 MADC"
274 depends on TWL4030_CORE
276 This driver provides support for triton TWL4030-MADC. The
277 driver supports both RT and SW conversion methods.
279 This driver can be built as a module. If so it will be
283 bool "Support power resources on TWL4030 family chips"
284 depends on TWL4030_CORE && ARM
286 Say yes here if you want to use the power resources on the
287 TWL4030 family chips. Most of these resources are regulators,
288 which have a separate driver; some are control signals, such
289 as clock request handshaking.
291 This driver uses board-specific data to initialize the resources
292 and load scripts controlling which resources are switched off/on
293 or reset when a sleep, wakeup or warm reset event occurs.
295 config MFD_TWL4030_AUDIO
297 depends on TWL4030_CORE
302 bool "Support for TWL6040 audio codec"
303 depends on I2C=y && GENERIC_HARDIRQS
309 Say yes here if you want support for Texas Instruments TWL6040 audio
311 This driver provides common support for accessing the device,
312 additional drivers must be enabled in order to use the
313 functionality of the device (audio, vibra).
316 bool "Support STMicroelectronics STMPE"
317 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
320 Support for the STMPE family of I/O Expanders from
323 Currently supported devices are:
325 STMPE811: GPIO, Touchscreen
326 STMPE1601: GPIO, Keypad
327 STMPE2401: GPIO, Keypad
328 STMPE2403: GPIO, Keypad
330 This driver provides common support for accessing the device,
331 additional drivers must be enabled in order to use the functionality
332 of the device. Currently available sub drivers are:
336 Touchscreen: stmpe-ts
338 menu "STMPE Interface Drivers"
342 bool "STMPE I2C Inteface"
346 This is used to enable I2C interface of STMPE
349 bool "STMPE SPI Inteface"
350 depends on SPI_MASTER
352 This is used to enable SPI interface of STMPE
356 bool "Support Toshiba TC35892 and variants"
357 depends on I2C=y && GENERIC_HARDIRQS
360 Support for the Toshiba TC35892 and variants I/O Expander.
362 This driver provides common support for accessing the device,
363 additional drivers must be enabled in order to use the
364 functionality of the device.
371 bool "Support Toshiba T7L66XB"
372 depends on ARM && HAVE_CLK
376 Support for Toshiba Mobile IO Controller T7L66XB
379 bool "Support Toshiba TC6387XB"
380 depends on ARM && HAVE_CLK
384 Support for Toshiba Mobile IO Controller TC6387XB
387 bool "Support Toshiba TC6393XB"
388 depends on GPIOLIB && ARM && HAVE_CLK
392 Support for Toshiba Mobile IO Controller TC6393XB
395 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
398 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
399 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
400 usually found on PXA processors-based platforms. This includes
401 the I2C driver and the core APIs _only_, you have to select
402 individual components like LCD backlight, voltage regulators,
403 LEDs and battery-charger under the corresponding menus.
409 config MFD_DA9052_SPI
410 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
414 depends on SPI_MASTER=y
416 Support for the Dialog Semiconductor DA9052 PMIC
417 when controlled using SPI. This driver provides common support
418 for accessing the device, additional drivers must be enabled in
419 order to use the functionality of the device.
421 config MFD_DA9052_I2C
422 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
428 Support for the Dialog Semiconductor DA9052 PMIC
429 when controlled using I2C. This driver provides common support
430 for accessing the device, additional drivers must be enabled in
431 order to use the functionality of the device.
434 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
437 Say yes here to add support for Analog Devices AD5520 and ADP5501,
438 Multifunction Power Management IC. This includes
439 the I2C driver and the core APIs _only_, you have to select
440 individual components like LCD backlight, LEDs, GPIOs and Kepad
441 under the corresponding menus.
444 bool "Maxim Semiconductor MAX77686 PMIC Support"
445 depends on I2C=y && GENERIC_HARDIRQS
450 Say yes here to support for Maxim Semiconductor MAX77686.
451 This is a Power Management IC with RTC on chip.
452 This driver provides common support for accessing the device;
453 additional drivers must be enabled in order to use the functionality
457 bool "Maxim Semiconductor MAX77693 PMIC Support"
458 depends on I2C=y && GENERIC_HARDIRQS
462 Say yes here to support for Maxim Semiconductor MAX77693.
463 This is a companion Power Management IC with Flash, Haptic, Charger,
464 and MUIC(Micro USB Interface Controller) controls on chip.
465 This driver provides common support for accessing the device;
466 additional drivers must be enabled in order to use the functionality
470 tristate "Maxim Semiconductor MAX8907 PMIC Support"
472 depends on I2C=y && GENERIC_HARDIRQS
476 Say yes here to support for Maxim Semiconductor MAX8907. This is
477 a Power Management IC. This driver provides common support for
478 accessing the device; additional drivers must be enabled in order
479 to use the functionality of the device.
482 bool "Maxim Semiconductor MAX8925 PMIC Support"
483 depends on I2C=y && GENERIC_HARDIRQS
486 Say yes here to support for Maxim Semiconductor MAX8925. This is
487 a Power Management IC. This driver provides common support for
488 accessing the device, additional drivers must be enabled in order
489 to use the functionality of the device.
492 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
493 depends on I2C=y && GENERIC_HARDIRQS
497 Say yes here to support for Maxim Semiconductor MAX8997/8966.
498 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
499 MUIC controls on chip.
500 This driver provides common support for accessing the device;
501 additional drivers must be enabled in order to use the functionality
505 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
506 depends on I2C=y && GENERIC_HARDIRQS
509 Say yes here to support for Maxim Semiconductor MAX8998 and
510 National Semiconductor LP3974. This is a Power Management IC.
511 This driver provides common support for accessing the device,
512 additional drivers must be enabled in order to use the functionality
516 bool "SAMSUNG Electronics PMIC Series Support"
517 depends on I2C=y && GENERIC_HARDIRQS
522 Support for the Samsung Electronics MFD series.
523 This driver provides common support for accessing the device,
524 additional drivers must be enabled in order to use the functionality
533 config MFD_ARIZONA_I2C
534 tristate "Support Wolfson Microelectronics Arizona platform with I2C"
540 Support for the Wolfson Microelectronics Arizona platform audio SoC
541 core functionality controlled via I2C.
543 config MFD_ARIZONA_SPI
544 tristate "Support Wolfson Microelectronics Arizona platform with SPI"
548 depends on SPI_MASTER
550 Support for the Wolfson Microelectronics Arizona platform audio SoC
551 core functionality controlled via I2C.
554 bool "Support Wolfson Microelectronics WM5102"
555 depends on MFD_ARIZONA
557 Support for Wolfson Microelectronics WM5102 low power audio SoC
560 bool "Support Wolfson Microelectronics WM5110"
561 depends on MFD_ARIZONA
563 Support for Wolfson Microelectronics WM5110 low power audio SoC
566 bool "Support Wolfson Microelectronics WM8400"
571 Support for the Wolfson Microelecronics WM8400 PMIC and audio
572 CODEC. This driver provides common support for accessing
573 the device, additional drivers must be enabled in order to use
574 the functionality of the device.
578 depends on GENERIC_HARDIRQS
580 config MFD_WM831X_I2C
581 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
586 depends on I2C=y && GENERIC_HARDIRQS
588 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
589 when controlled using I2C. 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.
593 config MFD_WM831X_SPI
594 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
599 depends on SPI_MASTER && GENERIC_HARDIRQS
601 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
602 when controlled using SPI. This driver provides common support
603 for accessing the device, additional drivers must be enabled in
604 order to use the functionality of the device.
608 depends on GENERIC_HARDIRQS
610 config MFD_WM8350_CONFIG_MODE_0
612 depends on MFD_WM8350
614 config MFD_WM8350_CONFIG_MODE_1
616 depends on MFD_WM8350
618 config MFD_WM8350_CONFIG_MODE_2
620 depends on MFD_WM8350
622 config MFD_WM8350_CONFIG_MODE_3
624 depends on MFD_WM8350
626 config MFD_WM8351_CONFIG_MODE_0
628 depends on MFD_WM8350
630 config MFD_WM8351_CONFIG_MODE_1
632 depends on MFD_WM8350
634 config MFD_WM8351_CONFIG_MODE_2
636 depends on MFD_WM8350
638 config MFD_WM8351_CONFIG_MODE_3
640 depends on MFD_WM8350
642 config MFD_WM8352_CONFIG_MODE_0
644 depends on MFD_WM8350
646 config MFD_WM8352_CONFIG_MODE_1
648 depends on MFD_WM8350
650 config MFD_WM8352_CONFIG_MODE_2
652 depends on MFD_WM8350
654 config MFD_WM8352_CONFIG_MODE_3
656 depends on MFD_WM8350
658 config MFD_WM8350_I2C
659 bool "Support Wolfson Microelectronics WM8350 with I2C"
661 depends on I2C=y && GENERIC_HARDIRQS
663 The WM8350 is an integrated audio and power management
664 subsystem with watchdog and RTC functionality for embedded
665 systems. This option enables core support for the WM8350 with
666 I2C as the control interface. Additional options must be
667 selected to enable support for the functionality of the chip.
670 bool "Support Wolfson Microelectronics WM8994"
674 depends on I2C=y && GENERIC_HARDIRQS
676 The WM8994 is a highly integrated hi-fi CODEC designed for
677 smartphone applicatiosn. As well as audio functionality it
678 has on board GPIO and regulator functionality which is
679 supported via the relevant subsystems. This driver provides
680 core support for the WM8994, in order to use the actual
681 functionaltiy of the device other drivers must be enabled.
684 tristate "Support for NXP PCF50633"
688 Say yes here if you have NXP PCF50633 chip on your board.
689 This core driver provides register access and IRQ handling
690 facilities, and registers devices for the various functions
691 so that function-specific drivers can bind to them.
694 tristate "Support for NXP PCF50633 ADC"
695 depends on MFD_PCF50633
697 Say yes here if you want to include support for ADC in the
701 tristate "Support for NXP PCF50633 GPIO"
702 depends on MFD_PCF50633
704 Say yes here if you want to include support GPIO for pins on
712 depends on SPI_MASTER || I2C
716 Enable support for the Freescale MC13783 and MC13892 PMICs.
717 This driver provides common support for accessing the device,
718 additional drivers must be enabled in order to use the
719 functionality of the device.
721 config MFD_MC13XXX_SPI
722 tristate "Freescale MC13783 and MC13892 SPI interface"
723 depends on SPI_MASTER
727 Select this if your MC13xxx is connected via an SPI bus.
729 config MFD_MC13XXX_I2C
730 tristate "Freescale MC13892 I2C interface"
735 Select this if your MC13xxx is connected via an I2C bus.
738 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
739 default y if ARCH_U300 || ARCH_U8500
741 Say yes here if you have the ABX500 Mixed Signal IC family
742 chips. This core driver expose register access functions.
743 Functionality specific drivers using these functions can
744 remain unchanged when IC changes. Binding of the functions to
745 actual register access is done by the IC core driver.
748 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
749 depends on I2C=y && ABX500_CORE
751 default y if ARCH_U300
753 Select this to enable the AB3100 Mixed Signal IC core
754 functionality. This connects to a AB3100 on the I2C bus
755 and expose a number of symbols needed for dependent devices
756 to read and write registers and subscribe to events from
757 this multi-functional IC. This is needed to use other features
758 of the AB3100 such as battery-backed RTC, charging control,
759 LEDs, vibrator, system power and temperature, power management
763 tristate "ST-Ericsson AB3100 OTP functions"
764 depends on AB3100_CORE
765 default y if AB3100_CORE
767 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
768 programmable memory) support. This exposes a sysfs file to read
773 depends on GENERIC_HARDIRQS && SPI_MASTER
775 This enables the PCAP ASIC present on EZX Phones. This is
776 needed for MMC, TouchScreen, Sound, USB, etc..
779 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
780 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
784 Select this option to enable access to AB8500 power management
785 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
786 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
787 the irq_chip parts for handling the Mixed Signal chip events.
788 This chip embeds various other multimedia funtionalities as well.
791 bool "Enable debug info via debugfs"
792 depends on AB8500_CORE && DEBUG_FS
793 default y if DEBUG_FS
795 Select this option if you want debug information using the debug
799 bool "AB8500 GPADC driver"
800 depends on AB8500_CORE && REGULATOR_AB8500
803 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
805 config MFD_DB8500_PRCMU
806 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
807 depends on UX500_SOC_DB8500
810 Select this option to enable support for the DB8500 Power Reset
811 and Control Management Unit. This is basically an autonomous
812 system controller running an XP70 microprocessor, which is accessed
813 through a register map.
816 tristate "Support for CS5535 and CS5536 southbridge core functions"
818 depends on PCI && X86
820 This is the core driver for CS5535/CS5536 MFD functions. This is
821 necessary for using the board's GPIO and MFGPT functionality.
823 config MFD_TIMBERDALE
824 tristate "Support for the Timberdale FPGA"
826 depends on PCI && GPIOLIB
828 This is the core driver for the timberdale FPGA. This device is a
829 multifunction device which exposes numerous platform devices.
831 The timberdale FPGA can be found on the Intel Atom development board
832 for in-vehicle infontainment, called Russellville.
835 tristate "Intel SCH LPC"
839 LPC bridge function of the Intel SCH provides support for
840 System Management Bus and General Purpose I/O.
843 tristate "Intel ICH LPC"
847 The LPC bridge function of the Intel ICH provides support for
848 many functional units. This driver provides needed support for
849 other drivers to control these functions, currently GPIO and
853 tristate "Support for RDC-R321x southbridge"
857 Say yes here if you want to have support for the RDC R-321x SoC
858 southbridge which provides access to GPIOs and Watchdog using the
859 southbridge PCI device configuration space.
861 config MFD_JANZ_CMODIO
862 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
866 This is the core driver for the Janz CMOD-IO PCI MODULbus
867 carrier board. This device is a PCI to MODULbus bridge which may
868 host many different types of MODULbus daughterboards, including
869 CAN and GPIO controllers.
871 config MFD_JZ4740_ADC
872 bool "Support for the JZ4740 SoC ADC core"
874 select GENERIC_IRQ_CHIP
875 depends on MACH_JZ4740
877 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
878 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
881 tristate "Support for VIA VX855/VX875 integrated south bridge"
885 Say yes here to enable support for various functions of the
886 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
887 and/or vx855_gpio drivers for this to do anything useful.
889 config MFD_WL1273_CORE
890 tristate "Support for TI WL1273 FM radio."
895 This is the core driver for the TI WL1273 FM radio. This MFD
896 driver connects the radio-wl1273 V4L2 module and the wl1273
899 config MFD_OMAP_USB_HOST
900 bool "Support OMAP USBHS core and TLL driver"
901 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
904 This is the core driver for the OAMP EHCI and OHCI drivers.
905 This MFD driver does the required setup functionalities for
906 OMAP USB Host drivers.
911 config MFD_PM8921_CORE
912 tristate "Qualcomm PM8921 PMIC chip"
917 If you say yes to this option, support will be included for the
918 built-in PM8921 PMIC chip.
920 This is required if your board has a PM8921 and uses its features,
921 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
923 Say M here if you want to include support for PM8921 chip as a module.
924 This will build a module called "pm8921-core".
926 config MFD_PM8XXX_IRQ
927 bool "Support for Qualcomm PM8xxx IRQ features"
928 depends on MFD_PM8XXX
929 default y if MFD_PM8XXX
931 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
933 This is required to use certain other PM 8xxx features, such as GPIO
936 config TPS65911_COMPARATOR
940 bool "TPS65090 Power Management chips"
941 depends on I2C=y && GENERIC_HARDIRQS
945 If you say yes here you get support for the TPS65090 series of
946 Power Management chips.
947 This driver provides common support for accessing the device,
948 additional drivers must be enabled in order to use the
949 functionality of the device.
951 config MFD_AAT2870_CORE
952 bool "Support for the AnalogicTech AAT2870"
954 depends on I2C=y && GPIOLIB
956 If you say yes here you get support for the AAT2870.
957 This driver provides common support for accessing the device,
958 additional drivers must be enabled in order to use the
959 functionality of the device.
961 config MFD_INTEL_MSIC
962 bool "Support for Intel MSIC"
963 depends on INTEL_SCU_IPC
966 Select this option to enable access to Intel MSIC (Avatele
967 Passage) chip. This chip embeds audio, battery, GPIO, etc.
968 devices used in Intel Medfield platforms.
971 bool "Ricoh RC5T583 Power Management system device"
972 depends on I2C=y && GENERIC_HARDIRQS
976 Select this option to get support for the RICOH583 Power
977 Management system device.
978 This driver provides common support for accessing the device
979 through i2c interface. The device supports multiple sub-devices
980 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
981 Additional drivers must be enabled in order to use the
982 different functionality of the device.
985 bool "STA2X11 multi function device support"
990 bool "System Controller Register R/W Based on Regmap"
994 Select this option to enable accessing system control registers
998 bool "Support for the TI Palmas series chips"
1004 If you say yes here you get support for the Palmas
1005 series of PMIC chips from Texas Instruments.
1010 menu "Multimedia Capabilities Port drivers"
1011 depends on ARCH_SA1100
1018 tristate "Support SA11x0 MCP interface"
1019 depends on ARCH_SA1100
1024 bool "Support for UCB1200 / UCB1300"
1025 depends on MCP_SA11X0
1028 config MCP_UCB1200_TS
1029 tristate "Touchscreen interface support"
1030 depends on MCP_UCB1200 && INPUT