2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
26 depends on I2C=y && GENERIC_HARDIRQS
28 Support for the AS3711 PMIC from AMS
31 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
34 Say yes here to add support for Analog Devices AD5520 and ADP5501,
35 Multifunction Power Management IC. This includes
36 the I2C driver and the core APIs _only_, you have to select
37 individual components like LCD backlight, LEDs, GPIOs and Kepad
38 under the corresponding menus.
40 config MFD_AAT2870_CORE
41 bool "AnalogicTech AAT2870"
43 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
45 If you say yes here you get support for the AAT2870.
46 This driver provides common support for accessing the device,
47 additional drivers must be enabled in order to use the
48 functionality of the device.
51 tristate "ChromeOS Embedded Controller"
54 If you say Y here you get support for the ChromeOS Embedded
55 Controller (EC) providing keyboard, battery and power services.
56 You also need to enable the driver for the bus you are using. The
57 protocol for talking to the EC is defined by the bus driver.
59 config MFD_CROS_EC_I2C
60 tristate "ChromeOS Embedded Controller (I2C)"
61 depends on MFD_CROS_EC && I2C
64 If you say Y here, you get support for talking to the ChromeOS
65 EC through an I2C bus. This uses a simple byte-level protocol with
66 a checksum. Failing accesses will be retried three times to
69 config MFD_CROS_EC_SPI
70 tristate "ChromeOS Embedded Controller (SPI)"
71 depends on MFD_CROS_EC && SPI
74 If you say Y here, you get support for talking to the ChromeOS EC
75 through a SPI bus, using a byte-level protocol. Since the EC's
76 response time cannot be guaranteed, we support ignoring
77 'pre-amble' bytes before the response actually starts.
81 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
84 This driver supports the ASIC3 multifunction chip found on many
85 PDAs (mainly iPAQ and HTC based ones)
88 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
91 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
92 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
93 usually found on PXA processors-based platforms. This includes
94 the I2C driver and the core APIs _only_, you have to select
95 individual components like LCD backlight, voltage regulators,
96 LEDs and battery-charger under the corresponding menus.
102 config MFD_DA9052_SPI
103 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
107 depends on SPI_MASTER=y && GENERIC_HARDIRQS
109 Support for the Dialog Semiconductor DA9052 PMIC
110 when controlled using SPI. This driver provides common support
111 for accessing the device, additional drivers must be enabled in
112 order to use the functionality of the device.
114 config MFD_DA9052_I2C
115 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
119 depends on I2C=y && GENERIC_HARDIRQS
121 Support for the Dialog Semiconductor DA9052 PMIC
122 when controlled using I2C. This driver provides common support
123 for accessing the device, additional drivers must be enabled in
124 order to use the functionality of the device.
127 bool "Dialog Semiconductor DA9055 PMIC Support"
131 depends on I2C=y && GENERIC_HARDIRQS
133 Say yes here for support of Dialog Semiconductor DA9055. This is
134 a Power Management IC. This driver provides common support for
135 accessing the device as well as the I2C interface to the chip itself.
136 Additional drivers must be enabled in order to use the functionality
139 This driver can be built as a module. If built as a module it will be
147 depends on (SPI_MASTER || I2C) && GENERIC_HARDIRQS
151 Enable support for the Freescale MC13783 and MC13892 PMICs.
152 This driver provides common support for accessing the device,
153 additional drivers must be enabled in order to use the
154 functionality of the device.
156 config MFD_MC13XXX_SPI
157 tristate "Freescale MC13783 and MC13892 SPI interface"
158 depends on SPI_MASTER && GENERIC_HARDIRQS
162 Select this if your MC13xxx is connected via an SPI bus.
164 config MFD_MC13XXX_I2C
165 tristate "Freescale MC13892 I2C interface"
166 depends on I2C && GENERIC_HARDIRQS
170 Select this if your MC13xxx is connected via an I2C bus.
173 bool "HTC EGPIO support"
174 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
176 This driver supports the CPLD egpio chip present on
177 several HTC phones. It provides basic support for input
178 pins, output pins, and irqs.
181 tristate "HTC PASIC3 LED/DS1WM chip support"
183 depends on GENERIC_HARDIRQS
185 This core driver provides register access for the LED/DS1WM
186 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
187 HTC Magician devices, respectively. Actual functionality is
188 handled by the leds-pasic3 and ds1wm drivers.
191 bool "HTC I2C PLD chip support"
192 depends on I2C=y && GPIOLIB
194 If you say yes here you get support for the supposed CPLD
195 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
196 This device provides input and output GPIOs through an I2C
197 interface to one or more sub-chips.
200 tristate "Intel ICH LPC"
201 depends on PCI && GENERIC_HARDIRQS
204 The LPC bridge function of the Intel ICH provides support for
205 many functional units. This driver provides needed support for
206 other drivers to control these functions, currently GPIO and
210 tristate "Intel SCH LPC"
211 depends on PCI && GENERIC_HARDIRQS
214 LPC bridge function of the Intel SCH provides support for
215 System Management Bus and General Purpose I/O.
217 config MFD_INTEL_MSIC
219 depends on INTEL_SCU_IPC
222 Select this option to enable access to Intel MSIC (Avatele
223 Passage) chip. This chip embeds audio, battery, GPIO, etc.
224 devices used in Intel Medfield platforms.
226 config MFD_JANZ_CMODIO
227 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
229 depends on PCI && GENERIC_HARDIRQS
231 This is the core driver for the Janz CMOD-IO PCI MODULbus
232 carrier board. This device is a PCI to MODULbus bridge which may
233 host many different types of MODULbus daughterboards, including
234 CAN and GPIO controllers.
236 config MFD_JZ4740_ADC
237 bool "Janz JZ4740 ADC core"
239 select GENERIC_IRQ_CHIP
240 depends on MACH_JZ4740
242 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
243 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
246 tristate "Kontron module PLD device"
249 This is the core driver for the PLD (Programmable Logic Device) found
250 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
251 device may provide functions like watchdog, GPIO, UART and I2C bus.
253 The following modules are supported:
255 * COMe-bPC2 (ETXexpress-PC)
256 * COMe-bSC# (ETXexpress-SC T#)
258 * COMe-cDC2 (microETXexpress-DC)
259 * COMe-cPC2 (microETXexpress-PC)
263 This driver can also be built as a module. If so, the module
264 will be called kempld-core.
267 tristate "Marvell 88PM800"
268 depends on I2C=y && GENERIC_HARDIRQS
273 This supports for Marvell 88PM800 Power Management IC.
274 This includes the I2C driver and the core APIs _only_, you have to
275 select individual components like voltage regulators, RTC and
276 battery-charger under the corresponding menus.
279 tristate "Marvell 88PM805"
280 depends on I2C=y && GENERIC_HARDIRQS
285 This supports for Marvell 88PM805 Power Management IC. This includes
286 the I2C driver and the core APIs _only_, you have to select individual
287 components like codec device, headset/Mic device under the
291 bool "Marvell 88PM8606/88PM8607"
292 depends on I2C=y && GENERIC_HARDIRQS
296 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
297 This includes the I2C driver and the core APIs _only_, you have to
298 select individual components like voltage regulators, RTC and
299 battery-charger under the corresponding menus.
302 bool "Maxim Semiconductor MAX77686 PMIC Support"
303 depends on I2C=y && GENERIC_HARDIRQS
308 Say yes here to support for Maxim Semiconductor MAX77686.
309 This is a Power Management IC with RTC on chip.
310 This driver provides common support for accessing the device;
311 additional drivers must be enabled in order to use the functionality
315 bool "Maxim Semiconductor MAX77693 PMIC Support"
316 depends on I2C=y && GENERIC_HARDIRQS
320 Say yes here to support for Maxim Semiconductor MAX77693.
321 This is a companion Power Management IC with Flash, Haptic, Charger,
322 and MUIC(Micro USB Interface Controller) controls on chip.
323 This driver provides common support for accessing the device;
324 additional drivers must be enabled in order to use the functionality
328 tristate "Maxim Semiconductor MAX8907 PMIC Support"
330 depends on I2C=y && GENERIC_HARDIRQS
334 Say yes here to support for Maxim Semiconductor MAX8907. This is
335 a Power Management IC. This driver provides common support for
336 accessing the device; additional drivers must be enabled in order
337 to use the functionality of the device.
340 bool "Maxim Semiconductor MAX8925 PMIC Support"
341 depends on I2C=y && GENERIC_HARDIRQS
344 Say yes here to support for Maxim Semiconductor MAX8925. This is
345 a Power Management IC. This driver provides common support for
346 accessing the device, additional drivers must be enabled in order
347 to use the functionality of the device.
350 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
351 depends on I2C=y && GENERIC_HARDIRQS
355 Say yes here to support for Maxim Semiconductor MAX8997/8966.
356 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
357 MUIC controls on chip.
358 This driver provides common support for accessing the device;
359 additional drivers must be enabled in order to use the functionality
363 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
364 depends on I2C=y && GENERIC_HARDIRQS
368 Say yes here to support for Maxim Semiconductor MAX8998 and
369 National Semiconductor LP3974. This is a Power Management IC.
370 This driver provides common support for accessing the device,
371 additional drivers must be enabled in order to use the functionality
375 bool "Motorola EZXPCAP Support"
376 depends on GENERIC_HARDIRQS && SPI_MASTER
378 This enables the PCAP ASIC present on EZX Phones. This is
379 needed for MMC, TouchScreen, Sound, USB, etc..
381 config MFD_VIPERBOARD
382 tristate "Nano River Technologies Viperboard"
384 depends on USB && GENERIC_HARDIRQS
387 Say yes here if you want support for Nano River Technologies
389 There are mfd cell drivers available for i2c master, adc and
390 both gpios found on the board. The spi part does not yet
392 You need to select the mfd cell drivers separately.
393 The drivers do not support all features the board exposes.
396 tristate "Nokia Retu and Tahvo multi-function device"
398 depends on I2C && GENERIC_HARDIRQS
401 Retu and Tahvo are a multi-function devices found on Nokia
402 Internet Tablets (770, N800 and N810).
405 tristate "NXP PCF50633"
409 Say yes here if you have NXP PCF50633 chip on your board.
410 This core driver provides register access and IRQ handling
411 facilities, and registers devices for the various functions
412 so that function-specific drivers can bind to them.
415 tristate "NXP PCF50633 ADC"
416 depends on MFD_PCF50633
418 Say yes here if you want to include support for ADC in the
422 tristate "NXP PCF50633 GPIO"
423 depends on MFD_PCF50633
425 Say yes here if you want to include support GPIO for pins on
429 tristate "Philips UCB1400 Core driver"
433 This enables support for the Philips UCB1400 core functions.
434 The UCB1400 is an AC97 audio codec.
436 To compile this driver as a module, choose M here: the
437 module will be called ucb1400_core.
442 config MFD_PM8921_CORE
443 tristate "Qualcomm PM8921 PMIC chip"
444 depends on (ARCH_MSM || HEXAGON)
449 If you say yes to this option, support will be included for the
450 built-in PM8921 PMIC chip.
452 This is required if your board has a PM8921 and uses its features,
453 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
455 Say M here if you want to include support for PM8921 chip as a module.
456 This will build a module called "pm8921-core".
458 config MFD_PM8XXX_IRQ
459 bool "Qualcomm PM8xxx IRQ features"
460 depends on MFD_PM8XXX
461 default y if MFD_PM8XXX
463 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
465 This is required to use certain other PM 8xxx features, such as GPIO
469 tristate "RDC R-321x southbridge"
471 depends on PCI && GENERIC_HARDIRQS
473 Say yes here if you want to have support for the RDC R-321x SoC
474 southbridge which provides access to GPIOs and Watchdog using the
475 southbridge PCI device configuration space.
478 tristate "Realtek PCI-E card reader"
479 depends on PCI && GENERIC_HARDIRQS
482 This supports for Realtek PCI-Express card reader including rts5209,
483 rts5229, rtl8411, etc. Realtek card reader supports access to many
484 types of memory cards, such as Memory Stick, Memory Stick Pro,
485 Secure Digital and MultiMediaCard.
488 bool "Ricoh RC5T583 Power Management system device"
489 depends on I2C=y && GENERIC_HARDIRQS
493 Select this option to get support for the RICOH583 Power
494 Management system device.
495 This driver provides common support for accessing the device
496 through i2c interface. The device supports multiple sub-devices
497 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
498 Additional drivers must be enabled in order to use the
499 different functionality of the device.
502 bool "SAMSUNG Electronics PMIC Series Support"
503 depends on I2C=y && GENERIC_HARDIRQS
508 Support for the Samsung Electronics MFD series.
509 This driver provides common support for accessing the device,
510 additional drivers must be enabled in order to use the functionality
513 config MFD_SI476X_CORE
514 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
519 This is the core driver for the SI476x series of AM/FM
520 radio. This MFD driver connects the radio-si476x V4L2 module
521 and the si476x audio codec.
523 To compile this driver as a module, choose M here: the
524 module will be called si476x-core.
527 tristate "Silicon Motion SM501"
529 This is the core driver for the Silicon Motion SM501 multimedia
530 companion chip. This device is a multifunction device which may
531 provide numerous interfaces including USB host controller, USB gadget,
532 asynchronous serial ports, audio functions, and a dual display video
533 interface. The device may be connected by PCI or local bus with
534 varying functions enabled.
536 config MFD_SM501_GPIO
537 bool "Export GPIO via GPIO layer"
538 depends on MFD_SM501 && GPIOLIB
540 This option uses the gpio library layer to export the 64 GPIO
541 lines on the SM501. The platform data is used to supply the
542 base number for the first GPIO line to register.
545 bool "SMSC ECE1099 series chips"
546 depends on I2C=y && GENERIC_HARDIRQS
550 If you say yes here you get support for the
551 ece1099 chips from SMSC.
553 To compile this driver as a module, choose M here: the
554 module will be called smsc.
557 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
558 default y if ARCH_U300 || ARCH_U8500
560 Say yes here if you have the ABX500 Mixed Signal IC family
561 chips. This core driver expose register access functions.
562 Functionality specific drivers using these functions can
563 remain unchanged when IC changes. Binding of the functions to
564 actual register access is done by the IC core driver.
567 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
568 depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
570 default y if ARCH_U300
572 Select this to enable the AB3100 Mixed Signal IC core
573 functionality. This connects to a AB3100 on the I2C bus
574 and expose a number of symbols needed for dependent devices
575 to read and write registers and subscribe to events from
576 this multi-functional IC. This is needed to use other features
577 of the AB3100 such as battery-backed RTC, charging control,
578 LEDs, vibrator, system power and temperature, power management
582 tristate "ST-Ericsson AB3100 OTP functions"
583 depends on AB3100_CORE
584 default y if AB3100_CORE
586 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
587 programmable memory) support. This exposes a sysfs file to read
591 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
592 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
597 Select this option to enable access to AB8500 power management
598 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
599 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
600 the irq_chip parts for handling the Mixed Signal chip events.
601 This chip embeds various other multimedia funtionalities as well.
604 bool "Enable debug info via debugfs"
605 depends on AB8500_GPADC && DEBUG_FS
606 default y if DEBUG_FS
608 Select this option if you want debug information using the debug
612 bool "ST-Ericsson AB8500 GPADC driver"
613 depends on AB8500_CORE && REGULATOR_AB8500
616 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
618 config MFD_DB8500_PRCMU
619 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
620 depends on UX500_SOC_DB8500
623 Select this option to enable support for the DB8500 Power Reset
624 and Control Management Unit. This is basically an autonomous
625 system controller running an XP70 microprocessor, which is accessed
626 through a register map.
629 bool "STMicroelectronics STMPE"
630 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
633 Support for the STMPE family of I/O Expanders from
636 Currently supported devices are:
638 STMPE811: GPIO, Touchscreen
639 STMPE1601: GPIO, Keypad
640 STMPE1801: GPIO, Keypad
641 STMPE2401: GPIO, Keypad
642 STMPE2403: GPIO, Keypad
644 This driver provides common support for accessing the device,
645 additional drivers must be enabled in order to use the functionality
646 of the device. Currently available sub drivers are:
650 Touchscreen: stmpe-ts
652 menu "STMicroelectronics STMPE Interface Drivers"
656 bool "STMicroelectronics STMPE I2C Inteface"
660 This is used to enable I2C interface of STMPE
663 bool "STMicroelectronics STMPE SPI Inteface"
664 depends on SPI_MASTER
666 This is used to enable SPI interface of STMPE
670 bool "STMicroelectronics STA2X11"
671 depends on STA2X11 && GENERIC_HARDIRQS
676 bool "System Controller Register R/W Based on Regmap"
679 Select this option to enable accessing system control registers
682 config MFD_DAVINCI_VOICECODEC
686 config MFD_TI_AM335X_TSCADC
687 tristate "TI ADC / Touch Screen chip support"
691 depends on GENERIC_HARDIRQS
693 If you say yes here you get support for Texas Instruments series
694 of Touch Screen /ADC chips.
695 To compile this driver as a module, choose M here: the
696 module will be called ti_am335x_tscadc.
698 config MFD_DM355EVM_MSP
699 bool "TI DaVinci DM355 EVM microcontroller"
700 depends on I2C=y && MACH_DAVINCI_DM355_EVM
702 This driver supports the MSP430 microcontroller used on these
703 boards. MSP430 firmware manages resets and power sequencing,
704 inputs from buttons and the IR remote, LEDs, an RTC, and more.
707 bool "TI LP8788 Power Management Unit Driver"
708 depends on I2C=y && GENERIC_HARDIRQS
713 TI LP8788 PMU supports regulators, battery charger, RTC,
714 ADC, backlight driver and current sinks.
716 config MFD_OMAP_USB_HOST
717 bool "TI OMAP USBHS core and TLL driver"
718 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
721 This is the core driver for the OAMP EHCI and OHCI drivers.
722 This MFD driver does the required setup functionalities for
723 OMAP USB Host drivers.
726 bool "TI Palmas series chips"
730 depends on I2C=y && GENERIC_HARDIRQS
732 If you say yes here you get support for the Palmas
733 series of PMIC chips from Texas Instruments.
736 tristate "TI Sequencer Serial Port support"
737 depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
740 Say Y here if you want support for the Sequencer Serial Port
741 in a Texas Instruments TNETV107X SoC.
743 To compile this driver as a module, choose M here: the
744 module will be called ti-ssp.
747 tristate "TI TPS61050/61052 Boost Converters"
751 select REGULATOR_FIXED_VOLTAGE
752 depends on GENERIC_HARDIRQS
754 This option enables a driver for the TP61050/TPS61052
755 high-power "white LED driver". This boost converter is
756 sometimes used for other things than white LEDs, and
757 also contains a GPIO pin.
760 tristate "TI TPS6501x Power Management chips"
761 depends on I2C && GPIOLIB
762 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
764 If you say yes here you get support for the TPS6501x series of
765 Power Management chips. These include voltage regulators,
766 lithium ion/polymer battery charging, and other features that
767 are often used in portable devices like cell phones and cameras.
769 This driver can also be built as a module. If so, the module
770 will be called tps65010.
773 tristate "TI TPS6507x Power Management / Touch Screen chips"
775 depends on I2C && GENERIC_HARDIRQS
777 If you say yes here you get support for the TPS6507x series of
778 Power Management / Touch Screen chips. These include voltage
779 regulators, lithium ion/polymer battery charging, touch screen
780 and other features that are often used in portable devices.
781 This driver can also be built as a module. If so, the module
782 will be called tps6507x.
784 config TPS65911_COMPARATOR
788 bool "TI TPS65090 Power Management chips"
789 depends on I2C=y && GENERIC_HARDIRQS
794 If you say yes here you get support for the TPS65090 series of
795 Power Management chips.
796 This driver provides common support for accessing the device,
797 additional drivers must be enabled in order to use the
798 functionality of the device.
801 tristate "TI TPS65217 Power Management / White LED chips"
802 depends on I2C && GENERIC_HARDIRQS
806 If you say yes here you get support for the TPS65217 series of
807 Power Management / White LED chips.
808 These include voltage regulators, lithium ion/polymer battery
809 charger, wled and other features that are often used in portable
812 This driver can also be built as a module. If so, the module
813 will be called tps65217.
816 bool "TI TPS6586x Power Management chips"
817 depends on I2C=y && GENERIC_HARDIRQS
821 If you say yes here you get support for the TPS6586X series of
822 Power Management chips.
823 This driver provides common support for accessing the device,
824 additional drivers must be enabled in order to use the
825 functionality of the device.
827 This driver can also be built as a module. If so, the module
828 will be called tps6586x.
831 bool "TI TPS65910 Power Management chip"
832 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
838 if you say yes here you get support for the TPS65910 series of
839 Power Management chips.
842 bool "TI TPS65912 Power Management chip"
846 If you say yes here you get support for the TPS65912 series of
849 config MFD_TPS65912_I2C
850 bool "TI TPS65912 Power Management chip with I2C"
853 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
855 If you say yes here you get support for the TPS65912 series of
856 PM chips with I2C interface.
858 config MFD_TPS65912_SPI
859 bool "TI TPS65912 Power Management chip with SPI"
862 depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
864 If you say yes here you get support for the TPS65912 series of
865 PM chips with SPI interface.
868 bool "TI TPS80031/TPS80032 Power Management chips"
869 depends on I2C=y && GENERIC_HARDIRQS
874 If you say yes here you get support for the Texas Instruments
875 TPS80031/ TPS80032 Fully Integrated Power Management with Power
876 Path and Battery Charger. The device provides five configurable
877 step-down converters, 11 general purpose LDOs, USB OTG Module,
878 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
879 Power Path from USB, 32K clock generator.
882 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
883 depends on I2C=y && GENERIC_HARDIRQS
887 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
888 This core driver provides register access and IRQ handling
889 facilities, and registers devices for the various functions
890 so that function-specific drivers can bind to them.
892 These multi-function chips are found on many OMAP2 and OMAP3
893 boards, providing power management, RTC, GPIO, keypad, a
894 high speed USB OTG transceiver, an audio codec (on most
895 versions) and many other features.
898 tristate "TI TWL4030 MADC"
899 depends on TWL4030_CORE
901 This driver provides support for triton TWL4030-MADC. The
902 driver supports both RT and SW conversion methods.
904 This driver can be built as a module. If so it will be
908 bool "TI TWL4030 power resources"
909 depends on TWL4030_CORE && ARM
911 Say yes here if you want to use the power resources on the
912 TWL4030 family chips. Most of these resources are regulators,
913 which have a separate driver; some are control signals, such
914 as clock request handshaking.
916 This driver uses board-specific data to initialize the resources
917 and load scripts controlling which resources are switched off/on
918 or reset when a sleep, wakeup or warm reset event occurs.
920 config MFD_TWL4030_AUDIO
921 bool "TI TWL4030 Audio"
922 depends on TWL4030_CORE && GENERIC_HARDIRQS
927 bool "TI TWL6040 audio codec"
928 depends on I2C=y && GENERIC_HARDIRQS
934 Say yes here if you want support for Texas Instruments TWL6040 audio
936 This driver provides common support for accessing the device,
937 additional drivers must be enabled in order to use the
938 functionality of the device (audio, vibra).
941 bool "TI TWL92330/Menelaus PM chip"
942 depends on I2C=y && ARCH_OMAP2
944 If you say yes here you get support for the Texas Instruments
945 TWL92330/Menelaus Power Management chip. This include voltage
946 regulators, Dual slot memory card transceivers, real-time clock
947 and other features that are often used in portable devices like
948 cell phones and PDAs.
950 config MFD_WL1273_CORE
951 tristate "TI WL1273 FM radio"
952 depends on I2C && GENERIC_HARDIRQS
956 This is the core driver for the TI WL1273 FM radio. This MFD
957 driver connects the radio-wl1273 V4L2 module and the wl1273
961 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
965 depends on GENERIC_HARDIRQS
967 Say yes here to enable support for National Semiconductor / TI
968 LM3533 Lighting Power chips.
970 This driver provides common support for accessing the device;
971 additional drivers must be enabled in order to use the LED,
972 backlight or ambient-light-sensor functionality of the device.
974 config MFD_TIMBERDALE
975 tristate "Timberdale FPGA"
977 depends on PCI && GPIOLIB
979 This is the core driver for the timberdale FPGA. This device is a
980 multifunction device which exposes numerous platform devices.
982 The timberdale FPGA can be found on the Intel Atom development board
983 for in-vehicle infontainment, called Russellville.
986 bool "Toshiba TC35892 and variants"
987 depends on I2C=y && GENERIC_HARDIRQS
990 Support for the Toshiba TC35892 and variants I/O Expander.
992 This driver provides common support for accessing the device,
993 additional drivers must be enabled in order to use the
994 functionality of the device.
1001 bool "Toshiba T7L66XB"
1002 depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
1006 Support for Toshiba Mobile IO Controller T7L66XB
1009 bool "Toshiba TC6387XB"
1010 depends on ARM && HAVE_CLK
1014 Support for Toshiba Mobile IO Controller TC6387XB
1017 bool "Toshiba TC6393XB"
1018 depends on ARM && HAVE_CLK
1023 Support for Toshiba Mobile IO Controller TC6393XB
1026 tristate "VIA VX855/VX875 integrated south bridge"
1027 depends on PCI && GENERIC_HARDIRQS
1030 Say yes here to enable support for various functions of the
1031 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1032 and/or vx855_gpio drivers for this to do anything useful.
1040 config MFD_ARIZONA_I2C
1041 tristate "Wolfson Microelectronics Arizona platform with I2C"
1045 depends on I2C && GENERIC_HARDIRQS
1047 Support for the Wolfson Microelectronics Arizona platform audio SoC
1048 core functionality controlled via I2C.
1050 config MFD_ARIZONA_SPI
1051 tristate "Wolfson Microelectronics Arizona platform with SPI"
1055 depends on SPI_MASTER && GENERIC_HARDIRQS
1057 Support for the Wolfson Microelectronics Arizona platform audio SoC
1058 core functionality controlled via I2C.
1061 bool "Wolfson Microelectronics WM5102"
1062 depends on MFD_ARIZONA
1064 Support for Wolfson Microelectronics WM5102 low power audio SoC
1067 bool "Wolfson Microelectronics WM5110"
1068 depends on MFD_ARIZONA
1070 Support for Wolfson Microelectronics WM5110 low power audio SoC
1073 bool "Support Wolfson Microelectronics WM8997"
1074 depends on MFD_ARIZONA
1076 Support for Wolfson Microelectronics WM8997 low power audio SoC
1079 bool "Wolfson Microelectronics WM8400"
1081 depends on I2C=y && GENERIC_HARDIRQS
1084 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1085 CODEC. This driver provides common support for accessing
1086 the device, additional drivers must be enabled in order to use
1087 the functionality of the device.
1091 depends on GENERIC_HARDIRQS
1093 config MFD_WM831X_I2C
1094 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1099 depends on I2C=y && GENERIC_HARDIRQS
1101 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1102 when controlled using I2C. This driver provides common support
1103 for accessing the device, additional drivers must be enabled in
1104 order to use the functionality of the device.
1106 config MFD_WM831X_SPI
1107 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1112 depends on SPI_MASTER && GENERIC_HARDIRQS
1114 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1115 when controlled using SPI. This driver provides common support
1116 for accessing the device, additional drivers must be enabled in
1117 order to use the functionality of the device.
1121 depends on GENERIC_HARDIRQS
1123 config MFD_WM8350_I2C
1124 bool "Wolfson Microelectronics WM8350 with I2C"
1126 depends on I2C=y && GENERIC_HARDIRQS
1128 The WM8350 is an integrated audio and power management
1129 subsystem with watchdog and RTC functionality for embedded
1130 systems. This option enables core support for the WM8350 with
1131 I2C as the control interface. Additional options must be
1132 selected to enable support for the functionality of the chip.
1135 bool "Wolfson Microelectronics WM8994"
1139 depends on I2C=y && GENERIC_HARDIRQS
1141 The WM8994 is a highly integrated hi-fi CODEC designed for
1142 smartphone applicatiosn. As well as audio functionality it
1143 has on board GPIO and regulator functionality which is
1144 supported via the relevant subsystems. This driver provides
1145 core support for the WM8994, in order to use the actual
1146 functionaltiy of the device other drivers must be enabled.
1151 menu "Multimedia Capabilities Port drivers"
1152 depends on ARCH_SA1100
1159 tristate "Support SA11x0 MCP interface"
1160 depends on ARCH_SA1100
1165 bool "Support for UCB1200 / UCB1300"
1166 depends on MCP_SA11X0
1169 config MCP_UCB1200_TS
1170 tristate "Touchscreen interface support"
1171 depends on MCP_UCB1200 && INPUT
1175 config VEXPRESS_CONFIG
1176 bool "ARM Versatile Express platform infrastructure"
1177 depends on ARM || ARM64
1179 Platform configuration infrastructure for the ARM Ltd.