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.
26 depends on I2C=y && GENERIC_HARDIRQS
28 Support for the AS3711 PMIC from AMS
31 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
34 Say yes here to add support for Analog Devices AD5520 and ADP5501,
35 Multifunction Power Management IC. This includes
36 the I2C driver and the core APIs _only_, you have to select
37 individual components like LCD backlight, LEDs, GPIOs and Kepad
38 under the corresponding menus.
40 config MFD_AAT2870_CORE
41 bool "AnalogicTech AAT2870"
43 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
45 If you say yes here you get support for the AAT2870.
46 This driver provides common support for accessing the device,
47 additional drivers must be enabled in order to use the
48 functionality of the device.
51 tristate "ChromeOS Embedded Controller"
54 If you say Y here you get support for the ChromeOS Embedded
55 Controller (EC) providing keyboard, battery and power services.
56 You also ned to enable the driver for the bus you are using. The
57 protocol for talking to the EC is defined by the bus driver.
59 config MFD_CROS_EC_I2C
60 tristate "ChromeOS Embedded Controller (I2C)"
61 depends on MFD_CROS_EC && I2C
64 If you say Y here, you get support for talking to the ChromeOS
65 EC through an I2C bus. This uses a simple byte-level protocol with
66 a checksum. Failing accesses will be retried three times to
69 config MFD_CROS_EC_SPI
70 tristate "ChromeOS Embedded Controller (SPI)"
71 depends on MFD_CROS_EC && SPI
74 If you say Y here, you get support for talking to the ChromeOS EC
75 through a SPI bus, using a byte-level protocol. Since the EC's
76 response time cannot be guaranteed, we support ignoring
77 'pre-amble' bytes before the response actually starts.
81 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
84 This driver supports the ASIC3 multifunction chip found on many
85 PDAs (mainly iPAQ and HTC based ones)
88 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
91 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
92 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
93 usually found on PXA processors-based platforms. This includes
94 the I2C driver and the core APIs _only_, you have to select
95 individual components like LCD backlight, voltage regulators,
96 LEDs and battery-charger under the corresponding menus.
102 config MFD_DA9052_SPI
103 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
107 depends on SPI_MASTER=y && GENERIC_HARDIRQS
109 Support for the Dialog Semiconductor DA9052 PMIC
110 when controlled using SPI. This driver provides common support
111 for accessing the device, additional drivers must be enabled in
112 order to use the functionality of the device.
114 config MFD_DA9052_I2C
115 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
119 depends on I2C=y && GENERIC_HARDIRQS
121 Support for the Dialog Semiconductor DA9052 PMIC
122 when controlled using I2C. This driver provides common support
123 for accessing the device, additional drivers must be enabled in
124 order to use the functionality of the device.
127 bool "Dialog Semiconductor DA9055 PMIC Support"
131 depends on I2C=y && GENERIC_HARDIRQS
133 Say yes here for support of Dialog Semiconductor DA9055. This is
134 a Power Management IC. This driver provides common support for
135 accessing the device as well as the I2C interface to the chip itself.
136 Additional drivers must be enabled in order to use the functionality
139 This driver can be built as a module. If built as a module it will be
147 depends on (SPI_MASTER || I2C) && GENERIC_HARDIRQS
151 Enable support for the Freescale MC13783 and MC13892 PMICs.
152 This driver provides common support for accessing the device,
153 additional drivers must be enabled in order to use the
154 functionality of the device.
156 config MFD_MC13XXX_SPI
157 tristate "Freescale MC13783 and MC13892 SPI interface"
158 depends on SPI_MASTER && GENERIC_HARDIRQS
162 Select this if your MC13xxx is connected via an SPI bus.
164 config MFD_MC13XXX_I2C
165 tristate "Freescale MC13892 I2C interface"
166 depends on I2C && GENERIC_HARDIRQS
170 Select this if your MC13xxx is connected via an I2C bus.
173 bool "HTC EGPIO support"
174 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
176 This driver supports the CPLD egpio chip present on
177 several HTC phones. It provides basic support for input
178 pins, output pins, and irqs.
181 tristate "HTC PASIC3 LED/DS1WM chip support"
183 depends on GENERIC_HARDIRQS
185 This core driver provides register access for the LED/DS1WM
186 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
187 HTC Magician devices, respectively. Actual functionality is
188 handled by the leds-pasic3 and ds1wm drivers.
191 bool "HTC I2C PLD chip support"
192 depends on I2C=y && GPIOLIB
194 If you say yes here you get support for the supposed CPLD
195 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
196 This device provides input and output GPIOs through an I2C
197 interface to one or more sub-chips.
200 tristate "Intel ICH LPC"
201 depends on PCI && GENERIC_HARDIRQS
204 The LPC bridge function of the Intel ICH provides support for
205 many functional units. This driver provides needed support for
206 other drivers to control these functions, currently GPIO and
210 tristate "Intel SCH LPC"
211 depends on PCI && GENERIC_HARDIRQS
214 LPC bridge function of the Intel SCH provides support for
215 System Management Bus and General Purpose I/O.
217 config MFD_INTEL_MSIC
219 depends on INTEL_SCU_IPC
222 Select this option to enable access to Intel MSIC (Avatele
223 Passage) chip. This chip embeds audio, battery, GPIO, etc.
224 devices used in Intel Medfield platforms.
226 config MFD_JANZ_CMODIO
227 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
229 depends on PCI && GENERIC_HARDIRQS
231 This is the core driver for the Janz CMOD-IO PCI MODULbus
232 carrier board. This device is a PCI to MODULbus bridge which may
233 host many different types of MODULbus daughterboards, including
234 CAN and GPIO controllers.
236 config MFD_JZ4740_ADC
237 bool "Janz JZ4740 ADC core"
239 select GENERIC_IRQ_CHIP
240 depends on MACH_JZ4740
242 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
243 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
246 tristate "Marvell 88PM800"
247 depends on I2C=y && GENERIC_HARDIRQS
252 This supports for Marvell 88PM800 Power Management IC.
253 This includes the I2C driver and the core APIs _only_, you have to
254 select individual components like voltage regulators, RTC and
255 battery-charger under the corresponding menus.
258 tristate "Marvell 88PM805"
259 depends on I2C=y && GENERIC_HARDIRQS
264 This supports for Marvell 88PM805 Power Management IC. This includes
265 the I2C driver and the core APIs _only_, you have to select individual
266 components like codec device, headset/Mic device under the
270 bool "Marvell 88PM8606/88PM8607"
271 depends on I2C=y && GENERIC_HARDIRQS
275 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
276 This includes the I2C driver and the core APIs _only_, you have to
277 select individual components like voltage regulators, RTC and
278 battery-charger under the corresponding menus.
281 bool "Maxim Semiconductor MAX77686 PMIC Support"
282 depends on I2C=y && GENERIC_HARDIRQS
287 Say yes here to support for Maxim Semiconductor MAX77686.
288 This is a Power Management IC with RTC on chip.
289 This driver provides common support for accessing the device;
290 additional drivers must be enabled in order to use the functionality
294 bool "Maxim Semiconductor MAX77693 PMIC Support"
295 depends on I2C=y && GENERIC_HARDIRQS
299 Say yes here to support for Maxim Semiconductor MAX77693.
300 This is a companion Power Management IC with Flash, Haptic, Charger,
301 and MUIC(Micro USB Interface Controller) controls on chip.
302 This driver provides common support for accessing the device;
303 additional drivers must be enabled in order to use the functionality
307 tristate "Maxim Semiconductor MAX8907 PMIC Support"
309 depends on I2C=y && GENERIC_HARDIRQS
313 Say yes here to support for Maxim Semiconductor MAX8907. This is
314 a Power Management IC. This driver provides common support for
315 accessing the device; additional drivers must be enabled in order
316 to use the functionality of the device.
319 bool "Maxim Semiconductor MAX8925 PMIC Support"
320 depends on I2C=y && GENERIC_HARDIRQS
323 Say yes here to support for Maxim Semiconductor MAX8925. This is
324 a Power Management IC. This driver provides common support for
325 accessing the device, additional drivers must be enabled in order
326 to use the functionality of the device.
329 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
330 depends on I2C=y && GENERIC_HARDIRQS
334 Say yes here to support for Maxim Semiconductor MAX8997/8966.
335 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
336 MUIC controls on chip.
337 This driver provides common support for accessing the device;
338 additional drivers must be enabled in order to use the functionality
342 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
343 depends on I2C=y && GENERIC_HARDIRQS
346 Say yes here to support for Maxim Semiconductor MAX8998 and
347 National Semiconductor LP3974. This is a Power Management IC.
348 This driver provides common support for accessing the device,
349 additional drivers must be enabled in order to use the functionality
353 bool "RK808 Power Management chip"
358 if you say yes here you get support for the RK808 series of
359 Power Management chips.
362 bool "Motorola EZXPCAP Support"
363 depends on GENERIC_HARDIRQS && SPI_MASTER
365 This enables the PCAP ASIC present on EZX Phones. This is
366 needed for MMC, TouchScreen, Sound, USB, etc..
368 config MFD_VIPERBOARD
369 tristate "Nano River Technologies Viperboard"
371 depends on USB && GENERIC_HARDIRQS
374 Say yes here if you want support for Nano River Technologies
376 There are mfd cell drivers available for i2c master, adc and
377 both gpios found on the board. The spi part does not yet
379 You need to select the mfd cell drivers separately.
380 The drivers do not support all features the board exposes.
383 tristate "Nokia Retu and Tahvo multi-function device"
385 depends on I2C && GENERIC_HARDIRQS
388 Retu and Tahvo are a multi-function devices found on Nokia
389 Internet Tablets (770, N800 and N810).
392 tristate "NXP PCF50633"
396 Say yes here if you have NXP PCF50633 chip on your board.
397 This core driver provides register access and IRQ handling
398 facilities, and registers devices for the various functions
399 so that function-specific drivers can bind to them.
402 tristate "NXP PCF50633 ADC"
403 depends on MFD_PCF50633
405 Say yes here if you want to include support for ADC in the
409 tristate "NXP PCF50633 GPIO"
410 depends on MFD_PCF50633
412 Say yes here if you want to include support GPIO for pins on
416 tristate "Philips UCB1400 Core driver"
420 This enables support for the Philips UCB1400 core functions.
421 The UCB1400 is an AC97 audio codec.
423 To compile this driver as a module, choose M here: the
424 module will be called ucb1400_core.
429 config MFD_PM8921_CORE
430 tristate "Qualcomm PM8921 PMIC chip"
431 depends on SSBI && BROKEN
435 If you say yes to this option, support will be included for the
436 built-in PM8921 PMIC chip.
438 This is required if your board has a PM8921 and uses its features,
439 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
441 Say M here if you want to include support for PM8921 chip as a module.
442 This will build a module called "pm8921-core".
444 config MFD_PM8XXX_IRQ
445 bool "Qualcomm PM8xxx IRQ features"
446 depends on MFD_PM8XXX
447 default y if MFD_PM8XXX
449 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
451 This is required to use certain other PM 8xxx features, such as GPIO
455 tristate "RDC R-321x southbridge"
457 depends on PCI && GENERIC_HARDIRQS
459 Say yes here if you want to have support for the RDC R-321x SoC
460 southbridge which provides access to GPIOs and Watchdog using the
461 southbridge PCI device configuration space.
464 tristate "Realtek PCI-E card reader"
465 depends on PCI && GENERIC_HARDIRQS
468 This supports for Realtek PCI-Express card reader including rts5209,
469 rts5229, rtl8411, etc. Realtek card reader supports access to many
470 types of memory cards, such as Memory Stick, Memory Stick Pro,
471 Secure Digital and MultiMediaCard.
474 bool "Ricoh RC5T583 Power Management system device"
475 depends on I2C=y && GENERIC_HARDIRQS
479 Select this option to get support for the RICOH583 Power
480 Management system device.
481 This driver provides common support for accessing the device
482 through i2c interface. The device supports multiple sub-devices
483 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
484 Additional drivers must be enabled in order to use the
485 different functionality of the device.
488 bool "SAMSUNG Electronics PMIC Series Support"
489 depends on I2C=y && GENERIC_HARDIRQS
494 Support for the Samsung Electronics MFD series.
495 This driver provides common support for accessing the device,
496 additional drivers must be enabled in order to use the functionality
499 config MFD_SI476X_CORE
500 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
505 This is the core driver for the SI476x series of AM/FM
506 radio. This MFD driver connects the radio-si476x V4L2 module
507 and the si476x audio codec.
509 To compile this driver as a module, choose M here: the
510 module will be called si476x-core.
513 tristate "Silicon Motion SM501"
515 This is the core driver for the Silicon Motion SM501 multimedia
516 companion chip. This device is a multifunction device which may
517 provide numerous interfaces including USB host controller, USB gadget,
518 asynchronous serial ports, audio functions, and a dual display video
519 interface. The device may be connected by PCI or local bus with
520 varying functions enabled.
522 config MFD_SM501_GPIO
523 bool "Export GPIO via GPIO layer"
524 depends on MFD_SM501 && GPIOLIB
526 This option uses the gpio library layer to export the 64 GPIO
527 lines on the SM501. The platform data is used to supply the
528 base number for the first GPIO line to register.
531 bool "SMSC ECE1099 series chips"
532 depends on I2C=y && GENERIC_HARDIRQS
536 If you say yes here you get support for the
537 ece1099 chips from SMSC.
539 To compile this driver as a module, choose M here: the
540 module will be called smsc.
543 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
544 default y if ARCH_U300 || ARCH_U8500
546 Say yes here if you have the ABX500 Mixed Signal IC family
547 chips. This core driver expose register access functions.
548 Functionality specific drivers using these functions can
549 remain unchanged when IC changes. Binding of the functions to
550 actual register access is done by the IC core driver.
553 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
554 depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
556 default y if ARCH_U300
558 Select this to enable the AB3100 Mixed Signal IC core
559 functionality. This connects to a AB3100 on the I2C bus
560 and expose a number of symbols needed for dependent devices
561 to read and write registers and subscribe to events from
562 this multi-functional IC. This is needed to use other features
563 of the AB3100 such as battery-backed RTC, charging control,
564 LEDs, vibrator, system power and temperature, power management
568 tristate "ST-Ericsson AB3100 OTP functions"
569 depends on AB3100_CORE
570 default y if AB3100_CORE
572 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
573 programmable memory) support. This exposes a sysfs file to read
577 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
578 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
583 Select this option to enable access to AB8500 power management
584 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
585 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
586 the irq_chip parts for handling the Mixed Signal chip events.
587 This chip embeds various other multimedia funtionalities as well.
590 bool "Enable debug info via debugfs"
591 depends on AB8500_GPADC && DEBUG_FS
592 default y if DEBUG_FS
594 Select this option if you want debug information using the debug
598 bool "ST-Ericsson AB8500 GPADC driver"
599 depends on AB8500_CORE && REGULATOR_AB8500
602 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
604 config MFD_DB8500_PRCMU
605 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
606 depends on UX500_SOC_DB8500
609 Select this option to enable support for the DB8500 Power Reset
610 and Control Management Unit. This is basically an autonomous
611 system controller running an XP70 microprocessor, which is accessed
612 through a register map.
615 bool "STMicroelectronics STMPE"
616 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
619 Support for the STMPE family of I/O Expanders from
622 Currently supported devices are:
624 STMPE811: GPIO, Touchscreen
625 STMPE1601: GPIO, Keypad
626 STMPE1801: GPIO, Keypad
627 STMPE2401: GPIO, Keypad
628 STMPE2403: GPIO, Keypad
630 This driver provides common support for accessing the device,
631 additional drivers must be enabled in order to use the functionality
632 of the device. Currently available sub drivers are:
636 Touchscreen: stmpe-ts
638 menu "STMicroelectronics STMPE Interface Drivers"
642 bool "STMicroelectronics STMPE I2C Inteface"
646 This is used to enable I2C interface of STMPE
649 bool "STMicroelectronics STMPE SPI Inteface"
650 depends on SPI_MASTER
652 This is used to enable SPI interface of STMPE
656 bool "STMicroelectronics STA2X11"
657 depends on STA2X11 && GENERIC_HARDIRQS
662 bool "System Controller Register R/W Based on Regmap"
665 Select this option to enable accessing system control registers
668 config MFD_DAVINCI_VOICECODEC
672 config MFD_TI_AM335X_TSCADC
673 tristate "TI ADC / Touch Screen chip support"
677 depends on GENERIC_HARDIRQS
679 If you say yes here you get support for Texas Instruments series
680 of Touch Screen /ADC chips.
681 To compile this driver as a module, choose M here: the
682 module will be called ti_am335x_tscadc.
684 config MFD_DM355EVM_MSP
685 bool "TI DaVinci DM355 EVM microcontroller"
686 depends on I2C=y && MACH_DAVINCI_DM355_EVM
688 This driver supports the MSP430 microcontroller used on these
689 boards. MSP430 firmware manages resets and power sequencing,
690 inputs from buttons and the IR remote, LEDs, an RTC, and more.
693 bool "TI LP8788 Power Management Unit Driver"
694 depends on I2C=y && GENERIC_HARDIRQS
699 TI LP8788 PMU supports regulators, battery charger, RTC,
700 ADC, backlight driver and current sinks.
702 config MFD_OMAP_USB_HOST
703 bool "TI OMAP USBHS core and TLL driver"
704 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
707 This is the core driver for the OAMP EHCI and OHCI drivers.
708 This MFD driver does the required setup functionalities for
709 OMAP USB Host drivers.
712 bool "TI Palmas series chips"
716 depends on I2C=y && GENERIC_HARDIRQS
718 If you say yes here you get support for the Palmas
719 series of PMIC chips from Texas Instruments.
722 tristate "TI Sequencer Serial Port support"
723 depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
726 Say Y here if you want support for the Sequencer Serial Port
727 in a Texas Instruments TNETV107X SoC.
729 To compile this driver as a module, choose M here: the
730 module will be called ti-ssp.
733 tristate "TI TPS61050/61052 Boost Converters"
737 select REGULATOR_FIXED_VOLTAGE
738 depends on GENERIC_HARDIRQS
740 This option enables a driver for the TP61050/TPS61052
741 high-power "white LED driver". This boost converter is
742 sometimes used for other things than white LEDs, and
743 also contains a GPIO pin.
746 tristate "TI TPS6501x Power Management chips"
747 depends on I2C && GPIOLIB
748 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
750 If you say yes here you get support for the TPS6501x series of
751 Power Management chips. These include voltage regulators,
752 lithium ion/polymer battery charging, and other features that
753 are often used in portable devices like cell phones and cameras.
755 This driver can also be built as a module. If so, the module
756 will be called tps65010.
759 tristate "TI TPS6507x Power Management / Touch Screen chips"
761 depends on I2C && GENERIC_HARDIRQS
763 If you say yes here you get support for the TPS6507x series of
764 Power Management / Touch Screen chips. These include voltage
765 regulators, lithium ion/polymer battery charging, touch screen
766 and other features that are often used in portable devices.
767 This driver can also be built as a module. If so, the module
768 will be called tps6507x.
770 config TPS65911_COMPARATOR
774 bool "TI TPS65090 Power Management chips"
775 depends on I2C=y && GENERIC_HARDIRQS
780 If you say yes here you get support for the TPS65090 series of
781 Power Management chips.
782 This driver provides common support for accessing the device,
783 additional drivers must be enabled in order to use the
784 functionality of the device.
787 tristate "TI TPS65217 Power Management / White LED chips"
788 depends on I2C && GENERIC_HARDIRQS
792 If you say yes here you get support for the TPS65217 series of
793 Power Management / White LED chips.
794 These include voltage regulators, lithium ion/polymer battery
795 charger, wled and other features that are often used in portable
798 This driver can also be built as a module. If so, the module
799 will be called tps65217.
802 bool "TI TPS6586x Power Management chips"
803 depends on I2C=y && GENERIC_HARDIRQS
807 If you say yes here you get support for the TPS6586X series of
808 Power Management chips.
809 This driver provides common support for accessing the device,
810 additional drivers must be enabled in order to use the
811 functionality of the device.
813 This driver can also be built as a module. If so, the module
814 will be called tps6586x.
817 bool "TI TPS65910 Power Management chip"
818 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
824 if you say yes here you get support for the TPS65910 series of
825 Power Management chips.
828 bool "TI TPS65912 Power Management chip"
832 If you say yes here you get support for the TPS65912 series of
835 config MFD_TPS65912_I2C
836 bool "TI TPS65912 Power Management chip with I2C"
839 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
841 If you say yes here you get support for the TPS65912 series of
842 PM chips with I2C interface.
844 config MFD_TPS65912_SPI
845 bool "TI TPS65912 Power Management chip with SPI"
848 depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
850 If you say yes here you get support for the TPS65912 series of
851 PM chips with SPI interface.
854 bool "TI TPS80031/TPS80032 Power Management chips"
855 depends on I2C=y && GENERIC_HARDIRQS
860 If you say yes here you get support for the Texas Instruments
861 TPS80031/ TPS80032 Fully Integrated Power Management with Power
862 Path and Battery Charger. The device provides five configurable
863 step-down converters, 11 general purpose LDOs, USB OTG Module,
864 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
865 Power Path from USB, 32K clock generator.
868 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
869 depends on I2C=y && GENERIC_HARDIRQS
873 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
874 This core driver provides register access and IRQ handling
875 facilities, and registers devices for the various functions
876 so that function-specific drivers can bind to them.
878 These multi-function chips are found on many OMAP2 and OMAP3
879 boards, providing power management, RTC, GPIO, keypad, a
880 high speed USB OTG transceiver, an audio codec (on most
881 versions) and many other features.
884 tristate "TI TWL4030 MADC"
885 depends on TWL4030_CORE
887 This driver provides support for triton TWL4030-MADC. The
888 driver supports both RT and SW conversion methods.
890 This driver can be built as a module. If so it will be
894 bool "TI TWL4030 power resources"
895 depends on TWL4030_CORE && ARM
897 Say yes here if you want to use the power resources on the
898 TWL4030 family chips. Most of these resources are regulators,
899 which have a separate driver; some are control signals, such
900 as clock request handshaking.
902 This driver uses board-specific data to initialize the resources
903 and load scripts controlling which resources are switched off/on
904 or reset when a sleep, wakeup or warm reset event occurs.
906 config MFD_TWL4030_AUDIO
907 bool "TI TWL4030 Audio"
908 depends on TWL4030_CORE && GENERIC_HARDIRQS
913 bool "TI TWL6040 audio codec"
914 depends on I2C=y && GENERIC_HARDIRQS
920 Say yes here if you want support for Texas Instruments TWL6040 audio
922 This driver provides common support for accessing the device,
923 additional drivers must be enabled in order to use the
924 functionality of the device (audio, vibra).
927 bool "TI TWL92330/Menelaus PM chip"
928 depends on I2C=y && ARCH_OMAP2
930 If you say yes here you get support for the Texas Instruments
931 TWL92330/Menelaus Power Management chip. This include voltage
932 regulators, Dual slot memory card transceivers, real-time clock
933 and other features that are often used in portable devices like
934 cell phones and PDAs.
936 config MFD_WL1273_CORE
937 tristate "TI WL1273 FM radio"
938 depends on I2C && GENERIC_HARDIRQS
942 This is the core driver for the TI WL1273 FM radio. This MFD
943 driver connects the radio-wl1273 V4L2 module and the wl1273
947 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
951 depends on GENERIC_HARDIRQS
953 Say yes here to enable support for National Semiconductor / TI
954 LM3533 Lighting Power chips.
956 This driver provides common support for accessing the device;
957 additional drivers must be enabled in order to use the LED,
958 backlight or ambient-light-sensor functionality of the device.
960 config MFD_TIMBERDALE
961 tristate "Timberdale FPGA"
963 depends on PCI && GPIOLIB
965 This is the core driver for the timberdale FPGA. This device is a
966 multifunction device which exposes numerous platform devices.
968 The timberdale FPGA can be found on the Intel Atom development board
969 for in-vehicle infontainment, called Russellville.
972 bool "Toshiba TC35892 and variants"
973 depends on I2C=y && GENERIC_HARDIRQS
976 Support for the Toshiba TC35892 and variants I/O Expander.
978 This driver provides common support for accessing the device,
979 additional drivers must be enabled in order to use the
980 functionality of the device.
987 bool "Toshiba T7L66XB"
988 depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
992 Support for Toshiba Mobile IO Controller T7L66XB
995 bool "Toshiba TC6387XB"
996 depends on ARM && HAVE_CLK
1000 Support for Toshiba Mobile IO Controller TC6387XB
1003 bool "Toshiba TC6393XB"
1004 depends on ARM && HAVE_CLK
1009 Support for Toshiba Mobile IO Controller TC6393XB
1012 tristate "VIA VX855/VX875 integrated south bridge"
1013 depends on PCI && GENERIC_HARDIRQS
1016 Say yes here to enable support for various functions of the
1017 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1018 and/or vx855_gpio drivers for this to do anything useful.
1026 config MFD_ARIZONA_I2C
1027 tristate "Wolfson Microelectronics Arizona platform with I2C"
1031 depends on I2C && GENERIC_HARDIRQS
1033 Support for the Wolfson Microelectronics Arizona platform audio SoC
1034 core functionality controlled via I2C.
1036 config MFD_ARIZONA_SPI
1037 tristate "Wolfson Microelectronics Arizona platform with SPI"
1041 depends on SPI_MASTER && GENERIC_HARDIRQS
1043 Support for the Wolfson Microelectronics Arizona platform audio SoC
1044 core functionality controlled via I2C.
1047 bool "Wolfson Microelectronics WM5102"
1048 depends on MFD_ARIZONA
1050 Support for Wolfson Microelectronics WM5102 low power audio SoC
1053 bool "Wolfson Microelectronics WM5110"
1054 depends on MFD_ARIZONA
1056 Support for Wolfson Microelectronics WM5110 low power audio SoC
1059 bool "Wolfson Microelectronics WM8400"
1061 depends on I2C=y && GENERIC_HARDIRQS
1064 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1065 CODEC. This driver provides common support for accessing
1066 the device, additional drivers must be enabled in order to use
1067 the functionality of the device.
1071 depends on GENERIC_HARDIRQS
1073 config MFD_WM831X_I2C
1074 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1079 depends on I2C=y && GENERIC_HARDIRQS
1081 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1082 when controlled using I2C. This driver provides common support
1083 for accessing the device, additional drivers must be enabled in
1084 order to use the functionality of the device.
1086 config MFD_WM831X_SPI
1087 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1092 depends on SPI_MASTER && GENERIC_HARDIRQS
1094 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1095 when controlled using SPI. This driver provides common support
1096 for accessing the device, additional drivers must be enabled in
1097 order to use the functionality of the device.
1101 depends on GENERIC_HARDIRQS
1103 config MFD_WM8350_I2C
1104 bool "Wolfson Microelectronics WM8350 with I2C"
1106 depends on I2C=y && GENERIC_HARDIRQS
1108 The WM8350 is an integrated audio and power management
1109 subsystem with watchdog and RTC functionality for embedded
1110 systems. This option enables core support for the WM8350 with
1111 I2C as the control interface. Additional options must be
1112 selected to enable support for the functionality of the chip.
1115 bool "Wolfson Microelectronics WM8994"
1119 depends on I2C=y && GENERIC_HARDIRQS
1121 The WM8994 is a highly integrated hi-fi CODEC designed for
1122 smartphone applicatiosn. As well as audio functionality it
1123 has on board GPIO and regulator functionality which is
1124 supported via the relevant subsystems. This driver provides
1125 core support for the WM8994, in order to use the actual
1126 functionaltiy of the device other drivers must be enabled.
1129 bool "RK610(Jetta) Multimedia support"
1130 depends on I2C=y && GPIOLIB
1133 if you say yes here you get support for the RK610, with func as
1134 HDMI LCD LVDS TVOUT CODEC.
1137 bool "RK616(Jetta B) Multifunction device support"
1141 if you say yes here you get support for the RK616, with func as
1142 HDMI、LCD、LVDS、CODEC、MIPI.
1144 config RK616_USE_MCLK_12M
1145 bool "Enable 12M clock for timing reconstruction"
1146 depends on MFD_RK616
1147 select RK_HDMI_CTL_CODEC
1150 if you say y here ,it will enable 12M clock for timing reconstruction
1153 bool "RK616(JettaB) debug enable"
1154 depends on MFD_RK616
1156 if you say y here ,it will enable rk616 debug function
1161 menu "Multimedia Capabilities Port drivers"
1162 depends on ARCH_SA1100
1169 tristate "Support SA11x0 MCP interface"
1170 depends on ARCH_SA1100
1175 bool "Support for UCB1200 / UCB1300"
1176 depends on MCP_SA11X0
1179 config MCP_UCB1200_TS
1180 tristate "Touchscreen interface support"
1181 depends on MCP_UCB1200 && INPUT
1185 config VEXPRESS_CONFIG
1186 bool "ARM Versatile Express platform infrastructure"
1187 depends on ARM || ARM64
1189 Platform configuration infrastructure for the ARM Ltd.
1193 bool "Versatile Express SPC driver support"
1195 depends on VEXPRESS_CONFIG
1197 Serial Power Controller driver for ARM Ltd. test chips.