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 "ams AS3722 Power Management IC"
35 depends on I2C=y && OF
37 The ams AS3722 is a compact system PMU suitable for mobile phones,
38 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
39 controllers, 11 LDOs, RTC, automatic battery, temperature and
40 over current monitoring, GPIOs, ADC and a watchdog.
43 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
46 Say yes here to add support for Analog Devices AD5520 and ADP5501,
47 Multifunction Power Management IC. This includes
48 the I2C driver and the core APIs _only_, you have to select
49 individual components like LCD backlight, LEDs, GPIOs and Kepad
50 under the corresponding menus.
52 config MFD_AAT2870_CORE
53 bool "AnalogicTech AAT2870"
55 depends on I2C=y && GPIOLIB
57 If you say yes here you get support for the AAT2870.
58 This driver provides common support for accessing the device,
59 additional drivers must be enabled in order to use the
60 functionality of the device.
63 tristate "ChromeOS Embedded Controller"
66 If you say Y here you get support for the ChromeOS Embedded
67 Controller (EC) providing keyboard, battery and power services.
68 You also need to enable the driver for the bus you are using. The
69 protocol for talking to the EC is defined by the bus driver.
71 config MFD_CROS_EC_I2C
72 tristate "ChromeOS Embedded Controller (I2C)"
73 depends on MFD_CROS_EC && I2C
76 If you say Y here, you get support for talking to the ChromeOS
77 EC through an I2C bus. This uses a simple byte-level protocol with
78 a checksum. Failing accesses will be retried three times to
81 config MFD_CROS_EC_SPI
82 tristate "ChromeOS Embedded Controller (SPI)"
83 depends on MFD_CROS_EC && SPI && OF
86 If you say Y here, you get support for talking to the ChromeOS EC
87 through a SPI bus, using a byte-level protocol. Since the EC's
88 response time cannot be guaranteed, we support ignoring
89 'pre-amble' bytes before the response actually starts.
93 depends on GPIOLIB && ARM
96 This driver supports the ASIC3 multifunction chip found on many
97 PDAs (mainly iPAQ and HTC based ones)
100 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
103 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
104 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
105 usually found on PXA processors-based platforms. This includes
106 the I2C driver and the core APIs _only_, you have to select
107 individual components like LCD backlight, voltage regulators,
108 LEDs and battery-charger under the corresponding menus.
114 config MFD_DA9052_SPI
115 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
119 depends on SPI_MASTER=y
121 Support for the Dialog Semiconductor DA9052 PMIC
122 when controlled using SPI. 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.
126 config MFD_DA9052_I2C
127 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
133 Support for the Dialog Semiconductor DA9052 PMIC
134 when controlled using I2C. This driver provides common support
135 for accessing the device, additional drivers must be enabled in
136 order to use the functionality of the device.
139 bool "Dialog Semiconductor DA9055 PMIC Support"
145 Say yes here for support of Dialog Semiconductor DA9055. This is
146 a Power Management IC. This driver provides common support for
147 accessing the device as well as the I2C interface to the chip itself.
148 Additional drivers must be enabled in order to use the functionality
151 This driver can be built as a module. If built as a module it will be
155 bool "Dialog Semiconductor DA9063 PMIC Support"
161 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
162 This includes the I2C driver and core APIs.
163 Additional drivers must be enabled in order to use the functionality
168 depends on (SPI_MASTER || I2C)
171 Enable support for the Freescale MC13783 and MC13892 PMICs.
172 This driver provides common support for accessing the device,
173 additional drivers must be enabled in order to use the
174 functionality of the device.
176 config MFD_MC13XXX_SPI
177 tristate "Freescale MC13783 and MC13892 SPI interface"
178 depends on SPI_MASTER
182 Select this if your MC13xxx is connected via an SPI bus.
184 config MFD_MC13XXX_I2C
185 tristate "Freescale MC13892 I2C interface"
190 Select this if your MC13xxx is connected via an I2C bus.
193 bool "HTC EGPIO support"
194 depends on GPIOLIB && ARM
196 This driver supports the CPLD egpio chip present on
197 several HTC phones. It provides basic support for input
198 pins, output pins, and irqs.
201 tristate "HTC PASIC3 LED/DS1WM chip support"
204 This core driver provides register access for the LED/DS1WM
205 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
206 HTC Magician devices, respectively. Actual functionality is
207 handled by the leds-pasic3 and ds1wm drivers.
210 bool "HTC I2C PLD chip support"
211 depends on I2C=y && GPIOLIB
213 If you say yes here you get support for the supposed CPLD
214 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
215 This device provides input and output GPIOs through an I2C
216 interface to one or more sub-chips.
219 tristate "Intel ICH LPC"
223 The LPC bridge function of the Intel ICH provides support for
224 many functional units. This driver provides needed support for
225 other drivers to control these functions, currently GPIO and
229 tristate "Intel SCH LPC"
233 LPC bridge function of the Intel SCH provides support for
234 System Management Bus and General Purpose I/O.
236 config MFD_INTEL_MSIC
238 depends on INTEL_SCU_IPC
241 Select this option to enable access to Intel MSIC (Avatele
242 Passage) chip. This chip embeds audio, battery, GPIO, etc.
243 devices used in Intel Medfield platforms.
245 config MFD_JANZ_CMODIO
246 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
250 This is the core driver for the Janz CMOD-IO PCI MODULbus
251 carrier board. This device is a PCI to MODULbus bridge which may
252 host many different types of MODULbus daughterboards, including
253 CAN and GPIO controllers.
255 config MFD_JZ4740_ADC
256 bool "Janz JZ4740 ADC core"
258 select GENERIC_IRQ_CHIP
259 depends on MACH_JZ4740
261 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
262 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
265 tristate "Kontron module PLD device"
268 This is the core driver for the PLD (Programmable Logic Device) found
269 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
270 device may provide functions like watchdog, GPIO, UART and I2C bus.
272 The following modules are supported:
274 * COMe-bPC2 (ETXexpress-PC)
275 * COMe-bSC# (ETXexpress-SC T#)
277 * COMe-cDC2 (microETXexpress-DC)
278 * COMe-cPC2 (microETXexpress-PC)
282 This driver can also be built as a module. If so, the module
283 will be called kempld-core.
286 tristate "Marvell 88PM800"
292 This supports for Marvell 88PM800 Power Management IC.
293 This includes the I2C driver and the core APIs _only_, you have to
294 select individual components like voltage regulators, RTC and
295 battery-charger under the corresponding menus.
298 tristate "Marvell 88PM805"
304 This supports for Marvell 88PM805 Power Management IC. This includes
305 the I2C driver and the core APIs _only_, you have to select individual
306 components like codec device, headset/Mic device under the
310 bool "Marvell 88PM8606/88PM8607"
315 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
316 This includes the I2C driver and the core APIs _only_, you have to
317 select individual components like voltage regulators, RTC and
318 battery-charger under the corresponding menus.
321 bool "Maxim Semiconductor MAX14577 MUIC + Charger Support"
327 Say yes here to support for Maxim Semiconductor MAX14577.
328 This is a Micro-USB IC with Charger controls on chip.
329 This driver provides common support for accessing the device;
330 additional drivers must be enabled in order to use the functionality
334 bool "Maxim Semiconductor MAX77686 PMIC Support"
340 Say yes here to support for Maxim Semiconductor MAX77686.
341 This is a Power Management IC with RTC on chip.
342 This driver provides common support for accessing the device;
343 additional drivers must be enabled in order to use the functionality
347 bool "Maxim Semiconductor MAX77693 PMIC Support"
352 Say yes here to support for Maxim Semiconductor MAX77693.
353 This is a companion Power Management IC with Flash, Haptic, Charger,
354 and MUIC(Micro USB Interface Controller) controls on chip.
355 This driver provides common support for accessing the device;
356 additional drivers must be enabled in order to use the functionality
360 tristate "Maxim Semiconductor MAX8907 PMIC Support"
366 Say yes here to support for Maxim Semiconductor MAX8907. This is
367 a Power Management IC. This driver provides common support for
368 accessing the device; additional drivers must be enabled in order
369 to use the functionality of the device.
372 bool "Maxim Semiconductor MAX8925 PMIC Support"
376 Say yes here to support for Maxim Semiconductor MAX8925. This is
377 a Power Management IC. This driver provides common support for
378 accessing the device, additional drivers must be enabled in order
379 to use the functionality of the device.
382 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
387 Say yes here to support for Maxim Semiconductor MAX8997/8966.
388 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
389 MUIC controls on chip.
390 This driver provides common support for accessing the device;
391 additional drivers must be enabled in order to use the functionality
395 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
400 Say yes here to support for Maxim Semiconductor MAX8998 and
401 National Semiconductor LP3974. This is a Power Management IC.
402 This driver provides common support for accessing the device,
403 additional drivers must be enabled in order to use the functionality
407 bool "Motorola EZXPCAP Support"
408 depends on SPI_MASTER
410 This enables the PCAP ASIC present on EZX Phones. This is
411 needed for MMC, TouchScreen, Sound, USB, etc..
413 config MFD_VIPERBOARD
414 tristate "Nano River Technologies Viperboard"
419 Say yes here if you want support for Nano River Technologies
421 There are mfd cell drivers available for i2c master, adc and
422 both gpios found on the board. The spi part does not yet
424 You need to select the mfd cell drivers separately.
425 The drivers do not support all features the board exposes.
428 tristate "Nokia Retu and Tahvo multi-function device"
433 Retu and Tahvo are a multi-function devices found on Nokia
434 Internet Tablets (770, N800 and N810).
437 tristate "NXP PCF50633"
441 Say yes here if you have NXP PCF50633 chip on your board.
442 This core driver provides register access and IRQ handling
443 facilities, and registers devices for the various functions
444 so that function-specific drivers can bind to them.
447 tristate "NXP PCF50633 ADC"
448 depends on MFD_PCF50633
450 Say yes here if you want to include support for ADC in the
454 tristate "NXP PCF50633 GPIO"
455 depends on MFD_PCF50633
457 Say yes here if you want to include support GPIO for pins on
461 tristate "Philips UCB1400 Core driver"
465 This enables support for the Philips UCB1400 core functions.
466 The UCB1400 is an AC97 audio codec.
468 To compile this driver as a module, choose M here: the
469 module will be called ucb1400_core.
474 config MFD_PM8921_CORE
475 tristate "Qualcomm PM8921 PMIC chip"
476 depends on (ARCH_MSM || HEXAGON)
481 If you say yes to this option, support will be included for the
482 built-in PM8921 PMIC chip.
484 This is required if your board has a PM8921 and uses its features,
485 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
487 Say M here if you want to include support for PM8921 chip as a module.
488 This will build a module called "pm8921-core".
490 config MFD_PM8XXX_IRQ
491 bool "Qualcomm PM8xxx IRQ features"
492 depends on MFD_PM8XXX
493 default y if MFD_PM8XXX
495 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
497 This is required to use certain other PM 8xxx features, such as GPIO
501 tristate "RDC R-321x southbridge"
505 Say yes here if you want to have support for the RDC R-321x SoC
506 southbridge which provides access to GPIOs and Watchdog using the
507 southbridge PCI device configuration space.
510 tristate "Realtek PCI-E card reader"
514 This supports for Realtek PCI-Express card reader including rts5209,
515 rts5229, rtl8411, etc. Realtek card reader supports access to many
516 types of memory cards, such as Memory Stick, Memory Stick Pro,
517 Secure Digital and MultiMediaCard.
520 bool "Ricoh RC5T583 Power Management system device"
525 Select this option to get support for the RICOH583 Power
526 Management system device.
527 This driver provides common support for accessing the device
528 through i2c interface. The device supports multiple sub-devices
529 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
530 Additional drivers must be enabled in order to use the
531 different functionality of the device.
534 bool "SAMSUNG Electronics PMIC Series Support"
540 Support for the Samsung Electronics MFD series.
541 This driver provides common support for accessing the device,
542 additional drivers must be enabled in order to use the functionality
545 config MFD_SI476X_CORE
546 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
551 This is the core driver for the SI476x series of AM/FM
552 radio. This MFD driver connects the radio-si476x V4L2 module
553 and the si476x audio codec.
555 To compile this driver as a module, choose M here: the
556 module will be called si476x-core.
559 tristate "Silicon Motion SM501"
561 This is the core driver for the Silicon Motion SM501 multimedia
562 companion chip. This device is a multifunction device which may
563 provide numerous interfaces including USB host controller, USB gadget,
564 asynchronous serial ports, audio functions, and a dual display video
565 interface. The device may be connected by PCI or local bus with
566 varying functions enabled.
568 config MFD_SM501_GPIO
569 bool "Export GPIO via GPIO layer"
570 depends on MFD_SM501 && GPIOLIB
572 This option uses the gpio library layer to export the 64 GPIO
573 lines on the SM501. The platform data is used to supply the
574 base number for the first GPIO line to register.
577 bool "SMSC ECE1099 series chips"
582 If you say yes here you get support for the
583 ece1099 chips from SMSC.
585 To compile this driver as a module, choose M here: the
586 module will be called smsc.
589 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
590 default y if ARCH_U300 || ARCH_U8500
592 Say yes here if you have the ABX500 Mixed Signal IC family
593 chips. This core driver expose register access functions.
594 Functionality specific drivers using these functions can
595 remain unchanged when IC changes. Binding of the functions to
596 actual register access is done by the IC core driver.
599 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
600 depends on I2C=y && ABX500_CORE
602 default y if ARCH_U300
604 Select this to enable the AB3100 Mixed Signal IC core
605 functionality. This connects to a AB3100 on the I2C bus
606 and expose a number of symbols needed for dependent devices
607 to read and write registers and subscribe to events from
608 this multi-functional IC. This is needed to use other features
609 of the AB3100 such as battery-backed RTC, charging control,
610 LEDs, vibrator, system power and temperature, power management
614 tristate "ST-Ericsson AB3100 OTP functions"
615 depends on AB3100_CORE
616 default y if AB3100_CORE
618 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
619 programmable memory) support. This exposes a sysfs file to read
623 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
624 depends on ABX500_CORE && MFD_DB8500_PRCMU
629 Select this option to enable access to AB8500 power management
630 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
631 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
632 the irq_chip parts for handling the Mixed Signal chip events.
633 This chip embeds various other multimedia funtionalities as well.
636 bool "Enable debug info via debugfs"
637 depends on AB8500_GPADC && DEBUG_FS
638 default y if DEBUG_FS
640 Select this option if you want debug information using the debug
644 bool "ST-Ericsson AB8500 GPADC driver"
645 depends on AB8500_CORE && REGULATOR_AB8500
648 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
650 config MFD_DB8500_PRCMU
651 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
652 depends on UX500_SOC_DB8500
655 Select this option to enable support for the DB8500 Power Reset
656 and Control Management Unit. This is basically an autonomous
657 system controller running an XP70 microprocessor, which is accessed
658 through a register map.
661 bool "STMicroelectronics STMPE"
662 depends on (I2C=y || SPI_MASTER=y)
665 Support for the STMPE family of I/O Expanders from
668 Currently supported devices are:
670 STMPE811: GPIO, Touchscreen
671 STMPE1601: GPIO, Keypad
672 STMPE1801: GPIO, Keypad
673 STMPE2401: GPIO, Keypad
674 STMPE2403: GPIO, Keypad
676 This driver provides common support for accessing the device,
677 additional drivers must be enabled in order to use the functionality
678 of the device. Currently available sub drivers are:
682 Touchscreen: stmpe-ts
684 menu "STMicroelectronics STMPE Interface Drivers"
688 bool "STMicroelectronics STMPE I2C Interface"
692 This is used to enable I2C interface of STMPE
695 bool "STMicroelectronics STMPE SPI Interface"
696 depends on SPI_MASTER
698 This is used to enable SPI interface of STMPE
702 bool "STMicroelectronics STA2X11"
708 bool "System Controller Register R/W Based on Regmap"
711 Select this option to enable accessing system control registers
714 config MFD_DAVINCI_VOICECODEC
718 config MFD_TI_AM335X_TSCADC
719 tristate "TI ADC / Touch Screen chip support"
724 If you say yes here you get support for Texas Instruments series
725 of Touch Screen /ADC chips.
726 To compile this driver as a module, choose M here: the
727 module will be called ti_am335x_tscadc.
729 config MFD_DM355EVM_MSP
730 bool "TI DaVinci DM355 EVM microcontroller"
731 depends on I2C=y && MACH_DAVINCI_DM355_EVM
733 This driver supports the MSP430 microcontroller used on these
734 boards. MSP430 firmware manages resets and power sequencing,
735 inputs from buttons and the IR remote, LEDs, an RTC, and more.
738 tristate "TI/National Semiconductor LP3943 MFD Driver"
743 Support for the TI/National Semiconductor LP3943.
744 This driver consists of GPIO and PWM drivers.
745 With these functionalities, it can be used for LED string control or
746 general usage such like a GPIO controller and a PWM controller.
749 bool "TI LP8788 Power Management Unit Driver"
755 TI LP8788 PMU supports regulators, battery charger, RTC,
756 ADC, backlight driver and current sinks.
758 config MFD_OMAP_USB_HOST
759 bool "TI OMAP USBHS core and TLL driver"
760 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
763 This is the core driver for the OAMP EHCI and OHCI drivers.
764 This MFD driver does the required setup functionalities for
765 OMAP USB Host drivers.
768 bool "TI Palmas series chips"
774 If you say yes here you get support for the Palmas
775 series of PMIC chips from Texas Instruments.
778 tristate "TI Sequencer Serial Port support"
779 depends on ARCH_DAVINCI_TNETV107X
782 Say Y here if you want support for the Sequencer Serial Port
783 in a Texas Instruments TNETV107X SoC.
785 To compile this driver as a module, choose M here: the
786 module will be called ti-ssp.
789 tristate "TI TPS61050/61052 Boost Converters"
793 select REGULATOR_FIXED_VOLTAGE
795 This option enables a driver for the TP61050/TPS61052
796 high-power "white LED driver". This boost converter is
797 sometimes used for other things than white LEDs, and
798 also contains a GPIO pin.
801 tristate "TI TPS6501x Power Management chips"
802 depends on I2C && GPIOLIB
803 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
805 If you say yes here you get support for the TPS6501x series of
806 Power Management chips. These include voltage regulators,
807 lithium ion/polymer battery charging, and other features that
808 are often used in portable devices like cell phones and cameras.
810 This driver can also be built as a module. If so, the module
811 will be called tps65010.
814 tristate "TI TPS6507x Power Management / Touch Screen chips"
818 If you say yes here you get support for the TPS6507x series of
819 Power Management / Touch Screen chips. These include voltage
820 regulators, lithium ion/polymer battery charging, touch screen
821 and other features that are often used in portable devices.
822 This driver can also be built as a module. If so, the module
823 will be called tps6507x.
825 config TPS65911_COMPARATOR
829 bool "TI TPS65090 Power Management chips"
835 If you say yes here you get support for the TPS65090 series of
836 Power Management chips.
837 This driver provides common support for accessing the device,
838 additional drivers must be enabled in order to use the
839 functionality of the device.
842 tristate "TI TPS65217 Power Management / White LED chips"
847 If you say yes here you get support for the TPS65217 series of
848 Power Management / White LED chips.
849 These include voltage regulators, lithium ion/polymer battery
850 charger, wled and other features that are often used in portable
853 This driver can also be built as a module. If so, the module
854 will be called tps65217.
857 bool "TI TPS6586x Power Management chips"
862 If you say yes here you get support for the TPS6586X series of
863 Power Management chips.
864 This driver provides common support for accessing the device,
865 additional drivers must be enabled in order to use the
866 functionality of the device.
868 This driver can also be built as a module. If so, the module
869 will be called tps6586x.
872 bool "TI TPS65910 Power Management chip"
873 depends on I2C=y && GPIOLIB
879 if you say yes here you get support for the TPS65910 series of
880 Power Management chips.
883 bool "TI TPS65912 Power Management chip"
887 If you say yes here you get support for the TPS65912 series of
890 config MFD_TPS65912_I2C
891 bool "TI TPS65912 Power Management chip with I2C"
894 depends on I2C=y && GPIOLIB
896 If you say yes here you get support for the TPS65912 series of
897 PM chips with I2C interface.
899 config MFD_TPS65912_SPI
900 bool "TI TPS65912 Power Management chip with SPI"
903 depends on SPI_MASTER && GPIOLIB
905 If you say yes here you get support for the TPS65912 series of
906 PM chips with SPI interface.
909 bool "TI TPS80031/TPS80032 Power Management chips"
915 If you say yes here you get support for the Texas Instruments
916 TPS80031/ TPS80032 Fully Integrated Power Management with Power
917 Path and Battery Charger. The device provides five configurable
918 step-down converters, 11 general purpose LDOs, USB OTG Module,
919 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
920 Power Path from USB, 32K clock generator.
923 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
928 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
929 This core driver provides register access and IRQ handling
930 facilities, and registers devices for the various functions
931 so that function-specific drivers can bind to them.
933 These multi-function chips are found on many OMAP2 and OMAP3
934 boards, providing power management, RTC, GPIO, keypad, a
935 high speed USB OTG transceiver, an audio codec (on most
936 versions) and many other features.
939 tristate "TI TWL4030 MADC"
940 depends on TWL4030_CORE
942 This driver provides support for triton TWL4030-MADC. The
943 driver supports both RT and SW conversion methods.
945 This driver can be built as a module. If so it will be
949 bool "TI TWL4030 power resources"
950 depends on TWL4030_CORE && ARM
952 Say yes here if you want to use the power resources on the
953 TWL4030 family chips. Most of these resources are regulators,
954 which have a separate driver; some are control signals, such
955 as clock request handshaking.
957 This driver uses board-specific data to initialize the resources
958 and load scripts controlling which resources are switched off/on
959 or reset when a sleep, wakeup or warm reset event occurs.
961 config MFD_TWL4030_AUDIO
962 bool "TI TWL4030 Audio"
963 depends on TWL4030_CORE
968 bool "TI TWL6040 audio codec"
975 Say yes here if you want support for Texas Instruments TWL6040 audio
977 This driver provides common support for accessing the device,
978 additional drivers must be enabled in order to use the
979 functionality of the device (audio, vibra).
982 bool "TI TWL92330/Menelaus PM chip"
983 depends on I2C=y && ARCH_OMAP2
985 If you say yes here you get support for the Texas Instruments
986 TWL92330/Menelaus Power Management chip. This include voltage
987 regulators, Dual slot memory card transceivers, real-time clock
988 and other features that are often used in portable devices like
989 cell phones and PDAs.
991 config MFD_WL1273_CORE
992 tristate "TI WL1273 FM radio"
997 This is the core driver for the TI WL1273 FM radio. This MFD
998 driver connects the radio-wl1273 V4L2 module and the wl1273
1002 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1007 Say yes here to enable support for National Semiconductor / TI
1008 LM3533 Lighting Power chips.
1010 This driver provides common support for accessing the device;
1011 additional drivers must be enabled in order to use the LED,
1012 backlight or ambient-light-sensor functionality of the device.
1014 config MFD_TIMBERDALE
1015 tristate "Timberdale FPGA"
1017 depends on PCI && GPIOLIB
1019 This is the core driver for the timberdale FPGA. This device is a
1020 multifunction device which exposes numerous platform devices.
1022 The timberdale FPGA can be found on the Intel Atom development board
1023 for in-vehicle infontainment, called Russellville.
1026 bool "Toshiba TC35892 and variants"
1030 Support for the Toshiba TC35892 and variants I/O Expander.
1032 This driver provides common support for accessing the device,
1033 additional drivers must be enabled in order to use the
1034 functionality of the device.
1041 bool "Toshiba T7L66XB"
1042 depends on ARM && HAVE_CLK
1046 Support for Toshiba Mobile IO Controller T7L66XB
1049 bool "Toshiba TC6387XB"
1050 depends on ARM && HAVE_CLK
1054 Support for Toshiba Mobile IO Controller TC6387XB
1057 bool "Toshiba TC6393XB"
1058 depends on ARM && HAVE_CLK
1063 Support for Toshiba Mobile IO Controller TC6393XB
1066 tristate "VIA VX855/VX875 integrated south bridge"
1070 Say yes here to enable support for various functions of the
1071 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1072 and/or vx855_gpio drivers for this to do anything useful.
1080 config MFD_ARIZONA_I2C
1081 tristate "Wolfson Microelectronics Arizona platform with I2C"
1087 Support for the Wolfson Microelectronics Arizona platform audio SoC
1088 core functionality controlled via I2C.
1090 config MFD_ARIZONA_SPI
1091 tristate "Wolfson Microelectronics Arizona platform with SPI"
1095 depends on SPI_MASTER
1097 Support for the Wolfson Microelectronics Arizona platform audio SoC
1098 core functionality controlled via I2C.
1101 bool "Wolfson Microelectronics WM5102"
1102 depends on MFD_ARIZONA
1104 Support for Wolfson Microelectronics WM5102 low power audio SoC
1107 bool "Wolfson Microelectronics WM5110"
1108 depends on MFD_ARIZONA
1110 Support for Wolfson Microelectronics WM5110 low power audio SoC
1113 bool "Wolfson Microelectronics WM8997"
1114 depends on MFD_ARIZONA
1116 Support for Wolfson Microelectronics WM8997 low power audio SoC
1119 bool "Wolfson Microelectronics WM8400"
1124 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1125 CODEC. This driver provides common support for accessing
1126 the device, additional drivers must be enabled in order to use
1127 the functionality of the device.
1132 config MFD_WM831X_I2C
1133 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1140 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1141 when controlled using I2C. This driver provides common support
1142 for accessing the device, additional drivers must be enabled in
1143 order to use the functionality of the device.
1145 config MFD_WM831X_SPI
1146 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1151 depends on SPI_MASTER
1153 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1154 when controlled using SPI. This driver provides common support
1155 for accessing the device, additional drivers must be enabled in
1156 order to use the functionality of the device.
1161 config MFD_WM8350_I2C
1162 bool "Wolfson Microelectronics WM8350 with I2C"
1166 The WM8350 is an integrated audio and power management
1167 subsystem with watchdog and RTC functionality for embedded
1168 systems. This option enables core support for the WM8350 with
1169 I2C as the control interface. Additional options must be
1170 selected to enable support for the functionality of the chip.
1173 bool "Wolfson Microelectronics WM8994"
1179 The WM8994 is a highly integrated hi-fi CODEC designed for
1180 smartphone applicatiosn. As well as audio functionality it
1181 has on board GPIO and regulator functionality which is
1182 supported via the relevant subsystems. This driver provides
1183 core support for the WM8994, in order to use the actual
1184 functionaltiy of the device other drivers must be enabled.
1187 bool "Support for ST Microelectronics STw481x"
1188 depends on I2C && ARCH_NOMADIK
1192 Select this option to enable the STw481x chip driver used
1193 in various ST Microelectronics and ST-Ericsson embedded
1199 menu "Multimedia Capabilities Port drivers"
1200 depends on ARCH_SA1100
1207 tristate "Support SA11x0 MCP interface"
1208 depends on ARCH_SA1100
1213 bool "Support for UCB1200 / UCB1300"
1214 depends on MCP_SA11X0
1217 config MCP_UCB1200_TS
1218 tristate "Touchscreen interface support"
1219 depends on MCP_UCB1200 && INPUT
1223 config VEXPRESS_CONFIG
1224 bool "ARM Versatile Express platform infrastructure"
1225 depends on ARM || ARM64
1227 Platform configuration infrastructure for the ARM Ltd.