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.
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
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 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
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"
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"
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
143 bool "Dialog Semiconductor DA9063 PMIC Support"
149 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
150 This includes the I2C driver and core APIs.
151 Additional drivers must be enabled in order to use the functionality
159 depends on (SPI_MASTER || I2C)
163 Enable support for the Freescale MC13783 and MC13892 PMICs.
164 This driver provides common support for accessing the device,
165 additional drivers must be enabled in order to use the
166 functionality of the device.
168 config MFD_MC13XXX_SPI
169 tristate "Freescale MC13783 and MC13892 SPI interface"
170 depends on SPI_MASTER
174 Select this if your MC13xxx is connected via an SPI bus.
176 config MFD_MC13XXX_I2C
177 tristate "Freescale MC13892 I2C interface"
182 Select this if your MC13xxx is connected via an I2C bus.
185 bool "HTC EGPIO support"
186 depends on GPIOLIB && ARM
188 This driver supports the CPLD egpio chip present on
189 several HTC phones. It provides basic support for input
190 pins, output pins, and irqs.
193 tristate "HTC PASIC3 LED/DS1WM chip support"
196 This core driver provides register access for the LED/DS1WM
197 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
198 HTC Magician devices, respectively. Actual functionality is
199 handled by the leds-pasic3 and ds1wm drivers.
202 bool "HTC I2C PLD chip support"
203 depends on I2C=y && GPIOLIB
205 If you say yes here you get support for the supposed CPLD
206 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
207 This device provides input and output GPIOs through an I2C
208 interface to one or more sub-chips.
211 tristate "Intel ICH LPC"
215 The LPC bridge function of the Intel ICH provides support for
216 many functional units. This driver provides needed support for
217 other drivers to control these functions, currently GPIO and
221 tristate "Intel SCH LPC"
225 LPC bridge function of the Intel SCH provides support for
226 System Management Bus and General Purpose I/O.
228 config MFD_INTEL_MSIC
230 depends on INTEL_SCU_IPC
233 Select this option to enable access to Intel MSIC (Avatele
234 Passage) chip. This chip embeds audio, battery, GPIO, etc.
235 devices used in Intel Medfield platforms.
237 config MFD_JANZ_CMODIO
238 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
242 This is the core driver for the Janz CMOD-IO PCI MODULbus
243 carrier board. This device is a PCI to MODULbus bridge which may
244 host many different types of MODULbus daughterboards, including
245 CAN and GPIO controllers.
247 config MFD_JZ4740_ADC
248 bool "Janz JZ4740 ADC core"
250 select GENERIC_IRQ_CHIP
251 depends on MACH_JZ4740
253 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
254 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
257 tristate "Kontron module PLD device"
260 This is the core driver for the PLD (Programmable Logic Device) found
261 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
262 device may provide functions like watchdog, GPIO, UART and I2C bus.
264 The following modules are supported:
266 * COMe-bPC2 (ETXexpress-PC)
267 * COMe-bSC# (ETXexpress-SC T#)
269 * COMe-cDC2 (microETXexpress-DC)
270 * COMe-cPC2 (microETXexpress-PC)
274 This driver can also be built as a module. If so, the module
275 will be called kempld-core.
278 tristate "Marvell 88PM800"
284 This supports for Marvell 88PM800 Power Management IC.
285 This includes the I2C driver and the core APIs _only_, you have to
286 select individual components like voltage regulators, RTC and
287 battery-charger under the corresponding menus.
290 tristate "Marvell 88PM805"
296 This supports for Marvell 88PM805 Power Management IC. This includes
297 the I2C driver and the core APIs _only_, you have to select individual
298 components like codec device, headset/Mic device under the
302 bool "Marvell 88PM8606/88PM8607"
307 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
308 This includes the I2C driver and the core APIs _only_, you have to
309 select individual components like voltage regulators, RTC and
310 battery-charger under the corresponding menus.
313 bool "Maxim Semiconductor MAX77686 PMIC Support"
319 Say yes here to support for Maxim Semiconductor MAX77686.
320 This is a Power Management IC with RTC on chip.
321 This driver provides common support for accessing the device;
322 additional drivers must be enabled in order to use the functionality
326 bool "Maxim Semiconductor MAX77693 PMIC Support"
331 Say yes here to support for Maxim Semiconductor MAX77693.
332 This is a companion Power Management IC with Flash, Haptic, Charger,
333 and MUIC(Micro USB Interface Controller) controls on chip.
334 This driver provides common support for accessing the device;
335 additional drivers must be enabled in order to use the functionality
339 tristate "Maxim Semiconductor MAX8907 PMIC Support"
345 Say yes here to support for Maxim Semiconductor MAX8907. This is
346 a Power Management IC. This driver provides common support for
347 accessing the device; additional drivers must be enabled in order
348 to use the functionality of the device.
351 bool "Maxim Semiconductor MAX8925 PMIC Support"
355 Say yes here to support for Maxim Semiconductor MAX8925. This is
356 a Power Management IC. This driver provides common support for
357 accessing the device, additional drivers must be enabled in order
358 to use the functionality of the device.
361 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
366 Say yes here to support for Maxim Semiconductor MAX8997/8966.
367 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
368 MUIC controls on chip.
369 This driver provides common support for accessing the device;
370 additional drivers must be enabled in order to use the functionality
374 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
379 Say yes here to support for Maxim Semiconductor MAX8998 and
380 National Semiconductor LP3974. This is a Power Management IC.
381 This driver provides common support for accessing the device,
382 additional drivers must be enabled in order to use the functionality
386 bool "Motorola EZXPCAP Support"
387 depends on SPI_MASTER
389 This enables the PCAP ASIC present on EZX Phones. This is
390 needed for MMC, TouchScreen, Sound, USB, etc..
392 config MFD_VIPERBOARD
393 tristate "Nano River Technologies Viperboard"
398 Say yes here if you want support for Nano River Technologies
400 There are mfd cell drivers available for i2c master, adc and
401 both gpios found on the board. The spi part does not yet
403 You need to select the mfd cell drivers separately.
404 The drivers do not support all features the board exposes.
407 tristate "Nokia Retu and Tahvo multi-function device"
412 Retu and Tahvo are a multi-function devices found on Nokia
413 Internet Tablets (770, N800 and N810).
416 tristate "NXP PCF50633"
420 Say yes here if you have NXP PCF50633 chip on your board.
421 This core driver provides register access and IRQ handling
422 facilities, and registers devices for the various functions
423 so that function-specific drivers can bind to them.
426 tristate "NXP PCF50633 ADC"
427 depends on MFD_PCF50633
429 Say yes here if you want to include support for ADC in the
433 tristate "NXP PCF50633 GPIO"
434 depends on MFD_PCF50633
436 Say yes here if you want to include support GPIO for pins on
440 tristate "Philips UCB1400 Core driver"
444 This enables support for the Philips UCB1400 core functions.
445 The UCB1400 is an AC97 audio codec.
447 To compile this driver as a module, choose M here: the
448 module will be called ucb1400_core.
453 config MFD_PM8921_CORE
454 tristate "Qualcomm PM8921 PMIC chip"
455 depends on (ARCH_MSM || HEXAGON)
460 If you say yes to this option, support will be included for the
461 built-in PM8921 PMIC chip.
463 This is required if your board has a PM8921 and uses its features,
464 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
466 Say M here if you want to include support for PM8921 chip as a module.
467 This will build a module called "pm8921-core".
469 config MFD_PM8XXX_IRQ
470 bool "Qualcomm PM8xxx IRQ features"
471 depends on MFD_PM8XXX
472 default y if MFD_PM8XXX
474 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
476 This is required to use certain other PM 8xxx features, such as GPIO
480 tristate "RDC R-321x southbridge"
484 Say yes here if you want to have support for the RDC R-321x SoC
485 southbridge which provides access to GPIOs and Watchdog using the
486 southbridge PCI device configuration space.
489 tristate "Realtek PCI-E card reader"
493 This supports for Realtek PCI-Express card reader including rts5209,
494 rts5229, rtl8411, etc. Realtek card reader supports access to many
495 types of memory cards, such as Memory Stick, Memory Stick Pro,
496 Secure Digital and MultiMediaCard.
499 bool "Ricoh RC5T583 Power Management system device"
504 Select this option to get support for the RICOH583 Power
505 Management system device.
506 This driver provides common support for accessing the device
507 through i2c interface. The device supports multiple sub-devices
508 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
509 Additional drivers must be enabled in order to use the
510 different functionality of the device.
513 bool "SAMSUNG Electronics PMIC Series Support"
519 Support for the Samsung Electronics MFD series.
520 This driver provides common support for accessing the device,
521 additional drivers must be enabled in order to use the functionality
524 config MFD_SI476X_CORE
525 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
530 This is the core driver for the SI476x series of AM/FM
531 radio. This MFD driver connects the radio-si476x V4L2 module
532 and the si476x audio codec.
534 To compile this driver as a module, choose M here: the
535 module will be called si476x-core.
538 tristate "Silicon Motion SM501"
540 This is the core driver for the Silicon Motion SM501 multimedia
541 companion chip. This device is a multifunction device which may
542 provide numerous interfaces including USB host controller, USB gadget,
543 asynchronous serial ports, audio functions, and a dual display video
544 interface. The device may be connected by PCI or local bus with
545 varying functions enabled.
547 config MFD_SM501_GPIO
548 bool "Export GPIO via GPIO layer"
549 depends on MFD_SM501 && GPIOLIB
551 This option uses the gpio library layer to export the 64 GPIO
552 lines on the SM501. The platform data is used to supply the
553 base number for the first GPIO line to register.
556 bool "SMSC ECE1099 series chips"
561 If you say yes here you get support for the
562 ece1099 chips from SMSC.
564 To compile this driver as a module, choose M here: the
565 module will be called smsc.
568 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
569 default y if ARCH_U300 || ARCH_U8500
571 Say yes here if you have the ABX500 Mixed Signal IC family
572 chips. This core driver expose register access functions.
573 Functionality specific drivers using these functions can
574 remain unchanged when IC changes. Binding of the functions to
575 actual register access is done by the IC core driver.
578 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
579 depends on I2C=y && ABX500_CORE
581 default y if ARCH_U300
583 Select this to enable the AB3100 Mixed Signal IC core
584 functionality. This connects to a AB3100 on the I2C bus
585 and expose a number of symbols needed for dependent devices
586 to read and write registers and subscribe to events from
587 this multi-functional IC. This is needed to use other features
588 of the AB3100 such as battery-backed RTC, charging control,
589 LEDs, vibrator, system power and temperature, power management
593 tristate "ST-Ericsson AB3100 OTP functions"
594 depends on AB3100_CORE
595 default y if AB3100_CORE
597 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
598 programmable memory) support. This exposes a sysfs file to read
602 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
603 depends on ABX500_CORE && MFD_DB8500_PRCMU
608 Select this option to enable access to AB8500 power management
609 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
610 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
611 the irq_chip parts for handling the Mixed Signal chip events.
612 This chip embeds various other multimedia funtionalities as well.
615 bool "Enable debug info via debugfs"
616 depends on AB8500_GPADC && DEBUG_FS
617 default y if DEBUG_FS
619 Select this option if you want debug information using the debug
623 bool "ST-Ericsson AB8500 GPADC driver"
624 depends on AB8500_CORE && REGULATOR_AB8500
627 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
629 config MFD_DB8500_PRCMU
630 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
631 depends on UX500_SOC_DB8500
634 Select this option to enable support for the DB8500 Power Reset
635 and Control Management Unit. This is basically an autonomous
636 system controller running an XP70 microprocessor, which is accessed
637 through a register map.
640 bool "STMicroelectronics STMPE"
641 depends on (I2C=y || SPI_MASTER=y)
644 Support for the STMPE family of I/O Expanders from
647 Currently supported devices are:
649 STMPE811: GPIO, Touchscreen
650 STMPE1601: GPIO, Keypad
651 STMPE1801: GPIO, Keypad
652 STMPE2401: GPIO, Keypad
653 STMPE2403: GPIO, Keypad
655 This driver provides common support for accessing the device,
656 additional drivers must be enabled in order to use the functionality
657 of the device. Currently available sub drivers are:
661 Touchscreen: stmpe-ts
663 menu "STMicroelectronics STMPE Interface Drivers"
667 bool "STMicroelectronics STMPE I2C Inteface"
671 This is used to enable I2C interface of STMPE
674 bool "STMicroelectronics STMPE SPI Inteface"
675 depends on SPI_MASTER
677 This is used to enable SPI interface of STMPE
681 bool "STMicroelectronics STA2X11"
687 bool "System Controller Register R/W Based on Regmap"
690 Select this option to enable accessing system control registers
693 config MFD_DAVINCI_VOICECODEC
697 config MFD_TI_AM335X_TSCADC
698 tristate "TI ADC / Touch Screen chip support"
703 If you say yes here you get support for Texas Instruments series
704 of Touch Screen /ADC chips.
705 To compile this driver as a module, choose M here: the
706 module will be called ti_am335x_tscadc.
708 config MFD_DM355EVM_MSP
709 bool "TI DaVinci DM355 EVM microcontroller"
710 depends on I2C=y && MACH_DAVINCI_DM355_EVM
712 This driver supports the MSP430 microcontroller used on these
713 boards. MSP430 firmware manages resets and power sequencing,
714 inputs from buttons and the IR remote, LEDs, an RTC, and more.
717 bool "TI LP8788 Power Management Unit Driver"
723 TI LP8788 PMU supports regulators, battery charger, RTC,
724 ADC, backlight driver and current sinks.
726 config MFD_OMAP_USB_HOST
727 bool "TI OMAP USBHS core and TLL driver"
728 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
731 This is the core driver for the OAMP EHCI and OHCI drivers.
732 This MFD driver does the required setup functionalities for
733 OMAP USB Host drivers.
736 bool "TI Palmas series chips"
742 If you say yes here you get support for the Palmas
743 series of PMIC chips from Texas Instruments.
746 tristate "TI Sequencer Serial Port support"
747 depends on ARCH_DAVINCI_TNETV107X
750 Say Y here if you want support for the Sequencer Serial Port
751 in a Texas Instruments TNETV107X SoC.
753 To compile this driver as a module, choose M here: the
754 module will be called ti-ssp.
757 tristate "TI TPS61050/61052 Boost Converters"
761 select REGULATOR_FIXED_VOLTAGE
763 This option enables a driver for the TP61050/TPS61052
764 high-power "white LED driver". This boost converter is
765 sometimes used for other things than white LEDs, and
766 also contains a GPIO pin.
769 tristate "TI TPS6501x Power Management chips"
770 depends on I2C && GPIOLIB
771 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
773 If you say yes here you get support for the TPS6501x series of
774 Power Management chips. These include voltage regulators,
775 lithium ion/polymer battery charging, and other features that
776 are often used in portable devices like cell phones and cameras.
778 This driver can also be built as a module. If so, the module
779 will be called tps65010.
782 tristate "TI TPS6507x Power Management / Touch Screen chips"
786 If you say yes here you get support for the TPS6507x series of
787 Power Management / Touch Screen chips. These include voltage
788 regulators, lithium ion/polymer battery charging, touch screen
789 and other features that are often used in portable devices.
790 This driver can also be built as a module. If so, the module
791 will be called tps6507x.
793 config TPS65911_COMPARATOR
797 bool "TI TPS65090 Power Management chips"
803 If you say yes here you get support for the TPS65090 series of
804 Power Management chips.
805 This driver provides common support for accessing the device,
806 additional drivers must be enabled in order to use the
807 functionality of the device.
810 tristate "TI TPS65217 Power Management / White LED chips"
815 If you say yes here you get support for the TPS65217 series of
816 Power Management / White LED chips.
817 These include voltage regulators, lithium ion/polymer battery
818 charger, wled and other features that are often used in portable
821 This driver can also be built as a module. If so, the module
822 will be called tps65217.
825 bool "TI TPS6586x Power Management chips"
830 If you say yes here you get support for the TPS6586X series of
831 Power Management chips.
832 This driver provides common support for accessing the device,
833 additional drivers must be enabled in order to use the
834 functionality of the device.
836 This driver can also be built as a module. If so, the module
837 will be called tps6586x.
840 bool "TI TPS65910 Power Management chip"
841 depends on I2C=y && GPIOLIB
847 if you say yes here you get support for the TPS65910 series of
848 Power Management chips.
851 bool "TI TPS65912 Power Management chip"
855 If you say yes here you get support for the TPS65912 series of
858 config MFD_TPS65912_I2C
859 bool "TI TPS65912 Power Management chip with I2C"
862 depends on I2C=y && GPIOLIB
864 If you say yes here you get support for the TPS65912 series of
865 PM chips with I2C interface.
867 config MFD_TPS65912_SPI
868 bool "TI TPS65912 Power Management chip with SPI"
871 depends on SPI_MASTER && GPIOLIB
873 If you say yes here you get support for the TPS65912 series of
874 PM chips with SPI interface.
877 bool "TI TPS80031/TPS80032 Power Management chips"
883 If you say yes here you get support for the Texas Instruments
884 TPS80031/ TPS80032 Fully Integrated Power Management with Power
885 Path and Battery Charger. The device provides five configurable
886 step-down converters, 11 general purpose LDOs, USB OTG Module,
887 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
888 Power Path from USB, 32K clock generator.
891 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
896 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
897 This core driver provides register access and IRQ handling
898 facilities, and registers devices for the various functions
899 so that function-specific drivers can bind to them.
901 These multi-function chips are found on many OMAP2 and OMAP3
902 boards, providing power management, RTC, GPIO, keypad, a
903 high speed USB OTG transceiver, an audio codec (on most
904 versions) and many other features.
907 tristate "TI TWL4030 MADC"
908 depends on TWL4030_CORE
910 This driver provides support for triton TWL4030-MADC. The
911 driver supports both RT and SW conversion methods.
913 This driver can be built as a module. If so it will be
917 bool "TI TWL4030 power resources"
918 depends on TWL4030_CORE && ARM
920 Say yes here if you want to use the power resources on the
921 TWL4030 family chips. Most of these resources are regulators,
922 which have a separate driver; some are control signals, such
923 as clock request handshaking.
925 This driver uses board-specific data to initialize the resources
926 and load scripts controlling which resources are switched off/on
927 or reset when a sleep, wakeup or warm reset event occurs.
929 config MFD_TWL4030_AUDIO
930 bool "TI TWL4030 Audio"
931 depends on TWL4030_CORE
936 bool "TI TWL6040 audio codec"
943 Say yes here if you want support for Texas Instruments TWL6040 audio
945 This driver provides common support for accessing the device,
946 additional drivers must be enabled in order to use the
947 functionality of the device (audio, vibra).
950 bool "TI TWL92330/Menelaus PM chip"
951 depends on I2C=y && ARCH_OMAP2
953 If you say yes here you get support for the Texas Instruments
954 TWL92330/Menelaus Power Management chip. This include voltage
955 regulators, Dual slot memory card transceivers, real-time clock
956 and other features that are often used in portable devices like
957 cell phones and PDAs.
959 config MFD_WL1273_CORE
960 tristate "TI WL1273 FM radio"
965 This is the core driver for the TI WL1273 FM radio. This MFD
966 driver connects the radio-wl1273 V4L2 module and the wl1273
970 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
975 Say yes here to enable support for National Semiconductor / TI
976 LM3533 Lighting Power chips.
978 This driver provides common support for accessing the device;
979 additional drivers must be enabled in order to use the LED,
980 backlight or ambient-light-sensor functionality of the device.
982 config MFD_TIMBERDALE
983 tristate "Timberdale FPGA"
985 depends on PCI && GPIOLIB
987 This is the core driver for the timberdale FPGA. This device is a
988 multifunction device which exposes numerous platform devices.
990 The timberdale FPGA can be found on the Intel Atom development board
991 for in-vehicle infontainment, called Russellville.
994 bool "Toshiba TC35892 and variants"
998 Support for the Toshiba TC35892 and variants I/O Expander.
1000 This driver provides common support for accessing the device,
1001 additional drivers must be enabled in order to use the
1002 functionality of the device.
1009 bool "Toshiba T7L66XB"
1010 depends on ARM && HAVE_CLK
1014 Support for Toshiba Mobile IO Controller T7L66XB
1017 bool "Toshiba TC6387XB"
1018 depends on ARM && HAVE_CLK
1022 Support for Toshiba Mobile IO Controller TC6387XB
1025 bool "Toshiba TC6393XB"
1026 depends on ARM && HAVE_CLK
1031 Support for Toshiba Mobile IO Controller TC6393XB
1034 tristate "VIA VX855/VX875 integrated south bridge"
1038 Say yes here to enable support for various functions of the
1039 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1040 and/or vx855_gpio drivers for this to do anything useful.
1048 config MFD_ARIZONA_I2C
1049 tristate "Wolfson Microelectronics Arizona platform with I2C"
1055 Support for the Wolfson Microelectronics Arizona platform audio SoC
1056 core functionality controlled via I2C.
1058 config MFD_ARIZONA_SPI
1059 tristate "Wolfson Microelectronics Arizona platform with SPI"
1063 depends on SPI_MASTER
1065 Support for the Wolfson Microelectronics Arizona platform audio SoC
1066 core functionality controlled via I2C.
1069 bool "Wolfson Microelectronics WM5102"
1070 depends on MFD_ARIZONA
1072 Support for Wolfson Microelectronics WM5102 low power audio SoC
1075 bool "Wolfson Microelectronics WM5110"
1076 depends on MFD_ARIZONA
1078 Support for Wolfson Microelectronics WM5110 low power audio SoC
1081 bool "Wolfson Microelectronics WM8997"
1082 depends on MFD_ARIZONA
1084 Support for Wolfson Microelectronics WM8997 low power audio SoC
1087 bool "Wolfson Microelectronics WM8400"
1092 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1093 CODEC. This driver provides common support for accessing
1094 the device, additional drivers must be enabled in order to use
1095 the functionality of the device.
1100 config MFD_WM831X_I2C
1101 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1108 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1109 when controlled using I2C. This driver provides common support
1110 for accessing the device, additional drivers must be enabled in
1111 order to use the functionality of the device.
1113 config MFD_WM831X_SPI
1114 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1119 depends on SPI_MASTER
1121 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1122 when controlled using SPI. This driver provides common support
1123 for accessing the device, additional drivers must be enabled in
1124 order to use the functionality of the device.
1129 config MFD_WM8350_I2C
1130 bool "Wolfson Microelectronics WM8350 with I2C"
1134 The WM8350 is an integrated audio and power management
1135 subsystem with watchdog and RTC functionality for embedded
1136 systems. This option enables core support for the WM8350 with
1137 I2C as the control interface. Additional options must be
1138 selected to enable support for the functionality of the chip.
1141 bool "Wolfson Microelectronics WM8994"
1147 The WM8994 is a highly integrated hi-fi CODEC designed for
1148 smartphone applicatiosn. As well as audio functionality it
1149 has on board GPIO and regulator functionality which is
1150 supported via the relevant subsystems. This driver provides
1151 core support for the WM8994, in order to use the actual
1152 functionaltiy of the device other drivers must be enabled.
1157 menu "Multimedia Capabilities Port drivers"
1158 depends on ARCH_SA1100
1165 tristate "Support SA11x0 MCP interface"
1166 depends on ARCH_SA1100
1171 bool "Support for UCB1200 / UCB1300"
1172 depends on MCP_SA11X0
1175 config MCP_UCB1200_TS
1176 tristate "Touchscreen interface support"
1177 depends on MCP_UCB1200 && INPUT
1181 config VEXPRESS_CONFIG
1182 bool "ARM Versatile Express platform infrastructure"
1183 depends on ARM || ARM64
1185 Platform configuration infrastructure for the ARM Ltd.