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 "RT5025 PMIC Chip Core driver"
178 Enable RT5025 core driver.
181 bool "RT5025 PMIC chip misc configuration"
182 depends on MFD_RT5025
185 Enable RT5025 Misc configuration.
188 bool "RT5025_PMIC chip irq driver"
189 depends on MFD_RT5025
192 Enable RT5025 IRQ configuration and interrupt.
195 bool "RT5025 PMIC Chip Core Debug"
196 depends on MFD_RT5025 && DEBUG_FS
199 Enable RT5025 core debug driver.
201 config MFD_RT_SHOW_INFO
202 bool "RT5025 PMIC Debug log Flag"
203 depends on MFD_RT5025
206 Enable the RT5025 PMIC debug log.
209 bool "Richtek RT5036 PMIC support"
213 Enable the RT5036 MFD driver.
215 config MFD_RT5036_DBGINFO
216 bool "Richtek RT5036 debug message enable."
217 depends on MFD_RT5036
220 Enable the RT5036 debug log.
223 bool "Richtek RT5036 MISC option driver support"
224 depends on MFD_RT5036
227 Enable the RT5036 Misc option driver support.
229 config MISC_RT5036_PWRKEY
230 bool "Richtek RT5036 Power key report in Misc module"
231 depends on MISC_RT5036
234 Enable the RT5036 Power Key report in Misc module.
237 bool "Richtek RT5036 irq option driver support"
238 depends on MFD_RT5036
241 Enable the Rt5036 IRQ option driver support.
244 bool "Richtek RT5036 PMIC DEBUGFS Support"
245 depends on DEBUG_FS && MFD_RT5036
248 Enable the RT5036 debugfs node that support
249 read/write registers.
252 bool "HTC EGPIO support"
253 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
255 This driver supports the CPLD egpio chip present on
256 several HTC phones. It provides basic support for input
257 pins, output pins, and irqs.
260 tristate "HTC PASIC3 LED/DS1WM chip support"
262 depends on GENERIC_HARDIRQS
264 This core driver provides register access for the LED/DS1WM
265 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
266 HTC Magician devices, respectively. Actual functionality is
267 handled by the leds-pasic3 and ds1wm drivers.
270 bool "HTC I2C PLD chip support"
271 depends on I2C=y && GPIOLIB
273 If you say yes here you get support for the supposed CPLD
274 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
275 This device provides input and output GPIOs through an I2C
276 interface to one or more sub-chips.
279 tristate "Intel ICH LPC"
280 depends on PCI && GENERIC_HARDIRQS
283 The LPC bridge function of the Intel ICH provides support for
284 many functional units. This driver provides needed support for
285 other drivers to control these functions, currently GPIO and
289 tristate "Intel SCH LPC"
290 depends on PCI && GENERIC_HARDIRQS
293 LPC bridge function of the Intel SCH provides support for
294 System Management Bus and General Purpose I/O.
296 config MFD_INTEL_MSIC
298 depends on INTEL_SCU_IPC
301 Select this option to enable access to Intel MSIC (Avatele
302 Passage) chip. This chip embeds audio, battery, GPIO, etc.
303 devices used in Intel Medfield platforms.
305 config MFD_JANZ_CMODIO
306 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
308 depends on PCI && GENERIC_HARDIRQS
310 This is the core driver for the Janz CMOD-IO PCI MODULbus
311 carrier board. This device is a PCI to MODULbus bridge which may
312 host many different types of MODULbus daughterboards, including
313 CAN and GPIO controllers.
315 config MFD_JZ4740_ADC
316 bool "Janz JZ4740 ADC core"
318 select GENERIC_IRQ_CHIP
319 depends on MACH_JZ4740
321 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
322 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
325 tristate "Marvell 88PM800"
326 depends on I2C=y && GENERIC_HARDIRQS
331 This supports for Marvell 88PM800 Power Management IC.
332 This includes the I2C driver and the core APIs _only_, you have to
333 select individual components like voltage regulators, RTC and
334 battery-charger under the corresponding menus.
337 tristate "Marvell 88PM805"
338 depends on I2C=y && GENERIC_HARDIRQS
343 This supports for Marvell 88PM805 Power Management IC. This includes
344 the I2C driver and the core APIs _only_, you have to select individual
345 components like codec device, headset/Mic device under the
349 bool "Marvell 88PM8606/88PM8607"
350 depends on I2C=y && GENERIC_HARDIRQS
354 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
355 This includes the I2C driver and the core APIs _only_, you have to
356 select individual components like voltage regulators, RTC and
357 battery-charger under the corresponding menus.
360 bool "Maxim Semiconductor MAX77686 PMIC Support"
361 depends on I2C=y && GENERIC_HARDIRQS
366 Say yes here to support for Maxim Semiconductor MAX77686.
367 This is a Power Management IC with RTC on chip.
368 This driver provides common support for accessing the device;
369 additional drivers must be enabled in order to use the functionality
373 bool "Maxim Semiconductor MAX77693 PMIC Support"
374 depends on I2C=y && GENERIC_HARDIRQS
378 Say yes here to support for Maxim Semiconductor MAX77693.
379 This is a companion Power Management IC with Flash, Haptic, Charger,
380 and MUIC(Micro USB Interface Controller) controls on chip.
381 This driver provides common support for accessing the device;
382 additional drivers must be enabled in order to use the functionality
386 tristate "Maxim Semiconductor MAX8907 PMIC Support"
388 depends on I2C=y && GENERIC_HARDIRQS
392 Say yes here to support for Maxim Semiconductor MAX8907. This is
393 a Power Management IC. This driver provides common support for
394 accessing the device; additional drivers must be enabled in order
395 to use the functionality of the device.
398 bool "Maxim Semiconductor MAX8925 PMIC Support"
399 depends on I2C=y && GENERIC_HARDIRQS
402 Say yes here to support for Maxim Semiconductor MAX8925. This is
403 a Power Management IC. This driver provides common support for
404 accessing the device, additional drivers must be enabled in order
405 to use the functionality of the device.
408 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
409 depends on I2C=y && GENERIC_HARDIRQS
413 Say yes here to support for Maxim Semiconductor MAX8997/8966.
414 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
415 MUIC controls on chip.
416 This driver provides common support for accessing the device;
417 additional drivers must be enabled in order to use the functionality
421 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
422 depends on I2C=y && GENERIC_HARDIRQS
425 Say yes here to support for Maxim Semiconductor MAX8998 and
426 National Semiconductor LP3974. This is a Power Management IC.
427 This driver provides common support for accessing the device,
428 additional drivers must be enabled in order to use the functionality
432 bool "RK808 Power Management chip"
438 if you say yes here you get support for the RK808 series of
439 Power Management chips.
442 bool "RK818 Power Management chip"
447 if you say yes here you get support for the RK818 series of
448 Power Management chips.
451 bool "Motorola EZXPCAP Support"
452 depends on GENERIC_HARDIRQS && SPI_MASTER
454 This enables the PCAP ASIC present on EZX Phones. This is
455 needed for MMC, TouchScreen, Sound, USB, etc..
457 config MFD_VIPERBOARD
458 tristate "Nano River Technologies Viperboard"
460 depends on USB && GENERIC_HARDIRQS
463 Say yes here if you want support for Nano River Technologies
465 There are mfd cell drivers available for i2c master, adc and
466 both gpios found on the board. The spi part does not yet
468 You need to select the mfd cell drivers separately.
469 The drivers do not support all features the board exposes.
472 tristate "Nokia Retu and Tahvo multi-function device"
474 depends on I2C && GENERIC_HARDIRQS
477 Retu and Tahvo are a multi-function devices found on Nokia
478 Internet Tablets (770, N800 and N810).
481 tristate "NXP PCF50633"
485 Say yes here if you have NXP PCF50633 chip on your board.
486 This core driver provides register access and IRQ handling
487 facilities, and registers devices for the various functions
488 so that function-specific drivers can bind to them.
491 tristate "NXP PCF50633 ADC"
492 depends on MFD_PCF50633
494 Say yes here if you want to include support for ADC in the
498 tristate "NXP PCF50633 GPIO"
499 depends on MFD_PCF50633
501 Say yes here if you want to include support GPIO for pins on
505 tristate "Philips UCB1400 Core driver"
509 This enables support for the Philips UCB1400 core functions.
510 The UCB1400 is an AC97 audio codec.
512 To compile this driver as a module, choose M here: the
513 module will be called ucb1400_core.
518 config MFD_PM8921_CORE
519 tristate "Qualcomm PM8921 PMIC chip"
520 depends on SSBI && BROKEN
524 If you say yes to this option, support will be included for the
525 built-in PM8921 PMIC chip.
527 This is required if your board has a PM8921 and uses its features,
528 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
530 Say M here if you want to include support for PM8921 chip as a module.
531 This will build a module called "pm8921-core".
533 config MFD_PM8XXX_IRQ
534 bool "Qualcomm PM8xxx IRQ features"
535 depends on MFD_PM8XXX
536 default y if MFD_PM8XXX
538 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
540 This is required to use certain other PM 8xxx features, such as GPIO
544 tristate "RDC R-321x southbridge"
546 depends on PCI && GENERIC_HARDIRQS
548 Say yes here if you want to have support for the RDC R-321x SoC
549 southbridge which provides access to GPIOs and Watchdog using the
550 southbridge PCI device configuration space.
553 tristate "Realtek PCI-E card reader"
554 depends on PCI && GENERIC_HARDIRQS
557 This supports for Realtek PCI-Express card reader including rts5209,
558 rts5229, rtl8411, etc. Realtek card reader supports access to many
559 types of memory cards, such as Memory Stick, Memory Stick Pro,
560 Secure Digital and MultiMediaCard.
563 bool "Ricoh RC5T583 Power Management system device"
564 depends on I2C=y && GENERIC_HARDIRQS
568 Select this option to get support for the RICOH583 Power
569 Management system device.
570 This driver provides common support for accessing the device
571 through i2c interface. The device supports multiple sub-devices
572 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
573 Additional drivers must be enabled in order to use the
574 different functionality of the device.
577 bool "SAMSUNG Electronics PMIC Series Support"
578 depends on I2C=y && GENERIC_HARDIRQS
583 Support for the Samsung Electronics MFD series.
584 This driver provides common support for accessing the device,
585 additional drivers must be enabled in order to use the functionality
588 config MFD_SI476X_CORE
589 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
594 This is the core driver for the SI476x series of AM/FM
595 radio. This MFD driver connects the radio-si476x V4L2 module
596 and the si476x audio codec.
598 To compile this driver as a module, choose M here: the
599 module will be called si476x-core.
602 tristate "Silicon Motion SM501"
604 This is the core driver for the Silicon Motion SM501 multimedia
605 companion chip. This device is a multifunction device which may
606 provide numerous interfaces including USB host controller, USB gadget,
607 asynchronous serial ports, audio functions, and a dual display video
608 interface. The device may be connected by PCI or local bus with
609 varying functions enabled.
611 config MFD_SM501_GPIO
612 bool "Export GPIO via GPIO layer"
613 depends on MFD_SM501 && GPIOLIB
615 This option uses the gpio library layer to export the 64 GPIO
616 lines on the SM501. The platform data is used to supply the
617 base number for the first GPIO line to register.
620 bool "SMSC ECE1099 series chips"
621 depends on I2C=y && GENERIC_HARDIRQS
625 If you say yes here you get support for the
626 ece1099 chips from SMSC.
628 To compile this driver as a module, choose M here: the
629 module will be called smsc.
632 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
633 default y if ARCH_U300 || ARCH_U8500
635 Say yes here if you have the ABX500 Mixed Signal IC family
636 chips. This core driver expose register access functions.
637 Functionality specific drivers using these functions can
638 remain unchanged when IC changes. Binding of the functions to
639 actual register access is done by the IC core driver.
642 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
643 depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
645 default y if ARCH_U300
647 Select this to enable the AB3100 Mixed Signal IC core
648 functionality. This connects to a AB3100 on the I2C bus
649 and expose a number of symbols needed for dependent devices
650 to read and write registers and subscribe to events from
651 this multi-functional IC. This is needed to use other features
652 of the AB3100 such as battery-backed RTC, charging control,
653 LEDs, vibrator, system power and temperature, power management
657 tristate "ST-Ericsson AB3100 OTP functions"
658 depends on AB3100_CORE
659 default y if AB3100_CORE
661 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
662 programmable memory) support. This exposes a sysfs file to read
666 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
667 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
672 Select this option to enable access to AB8500 power management
673 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
674 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
675 the irq_chip parts for handling the Mixed Signal chip events.
676 This chip embeds various other multimedia funtionalities as well.
679 bool "Enable debug info via debugfs"
680 depends on AB8500_GPADC && DEBUG_FS
681 default y if DEBUG_FS
683 Select this option if you want debug information using the debug
687 bool "ST-Ericsson AB8500 GPADC driver"
688 depends on AB8500_CORE && REGULATOR_AB8500
691 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
693 config MFD_DB8500_PRCMU
694 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
695 depends on UX500_SOC_DB8500
698 Select this option to enable support for the DB8500 Power Reset
699 and Control Management Unit. This is basically an autonomous
700 system controller running an XP70 microprocessor, which is accessed
701 through a register map.
704 bool "STMicroelectronics STMPE"
705 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
708 Support for the STMPE family of I/O Expanders from
711 Currently supported devices are:
713 STMPE811: GPIO, Touchscreen
714 STMPE1601: GPIO, Keypad
715 STMPE1801: GPIO, Keypad
716 STMPE2401: GPIO, Keypad
717 STMPE2403: GPIO, Keypad
719 This driver provides common support for accessing the device,
720 additional drivers must be enabled in order to use the functionality
721 of the device. Currently available sub drivers are:
725 Touchscreen: stmpe-ts
727 menu "STMicroelectronics STMPE Interface Drivers"
731 bool "STMicroelectronics STMPE I2C Inteface"
735 This is used to enable I2C interface of STMPE
738 bool "STMicroelectronics STMPE SPI Inteface"
739 depends on SPI_MASTER
741 This is used to enable SPI interface of STMPE
745 bool "STMicroelectronics STA2X11"
746 depends on STA2X11 && GENERIC_HARDIRQS
751 bool "System Controller Register R/W Based on Regmap"
754 Select this option to enable accessing system control registers
757 config MFD_DAVINCI_VOICECODEC
761 config MFD_TI_AM335X_TSCADC
762 tristate "TI ADC / Touch Screen chip support"
766 depends on GENERIC_HARDIRQS
768 If you say yes here you get support for Texas Instruments series
769 of Touch Screen /ADC chips.
770 To compile this driver as a module, choose M here: the
771 module will be called ti_am335x_tscadc.
773 config MFD_DM355EVM_MSP
774 bool "TI DaVinci DM355 EVM microcontroller"
775 depends on I2C=y && MACH_DAVINCI_DM355_EVM
777 This driver supports the MSP430 microcontroller used on these
778 boards. MSP430 firmware manages resets and power sequencing,
779 inputs from buttons and the IR remote, LEDs, an RTC, and more.
782 bool "TI LP8788 Power Management Unit Driver"
783 depends on I2C=y && GENERIC_HARDIRQS
788 TI LP8788 PMU supports regulators, battery charger, RTC,
789 ADC, backlight driver and current sinks.
791 config MFD_OMAP_USB_HOST
792 bool "TI OMAP USBHS core and TLL driver"
793 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
796 This is the core driver for the OAMP EHCI and OHCI drivers.
797 This MFD driver does the required setup functionalities for
798 OMAP USB Host drivers.
801 bool "TI Palmas series chips"
805 depends on I2C=y && GENERIC_HARDIRQS
807 If you say yes here you get support for the Palmas
808 series of PMIC chips from Texas Instruments.
811 tristate "TI Sequencer Serial Port support"
812 depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
815 Say Y here if you want support for the Sequencer Serial Port
816 in a Texas Instruments TNETV107X SoC.
818 To compile this driver as a module, choose M here: the
819 module will be called ti-ssp.
822 tristate "TI TPS61050/61052 Boost Converters"
826 select REGULATOR_FIXED_VOLTAGE
827 depends on GENERIC_HARDIRQS
829 This option enables a driver for the TP61050/TPS61052
830 high-power "white LED driver". This boost converter is
831 sometimes used for other things than white LEDs, and
832 also contains a GPIO pin.
835 tristate "TI TPS6501x Power Management chips"
836 depends on I2C && GPIOLIB
837 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
839 If you say yes here you get support for the TPS6501x series of
840 Power Management chips. These include voltage regulators,
841 lithium ion/polymer battery charging, and other features that
842 are often used in portable devices like cell phones and cameras.
844 This driver can also be built as a module. If so, the module
845 will be called tps65010.
848 tristate "TI TPS6507x Power Management / Touch Screen chips"
850 depends on I2C && GENERIC_HARDIRQS
852 If you say yes here you get support for the TPS6507x series of
853 Power Management / Touch Screen chips. These include voltage
854 regulators, lithium ion/polymer battery charging, touch screen
855 and other features that are often used in portable devices.
856 This driver can also be built as a module. If so, the module
857 will be called tps6507x.
859 config TPS65911_COMPARATOR
863 bool "TI TPS65090 Power Management chips"
864 depends on I2C=y && GENERIC_HARDIRQS
869 If you say yes here you get support for the TPS65090 series of
870 Power Management chips.
871 This driver provides common support for accessing the device,
872 additional drivers must be enabled in order to use the
873 functionality of the device.
876 tristate "TI TPS65217 Power Management / White LED chips"
877 depends on I2C && GENERIC_HARDIRQS
881 If you say yes here you get support for the TPS65217 series of
882 Power Management / White LED chips.
883 These include voltage regulators, lithium ion/polymer battery
884 charger, wled and other features that are often used in portable
887 This driver can also be built as a module. If so, the module
888 will be called tps65217.
891 bool "TI TPS6586x Power Management chips"
892 depends on I2C=y && GENERIC_HARDIRQS
896 If you say yes here you get support for the TPS6586X series of
897 Power Management chips.
898 This driver provides common support for accessing the device,
899 additional drivers must be enabled in order to use the
900 functionality of the device.
902 This driver can also be built as a module. If so, the module
903 will be called tps6586x.
906 bool "TI TPS65910 Power Management chip"
907 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
913 if you say yes here you get support for the TPS65910 series of
914 Power Management chips.
917 bool "TI TPS65912 Power Management chip"
921 If you say yes here you get support for the TPS65912 series of
924 config MFD_TPS65912_I2C
925 bool "TI TPS65912 Power Management chip with I2C"
928 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
930 If you say yes here you get support for the TPS65912 series of
931 PM chips with I2C interface.
933 config MFD_TPS65912_SPI
934 bool "TI TPS65912 Power Management chip with SPI"
937 depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
939 If you say yes here you get support for the TPS65912 series of
940 PM chips with SPI interface.
943 bool "TI TPS80031/TPS80032 Power Management chips"
944 depends on I2C=y && GENERIC_HARDIRQS
949 If you say yes here you get support for the Texas Instruments
950 TPS80031/ TPS80032 Fully Integrated Power Management with Power
951 Path and Battery Charger. The device provides five configurable
952 step-down converters, 11 general purpose LDOs, USB OTG Module,
953 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
954 Power Path from USB, 32K clock generator.
957 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
958 depends on I2C=y && GENERIC_HARDIRQS
962 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
963 This core driver provides register access and IRQ handling
964 facilities, and registers devices for the various functions
965 so that function-specific drivers can bind to them.
967 These multi-function chips are found on many OMAP2 and OMAP3
968 boards, providing power management, RTC, GPIO, keypad, a
969 high speed USB OTG transceiver, an audio codec (on most
970 versions) and many other features.
973 tristate "TI TWL4030 MADC"
974 depends on TWL4030_CORE
976 This driver provides support for triton TWL4030-MADC. The
977 driver supports both RT and SW conversion methods.
979 This driver can be built as a module. If so it will be
983 bool "TI TWL4030 power resources"
984 depends on TWL4030_CORE && ARM
986 Say yes here if you want to use the power resources on the
987 TWL4030 family chips. Most of these resources are regulators,
988 which have a separate driver; some are control signals, such
989 as clock request handshaking.
991 This driver uses board-specific data to initialize the resources
992 and load scripts controlling which resources are switched off/on
993 or reset when a sleep, wakeup or warm reset event occurs.
995 config MFD_TWL4030_AUDIO
996 bool "TI TWL4030 Audio"
997 depends on TWL4030_CORE && GENERIC_HARDIRQS
1002 bool "TI TWL6040 audio codec"
1003 depends on I2C=y && GENERIC_HARDIRQS
1009 Say yes here if you want support for Texas Instruments TWL6040 audio
1011 This driver provides common support for accessing the device,
1012 additional drivers must be enabled in order to use the
1013 functionality of the device (audio, vibra).
1016 bool "Ricoh RC5T619 Power Management system device"
1017 depends on I2C && GPIOLIB && GENERIC_HARDIRQS
1021 If you say yes here you get support for the RICOH619 Power
1022 Management system device.
1023 This driver provides common support for accessing the device,
1024 additional drivers must be enabled in order to use the
1025 functionality of the device.
1028 bool "TI TWL92330/Menelaus PM chip"
1029 depends on I2C=y && ARCH_OMAP2
1031 If you say yes here you get support for the Texas Instruments
1032 TWL92330/Menelaus Power Management chip. This include voltage
1033 regulators, Dual slot memory card transceivers, real-time clock
1034 and other features that are often used in portable devices like
1035 cell phones and PDAs.
1037 config MFD_WL1273_CORE
1038 tristate "TI WL1273 FM radio"
1039 depends on I2C && GENERIC_HARDIRQS
1043 This is the core driver for the TI WL1273 FM radio. This MFD
1044 driver connects the radio-wl1273 V4L2 module and the wl1273
1048 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1052 depends on GENERIC_HARDIRQS
1054 Say yes here to enable support for National Semiconductor / TI
1055 LM3533 Lighting Power chips.
1057 This driver provides common support for accessing the device;
1058 additional drivers must be enabled in order to use the LED,
1059 backlight or ambient-light-sensor functionality of the device.
1061 config MFD_TIMBERDALE
1062 tristate "Timberdale FPGA"
1064 depends on PCI && GPIOLIB
1066 This is the core driver for the timberdale FPGA. This device is a
1067 multifunction device which exposes numerous platform devices.
1069 The timberdale FPGA can be found on the Intel Atom development board
1070 for in-vehicle infontainment, called Russellville.
1073 bool "Toshiba TC35892 and variants"
1074 depends on I2C=y && GENERIC_HARDIRQS
1077 Support for the Toshiba TC35892 and variants I/O Expander.
1079 This driver provides common support for accessing the device,
1080 additional drivers must be enabled in order to use the
1081 functionality of the device.
1088 bool "Toshiba T7L66XB"
1089 depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
1093 Support for Toshiba Mobile IO Controller T7L66XB
1096 bool "Toshiba TC6387XB"
1097 depends on ARM && HAVE_CLK
1101 Support for Toshiba Mobile IO Controller TC6387XB
1104 bool "Toshiba TC6393XB"
1105 depends on ARM && HAVE_CLK
1110 Support for Toshiba Mobile IO Controller TC6393XB
1113 tristate "VIA VX855/VX875 integrated south bridge"
1114 depends on PCI && GENERIC_HARDIRQS
1117 Say yes here to enable support for various functions of the
1118 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1119 and/or vx855_gpio drivers for this to do anything useful.
1127 config MFD_ARIZONA_I2C
1128 tristate "Wolfson Microelectronics Arizona platform with I2C"
1132 depends on I2C && GENERIC_HARDIRQS
1134 Support for the Wolfson Microelectronics Arizona platform audio SoC
1135 core functionality controlled via I2C.
1137 config MFD_ARIZONA_SPI
1138 tristate "Wolfson Microelectronics Arizona platform with SPI"
1142 depends on SPI_MASTER && GENERIC_HARDIRQS
1144 Support for the Wolfson Microelectronics Arizona platform audio SoC
1145 core functionality controlled via I2C.
1148 bool "Wolfson Microelectronics WM5102"
1149 depends on MFD_ARIZONA
1151 Support for Wolfson Microelectronics WM5102 low power audio SoC
1154 bool "Wolfson Microelectronics WM5110"
1155 depends on MFD_ARIZONA
1157 Support for Wolfson Microelectronics WM5110 low power audio SoC
1160 bool "Wolfson Microelectronics WM8400"
1162 depends on I2C=y && GENERIC_HARDIRQS
1165 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1166 CODEC. This driver provides common support for accessing
1167 the device, additional drivers must be enabled in order to use
1168 the functionality of the device.
1172 depends on GENERIC_HARDIRQS
1174 config MFD_WM831X_I2C
1175 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1180 depends on I2C=y && GENERIC_HARDIRQS
1182 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1183 when controlled using I2C. This driver provides common support
1184 for accessing the device, additional drivers must be enabled in
1185 order to use the functionality of the device.
1187 config MFD_WM831X_SPI
1188 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1193 depends on SPI_MASTER && GENERIC_HARDIRQS
1195 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1196 when controlled using SPI. This driver provides common support
1197 for accessing the device, additional drivers must be enabled in
1198 order to use the functionality of the device.
1202 depends on GENERIC_HARDIRQS
1204 config MFD_WM8350_I2C
1205 bool "Wolfson Microelectronics WM8350 with I2C"
1207 depends on I2C=y && GENERIC_HARDIRQS
1209 The WM8350 is an integrated audio and power management
1210 subsystem with watchdog and RTC functionality for embedded
1211 systems. This option enables core support for the WM8350 with
1212 I2C as the control interface. Additional options must be
1213 selected to enable support for the functionality of the chip.
1216 bool "Wolfson Microelectronics WM8994"
1220 depends on I2C=y && GENERIC_HARDIRQS
1222 The WM8994 is a highly integrated hi-fi CODEC designed for
1223 smartphone applicatiosn. As well as audio functionality it
1224 has on board GPIO and regulator functionality which is
1225 supported via the relevant subsystems. This driver provides
1226 core support for the WM8994, in order to use the actual
1227 functionaltiy of the device other drivers must be enabled.
1230 bool "RK1000 Multimedia support"
1231 depends on I2C=y && GPIOLIB
1234 if you say yes here you get support for the RK1000, with func as
1238 bool "RK610(Jetta) Multimedia support"
1239 depends on I2C=y && GPIOLIB
1242 if you say yes here you get support for the RK610, with func as
1243 HDMI LCD LVDS TVOUT CODEC.
1246 bool "RK616(Jetta B) Multifunction device support"
1250 if you say yes here you get support for the RK616, with func as
1251 HDMI、LCD、LVDS、CODEC、MIPI.
1253 config RK616_USE_MCLK_12M
1254 bool "Enable 12M clock for timing reconstruction"
1255 depends on MFD_RK616
1256 select RK_HDMI_CTL_CODEC
1259 if you say y here ,it will enable 12M clock for timing reconstruction
1262 bool "RK616(JettaB) debug enable"
1263 depends on MFD_RK616
1265 if you say y here ,it will enable rk616 debug function
1270 menu "Multimedia Capabilities Port drivers"
1271 depends on ARCH_SA1100
1278 tristate "Support SA11x0 MCP interface"
1279 depends on ARCH_SA1100
1284 bool "Support for UCB1200 / UCB1300"
1285 depends on MCP_SA11X0
1288 config MCP_UCB1200_TS
1289 tristate "Touchscreen interface support"
1290 depends on MCP_UCB1200 && INPUT
1294 config VEXPRESS_CONFIG
1295 bool "ARM Versatile Express platform infrastructure"
1296 depends on ARM || ARM64
1298 Platform configuration infrastructure for the ARM Ltd.
1302 bool "Versatile Express SPC driver support"
1304 depends on VEXPRESS_CONFIG
1306 Serial Power Controller driver for ARM Ltd. test chips.