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"
333 Say yes here to add support for Maxim Semiconductor MAX14577.
334 This is a Micro-USB IC with Charger controls on chip.
335 This driver provides common support for accessing the device;
336 additional drivers must be enabled in order to use the functionality
340 bool "Maxim Semiconductor MAX77686 PMIC Support"
346 Say yes here to add support for Maxim Semiconductor MAX77686.
347 This is a Power Management IC with RTC on chip.
348 This driver provides common support for accessing the device;
349 additional drivers must be enabled in order to use the functionality
353 bool "Maxim Semiconductor MAX77693 PMIC Support"
358 Say yes here to add support for Maxim Semiconductor MAX77693.
359 This is a companion Power Management IC with Flash, Haptic, Charger,
360 and MUIC(Micro USB Interface Controller) controls on chip.
361 This driver provides common support for accessing the device;
362 additional drivers must be enabled in order to use the functionality
366 tristate "Maxim Semiconductor MAX8907 PMIC Support"
372 Say yes here to add support for Maxim Semiconductor MAX8907. This is
373 a Power Management IC. This driver provides common support for
374 accessing the device; additional drivers must be enabled in order
375 to use the functionality of the device.
378 bool "Maxim Semiconductor MAX8925 PMIC Support"
382 Say yes here to add support for Maxim Semiconductor MAX8925. This is
383 a Power Management IC. This driver provides common support for
384 accessing the device, additional drivers must be enabled in order
385 to use the functionality of the device.
388 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
393 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
394 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
395 MUIC controls on chip.
396 This driver provides common support for accessing the device;
397 additional drivers must be enabled in order to use the functionality
401 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
406 Say yes here to add support for Maxim Semiconductor MAX8998 and
407 National Semiconductor LP3974. This is a Power Management IC.
408 This driver provides common support for accessing the device,
409 additional drivers must be enabled in order to use the functionality
413 bool "Motorola EZXPCAP Support"
414 depends on SPI_MASTER
416 This enables the PCAP ASIC present on EZX Phones. This is
417 needed for MMC, TouchScreen, Sound, USB, etc..
419 config MFD_VIPERBOARD
420 tristate "Nano River Technologies Viperboard"
425 Say yes here if you want support for Nano River Technologies
427 There are mfd cell drivers available for i2c master, adc and
428 both gpios found on the board. The spi part does not yet
430 You need to select the mfd cell drivers separately.
431 The drivers do not support all features the board exposes.
434 tristate "Nokia Retu and Tahvo multi-function device"
439 Retu and Tahvo are a multi-function devices found on Nokia
440 Internet Tablets (770, N800 and N810).
443 tristate "NXP PCF50633"
447 Say yes here if you have NXP PCF50633 chip on your board.
448 This core driver provides register access and IRQ handling
449 facilities, and registers devices for the various functions
450 so that function-specific drivers can bind to them.
453 tristate "NXP PCF50633 ADC"
454 depends on MFD_PCF50633
456 Say yes here if you want to include support for ADC in the
460 tristate "NXP PCF50633 GPIO"
461 depends on MFD_PCF50633
463 Say yes here if you want to include support GPIO for pins on
467 tristate "Philips UCB1400 Core driver"
471 This enables support for the Philips UCB1400 core functions.
472 The UCB1400 is an AC97 audio codec.
474 To compile this driver as a module, choose M here: the
475 module will be called ucb1400_core.
480 config MFD_PM8921_CORE
481 tristate "Qualcomm PM8921 PMIC chip"
482 depends on (ARM || HEXAGON)
488 If you say yes to this option, support will be included for the
489 built-in PM8921 PMIC chip.
491 This is required if your board has a PM8921 and uses its features,
492 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
494 Say M here if you want to include support for PM8921 chip as a module.
495 This will build a module called "pm8921-core".
498 tristate "RDC R-321x southbridge"
502 Say yes here if you want to have support for the RDC R-321x SoC
503 southbridge which provides access to GPIOs and Watchdog using the
504 southbridge PCI device configuration space.
507 tristate "Realtek PCI-E card reader"
511 This supports for Realtek PCI-Express card reader including rts5209,
512 rts5229, rtl8411, etc. Realtek card reader supports access to many
513 types of memory cards, such as Memory Stick, Memory Stick Pro,
514 Secure Digital and MultiMediaCard.
517 tristate "Realtek USB card reader"
521 Select this option to get support for Realtek USB 2.0 card readers
522 including RTS5129, RTS5139, RTS5179 and RTS5170.
523 Realtek card reader supports access to many types of memory cards,
524 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
527 bool "Ricoh RC5T583 Power Management system device"
532 Select this option to get support for the RICOH583 Power
533 Management system device.
534 This driver provides common support for accessing the device
535 through i2c interface. The device supports multiple sub-devices
536 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
537 Additional drivers must be enabled in order to use the
538 different functionality of the device.
541 bool "SAMSUNG Electronics PMIC Series Support"
547 Support for the Samsung Electronics MFD series.
548 This driver provides common support for accessing the device,
549 additional drivers must be enabled in order to use the functionality
552 config MFD_SI476X_CORE
553 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
558 This is the core driver for the SI476x series of AM/FM
559 radio. This MFD driver connects the radio-si476x V4L2 module
560 and the si476x audio codec.
562 To compile this driver as a module, choose M here: the
563 module will be called si476x-core.
566 tristate "Silicon Motion SM501"
568 This is the core driver for the Silicon Motion SM501 multimedia
569 companion chip. This device is a multifunction device which may
570 provide numerous interfaces including USB host controller, USB gadget,
571 asynchronous serial ports, audio functions, and a dual display video
572 interface. The device may be connected by PCI or local bus with
573 varying functions enabled.
575 config MFD_SM501_GPIO
576 bool "Export GPIO via GPIO layer"
577 depends on MFD_SM501 && GPIOLIB
579 This option uses the gpio library layer to export the 64 GPIO
580 lines on the SM501. The platform data is used to supply the
581 base number for the first GPIO line to register.
584 bool "SMSC ECE1099 series chips"
589 If you say yes here you get support for the
590 ece1099 chips from SMSC.
592 To compile this driver as a module, choose M here: the
593 module will be called smsc.
596 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
597 default y if ARCH_U300 || ARCH_U8500
599 Say yes here if you have the ABX500 Mixed Signal IC family
600 chips. This core driver expose register access functions.
601 Functionality specific drivers using these functions can
602 remain unchanged when IC changes. Binding of the functions to
603 actual register access is done by the IC core driver.
606 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
607 depends on I2C=y && ABX500_CORE
609 default y if ARCH_U300
611 Select this to enable the AB3100 Mixed Signal IC core
612 functionality. This connects to a AB3100 on the I2C bus
613 and expose a number of symbols needed for dependent devices
614 to read and write registers and subscribe to events from
615 this multi-functional IC. This is needed to use other features
616 of the AB3100 such as battery-backed RTC, charging control,
617 LEDs, vibrator, system power and temperature, power management
621 tristate "ST-Ericsson AB3100 OTP functions"
622 depends on AB3100_CORE
623 default y if AB3100_CORE
625 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
626 programmable memory) support. This exposes a sysfs file to read
630 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
631 depends on ABX500_CORE && MFD_DB8500_PRCMU
636 Select this option to enable access to AB8500 power management
637 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
638 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
639 the irq_chip parts for handling the Mixed Signal chip events.
640 This chip embeds various other multimedia funtionalities as well.
643 bool "Enable debug info via debugfs"
644 depends on AB8500_GPADC && DEBUG_FS
645 default y if DEBUG_FS
647 Select this option if you want debug information using the debug
651 bool "ST-Ericsson AB8500 GPADC driver"
652 depends on AB8500_CORE && REGULATOR_AB8500
655 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
657 config MFD_DB8500_PRCMU
658 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
659 depends on UX500_SOC_DB8500
662 Select this option to enable support for the DB8500 Power Reset
663 and Control Management Unit. This is basically an autonomous
664 system controller running an XP70 microprocessor, which is accessed
665 through a register map.
668 bool "STMicroelectronics STMPE"
669 depends on (I2C=y || SPI_MASTER=y)
672 Support for the STMPE family of I/O Expanders from
675 Currently supported devices are:
677 STMPE811: GPIO, Touchscreen
678 STMPE1601: GPIO, Keypad
679 STMPE1801: GPIO, Keypad
680 STMPE2401: GPIO, Keypad
681 STMPE2403: GPIO, Keypad
683 This driver provides common support for accessing the device,
684 additional drivers must be enabled in order to use the functionality
685 of the device. Currently available sub drivers are:
689 Touchscreen: stmpe-ts
691 menu "STMicroelectronics STMPE Interface Drivers"
695 bool "STMicroelectronics STMPE I2C Interface"
699 This is used to enable I2C interface of STMPE
702 bool "STMicroelectronics STMPE SPI Interface"
703 depends on SPI_MASTER
705 This is used to enable SPI interface of STMPE
709 bool "STMicroelectronics STA2X11"
715 bool "System Controller Register R/W Based on Regmap"
718 Select this option to enable accessing system control registers
721 config MFD_DAVINCI_VOICECODEC
725 config MFD_TI_AM335X_TSCADC
726 tristate "TI ADC / Touch Screen chip support"
731 If you say yes here you get support for Texas Instruments series
732 of Touch Screen /ADC chips.
733 To compile this driver as a module, choose M here: the
734 module will be called ti_am335x_tscadc.
736 config MFD_DM355EVM_MSP
737 bool "TI DaVinci DM355 EVM microcontroller"
738 depends on I2C=y && MACH_DAVINCI_DM355_EVM
740 This driver supports the MSP430 microcontroller used on these
741 boards. MSP430 firmware manages resets and power sequencing,
742 inputs from buttons and the IR remote, LEDs, an RTC, and more.
745 tristate "TI/National Semiconductor LP3943 MFD Driver"
750 Support for the TI/National Semiconductor LP3943.
751 This driver consists of GPIO and PWM drivers.
752 With these functionalities, it can be used for LED string control or
753 general usage such like a GPIO controller and a PWM controller.
756 bool "TI LP8788 Power Management Unit Driver"
762 TI LP8788 PMU supports regulators, battery charger, RTC,
763 ADC, backlight driver and current sinks.
765 config MFD_OMAP_USB_HOST
766 bool "TI OMAP USBHS core and TLL driver"
767 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
770 This is the core driver for the OAMP EHCI and OHCI drivers.
771 This MFD driver does the required setup functionalities for
772 OMAP USB Host drivers.
775 bool "TI Palmas series chips"
781 If you say yes here you get support for the Palmas
782 series of PMIC chips from Texas Instruments.
785 tristate "TI Sequencer Serial Port support"
786 depends on ARCH_DAVINCI_TNETV107X
789 Say Y here if you want support for the Sequencer Serial Port
790 in a Texas Instruments TNETV107X SoC.
792 To compile this driver as a module, choose M here: the
793 module will be called ti-ssp.
796 tristate "TI TPS61050/61052 Boost Converters"
800 select REGULATOR_FIXED_VOLTAGE
802 This option enables a driver for the TP61050/TPS61052
803 high-power "white LED driver". This boost converter is
804 sometimes used for other things than white LEDs, and
805 also contains a GPIO pin.
808 tristate "TI TPS6501x Power Management chips"
809 depends on I2C && GPIOLIB
810 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
812 If you say yes here you get support for the TPS6501x series of
813 Power Management chips. These include voltage regulators,
814 lithium ion/polymer battery charging, and other features that
815 are often used in portable devices like cell phones and cameras.
817 This driver can also be built as a module. If so, the module
818 will be called tps65010.
821 tristate "TI TPS6507x Power Management / Touch Screen chips"
825 If you say yes here you get support for the TPS6507x series of
826 Power Management / Touch Screen chips. These include voltage
827 regulators, lithium ion/polymer battery charging, touch screen
828 and other features that are often used in portable devices.
829 This driver can also be built as a module. If so, the module
830 will be called tps6507x.
832 config TPS65911_COMPARATOR
836 bool "TI TPS65090 Power Management chips"
842 If you say yes here you get support for the TPS65090 series of
843 Power Management chips.
844 This driver provides common support for accessing the device,
845 additional drivers must be enabled in order to use the
846 functionality of the device.
849 tristate "TI TPS65217 Power Management / White LED chips"
854 If you say yes here you get support for the TPS65217 series of
855 Power Management / White LED chips.
856 These include voltage regulators, lithium ion/polymer battery
857 charger, wled and other features that are often used in portable
860 This driver can also be built as a module. If so, the module
861 will be called tps65217.
864 tristate "TI TPS65218 Power Management chips"
870 If you say yes here you get support for the TPS65218 series of
871 Power Management chips.
872 These include voltage regulators, gpio and other features
873 that are often used in portable devices. Only regulator
874 component is currently supported.
876 This driver can also be built as a module. If so, the module
877 will be called tps65218.
880 bool "TI TPS6586x Power Management chips"
885 If you say yes here you get support for the TPS6586X series of
886 Power Management chips.
887 This driver provides common support for accessing the device,
888 additional drivers must be enabled in order to use the
889 functionality of the device.
891 This driver can also be built as a module. If so, the module
892 will be called tps6586x.
895 bool "TI TPS65910 Power Management chip"
896 depends on I2C=y && GPIOLIB
902 if you say yes here you get support for the TPS65910 series of
903 Power Management chips.
906 bool "TI TPS65912 Power Management chip"
910 If you say yes here you get support for the TPS65912 series of
913 config MFD_TPS65912_I2C
914 bool "TI TPS65912 Power Management chip with I2C"
917 depends on I2C=y && GPIOLIB
919 If you say yes here you get support for the TPS65912 series of
920 PM chips with I2C interface.
922 config MFD_TPS65912_SPI
923 bool "TI TPS65912 Power Management chip with SPI"
926 depends on SPI_MASTER && GPIOLIB
928 If you say yes here you get support for the TPS65912 series of
929 PM chips with SPI interface.
932 bool "TI TPS80031/TPS80032 Power Management chips"
938 If you say yes here you get support for the Texas Instruments
939 TPS80031/ TPS80032 Fully Integrated Power Management with Power
940 Path and Battery Charger. The device provides five configurable
941 step-down converters, 11 general purpose LDOs, USB OTG Module,
942 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
943 Power Path from USB, 32K clock generator.
946 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
951 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
952 This core driver provides register access and IRQ handling
953 facilities, and registers devices for the various functions
954 so that function-specific drivers can bind to them.
956 These multi-function chips are found on many OMAP2 and OMAP3
957 boards, providing power management, RTC, GPIO, keypad, a
958 high speed USB OTG transceiver, an audio codec (on most
959 versions) and many other features.
962 bool "TI TWL4030 power resources"
963 depends on TWL4030_CORE && ARM
965 Say yes here if you want to use the power resources on the
966 TWL4030 family chips. Most of these resources are regulators,
967 which have a separate driver; some are control signals, such
968 as clock request handshaking.
970 This driver uses board-specific data to initialize the resources
971 and load scripts controlling which resources are switched off/on
972 or reset when a sleep, wakeup or warm reset event occurs.
974 config MFD_TWL4030_AUDIO
975 bool "TI TWL4030 Audio"
976 depends on TWL4030_CORE
981 bool "TI TWL6040 audio codec"
988 Say yes here if you want support for Texas Instruments TWL6040 audio
990 This driver provides common support for accessing the device,
991 additional drivers must be enabled in order to use the
992 functionality of the device (audio, vibra).
995 bool "TI TWL92330/Menelaus PM chip"
996 depends on I2C=y && ARCH_OMAP2
998 If you say yes here you get support for the Texas Instruments
999 TWL92330/Menelaus Power Management chip. This include voltage
1000 regulators, Dual slot memory card transceivers, real-time clock
1001 and other features that are often used in portable devices like
1002 cell phones and PDAs.
1004 config MFD_WL1273_CORE
1005 tristate "TI WL1273 FM radio"
1010 This is the core driver for the TI WL1273 FM radio. This MFD
1011 driver connects the radio-wl1273 V4L2 module and the wl1273
1015 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1020 Say yes here to enable support for National Semiconductor / TI
1021 LM3533 Lighting Power chips.
1023 This driver provides common support for accessing the device;
1024 additional drivers must be enabled in order to use the LED,
1025 backlight or ambient-light-sensor functionality of the device.
1027 config MFD_TIMBERDALE
1028 tristate "Timberdale FPGA"
1030 depends on PCI && GPIOLIB
1032 This is the core driver for the timberdale FPGA. This device is a
1033 multifunction device which exposes numerous platform devices.
1035 The timberdale FPGA can be found on the Intel Atom development board
1036 for in-vehicle infontainment, called Russellville.
1039 bool "Toshiba TC35892 and variants"
1043 Support for the Toshiba TC35892 and variants I/O Expander.
1045 This driver provides common support for accessing the device,
1046 additional drivers must be enabled in order to use the
1047 functionality of the device.
1054 bool "Toshiba T7L66XB"
1055 depends on ARM && HAVE_CLK
1059 Support for Toshiba Mobile IO Controller T7L66XB
1062 bool "Toshiba TC6387XB"
1063 depends on ARM && HAVE_CLK
1067 Support for Toshiba Mobile IO Controller TC6387XB
1070 bool "Toshiba TC6393XB"
1071 depends on ARM && HAVE_CLK
1076 Support for Toshiba Mobile IO Controller TC6393XB
1079 tristate "VIA VX855/VX875 integrated south bridge"
1083 Say yes here to enable support for various functions of the
1084 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1085 and/or vx855_gpio drivers for this to do anything useful.
1093 config MFD_ARIZONA_I2C
1094 tristate "Wolfson Microelectronics Arizona platform with I2C"
1100 Support for the Wolfson Microelectronics Arizona platform audio SoC
1101 core functionality controlled via I2C.
1103 config MFD_ARIZONA_SPI
1104 tristate "Wolfson Microelectronics Arizona platform with SPI"
1108 depends on SPI_MASTER
1110 Support for the Wolfson Microelectronics Arizona platform audio SoC
1111 core functionality controlled via I2C.
1114 bool "Wolfson Microelectronics WM5102"
1115 depends on MFD_ARIZONA
1117 Support for Wolfson Microelectronics WM5102 low power audio SoC
1120 bool "Wolfson Microelectronics WM5110"
1121 depends on MFD_ARIZONA
1123 Support for Wolfson Microelectronics WM5110 low power audio SoC
1126 bool "Wolfson Microelectronics WM8997"
1127 depends on MFD_ARIZONA
1129 Support for Wolfson Microelectronics WM8997 low power audio SoC
1132 bool "Wolfson Microelectronics WM8400"
1137 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1138 CODEC. This driver provides common support for accessing
1139 the device, additional drivers must be enabled in order to use
1140 the functionality of the device.
1145 config MFD_WM831X_I2C
1146 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1153 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1154 when controlled using I2C. 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.
1158 config MFD_WM831X_SPI
1159 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1164 depends on SPI_MASTER
1166 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1167 when controlled using SPI. This driver provides common support
1168 for accessing the device, additional drivers must be enabled in
1169 order to use the functionality of the device.
1174 config MFD_WM8350_I2C
1175 bool "Wolfson Microelectronics WM8350 with I2C"
1179 The WM8350 is an integrated audio and power management
1180 subsystem with watchdog and RTC functionality for embedded
1181 systems. This option enables core support for the WM8350 with
1182 I2C as the control interface. Additional options must be
1183 selected to enable support for the functionality of the chip.
1186 bool "Wolfson Microelectronics WM8994"
1192 The WM8994 is a highly integrated hi-fi CODEC designed for
1193 smartphone applicatiosn. As well as audio functionality it
1194 has on board GPIO and regulator functionality which is
1195 supported via the relevant subsystems. This driver provides
1196 core support for the WM8994, in order to use the actual
1197 functionaltiy of the device other drivers must be enabled.
1200 bool "Support for ST Microelectronics STw481x"
1201 depends on I2C && ARCH_NOMADIK
1205 Select this option to enable the STw481x chip driver used
1206 in various ST Microelectronics and ST-Ericsson embedded
1209 menu "Multimedia Capabilities Port drivers"
1210 depends on ARCH_SA1100
1217 tristate "Support SA11x0 MCP interface"
1218 depends on ARCH_SA1100
1223 bool "Support for UCB1200 / UCB1300"
1224 depends on MCP_SA11X0
1227 config MCP_UCB1200_TS
1228 tristate "Touchscreen interface support"
1229 depends on MCP_UCB1200 && INPUT
1233 config VEXPRESS_CONFIG
1234 bool "ARM Versatile Express platform infrastructure"
1235 depends on ARM || ARM64
1237 Platform configuration infrastructure for the ARM Ltd.