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 add 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:
275 * COMe-bPC2 (ETXexpress-PC)
276 * COMe-bSC# (ETXexpress-SC T#)
279 * COMe-cDC2 (microETXexpress-DC)
281 * COMe-cPC2 (microETXexpress-PC)
284 * COMe-mTT10 (nanoETXexpress-TT)
287 This driver can also be built as a module. If so, the module
288 will be called kempld-core.
291 tristate "Marvell 88PM800"
297 This supports for Marvell 88PM800 Power Management IC.
298 This includes the I2C driver and the core APIs _only_, you have to
299 select individual components like voltage regulators, RTC and
300 battery-charger under the corresponding menus.
303 tristate "Marvell 88PM805"
309 This supports for Marvell 88PM805 Power Management IC. This includes
310 the I2C driver and the core APIs _only_, you have to select individual
311 components like codec device, headset/Mic device under the
315 bool "Marvell 88PM8606/88PM8607"
320 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
321 This includes the I2C driver and the core APIs _only_, you have to
322 select individual components like voltage regulators, RTC and
323 battery-charger under the corresponding menus.
326 bool "Maxim Semiconductor MAX14577 MUIC + Charger Support"
332 Say yes here to add support for Maxim Semiconductor MAX14577.
333 This is a Micro-USB IC with Charger 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 bool "Maxim Semiconductor MAX77686 PMIC Support"
345 Say yes here to add support for Maxim Semiconductor MAX77686.
346 This is a Power Management IC with RTC on chip.
347 This driver provides common support for accessing the device;
348 additional drivers must be enabled in order to use the functionality
352 bool "Maxim Semiconductor MAX77693 PMIC Support"
357 Say yes here to add support for Maxim Semiconductor MAX77693.
358 This is a companion Power Management IC with Flash, Haptic, Charger,
359 and MUIC(Micro USB Interface Controller) controls on chip.
360 This driver provides common support for accessing the device;
361 additional drivers must be enabled in order to use the functionality
365 tristate "Maxim Semiconductor MAX8907 PMIC Support"
371 Say yes here to add support for Maxim Semiconductor MAX8907. This is
372 a Power Management IC. This driver provides common support for
373 accessing the device; additional drivers must be enabled in order
374 to use the functionality of the device.
377 bool "Maxim Semiconductor MAX8925 PMIC Support"
381 Say yes here to add support for Maxim Semiconductor MAX8925. This is
382 a Power Management IC. This driver provides common support for
383 accessing the device, additional drivers must be enabled in order
384 to use the functionality of the device.
387 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
392 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
393 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
394 MUIC controls on chip.
395 This driver provides common support for accessing the device;
396 additional drivers must be enabled in order to use the functionality
400 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
405 Say yes here to add support for Maxim Semiconductor MAX8998 and
406 National Semiconductor LP3974. This is a Power Management IC.
407 This driver provides common support for accessing the device,
408 additional drivers must be enabled in order to use the functionality
412 bool "Motorola EZXPCAP Support"
413 depends on SPI_MASTER
415 This enables the PCAP ASIC present on EZX Phones. This is
416 needed for MMC, TouchScreen, Sound, USB, etc..
418 config MFD_VIPERBOARD
419 tristate "Nano River Technologies Viperboard"
424 Say yes here if you want support for Nano River Technologies
426 There are mfd cell drivers available for i2c master, adc and
427 both gpios found on the board. The spi part does not yet
429 You need to select the mfd cell drivers separately.
430 The drivers do not support all features the board exposes.
433 tristate "Nokia Retu and Tahvo multi-function device"
438 Retu and Tahvo are a multi-function devices found on Nokia
439 Internet Tablets (770, N800 and N810).
442 tristate "NXP PCF50633"
446 Say yes here if you have NXP PCF50633 chip on your board.
447 This core driver provides register access and IRQ handling
448 facilities, and registers devices for the various functions
449 so that function-specific drivers can bind to them.
452 tristate "NXP PCF50633 ADC"
453 depends on MFD_PCF50633
455 Say yes here if you want to include support for ADC in the
459 tristate "NXP PCF50633 GPIO"
460 depends on MFD_PCF50633
462 Say yes here if you want to include support GPIO for pins on
466 tristate "Philips UCB1400 Core driver"
470 This enables support for the Philips UCB1400 core functions.
471 The UCB1400 is an AC97 audio codec.
473 To compile this driver as a module, choose M here: the
474 module will be called ucb1400_core.
479 config MFD_PM8921_CORE
480 tristate "Qualcomm PM8921 PMIC chip"
481 depends on (ARM || HEXAGON)
487 If you say yes to this option, support will be included for the
488 built-in PM8921 PMIC chip.
490 This is required if your board has a PM8921 and uses its features,
491 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
493 Say M here if you want to include support for PM8921 chip as a module.
494 This will build a module called "pm8921-core".
497 tristate "RDC R-321x southbridge"
501 Say yes here if you want to have support for the RDC R-321x SoC
502 southbridge which provides access to GPIOs and Watchdog using the
503 southbridge PCI device configuration space.
506 tristate "Realtek PCI-E card reader"
510 This supports for Realtek PCI-Express card reader including rts5209,
511 rts5229, rtl8411, etc. Realtek card reader supports access to many
512 types of memory cards, such as Memory Stick, Memory Stick Pro,
513 Secure Digital and MultiMediaCard.
516 tristate "Realtek USB card reader"
520 Select this option to get support for Realtek USB 2.0 card readers
521 including RTS5129, RTS5139, RTS5179 and RTS5170.
522 Realtek card reader supports access to many types of memory cards,
523 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
526 bool "Ricoh RC5T583 Power Management system device"
531 Select this option to get support for the RICOH583 Power
532 Management system device.
533 This driver provides common support for accessing the device
534 through i2c interface. The device supports multiple sub-devices
535 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
536 Additional drivers must be enabled in order to use the
537 different functionality of the device.
540 bool "SAMSUNG Electronics PMIC Series Support"
546 Support for the Samsung Electronics MFD series.
547 This driver provides common support for accessing the device,
548 additional drivers must be enabled in order to use the functionality
551 config MFD_SI476X_CORE
552 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
557 This is the core driver for the SI476x series of AM/FM
558 radio. This MFD driver connects the radio-si476x V4L2 module
559 and the si476x audio codec.
561 To compile this driver as a module, choose M here: the
562 module will be called si476x-core.
565 tristate "Silicon Motion SM501"
567 This is the core driver for the Silicon Motion SM501 multimedia
568 companion chip. This device is a multifunction device which may
569 provide numerous interfaces including USB host controller, USB gadget,
570 asynchronous serial ports, audio functions, and a dual display video
571 interface. The device may be connected by PCI or local bus with
572 varying functions enabled.
574 config MFD_SM501_GPIO
575 bool "Export GPIO via GPIO layer"
576 depends on MFD_SM501 && GPIOLIB
578 This option uses the gpio library layer to export the 64 GPIO
579 lines on the SM501. The platform data is used to supply the
580 base number for the first GPIO line to register.
583 bool "SMSC ECE1099 series chips"
588 If you say yes here you get support for the
589 ece1099 chips from SMSC.
591 To compile this driver as a module, choose M here: the
592 module will be called smsc.
595 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
596 default y if ARCH_U300 || ARCH_U8500
598 Say yes here if you have the ABX500 Mixed Signal IC family
599 chips. This core driver expose register access functions.
600 Functionality specific drivers using these functions can
601 remain unchanged when IC changes. Binding of the functions to
602 actual register access is done by the IC core driver.
605 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
606 depends on I2C=y && ABX500_CORE
608 default y if ARCH_U300
610 Select this to enable the AB3100 Mixed Signal IC core
611 functionality. This connects to a AB3100 on the I2C bus
612 and expose a number of symbols needed for dependent devices
613 to read and write registers and subscribe to events from
614 this multi-functional IC. This is needed to use other features
615 of the AB3100 such as battery-backed RTC, charging control,
616 LEDs, vibrator, system power and temperature, power management
620 tristate "ST-Ericsson AB3100 OTP functions"
621 depends on AB3100_CORE
622 default y if AB3100_CORE
624 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
625 programmable memory) support. This exposes a sysfs file to read
629 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
630 depends on ABX500_CORE && MFD_DB8500_PRCMU
635 Select this option to enable access to AB8500 power management
636 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
637 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
638 the irq_chip parts for handling the Mixed Signal chip events.
639 This chip embeds various other multimedia funtionalities as well.
642 bool "Enable debug info via debugfs"
643 depends on AB8500_GPADC && DEBUG_FS
644 default y if DEBUG_FS
646 Select this option if you want debug information using the debug
650 bool "ST-Ericsson AB8500 GPADC driver"
651 depends on AB8500_CORE && REGULATOR_AB8500
654 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
656 config MFD_DB8500_PRCMU
657 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
658 depends on UX500_SOC_DB8500
661 Select this option to enable support for the DB8500 Power Reset
662 and Control Management Unit. This is basically an autonomous
663 system controller running an XP70 microprocessor, which is accessed
664 through a register map.
667 bool "STMicroelectronics STMPE"
668 depends on (I2C=y || SPI_MASTER=y)
671 Support for the STMPE family of I/O Expanders from
674 Currently supported devices are:
676 STMPE811: GPIO, Touchscreen
677 STMPE1601: GPIO, Keypad
678 STMPE1801: GPIO, Keypad
679 STMPE2401: GPIO, Keypad
680 STMPE2403: GPIO, Keypad
682 This driver provides common support for accessing the device,
683 additional drivers must be enabled in order to use the functionality
684 of the device. Currently available sub drivers are:
688 Touchscreen: stmpe-ts
690 menu "STMicroelectronics STMPE Interface Drivers"
694 bool "STMicroelectronics STMPE I2C Interface"
698 This is used to enable I2C interface of STMPE
701 bool "STMicroelectronics STMPE SPI Interface"
702 depends on SPI_MASTER
704 This is used to enable SPI interface of STMPE
708 bool "STMicroelectronics STA2X11"
714 bool "System Controller Register R/W Based on Regmap"
717 Select this option to enable accessing system control registers
720 config MFD_DAVINCI_VOICECODEC
724 config MFD_TI_AM335X_TSCADC
725 tristate "TI ADC / Touch Screen chip support"
730 If you say yes here you get support for Texas Instruments series
731 of Touch Screen /ADC chips.
732 To compile this driver as a module, choose M here: the
733 module will be called ti_am335x_tscadc.
735 config MFD_DM355EVM_MSP
736 bool "TI DaVinci DM355 EVM microcontroller"
737 depends on I2C=y && MACH_DAVINCI_DM355_EVM
739 This driver supports the MSP430 microcontroller used on these
740 boards. MSP430 firmware manages resets and power sequencing,
741 inputs from buttons and the IR remote, LEDs, an RTC, and more.
744 tristate "TI/National Semiconductor LP3943 MFD Driver"
749 Support for the TI/National Semiconductor LP3943.
750 This driver consists of GPIO and PWM drivers.
751 With these functionalities, it can be used for LED string control or
752 general usage such like a GPIO controller and a PWM controller.
755 bool "TI LP8788 Power Management Unit Driver"
761 TI LP8788 PMU supports regulators, battery charger, RTC,
762 ADC, backlight driver and current sinks.
764 config MFD_OMAP_USB_HOST
765 bool "TI OMAP USBHS core and TLL driver"
766 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
769 This is the core driver for the OAMP EHCI and OHCI drivers.
770 This MFD driver does the required setup functionalities for
771 OMAP USB Host drivers.
774 bool "TI Palmas series chips"
780 If you say yes here you get support for the Palmas
781 series of PMIC chips from Texas Instruments.
784 tristate "TI Sequencer Serial Port support"
785 depends on ARCH_DAVINCI_TNETV107X
788 Say Y here if you want support for the Sequencer Serial Port
789 in a Texas Instruments TNETV107X SoC.
791 To compile this driver as a module, choose M here: the
792 module will be called ti-ssp.
795 tristate "TI TPS61050/61052 Boost Converters"
799 select REGULATOR_FIXED_VOLTAGE
801 This option enables a driver for the TP61050/TPS61052
802 high-power "white LED driver". This boost converter is
803 sometimes used for other things than white LEDs, and
804 also contains a GPIO pin.
807 tristate "TI TPS6501x Power Management chips"
808 depends on I2C && GPIOLIB
809 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
811 If you say yes here you get support for the TPS6501x series of
812 Power Management chips. These include voltage regulators,
813 lithium ion/polymer battery charging, and other features that
814 are often used in portable devices like cell phones and cameras.
816 This driver can also be built as a module. If so, the module
817 will be called tps65010.
820 tristate "TI TPS6507x Power Management / Touch Screen chips"
824 If you say yes here you get support for the TPS6507x series of
825 Power Management / Touch Screen chips. These include voltage
826 regulators, lithium ion/polymer battery charging, touch screen
827 and other features that are often used in portable devices.
828 This driver can also be built as a module. If so, the module
829 will be called tps6507x.
831 config TPS65911_COMPARATOR
835 bool "TI TPS65090 Power Management chips"
841 If you say yes here you get support for the TPS65090 series of
842 Power Management chips.
843 This driver provides common support for accessing the device,
844 additional drivers must be enabled in order to use the
845 functionality of the device.
848 tristate "TI TPS65217 Power Management / White LED chips"
853 If you say yes here you get support for the TPS65217 series of
854 Power Management / White LED chips.
855 These include voltage regulators, lithium ion/polymer battery
856 charger, wled and other features that are often used in portable
859 This driver can also be built as a module. If so, the module
860 will be called tps65217.
863 tristate "TI TPS65218 Power Management chips"
869 If you say yes here you get support for the TPS65218 series of
870 Power Management chips.
871 These include voltage regulators, gpio and other features
872 that are often used in portable devices. Only regulator
873 component is currently supported.
875 This driver can also be built as a module. If so, the module
876 will be called tps65218.
879 bool "TI TPS6586x Power Management chips"
884 If you say yes here you get support for the TPS6586X series of
885 Power Management chips.
886 This driver provides common support for accessing the device,
887 additional drivers must be enabled in order to use the
888 functionality of the device.
890 This driver can also be built as a module. If so, the module
891 will be called tps6586x.
894 bool "TI TPS65910 Power Management chip"
895 depends on I2C=y && GPIOLIB
901 if you say yes here you get support for the TPS65910 series of
902 Power Management chips.
905 bool "TI TPS65912 Power Management chip"
909 If you say yes here you get support for the TPS65912 series of
912 config MFD_TPS65912_I2C
913 bool "TI TPS65912 Power Management chip with I2C"
916 depends on I2C=y && GPIOLIB
918 If you say yes here you get support for the TPS65912 series of
919 PM chips with I2C interface.
921 config MFD_TPS65912_SPI
922 bool "TI TPS65912 Power Management chip with SPI"
925 depends on SPI_MASTER && GPIOLIB
927 If you say yes here you get support for the TPS65912 series of
928 PM chips with SPI interface.
931 bool "TI TPS80031/TPS80032 Power Management chips"
937 If you say yes here you get support for the Texas Instruments
938 TPS80031/ TPS80032 Fully Integrated Power Management with Power
939 Path and Battery Charger. The device provides five configurable
940 step-down converters, 11 general purpose LDOs, USB OTG Module,
941 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
942 Power Path from USB, 32K clock generator.
945 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
950 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
951 This core driver provides register access and IRQ handling
952 facilities, and registers devices for the various functions
953 so that function-specific drivers can bind to them.
955 These multi-function chips are found on many OMAP2 and OMAP3
956 boards, providing power management, RTC, GPIO, keypad, a
957 high speed USB OTG transceiver, an audio codec (on most
958 versions) and many other features.
961 bool "TI TWL4030 power resources"
962 depends on TWL4030_CORE && ARM
964 Say yes here if you want to use the power resources on the
965 TWL4030 family chips. Most of these resources are regulators,
966 which have a separate driver; some are control signals, such
967 as clock request handshaking.
969 This driver uses board-specific data to initialize the resources
970 and load scripts controlling which resources are switched off/on
971 or reset when a sleep, wakeup or warm reset event occurs.
973 config MFD_TWL4030_AUDIO
974 bool "TI TWL4030 Audio"
975 depends on TWL4030_CORE
980 bool "TI TWL6040 audio codec"
987 Say yes here if you want support for Texas Instruments TWL6040 audio
989 This driver provides common support for accessing the device,
990 additional drivers must be enabled in order to use the
991 functionality of the device (audio, vibra).
994 bool "TI TWL92330/Menelaus PM chip"
995 depends on I2C=y && ARCH_OMAP2
997 If you say yes here you get support for the Texas Instruments
998 TWL92330/Menelaus Power Management chip. This include voltage
999 regulators, Dual slot memory card transceivers, real-time clock
1000 and other features that are often used in portable devices like
1001 cell phones and PDAs.
1003 config MFD_WL1273_CORE
1004 tristate "TI WL1273 FM radio"
1009 This is the core driver for the TI WL1273 FM radio. This MFD
1010 driver connects the radio-wl1273 V4L2 module and the wl1273
1014 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1019 Say yes here to enable support for National Semiconductor / TI
1020 LM3533 Lighting Power chips.
1022 This driver provides common support for accessing the device;
1023 additional drivers must be enabled in order to use the LED,
1024 backlight or ambient-light-sensor functionality of the device.
1026 config MFD_TIMBERDALE
1027 tristate "Timberdale FPGA"
1029 depends on PCI && GPIOLIB
1031 This is the core driver for the timberdale FPGA. This device is a
1032 multifunction device which exposes numerous platform devices.
1034 The timberdale FPGA can be found on the Intel Atom development board
1035 for in-vehicle infontainment, called Russellville.
1038 bool "Toshiba TC35892 and variants"
1042 Support for the Toshiba TC35892 and variants I/O Expander.
1044 This driver provides common support for accessing the device,
1045 additional drivers must be enabled in order to use the
1046 functionality of the device.
1053 bool "Toshiba T7L66XB"
1054 depends on ARM && HAVE_CLK
1058 Support for Toshiba Mobile IO Controller T7L66XB
1061 bool "Toshiba TC6387XB"
1062 depends on ARM && HAVE_CLK
1066 Support for Toshiba Mobile IO Controller TC6387XB
1069 bool "Toshiba TC6393XB"
1070 depends on ARM && HAVE_CLK
1075 Support for Toshiba Mobile IO Controller TC6393XB
1078 tristate "VIA VX855/VX875 integrated south bridge"
1082 Say yes here to enable support for various functions of the
1083 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1084 and/or vx855_gpio drivers for this to do anything useful.
1092 config MFD_ARIZONA_I2C
1093 tristate "Wolfson Microelectronics Arizona platform with I2C"
1099 Support for the Wolfson Microelectronics Arizona platform audio SoC
1100 core functionality controlled via I2C.
1102 config MFD_ARIZONA_SPI
1103 tristate "Wolfson Microelectronics Arizona platform with SPI"
1107 depends on SPI_MASTER
1109 Support for the Wolfson Microelectronics Arizona platform audio SoC
1110 core functionality controlled via I2C.
1113 bool "Wolfson Microelectronics WM5102"
1114 depends on MFD_ARIZONA
1116 Support for Wolfson Microelectronics WM5102 low power audio SoC
1119 bool "Wolfson Microelectronics WM5110"
1120 depends on MFD_ARIZONA
1122 Support for Wolfson Microelectronics WM5110 low power audio SoC
1125 bool "Wolfson Microelectronics WM8997"
1126 depends on MFD_ARIZONA
1128 Support for Wolfson Microelectronics WM8997 low power audio SoC
1131 bool "Wolfson Microelectronics WM8400"
1136 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1137 CODEC. This driver provides common support for accessing
1138 the device, additional drivers must be enabled in order to use
1139 the functionality of the device.
1144 config MFD_WM831X_I2C
1145 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1152 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1153 when controlled using I2C. This driver provides common support
1154 for accessing the device, additional drivers must be enabled in
1155 order to use the functionality of the device.
1157 config MFD_WM831X_SPI
1158 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1163 depends on SPI_MASTER
1165 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1166 when controlled using SPI. This driver provides common support
1167 for accessing the device, additional drivers must be enabled in
1168 order to use the functionality of the device.
1173 config MFD_WM8350_I2C
1174 bool "Wolfson Microelectronics WM8350 with I2C"
1178 The WM8350 is an integrated audio and power management
1179 subsystem with watchdog and RTC functionality for embedded
1180 systems. This option enables core support for the WM8350 with
1181 I2C as the control interface. Additional options must be
1182 selected to enable support for the functionality of the chip.
1185 bool "Wolfson Microelectronics WM8994"
1191 The WM8994 is a highly integrated hi-fi CODEC designed for
1192 smartphone applicatiosn. As well as audio functionality it
1193 has on board GPIO and regulator functionality which is
1194 supported via the relevant subsystems. This driver provides
1195 core support for the WM8994, in order to use the actual
1196 functionaltiy of the device other drivers must be enabled.
1199 bool "Support for ST Microelectronics STw481x"
1200 depends on I2C && ARCH_NOMADIK
1204 Select this option to enable the STw481x chip driver used
1205 in various ST Microelectronics and ST-Ericsson embedded
1208 menu "Multimedia Capabilities Port drivers"
1209 depends on ARCH_SA1100
1216 tristate "Support SA11x0 MCP interface"
1217 depends on ARCH_SA1100
1222 bool "Support for UCB1200 / UCB1300"
1223 depends on MCP_SA11X0
1226 config MCP_UCB1200_TS
1227 tristate "Touchscreen interface support"
1228 depends on MCP_UCB1200 && INPUT
1232 config VEXPRESS_CONFIG
1233 bool "ARM Versatile Express platform infrastructure"
1234 depends on ARM || ARM64
1236 Platform configuration infrastructure for the ARM Ltd.