2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
18 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
19 This includes the I2C driver and the core APIs _only_, you have to
20 select individual components like voltage regulators, RTC and
21 battery-charger under the corresponding menus.
24 tristate "Support for Silicon Motion SM501"
26 This is the core driver for the Silicon Motion SM501 multimedia
27 companion chip. This device is a multifunction device which may
28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
34 bool "Export GPIO via GPIO layer"
35 depends on MFD_SM501 && GPIOLIB
37 This option uses the gpio library layer to export the 64 GPIO
38 lines on the SM501. The platform data is used to supply the
39 base number for the first GPIO line to register.
42 bool "Support for Compaq ASIC3"
43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
49 config MFD_DAVINCI_VOICECODEC
53 config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
57 This driver supports the MSP430 microcontroller used on these
58 boards. MSP430 firmware manages resets and power sequencing,
59 inputs from buttons and the IR remote, LEDs, an RTC, and more.
62 tristate "TI Sequencer Serial Port support"
63 depends on ARCH_DAVINCI_TNETV107X
66 Say Y here if you want support for the Sequencer Serial Port
67 in a Texas Instruments TNETV107X SoC.
69 To compile this driver as a module, choose M here: the
70 module will be called ti-ssp.
73 bool "HTC EGPIO support"
74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
76 This driver supports the CPLD egpio chip present on
77 several HTC phones. It provides basic support for input
78 pins, output pins, and irqs.
81 tristate "HTC PASIC3 LED/DS1WM chip support"
84 This core driver provides register access for the LED/DS1WM
85 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
86 HTC Magician devices, respectively. Actual functionality is
87 handled by the leds-pasic3 and ds1wm drivers.
90 bool "HTC I2C PLD chip support"
91 depends on I2C=y && GPIOLIB
93 If you say yes here you get support for the supposed CPLD
94 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
95 This device provides input and output GPIOs through an I2C
96 interface to one or more sub-chips.
99 tristate "Philips UCB1400 Core driver"
103 This enables support for the Philips UCB1400 core functions.
104 The UCB1400 is an AC97 audio codec.
106 To compile this driver as a module, choose M here: the
107 module will be called ucb1400_core.
110 tristate "TPS61050/61052 Boost Converters"
114 select REGULATOR_FIXED_VOLTAGE
116 This option enables a driver for the TP61050/TPS61052
117 high-power "white LED driver". This boost converter is
118 sometimes used for other things than white LEDs, and
119 also contains a GPIO pin.
122 tristate "TPS6501x Power Management chips"
123 depends on I2C && GPIOLIB
124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
126 If you say yes here you get support for the TPS6501x series of
127 Power Management chips. These include voltage regulators,
128 lithium ion/polymer battery charging, and other features that
129 are often used in portable devices like cell phones and cameras.
131 This driver can also be built as a module. If so, the module
132 will be called tps65010.
135 tristate "TPS6507x Power Management / Touch Screen chips"
139 If you say yes here you get support for the TPS6507x series of
140 Power Management / Touch Screen chips. These include voltage
141 regulators, lithium ion/polymer battery charging, touch screen
142 and other features that are often used in portable devices.
143 This driver can also be built as a module. If so, the module
144 will be called tps6507x.
147 tristate "TPS65217 Power Management / White LED chips"
152 If you say yes here you get support for the TPS65217 series of
153 Power Management / White LED chips.
154 These include voltage regulators, lithium ion/polymer battery
155 charger, wled and other features that are often used in portable
158 This driver can also be built as a module. If so, the module
159 will be called tps65217.
162 bool "TPS6586x Power Management chips"
163 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
166 If you say yes here you get support for the TPS6586X series of
167 Power Management chips.
168 This driver provides common support for accessing the device,
169 additional drivers must be enabled in order to use the
170 functionality of the device.
172 This driver can also be built as a module. If so, the module
173 will be called tps6586x.
176 bool "TPS65910 Power Management chip"
177 depends on I2C=y && GPIOLIB
182 if you say yes here you get support for the TPS65910 series of
183 Power Management chips.
189 config MFD_TPS65912_I2C
190 bool "TPS65912 Power Management chip with I2C"
193 depends on I2C=y && GPIOLIB
195 If you say yes here you get support for the TPS65912 series of
196 PM chips with I2C interface.
198 config MFD_TPS65912_SPI
199 bool "TPS65912 Power Management chip with SPI"
202 depends on SPI_MASTER && GPIOLIB
204 If you say yes here you get support for the TPS65912 series of
205 PM chips with SPI interface.
208 bool "Texas Instruments TWL92330/Menelaus PM chip"
209 depends on I2C=y && ARCH_OMAP2
211 If you say yes here you get support for the Texas Instruments
212 TWL92330/Menelaus Power Management chip. This include voltage
213 regulators, Dual slot memory card transceivers, real-time clock
214 and other features that are often used in portable devices like
215 cell phones and PDAs.
218 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
219 depends on I2C=y && GENERIC_HARDIRQS
221 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
222 This core driver provides register access and IRQ handling
223 facilities, and registers devices for the various functions
224 so that function-specific drivers can bind to them.
226 These multi-function chips are found on many OMAP2 and OMAP3
227 boards, providing power management, RTC, GPIO, keypad, a
228 high speed USB OTG transceiver, an audio codec (on most
229 versions) and many other features.
232 tristate "Texas Instruments TWL4030 MADC"
233 depends on TWL4030_CORE
235 This driver provides support for triton TWL4030-MADC. The
236 driver supports both RT and SW conversion methods.
238 This driver can be built as a module. If so it will be
242 bool "Support power resources on TWL4030 family chips"
243 depends on TWL4030_CORE && ARM
245 Say yes here if you want to use the power resources on the
246 TWL4030 family chips. Most of these resources are regulators,
247 which have a separate driver; some are control signals, such
248 as clock request handshaking.
250 This driver uses board-specific data to initialize the resources
251 and load scripts controlling which resources are switched off/on
252 or reset when a sleep, wakeup or warm reset event occurs.
254 config MFD_TWL4030_AUDIO
256 depends on TWL4030_CORE
261 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
262 depends on TWL4030_CORE
266 Say yes here if you want support for TWL6030 PWM.
267 This is used to control charging LED brightness.
271 depends on TWL4030_CORE && GENERIC_HARDIRQS
276 bool "Support STMicroelectronics STMPE"
277 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
280 Support for the STMPE family of I/O Expanders from
283 Currently supported devices are:
285 STMPE811: GPIO, Touchscreen
286 STMPE1601: GPIO, Keypad
287 STMPE2401: GPIO, Keypad
288 STMPE2403: GPIO, Keypad
290 This driver provides common support for accessing the device,
291 additional drivers must be enabled in order to use the functionality
292 of the device. Currently available sub drivers are:
296 Touchscreen: stmpe-ts
298 menu "STMPE Interface Drivers"
302 bool "STMPE I2C Inteface"
306 This is used to enable I2C interface of STMPE
309 bool "STMPE SPI Inteface"
310 depends on SPI_MASTER
312 This is used to enable SPI interface of STMPE
316 bool "Support Toshiba TC35892 and variants"
317 depends on I2C=y && GENERIC_HARDIRQS
320 Support for the Toshiba TC35892 and variants I/O Expander.
322 This driver provides common support for accessing the device,
323 additional drivers must be enabled in order to use the
324 functionality of the device.
331 bool "Support Toshiba T7L66XB"
332 depends on ARM && HAVE_CLK
336 Support for Toshiba Mobile IO Controller T7L66XB
339 bool "Support Toshiba TC6387XB"
340 depends on ARM && HAVE_CLK
344 Support for Toshiba Mobile IO Controller TC6387XB
347 bool "Support Toshiba TC6393XB"
348 depends on GPIOLIB && ARM && HAVE_CLK
352 Support for Toshiba Mobile IO Controller TC6393XB
355 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
358 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
359 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
360 usually found on PXA processors-based platforms. This includes
361 the I2C driver and the core APIs _only_, you have to select
362 individual components like LCD backlight, voltage regulators,
363 LEDs and battery-charger under the corresponding menus.
369 config MFD_DA9052_SPI
370 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
374 depends on SPI_MASTER=y
376 Support for the Dialog Semiconductor DA9052 PMIC
377 when controlled using SPI. This driver provides common support
378 for accessing the device, additional drivers must be enabled in
379 order to use the functionality of the device.
381 config MFD_DA9052_I2C
382 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
388 Support for the Dialog Semiconductor DA9052 PMIC
389 when controlled using I2C. This driver provides common support
390 for accessing the device, additional drivers must be enabled in
391 order to use the functionality of the device.
394 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
397 Say yes here to add support for Analog Devices AD5520 and ADP5501,
398 Multifunction Power Management IC. This includes
399 the I2C driver and the core APIs _only_, you have to select
400 individual components like LCD backlight, LEDs, GPIOs and Kepad
401 under the corresponding menus.
404 bool "Maxim Semiconductor MAX8925 PMIC Support"
405 depends on I2C=y && GENERIC_HARDIRQS
408 Say yes here to support for Maxim Semiconductor MAX8925. This is
409 a Power Management IC. This driver provies common support for
410 accessing the device, additional drivers must be enabled in order
411 to use the functionality of the device.
414 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
415 depends on I2C=y && GENERIC_HARDIRQS
418 Say yes here to support for Maxim Semiconductor MAX8997/8966.
419 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
420 MUIC controls on chip.
421 This driver provides common support for accessing the device;
422 additional drivers must be enabled in order to use the functionality
426 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
427 depends on I2C=y && GENERIC_HARDIRQS
430 Say yes here to support for Maxim Semiconductor MAX8998 and
431 National Semiconductor LP3974. This is a Power Management IC.
432 This driver provies common support for accessing the device,
433 additional drivers must be enabled in order to use the functionality
437 bool "SAMSUNG S5M Series Support"
438 depends on I2C=y && GENERIC_HARDIRQS
442 Support for the Samsung Electronics S5M MFD series.
443 This driver provies common support for accessing the device,
444 additional drivers must be enabled in order to use the functionality
448 tristate "Support Wolfson Microelectronics WM8400"
453 Support for the Wolfson Microelecronics WM8400 PMIC and audio
454 CODEC. This driver provides common support for accessing
455 the device, additional drivers must be enabled in order to use
456 the functionality of the device.
460 depends on GENERIC_HARDIRQS
462 config MFD_WM831X_I2C
463 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
467 depends on I2C=y && GENERIC_HARDIRQS
469 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
470 when controlled using I2C. This driver provides common support
471 for accessing the device, additional drivers must be enabled in
472 order to use the functionality of the device.
474 config MFD_WM831X_SPI
475 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
479 depends on SPI_MASTER && GENERIC_HARDIRQS
481 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
482 when controlled using SPI. This driver provides common support
483 for accessing the device, additional drivers must be enabled in
484 order to use the functionality of the device.
488 depends on GENERIC_HARDIRQS
490 config MFD_WM8350_CONFIG_MODE_0
492 depends on MFD_WM8350
494 config MFD_WM8350_CONFIG_MODE_1
496 depends on MFD_WM8350
498 config MFD_WM8350_CONFIG_MODE_2
500 depends on MFD_WM8350
502 config MFD_WM8350_CONFIG_MODE_3
504 depends on MFD_WM8350
506 config MFD_WM8351_CONFIG_MODE_0
508 depends on MFD_WM8350
510 config MFD_WM8351_CONFIG_MODE_1
512 depends on MFD_WM8350
514 config MFD_WM8351_CONFIG_MODE_2
516 depends on MFD_WM8350
518 config MFD_WM8351_CONFIG_MODE_3
520 depends on MFD_WM8350
522 config MFD_WM8352_CONFIG_MODE_0
524 depends on MFD_WM8350
526 config MFD_WM8352_CONFIG_MODE_1
528 depends on MFD_WM8350
530 config MFD_WM8352_CONFIG_MODE_2
532 depends on MFD_WM8350
534 config MFD_WM8352_CONFIG_MODE_3
536 depends on MFD_WM8350
538 config MFD_WM8350_I2C
539 bool "Support Wolfson Microelectronics WM8350 with I2C"
541 depends on I2C=y && GENERIC_HARDIRQS
543 The WM8350 is an integrated audio and power management
544 subsystem with watchdog and RTC functionality for embedded
545 systems. This option enables core support for the WM8350 with
546 I2C as the control interface. Additional options must be
547 selected to enable support for the functionality of the chip.
550 bool "Support Wolfson Microelectronics WM8994"
554 depends on I2C=y && GENERIC_HARDIRQS
556 The WM8994 is a highly integrated hi-fi CODEC designed for
557 smartphone applicatiosn. As well as audio functionality it
558 has on board GPIO and regulator functionality which is
559 supported via the relevant subsystems. This driver provides
560 core support for the WM8994, in order to use the actual
561 functionaltiy of the device other drivers must be enabled.
564 tristate "Support for NXP PCF50633"
568 Say yes here if you have NXP PCF50633 chip on your board.
569 This core driver provides register access and IRQ handling
570 facilities, and registers devices for the various functions
571 so that function-specific drivers can bind to them.
574 tristate "Support for NXP PCF50633 ADC"
575 depends on MFD_PCF50633
577 Say yes here if you want to include support for ADC in the
581 tristate "Support for NXP PCF50633 GPIO"
582 depends on MFD_PCF50633
584 Say yes here if you want to include support GPIO for pins on
591 tristate "Support Freescale MC13783 and MC13892"
592 depends on SPI_MASTER
596 Support for the Freescale (Atlas) PMIC and audio CODECs
598 This driver provides common support for accessing the device,
599 additional drivers must be enabled in order to use the
600 functionality of the device.
603 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
604 default y if ARCH_U300 || ARCH_U8500
606 Say yes here if you have the ABX500 Mixed Signal IC family
607 chips. This core driver expose register access functions.
608 Functionality specific drivers using these functions can
609 remain unchanged when IC changes. Binding of the functions to
610 actual register access is done by the IC core driver.
613 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
614 depends on I2C=y && ABX500_CORE
616 default y if ARCH_U300
618 Select this to enable the AB3100 Mixed Signal IC core
619 functionality. This connects to a AB3100 on the I2C bus
620 and expose a number of symbols needed for dependent devices
621 to read and write registers and subscribe to events from
622 this multi-functional IC. This is needed to use other features
623 of the AB3100 such as battery-backed RTC, charging control,
624 LEDs, vibrator, system power and temperature, power management
628 tristate "ST-Ericsson AB3100 OTP functions"
629 depends on AB3100_CORE
630 default y if AB3100_CORE
632 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
633 programmable memory) support. This exposes a sysfs file to read
638 depends on GENERIC_HARDIRQS && SPI_MASTER
640 This enables the PCAP ASIC present on EZX Phones. This is
641 needed for MMC, TouchScreen, Sound, USB, etc..
644 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
645 depends on ABX500_CORE && MFD_DB5500_PRCMU
648 Select this option to enable access to AB5500 power management
649 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
650 This chip embeds various other multimedia funtionalities as well.
653 bool "Enable debug info via debugfs"
654 depends on AB5500_CORE && DEBUG_FS
655 default y if DEBUG_FS
657 Select this option if you want debug information from the AB5500
658 using the debug filesystem, debugfs.
661 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
662 depends on GENERIC_HARDIRQS && ABX500_CORE
665 Select this option to enable access to AB8500 power management
666 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
667 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
668 the irq_chip parts for handling the Mixed Signal chip events.
669 This chip embeds various other multimedia funtionalities as well.
671 config AB8500_I2C_CORE
672 bool "AB8500 register access via PRCMU I2C"
673 depends on AB8500_CORE && MFD_DB8500_PRCMU
676 This enables register access to the AB8500 chip via PRCMU I2C.
677 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
678 the I2C bus is connected to the Power Reset
679 and Mangagement Unit, PRCMU.
682 bool "Enable debug info via debugfs"
683 depends on AB8500_CORE && DEBUG_FS
684 default y if DEBUG_FS
686 Select this option if you want debug information using the debug
690 bool "AB8500 GPADC driver"
691 depends on AB8500_CORE && REGULATOR_AB8500
694 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
696 config MFD_DB8500_PRCMU
697 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
698 depends on UX500_SOC_DB8500
701 Select this option to enable support for the DB8500 Power Reset
702 and Control Management Unit. This is basically an autonomous
703 system controller running an XP70 microprocessor, which is accessed
704 through a register map.
706 config MFD_DB5500_PRCMU
707 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
708 depends on UX500_SOC_DB5500
711 Select this option to enable support for the DB5500 Power Reset
712 and Control Management Unit. This is basically an autonomous
713 system controller running an XP70 microprocessor, which is accessed
714 through a register map.
717 tristate "Support for CS5535 and CS5536 southbridge core functions"
719 depends on PCI && X86
721 This is the core driver for CS5535/CS5536 MFD functions. This is
722 necessary for using the board's GPIO and MFGPT functionality.
724 config MFD_TIMBERDALE
725 tristate "Support for the Timberdale FPGA"
727 depends on PCI && GPIOLIB
729 This is the core driver for the timberdale FPGA. This device is a
730 multifunction device which exposes numerous platform devices.
732 The timberdale FPGA can be found on the Intel Atom development board
733 for in-vehicle infontainment, called Russellville.
736 tristate "Intel SCH LPC"
740 LPC bridge function of the Intel SCH provides support for
741 System Management Bus and General Purpose I/O.
744 tristate "Support for RDC-R321x southbridge"
748 Say yes here if you want to have support for the RDC R-321x SoC
749 southbridge which provides access to GPIOs and Watchdog using the
750 southbridge PCI device configuration space.
752 config MFD_JANZ_CMODIO
753 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
757 This is the core driver for the Janz CMOD-IO PCI MODULbus
758 carrier board. This device is a PCI to MODULbus bridge which may
759 host many different types of MODULbus daughterboards, including
760 CAN and GPIO controllers.
762 config MFD_JZ4740_ADC
763 bool "Support for the JZ4740 SoC ADC core"
765 select GENERIC_IRQ_CHIP
766 depends on MACH_JZ4740
768 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
769 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
772 tristate "Support for VIA VX855/VX875 integrated south bridge"
776 Say yes here to enable support for various functions of the
777 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
778 and/or vx855_gpio drivers for this to do anything useful.
780 config MFD_WL1273_CORE
781 tristate "Support for TI WL1273 FM radio."
786 This is the core driver for the TI WL1273 FM radio. This MFD
787 driver connects the radio-wl1273 V4L2 module and the wl1273
790 config MFD_OMAP_USB_HOST
791 bool "Support OMAP USBHS core driver"
792 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
795 This is the core driver for the OAMP EHCI and OHCI drivers.
796 This MFD driver does the required setup functionalities for
797 OMAP USB Host drivers.
802 config MFD_PM8921_CORE
803 tristate "Qualcomm PM8921 PMIC chip"
808 If you say yes to this option, support will be included for the
809 built-in PM8921 PMIC chip.
811 This is required if your board has a PM8921 and uses its features,
812 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
814 Say M here if you want to include support for PM8921 chip as a module.
815 This will build a module called "pm8921-core".
817 config MFD_PM8XXX_IRQ
818 bool "Support for Qualcomm PM8xxx IRQ features"
819 depends on MFD_PM8XXX
820 default y if MFD_PM8XXX
822 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
824 This is required to use certain other PM 8xxx features, such as GPIO
827 config TPS65911_COMPARATOR
830 config MFD_AAT2870_CORE
831 bool "Support for the AnalogicTech AAT2870"
833 depends on I2C=y && GPIOLIB
835 If you say yes here you get support for the AAT2870.
836 This driver provides common support for accessing the device,
837 additional drivers must be enabled in order to use the
838 functionality of the device.
840 config MFD_INTEL_MSIC
841 bool "Support for Intel MSIC"
842 depends on INTEL_SCU_IPC
845 Select this option to enable access to Intel MSIC (Avatele
846 Passage) chip. This chip embeds audio, battery, GPIO, etc.
847 devices used in Intel Medfield platforms.
850 bool "Ricoh RC5T583 Power Management system device"
851 depends on I2C=y && GENERIC_HARDIRQS
855 Select this option to get support for the RICOH583 Power
856 Management system device.
857 This driver provides common support for accessing the device
858 through i2c interface. The device supports multiple sub-devices
859 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
860 Additional drivers must be enabled in order to use the
861 different functionality of the device.
864 bool "Support for Freescale i.MX on-chip ANATOP controller"
867 Select this option to enable Freescale i.MX on-chip ANATOP
868 MFD controller. This controller embeds regulator and
869 thermal devices for Freescale i.MX platforms.
874 menu "Multimedia Capabilities Port drivers"
875 depends on ARCH_SA1100
882 tristate "Support SA11x0 MCP interface"
883 depends on ARCH_SA1100
888 tristate "Support for UCB1200 / UCB1300"
891 config MCP_UCB1200_TS
892 tristate "Touchscreen interface support"
893 depends on MCP_UCB1200 && INPUT