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 (ARCH_MSM || HEXAGON)
485 If you say yes to this option, support will be included for the
486 built-in PM8921 PMIC chip.
488 This is required if your board has a PM8921 and uses its features,
489 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
491 Say M here if you want to include support for PM8921 chip as a module.
492 This will build a module called "pm8921-core".
495 tristate "RDC R-321x southbridge"
499 Say yes here if you want to have support for the RDC R-321x SoC
500 southbridge which provides access to GPIOs and Watchdog using the
501 southbridge PCI device configuration space.
504 tristate "Realtek PCI-E card reader"
508 This supports for Realtek PCI-Express card reader including rts5209,
509 rts5229, rtl8411, etc. Realtek card reader supports access to many
510 types of memory cards, such as Memory Stick, Memory Stick Pro,
511 Secure Digital and MultiMediaCard.
514 tristate "Realtek USB card reader"
518 Select this option to get support for Realtek USB 2.0 card readers
519 including RTS5129, RTS5139, RTS5179 and RTS5170.
520 Realtek card reader supports access to many types of memory cards,
521 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
524 bool "Ricoh RC5T583 Power Management system device"
529 Select this option to get support for the RICOH583 Power
530 Management system device.
531 This driver provides common support for accessing the device
532 through i2c interface. The device supports multiple sub-devices
533 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
534 Additional drivers must be enabled in order to use the
535 different functionality of the device.
538 bool "SAMSUNG Electronics PMIC Series Support"
544 Support for the Samsung Electronics MFD series.
545 This driver provides common support for accessing the device,
546 additional drivers must be enabled in order to use the functionality
549 config MFD_SI476X_CORE
550 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
555 This is the core driver for the SI476x series of AM/FM
556 radio. This MFD driver connects the radio-si476x V4L2 module
557 and the si476x audio codec.
559 To compile this driver as a module, choose M here: the
560 module will be called si476x-core.
563 tristate "Silicon Motion SM501"
565 This is the core driver for the Silicon Motion SM501 multimedia
566 companion chip. This device is a multifunction device which may
567 provide numerous interfaces including USB host controller, USB gadget,
568 asynchronous serial ports, audio functions, and a dual display video
569 interface. The device may be connected by PCI or local bus with
570 varying functions enabled.
572 config MFD_SM501_GPIO
573 bool "Export GPIO via GPIO layer"
574 depends on MFD_SM501 && GPIOLIB
576 This option uses the gpio library layer to export the 64 GPIO
577 lines on the SM501. The platform data is used to supply the
578 base number for the first GPIO line to register.
581 bool "SMSC ECE1099 series chips"
586 If you say yes here you get support for the
587 ece1099 chips from SMSC.
589 To compile this driver as a module, choose M here: the
590 module will be called smsc.
593 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
594 default y if ARCH_U300 || ARCH_U8500
596 Say yes here if you have the ABX500 Mixed Signal IC family
597 chips. This core driver expose register access functions.
598 Functionality specific drivers using these functions can
599 remain unchanged when IC changes. Binding of the functions to
600 actual register access is done by the IC core driver.
603 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
604 depends on I2C=y && ABX500_CORE
606 default y if ARCH_U300
608 Select this to enable the AB3100 Mixed Signal IC core
609 functionality. This connects to a AB3100 on the I2C bus
610 and expose a number of symbols needed for dependent devices
611 to read and write registers and subscribe to events from
612 this multi-functional IC. This is needed to use other features
613 of the AB3100 such as battery-backed RTC, charging control,
614 LEDs, vibrator, system power and temperature, power management
618 tristate "ST-Ericsson AB3100 OTP functions"
619 depends on AB3100_CORE
620 default y if AB3100_CORE
622 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
623 programmable memory) support. This exposes a sysfs file to read
627 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
628 depends on ABX500_CORE && MFD_DB8500_PRCMU
633 Select this option to enable access to AB8500 power management
634 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
635 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
636 the irq_chip parts for handling the Mixed Signal chip events.
637 This chip embeds various other multimedia funtionalities as well.
640 bool "Enable debug info via debugfs"
641 depends on AB8500_GPADC && DEBUG_FS
642 default y if DEBUG_FS
644 Select this option if you want debug information using the debug
648 bool "ST-Ericsson AB8500 GPADC driver"
649 depends on AB8500_CORE && REGULATOR_AB8500
652 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
654 config MFD_DB8500_PRCMU
655 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
656 depends on UX500_SOC_DB8500
659 Select this option to enable support for the DB8500 Power Reset
660 and Control Management Unit. This is basically an autonomous
661 system controller running an XP70 microprocessor, which is accessed
662 through a register map.
665 bool "STMicroelectronics STMPE"
666 depends on (I2C=y || SPI_MASTER=y)
669 Support for the STMPE family of I/O Expanders from
672 Currently supported devices are:
674 STMPE811: GPIO, Touchscreen
675 STMPE1601: GPIO, Keypad
676 STMPE1801: GPIO, Keypad
677 STMPE2401: GPIO, Keypad
678 STMPE2403: GPIO, Keypad
680 This driver provides common support for accessing the device,
681 additional drivers must be enabled in order to use the functionality
682 of the device. Currently available sub drivers are:
686 Touchscreen: stmpe-ts
688 menu "STMicroelectronics STMPE Interface Drivers"
692 bool "STMicroelectronics STMPE I2C Interface"
696 This is used to enable I2C interface of STMPE
699 bool "STMicroelectronics STMPE SPI Interface"
700 depends on SPI_MASTER
702 This is used to enable SPI interface of STMPE
706 bool "STMicroelectronics STA2X11"
712 bool "System Controller Register R/W Based on Regmap"
715 Select this option to enable accessing system control registers
718 config MFD_DAVINCI_VOICECODEC
722 config MFD_TI_AM335X_TSCADC
723 tristate "TI ADC / Touch Screen chip support"
728 If you say yes here you get support for Texas Instruments series
729 of Touch Screen /ADC chips.
730 To compile this driver as a module, choose M here: the
731 module will be called ti_am335x_tscadc.
733 config MFD_DM355EVM_MSP
734 bool "TI DaVinci DM355 EVM microcontroller"
735 depends on I2C=y && MACH_DAVINCI_DM355_EVM
737 This driver supports the MSP430 microcontroller used on these
738 boards. MSP430 firmware manages resets and power sequencing,
739 inputs from buttons and the IR remote, LEDs, an RTC, and more.
742 tristate "TI/National Semiconductor LP3943 MFD Driver"
747 Support for the TI/National Semiconductor LP3943.
748 This driver consists of GPIO and PWM drivers.
749 With these functionalities, it can be used for LED string control or
750 general usage such like a GPIO controller and a PWM controller.
753 bool "TI LP8788 Power Management Unit Driver"
759 TI LP8788 PMU supports regulators, battery charger, RTC,
760 ADC, backlight driver and current sinks.
762 config MFD_OMAP_USB_HOST
763 bool "TI OMAP USBHS core and TLL driver"
764 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
767 This is the core driver for the OAMP EHCI and OHCI drivers.
768 This MFD driver does the required setup functionalities for
769 OMAP USB Host drivers.
772 bool "TI Palmas series chips"
778 If you say yes here you get support for the Palmas
779 series of PMIC chips from Texas Instruments.
782 tristate "TI Sequencer Serial Port support"
783 depends on ARCH_DAVINCI_TNETV107X
786 Say Y here if you want support for the Sequencer Serial Port
787 in a Texas Instruments TNETV107X SoC.
789 To compile this driver as a module, choose M here: the
790 module will be called ti-ssp.
793 tristate "TI TPS61050/61052 Boost Converters"
797 select REGULATOR_FIXED_VOLTAGE
799 This option enables a driver for the TP61050/TPS61052
800 high-power "white LED driver". This boost converter is
801 sometimes used for other things than white LEDs, and
802 also contains a GPIO pin.
805 tristate "TI TPS6501x Power Management chips"
806 depends on I2C && GPIOLIB
807 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
809 If you say yes here you get support for the TPS6501x series of
810 Power Management chips. These include voltage regulators,
811 lithium ion/polymer battery charging, and other features that
812 are often used in portable devices like cell phones and cameras.
814 This driver can also be built as a module. If so, the module
815 will be called tps65010.
818 tristate "TI TPS6507x Power Management / Touch Screen chips"
822 If you say yes here you get support for the TPS6507x series of
823 Power Management / Touch Screen chips. These include voltage
824 regulators, lithium ion/polymer battery charging, touch screen
825 and other features that are often used in portable devices.
826 This driver can also be built as a module. If so, the module
827 will be called tps6507x.
829 config TPS65911_COMPARATOR
833 bool "TI TPS65090 Power Management chips"
839 If you say yes here you get support for the TPS65090 series of
840 Power Management chips.
841 This driver provides common support for accessing the device,
842 additional drivers must be enabled in order to use the
843 functionality of the device.
846 tristate "TI TPS65217 Power Management / White LED chips"
851 If you say yes here you get support for the TPS65217 series of
852 Power Management / White LED chips.
853 These include voltage regulators, lithium ion/polymer battery
854 charger, wled and other features that are often used in portable
857 This driver can also be built as a module. If so, the module
858 will be called tps65217.
861 tristate "TI TPS65218 Power Management chips"
866 If you say yes here you get support for the TPS65218 series of
867 Power Management chips.
868 These include voltage regulators, gpio and other features
869 that are often used in portable devices. Only regulator
870 component is currently supported.
872 This driver can also be built as a module. If so, the module
873 will be called tps65218.
876 bool "TI TPS6586x Power Management chips"
881 If you say yes here you get support for the TPS6586X series of
882 Power Management chips.
883 This driver provides common support for accessing the device,
884 additional drivers must be enabled in order to use the
885 functionality of the device.
887 This driver can also be built as a module. If so, the module
888 will be called tps6586x.
891 bool "TI TPS65910 Power Management chip"
892 depends on I2C=y && GPIOLIB
898 if you say yes here you get support for the TPS65910 series of
899 Power Management chips.
902 bool "TI TPS65912 Power Management chip"
906 If you say yes here you get support for the TPS65912 series of
909 config MFD_TPS65912_I2C
910 bool "TI TPS65912 Power Management chip with I2C"
913 depends on I2C=y && GPIOLIB
915 If you say yes here you get support for the TPS65912 series of
916 PM chips with I2C interface.
918 config MFD_TPS65912_SPI
919 bool "TI TPS65912 Power Management chip with SPI"
922 depends on SPI_MASTER && GPIOLIB
924 If you say yes here you get support for the TPS65912 series of
925 PM chips with SPI interface.
928 bool "TI TPS80031/TPS80032 Power Management chips"
934 If you say yes here you get support for the Texas Instruments
935 TPS80031/ TPS80032 Fully Integrated Power Management with Power
936 Path and Battery Charger. The device provides five configurable
937 step-down converters, 11 general purpose LDOs, USB OTG Module,
938 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
939 Power Path from USB, 32K clock generator.
942 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
947 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
948 This core driver provides register access and IRQ handling
949 facilities, and registers devices for the various functions
950 so that function-specific drivers can bind to them.
952 These multi-function chips are found on many OMAP2 and OMAP3
953 boards, providing power management, RTC, GPIO, keypad, a
954 high speed USB OTG transceiver, an audio codec (on most
955 versions) and many other features.
958 bool "TI TWL4030 power resources"
959 depends on TWL4030_CORE && ARM
961 Say yes here if you want to use the power resources on the
962 TWL4030 family chips. Most of these resources are regulators,
963 which have a separate driver; some are control signals, such
964 as clock request handshaking.
966 This driver uses board-specific data to initialize the resources
967 and load scripts controlling which resources are switched off/on
968 or reset when a sleep, wakeup or warm reset event occurs.
970 config MFD_TWL4030_AUDIO
971 bool "TI TWL4030 Audio"
972 depends on TWL4030_CORE
977 bool "TI TWL6040 audio codec"
984 Say yes here if you want support for Texas Instruments TWL6040 audio
986 This driver provides common support for accessing the device,
987 additional drivers must be enabled in order to use the
988 functionality of the device (audio, vibra).
991 bool "TI TWL92330/Menelaus PM chip"
992 depends on I2C=y && ARCH_OMAP2
994 If you say yes here you get support for the Texas Instruments
995 TWL92330/Menelaus Power Management chip. This include voltage
996 regulators, Dual slot memory card transceivers, real-time clock
997 and other features that are often used in portable devices like
998 cell phones and PDAs.
1000 config MFD_WL1273_CORE
1001 tristate "TI WL1273 FM radio"
1006 This is the core driver for the TI WL1273 FM radio. This MFD
1007 driver connects the radio-wl1273 V4L2 module and the wl1273
1011 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1016 Say yes here to enable support for National Semiconductor / TI
1017 LM3533 Lighting Power chips.
1019 This driver provides common support for accessing the device;
1020 additional drivers must be enabled in order to use the LED,
1021 backlight or ambient-light-sensor functionality of the device.
1023 config MFD_TIMBERDALE
1024 tristate "Timberdale FPGA"
1026 depends on PCI && GPIOLIB
1028 This is the core driver for the timberdale FPGA. This device is a
1029 multifunction device which exposes numerous platform devices.
1031 The timberdale FPGA can be found on the Intel Atom development board
1032 for in-vehicle infontainment, called Russellville.
1035 bool "Toshiba TC35892 and variants"
1039 Support for the Toshiba TC35892 and variants I/O Expander.
1041 This driver provides common support for accessing the device,
1042 additional drivers must be enabled in order to use the
1043 functionality of the device.
1050 bool "Toshiba T7L66XB"
1051 depends on ARM && HAVE_CLK
1055 Support for Toshiba Mobile IO Controller T7L66XB
1058 bool "Toshiba TC6387XB"
1059 depends on ARM && HAVE_CLK
1063 Support for Toshiba Mobile IO Controller TC6387XB
1066 bool "Toshiba TC6393XB"
1067 depends on ARM && HAVE_CLK
1072 Support for Toshiba Mobile IO Controller TC6393XB
1075 tristate "VIA VX855/VX875 integrated south bridge"
1079 Say yes here to enable support for various functions of the
1080 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1081 and/or vx855_gpio drivers for this to do anything useful.
1089 config MFD_ARIZONA_I2C
1090 tristate "Wolfson Microelectronics Arizona platform with I2C"
1096 Support for the Wolfson Microelectronics Arizona platform audio SoC
1097 core functionality controlled via I2C.
1099 config MFD_ARIZONA_SPI
1100 tristate "Wolfson Microelectronics Arizona platform with SPI"
1104 depends on SPI_MASTER
1106 Support for the Wolfson Microelectronics Arizona platform audio SoC
1107 core functionality controlled via I2C.
1110 bool "Wolfson Microelectronics WM5102"
1111 depends on MFD_ARIZONA
1113 Support for Wolfson Microelectronics WM5102 low power audio SoC
1116 bool "Wolfson Microelectronics WM5110"
1117 depends on MFD_ARIZONA
1119 Support for Wolfson Microelectronics WM5110 low power audio SoC
1122 bool "Wolfson Microelectronics WM8997"
1123 depends on MFD_ARIZONA
1125 Support for Wolfson Microelectronics WM8997 low power audio SoC
1128 bool "Wolfson Microelectronics WM8400"
1133 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1134 CODEC. This driver provides common support for accessing
1135 the device, additional drivers must be enabled in order to use
1136 the functionality of the device.
1141 config MFD_WM831X_I2C
1142 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1149 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1150 when controlled using I2C. This driver provides common support
1151 for accessing the device, additional drivers must be enabled in
1152 order to use the functionality of the device.
1154 config MFD_WM831X_SPI
1155 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1160 depends on SPI_MASTER
1162 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1163 when controlled using SPI. This driver provides common support
1164 for accessing the device, additional drivers must be enabled in
1165 order to use the functionality of the device.
1170 config MFD_WM8350_I2C
1171 bool "Wolfson Microelectronics WM8350 with I2C"
1175 The WM8350 is an integrated audio and power management
1176 subsystem with watchdog and RTC functionality for embedded
1177 systems. This option enables core support for the WM8350 with
1178 I2C as the control interface. Additional options must be
1179 selected to enable support for the functionality of the chip.
1182 bool "Wolfson Microelectronics WM8994"
1188 The WM8994 is a highly integrated hi-fi CODEC designed for
1189 smartphone applicatiosn. As well as audio functionality it
1190 has on board GPIO and regulator functionality which is
1191 supported via the relevant subsystems. This driver provides
1192 core support for the WM8994, in order to use the actual
1193 functionaltiy of the device other drivers must be enabled.
1196 bool "Support for ST Microelectronics STw481x"
1197 depends on I2C && ARCH_NOMADIK
1201 Select this option to enable the STw481x chip driver used
1202 in various ST Microelectronics and ST-Ericsson embedded
1205 menu "Multimedia Capabilities Port drivers"
1206 depends on ARCH_SA1100
1213 tristate "Support SA11x0 MCP interface"
1214 depends on ARCH_SA1100
1219 bool "Support for UCB1200 / UCB1300"
1220 depends on MCP_SA11X0
1223 config MCP_UCB1200_TS
1224 tristate "Touchscreen interface support"
1225 depends on MCP_UCB1200 && INPUT
1229 config VEXPRESS_CONFIG
1230 bool "ARM Versatile Express platform infrastructure"
1231 depends on ARM || ARM64
1233 Platform configuration infrastructure for the ARM Ltd.