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 need 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 "Motorola EZXPCAP Support"
354 depends on GENERIC_HARDIRQS && SPI_MASTER
356 This enables the PCAP ASIC present on EZX Phones. This is
357 needed for MMC, TouchScreen, Sound, USB, etc..
359 config MFD_VIPERBOARD
360 tristate "Nano River Technologies Viperboard"
362 depends on USB && GENERIC_HARDIRQS
365 Say yes here if you want support for Nano River Technologies
367 There are mfd cell drivers available for i2c master, adc and
368 both gpios found on the board. The spi part does not yet
370 You need to select the mfd cell drivers separately.
371 The drivers do not support all features the board exposes.
374 tristate "Nokia Retu and Tahvo multi-function device"
376 depends on I2C && GENERIC_HARDIRQS
379 Retu and Tahvo are a multi-function devices found on Nokia
380 Internet Tablets (770, N800 and N810).
383 tristate "NXP PCF50633"
387 Say yes here if you have NXP PCF50633 chip on your board.
388 This core driver provides register access and IRQ handling
389 facilities, and registers devices for the various functions
390 so that function-specific drivers can bind to them.
393 tristate "NXP PCF50633 ADC"
394 depends on MFD_PCF50633
396 Say yes here if you want to include support for ADC in the
400 tristate "NXP PCF50633 GPIO"
401 depends on MFD_PCF50633
403 Say yes here if you want to include support GPIO for pins on
407 tristate "Philips UCB1400 Core driver"
411 This enables support for the Philips UCB1400 core functions.
412 The UCB1400 is an AC97 audio codec.
414 To compile this driver as a module, choose M here: the
415 module will be called ucb1400_core.
420 config MFD_PM8921_CORE
421 tristate "Qualcomm PM8921 PMIC chip"
422 depends on (ARCH_MSM || HEXAGON)
427 If you say yes to this option, support will be included for the
428 built-in PM8921 PMIC chip.
430 This is required if your board has a PM8921 and uses its features,
431 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
433 Say M here if you want to include support for PM8921 chip as a module.
434 This will build a module called "pm8921-core".
436 config MFD_PM8XXX_IRQ
437 bool "Qualcomm PM8xxx IRQ features"
438 depends on MFD_PM8XXX
439 default y if MFD_PM8XXX
441 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
443 This is required to use certain other PM 8xxx features, such as GPIO
447 tristate "RDC R-321x southbridge"
449 depends on PCI && GENERIC_HARDIRQS
451 Say yes here if you want to have support for the RDC R-321x SoC
452 southbridge which provides access to GPIOs and Watchdog using the
453 southbridge PCI device configuration space.
456 tristate "Realtek PCI-E card reader"
457 depends on PCI && GENERIC_HARDIRQS
460 This supports for Realtek PCI-Express card reader including rts5209,
461 rts5229, rtl8411, etc. Realtek card reader supports access to many
462 types of memory cards, such as Memory Stick, Memory Stick Pro,
463 Secure Digital and MultiMediaCard.
466 bool "Ricoh RC5T583 Power Management system device"
467 depends on I2C=y && GENERIC_HARDIRQS
471 Select this option to get support for the RICOH583 Power
472 Management system device.
473 This driver provides common support for accessing the device
474 through i2c interface. The device supports multiple sub-devices
475 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
476 Additional drivers must be enabled in order to use the
477 different functionality of the device.
480 bool "SAMSUNG Electronics PMIC Series Support"
481 depends on I2C=y && GENERIC_HARDIRQS
486 Support for the Samsung Electronics MFD series.
487 This driver provides common support for accessing the device,
488 additional drivers must be enabled in order to use the functionality
491 config MFD_SI476X_CORE
492 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
497 This is the core driver for the SI476x series of AM/FM
498 radio. This MFD driver connects the radio-si476x V4L2 module
499 and the si476x audio codec.
501 To compile this driver as a module, choose M here: the
502 module will be called si476x-core.
505 tristate "Silicon Motion SM501"
507 This is the core driver for the Silicon Motion SM501 multimedia
508 companion chip. This device is a multifunction device which may
509 provide numerous interfaces including USB host controller, USB gadget,
510 asynchronous serial ports, audio functions, and a dual display video
511 interface. The device may be connected by PCI or local bus with
512 varying functions enabled.
514 config MFD_SM501_GPIO
515 bool "Export GPIO via GPIO layer"
516 depends on MFD_SM501 && GPIOLIB
518 This option uses the gpio library layer to export the 64 GPIO
519 lines on the SM501. The platform data is used to supply the
520 base number for the first GPIO line to register.
523 bool "SMSC ECE1099 series chips"
524 depends on I2C=y && GENERIC_HARDIRQS
528 If you say yes here you get support for the
529 ece1099 chips from SMSC.
531 To compile this driver as a module, choose M here: the
532 module will be called smsc.
535 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
536 default y if ARCH_U300 || ARCH_U8500
538 Say yes here if you have the ABX500 Mixed Signal IC family
539 chips. This core driver expose register access functions.
540 Functionality specific drivers using these functions can
541 remain unchanged when IC changes. Binding of the functions to
542 actual register access is done by the IC core driver.
545 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
546 depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
548 default y if ARCH_U300
550 Select this to enable the AB3100 Mixed Signal IC core
551 functionality. This connects to a AB3100 on the I2C bus
552 and expose a number of symbols needed for dependent devices
553 to read and write registers and subscribe to events from
554 this multi-functional IC. This is needed to use other features
555 of the AB3100 such as battery-backed RTC, charging control,
556 LEDs, vibrator, system power and temperature, power management
560 tristate "ST-Ericsson AB3100 OTP functions"
561 depends on AB3100_CORE
562 default y if AB3100_CORE
564 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
565 programmable memory) support. This exposes a sysfs file to read
569 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
570 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
575 Select this option to enable access to AB8500 power management
576 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
577 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
578 the irq_chip parts for handling the Mixed Signal chip events.
579 This chip embeds various other multimedia funtionalities as well.
582 bool "Enable debug info via debugfs"
583 depends on AB8500_GPADC && DEBUG_FS
584 default y if DEBUG_FS
586 Select this option if you want debug information using the debug
590 bool "ST-Ericsson AB8500 GPADC driver"
591 depends on AB8500_CORE && REGULATOR_AB8500
594 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
596 config MFD_DB8500_PRCMU
597 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
598 depends on UX500_SOC_DB8500
601 Select this option to enable support for the DB8500 Power Reset
602 and Control Management Unit. This is basically an autonomous
603 system controller running an XP70 microprocessor, which is accessed
604 through a register map.
607 bool "STMicroelectronics STMPE"
608 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
611 Support for the STMPE family of I/O Expanders from
614 Currently supported devices are:
616 STMPE811: GPIO, Touchscreen
617 STMPE1601: GPIO, Keypad
618 STMPE1801: GPIO, Keypad
619 STMPE2401: GPIO, Keypad
620 STMPE2403: GPIO, Keypad
622 This driver provides common support for accessing the device,
623 additional drivers must be enabled in order to use the functionality
624 of the device. Currently available sub drivers are:
628 Touchscreen: stmpe-ts
630 menu "STMicroelectronics STMPE Interface Drivers"
634 bool "STMicroelectronics STMPE I2C Inteface"
638 This is used to enable I2C interface of STMPE
641 bool "STMicroelectronics STMPE SPI Inteface"
642 depends on SPI_MASTER
644 This is used to enable SPI interface of STMPE
648 bool "STMicroelectronics STA2X11"
649 depends on STA2X11 && GENERIC_HARDIRQS
654 bool "System Controller Register R/W Based on Regmap"
657 Select this option to enable accessing system control registers
660 config MFD_DAVINCI_VOICECODEC
664 config MFD_TI_AM335X_TSCADC
665 tristate "TI ADC / Touch Screen chip support"
669 depends on GENERIC_HARDIRQS
671 If you say yes here you get support for Texas Instruments series
672 of Touch Screen /ADC chips.
673 To compile this driver as a module, choose M here: the
674 module will be called ti_am335x_tscadc.
676 config MFD_DM355EVM_MSP
677 bool "TI DaVinci DM355 EVM microcontroller"
678 depends on I2C=y && MACH_DAVINCI_DM355_EVM
680 This driver supports the MSP430 microcontroller used on these
681 boards. MSP430 firmware manages resets and power sequencing,
682 inputs from buttons and the IR remote, LEDs, an RTC, and more.
685 bool "TI LP8788 Power Management Unit Driver"
686 depends on I2C=y && GENERIC_HARDIRQS
691 TI LP8788 PMU supports regulators, battery charger, RTC,
692 ADC, backlight driver and current sinks.
694 config MFD_OMAP_USB_HOST
695 bool "TI OMAP USBHS core and TLL driver"
696 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
699 This is the core driver for the OAMP EHCI and OHCI drivers.
700 This MFD driver does the required setup functionalities for
701 OMAP USB Host drivers.
704 bool "TI Palmas series chips"
708 depends on I2C=y && GENERIC_HARDIRQS
710 If you say yes here you get support for the Palmas
711 series of PMIC chips from Texas Instruments.
714 tristate "TI Sequencer Serial Port support"
715 depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
718 Say Y here if you want support for the Sequencer Serial Port
719 in a Texas Instruments TNETV107X SoC.
721 To compile this driver as a module, choose M here: the
722 module will be called ti-ssp.
725 tristate "TI TPS61050/61052 Boost Converters"
729 select REGULATOR_FIXED_VOLTAGE
730 depends on GENERIC_HARDIRQS
732 This option enables a driver for the TP61050/TPS61052
733 high-power "white LED driver". This boost converter is
734 sometimes used for other things than white LEDs, and
735 also contains a GPIO pin.
738 tristate "TI TPS6501x Power Management chips"
739 depends on I2C && GPIOLIB
740 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
742 If you say yes here you get support for the TPS6501x series of
743 Power Management chips. These include voltage regulators,
744 lithium ion/polymer battery charging, and other features that
745 are often used in portable devices like cell phones and cameras.
747 This driver can also be built as a module. If so, the module
748 will be called tps65010.
751 tristate "TI TPS6507x Power Management / Touch Screen chips"
753 depends on I2C && GENERIC_HARDIRQS
755 If you say yes here you get support for the TPS6507x series of
756 Power Management / Touch Screen chips. These include voltage
757 regulators, lithium ion/polymer battery charging, touch screen
758 and other features that are often used in portable devices.
759 This driver can also be built as a module. If so, the module
760 will be called tps6507x.
762 config TPS65911_COMPARATOR
766 bool "TI TPS65090 Power Management chips"
767 depends on I2C=y && GENERIC_HARDIRQS
772 If you say yes here you get support for the TPS65090 series of
773 Power Management chips.
774 This driver provides common support for accessing the device,
775 additional drivers must be enabled in order to use the
776 functionality of the device.
779 tristate "TI TPS65217 Power Management / White LED chips"
780 depends on I2C && GENERIC_HARDIRQS
784 If you say yes here you get support for the TPS65217 series of
785 Power Management / White LED chips.
786 These include voltage regulators, lithium ion/polymer battery
787 charger, wled and other features that are often used in portable
790 This driver can also be built as a module. If so, the module
791 will be called tps65217.
794 bool "TI TPS6586x Power Management chips"
795 depends on I2C=y && GENERIC_HARDIRQS
799 If you say yes here you get support for the TPS6586X series of
800 Power Management chips.
801 This driver provides common support for accessing the device,
802 additional drivers must be enabled in order to use the
803 functionality of the device.
805 This driver can also be built as a module. If so, the module
806 will be called tps6586x.
809 bool "TI TPS65910 Power Management chip"
810 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
816 if you say yes here you get support for the TPS65910 series of
817 Power Management chips.
820 bool "TI TPS65912 Power Management chip"
824 If you say yes here you get support for the TPS65912 series of
827 config MFD_TPS65912_I2C
828 bool "TI TPS65912 Power Management chip with I2C"
831 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
833 If you say yes here you get support for the TPS65912 series of
834 PM chips with I2C interface.
836 config MFD_TPS65912_SPI
837 bool "TI TPS65912 Power Management chip with SPI"
840 depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
842 If you say yes here you get support for the TPS65912 series of
843 PM chips with SPI interface.
846 bool "TI TPS80031/TPS80032 Power Management chips"
847 depends on I2C=y && GENERIC_HARDIRQS
852 If you say yes here you get support for the Texas Instruments
853 TPS80031/ TPS80032 Fully Integrated Power Management with Power
854 Path and Battery Charger. The device provides five configurable
855 step-down converters, 11 general purpose LDOs, USB OTG Module,
856 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
857 Power Path from USB, 32K clock generator.
860 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
861 depends on I2C=y && GENERIC_HARDIRQS
865 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
866 This core driver provides register access and IRQ handling
867 facilities, and registers devices for the various functions
868 so that function-specific drivers can bind to them.
870 These multi-function chips are found on many OMAP2 and OMAP3
871 boards, providing power management, RTC, GPIO, keypad, a
872 high speed USB OTG transceiver, an audio codec (on most
873 versions) and many other features.
876 tristate "TI TWL4030 MADC"
877 depends on TWL4030_CORE
879 This driver provides support for triton TWL4030-MADC. The
880 driver supports both RT and SW conversion methods.
882 This driver can be built as a module. If so it will be
886 bool "TI TWL4030 power resources"
887 depends on TWL4030_CORE && ARM
889 Say yes here if you want to use the power resources on the
890 TWL4030 family chips. Most of these resources are regulators,
891 which have a separate driver; some are control signals, such
892 as clock request handshaking.
894 This driver uses board-specific data to initialize the resources
895 and load scripts controlling which resources are switched off/on
896 or reset when a sleep, wakeup or warm reset event occurs.
898 config MFD_TWL4030_AUDIO
899 bool "TI TWL4030 Audio"
900 depends on TWL4030_CORE && GENERIC_HARDIRQS
905 bool "TI TWL6040 audio codec"
906 depends on I2C=y && GENERIC_HARDIRQS
912 Say yes here if you want support for Texas Instruments TWL6040 audio
914 This driver provides common support for accessing the device,
915 additional drivers must be enabled in order to use the
916 functionality of the device (audio, vibra).
919 bool "TI TWL92330/Menelaus PM chip"
920 depends on I2C=y && ARCH_OMAP2
922 If you say yes here you get support for the Texas Instruments
923 TWL92330/Menelaus Power Management chip. This include voltage
924 regulators, Dual slot memory card transceivers, real-time clock
925 and other features that are often used in portable devices like
926 cell phones and PDAs.
928 config MFD_WL1273_CORE
929 tristate "TI WL1273 FM radio"
930 depends on I2C && GENERIC_HARDIRQS
934 This is the core driver for the TI WL1273 FM radio. This MFD
935 driver connects the radio-wl1273 V4L2 module and the wl1273
939 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
943 depends on GENERIC_HARDIRQS
945 Say yes here to enable support for National Semiconductor / TI
946 LM3533 Lighting Power chips.
948 This driver provides common support for accessing the device;
949 additional drivers must be enabled in order to use the LED,
950 backlight or ambient-light-sensor functionality of the device.
952 config MFD_TIMBERDALE
953 tristate "Timberdale FPGA"
955 depends on PCI && GPIOLIB
957 This is the core driver for the timberdale FPGA. This device is a
958 multifunction device which exposes numerous platform devices.
960 The timberdale FPGA can be found on the Intel Atom development board
961 for in-vehicle infontainment, called Russellville.
964 bool "Toshiba TC35892 and variants"
965 depends on I2C=y && GENERIC_HARDIRQS
968 Support for the Toshiba TC35892 and variants I/O Expander.
970 This driver provides common support for accessing the device,
971 additional drivers must be enabled in order to use the
972 functionality of the device.
979 bool "Toshiba T7L66XB"
980 depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
984 Support for Toshiba Mobile IO Controller T7L66XB
987 bool "Toshiba TC6387XB"
988 depends on ARM && HAVE_CLK
992 Support for Toshiba Mobile IO Controller TC6387XB
995 bool "Toshiba TC6393XB"
996 depends on ARM && HAVE_CLK
1001 Support for Toshiba Mobile IO Controller TC6393XB
1004 tristate "VIA VX855/VX875 integrated south bridge"
1005 depends on PCI && GENERIC_HARDIRQS
1008 Say yes here to enable support for various functions of the
1009 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1010 and/or vx855_gpio drivers for this to do anything useful.
1018 config MFD_ARIZONA_I2C
1019 tristate "Wolfson Microelectronics Arizona platform with I2C"
1023 depends on I2C && GENERIC_HARDIRQS
1025 Support for the Wolfson Microelectronics Arizona platform audio SoC
1026 core functionality controlled via I2C.
1028 config MFD_ARIZONA_SPI
1029 tristate "Wolfson Microelectronics Arizona platform with SPI"
1033 depends on SPI_MASTER && GENERIC_HARDIRQS
1035 Support for the Wolfson Microelectronics Arizona platform audio SoC
1036 core functionality controlled via I2C.
1039 bool "Wolfson Microelectronics WM5102"
1040 depends on MFD_ARIZONA
1042 Support for Wolfson Microelectronics WM5102 low power audio SoC
1045 bool "Wolfson Microelectronics WM5110"
1046 depends on MFD_ARIZONA
1048 Support for Wolfson Microelectronics WM5110 low power audio SoC
1051 bool "Wolfson Microelectronics WM8400"
1053 depends on I2C=y && GENERIC_HARDIRQS
1056 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1057 CODEC. This driver provides common support for accessing
1058 the device, additional drivers must be enabled in order to use
1059 the functionality of the device.
1063 depends on GENERIC_HARDIRQS
1065 config MFD_WM831X_I2C
1066 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1071 depends on I2C=y && GENERIC_HARDIRQS
1073 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1074 when controlled using I2C. This driver provides common support
1075 for accessing the device, additional drivers must be enabled in
1076 order to use the functionality of the device.
1078 config MFD_WM831X_SPI
1079 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1084 depends on SPI_MASTER && GENERIC_HARDIRQS
1086 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1087 when controlled using SPI. This driver provides common support
1088 for accessing the device, additional drivers must be enabled in
1089 order to use the functionality of the device.
1093 depends on GENERIC_HARDIRQS
1095 config MFD_WM8350_I2C
1096 bool "Wolfson Microelectronics WM8350 with I2C"
1098 depends on I2C=y && GENERIC_HARDIRQS
1100 The WM8350 is an integrated audio and power management
1101 subsystem with watchdog and RTC functionality for embedded
1102 systems. This option enables core support for the WM8350 with
1103 I2C as the control interface. Additional options must be
1104 selected to enable support for the functionality of the chip.
1107 bool "Wolfson Microelectronics WM8994"
1111 depends on I2C=y && GENERIC_HARDIRQS
1113 The WM8994 is a highly integrated hi-fi CODEC designed for
1114 smartphone applicatiosn. As well as audio functionality it
1115 has on board GPIO and regulator functionality which is
1116 supported via the relevant subsystems. This driver provides
1117 core support for the WM8994, in order to use the actual
1118 functionaltiy of the device other drivers must be enabled.
1123 menu "Multimedia Capabilities Port drivers"
1124 depends on ARCH_SA1100
1131 tristate "Support SA11x0 MCP interface"
1132 depends on ARCH_SA1100
1137 bool "Support for UCB1200 / UCB1300"
1138 depends on MCP_SA11X0
1141 config MCP_UCB1200_TS
1142 tristate "Touchscreen interface support"
1143 depends on MCP_UCB1200 && INPUT
1147 config VEXPRESS_CONFIG
1150 Platform configuration infrastructure for the ARM Ltd.