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
167 If you say yes here you get support for the TPS6586X series of
168 Power Management chips.
169 This driver provides common support for accessing the device,
170 additional drivers must be enabled in order to use the
171 functionality of the device.
173 This driver can also be built as a module. If so, the module
174 will be called tps6586x.
177 bool "TPS65910 Power Management chip"
178 depends on I2C=y && GPIOLIB
183 if you say yes here you get support for the TPS65910 series of
184 Power Management chips.
190 config MFD_TPS65912_I2C
191 bool "TPS65912 Power Management chip with I2C"
194 depends on I2C=y && GPIOLIB
196 If you say yes here you get support for the TPS65912 series of
197 PM chips with I2C interface.
199 config MFD_TPS65912_SPI
200 bool "TPS65912 Power Management chip with SPI"
203 depends on SPI_MASTER && GPIOLIB
205 If you say yes here you get support for the TPS65912 series of
206 PM chips with SPI interface.
209 bool "Texas Instruments TWL92330/Menelaus PM chip"
210 depends on I2C=y && ARCH_OMAP2
212 If you say yes here you get support for the Texas Instruments
213 TWL92330/Menelaus Power Management chip. This include voltage
214 regulators, Dual slot memory card transceivers, real-time clock
215 and other features that are often used in portable devices like
216 cell phones and PDAs.
219 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
220 depends on I2C=y && GENERIC_HARDIRQS
223 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
224 This core driver provides register access and IRQ handling
225 facilities, and registers devices for the various functions
226 so that function-specific drivers can bind to them.
228 These multi-function chips are found on many OMAP2 and OMAP3
229 boards, providing power management, RTC, GPIO, keypad, a
230 high speed USB OTG transceiver, an audio codec (on most
231 versions) and many other features.
234 tristate "Texas Instruments TWL4030 MADC"
235 depends on TWL4030_CORE
237 This driver provides support for triton TWL4030-MADC. The
238 driver supports both RT and SW conversion methods.
240 This driver can be built as a module. If so it will be
244 bool "Support power resources on TWL4030 family chips"
245 depends on TWL4030_CORE && ARM
247 Say yes here if you want to use the power resources on the
248 TWL4030 family chips. Most of these resources are regulators,
249 which have a separate driver; some are control signals, such
250 as clock request handshaking.
252 This driver uses board-specific data to initialize the resources
253 and load scripts controlling which resources are switched off/on
254 or reset when a sleep, wakeup or warm reset event occurs.
256 config MFD_TWL4030_AUDIO
258 depends on TWL4030_CORE
263 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
264 depends on TWL4030_CORE
268 Say yes here if you want support for TWL6030 PWM.
269 This is used to control charging LED brightness.
272 bool "Support for TWL6040 audio codec"
273 depends on I2C=y && GENERIC_HARDIRQS
278 Say yes here if you want support for Texas Instruments TWL6040 audio
280 This driver provides common support for accessing the device,
281 additional drivers must be enabled in order to use the
282 functionality of the device (audio, vibra).
285 bool "Support STMicroelectronics STMPE"
286 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
289 Support for the STMPE family of I/O Expanders from
292 Currently supported devices are:
294 STMPE811: GPIO, Touchscreen
295 STMPE1601: GPIO, Keypad
296 STMPE2401: GPIO, Keypad
297 STMPE2403: GPIO, Keypad
299 This driver provides common support for accessing the device,
300 additional drivers must be enabled in order to use the functionality
301 of the device. Currently available sub drivers are:
305 Touchscreen: stmpe-ts
307 menu "STMPE Interface Drivers"
311 bool "STMPE I2C Inteface"
315 This is used to enable I2C interface of STMPE
318 bool "STMPE SPI Inteface"
319 depends on SPI_MASTER
321 This is used to enable SPI interface of STMPE
325 bool "Support Toshiba TC35892 and variants"
326 depends on I2C=y && GENERIC_HARDIRQS
329 Support for the Toshiba TC35892 and variants I/O Expander.
331 This driver provides common support for accessing the device,
332 additional drivers must be enabled in order to use the
333 functionality of the device.
340 bool "Support Toshiba T7L66XB"
341 depends on ARM && HAVE_CLK
345 Support for Toshiba Mobile IO Controller T7L66XB
348 bool "Support Toshiba TC6387XB"
349 depends on ARM && HAVE_CLK
353 Support for Toshiba Mobile IO Controller TC6387XB
356 bool "Support Toshiba TC6393XB"
357 depends on GPIOLIB && ARM && HAVE_CLK
361 Support for Toshiba Mobile IO Controller TC6393XB
364 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
367 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
368 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
369 usually found on PXA processors-based platforms. This includes
370 the I2C driver and the core APIs _only_, you have to select
371 individual components like LCD backlight, voltage regulators,
372 LEDs and battery-charger under the corresponding menus.
378 config MFD_DA9052_SPI
379 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
383 depends on SPI_MASTER=y
385 Support for the Dialog Semiconductor DA9052 PMIC
386 when controlled using SPI. This driver provides common support
387 for accessing the device, additional drivers must be enabled in
388 order to use the functionality of the device.
390 config MFD_DA9052_I2C
391 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
397 Support for the Dialog Semiconductor DA9052 PMIC
398 when controlled using I2C. This driver provides common support
399 for accessing the device, additional drivers must be enabled in
400 order to use the functionality of the device.
403 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
406 Say yes here to add support for Analog Devices AD5520 and ADP5501,
407 Multifunction Power Management IC. This includes
408 the I2C driver and the core APIs _only_, you have to select
409 individual components like LCD backlight, LEDs, GPIOs and Kepad
410 under the corresponding menus.
413 bool "Maxim Semiconductor MAX8925 PMIC Support"
414 depends on I2C=y && GENERIC_HARDIRQS
417 Say yes here to support for Maxim Semiconductor MAX8925. This is
418 a Power Management IC. This driver provides common support for
419 accessing the device, additional drivers must be enabled in order
420 to use the functionality of the device.
423 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
424 depends on I2C=y && GENERIC_HARDIRQS
427 Say yes here to support for Maxim Semiconductor MAX8997/8966.
428 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
429 MUIC controls on chip.
430 This driver provides common support for accessing the device;
431 additional drivers must be enabled in order to use the functionality
435 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
436 depends on I2C=y && GENERIC_HARDIRQS
439 Say yes here to support for Maxim Semiconductor MAX8998 and
440 National Semiconductor LP3974. This is a Power Management IC.
441 This driver provides common support for accessing the device,
442 additional drivers must be enabled in order to use the functionality
446 bool "SAMSUNG S5M Series Support"
447 depends on I2C=y && GENERIC_HARDIRQS
451 Support for the Samsung Electronics S5M MFD series.
452 This driver provides common support for accessing the device,
453 additional drivers must be enabled in order to use the functionality
457 tristate "Support Wolfson Microelectronics WM8400"
462 Support for the Wolfson Microelecronics WM8400 PMIC and audio
463 CODEC. This driver provides common support for accessing
464 the device, additional drivers must be enabled in order to use
465 the functionality of the device.
469 depends on GENERIC_HARDIRQS
471 config MFD_WM831X_I2C
472 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
476 depends on I2C=y && GENERIC_HARDIRQS
478 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
479 when controlled using I2C. This driver provides common support
480 for accessing the device, additional drivers must be enabled in
481 order to use the functionality of the device.
483 config MFD_WM831X_SPI
484 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
488 depends on SPI_MASTER && GENERIC_HARDIRQS
490 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
491 when controlled using SPI. This driver provides common support
492 for accessing the device, additional drivers must be enabled in
493 order to use the functionality of the device.
497 depends on GENERIC_HARDIRQS
499 config MFD_WM8350_CONFIG_MODE_0
501 depends on MFD_WM8350
503 config MFD_WM8350_CONFIG_MODE_1
505 depends on MFD_WM8350
507 config MFD_WM8350_CONFIG_MODE_2
509 depends on MFD_WM8350
511 config MFD_WM8350_CONFIG_MODE_3
513 depends on MFD_WM8350
515 config MFD_WM8351_CONFIG_MODE_0
517 depends on MFD_WM8350
519 config MFD_WM8351_CONFIG_MODE_1
521 depends on MFD_WM8350
523 config MFD_WM8351_CONFIG_MODE_2
525 depends on MFD_WM8350
527 config MFD_WM8351_CONFIG_MODE_3
529 depends on MFD_WM8350
531 config MFD_WM8352_CONFIG_MODE_0
533 depends on MFD_WM8350
535 config MFD_WM8352_CONFIG_MODE_1
537 depends on MFD_WM8350
539 config MFD_WM8352_CONFIG_MODE_2
541 depends on MFD_WM8350
543 config MFD_WM8352_CONFIG_MODE_3
545 depends on MFD_WM8350
547 config MFD_WM8350_I2C
548 bool "Support Wolfson Microelectronics WM8350 with I2C"
550 depends on I2C=y && GENERIC_HARDIRQS
552 The WM8350 is an integrated audio and power management
553 subsystem with watchdog and RTC functionality for embedded
554 systems. This option enables core support for the WM8350 with
555 I2C as the control interface. Additional options must be
556 selected to enable support for the functionality of the chip.
559 bool "Support Wolfson Microelectronics WM8994"
563 depends on I2C=y && GENERIC_HARDIRQS
565 The WM8994 is a highly integrated hi-fi CODEC designed for
566 smartphone applicatiosn. As well as audio functionality it
567 has on board GPIO and regulator functionality which is
568 supported via the relevant subsystems. This driver provides
569 core support for the WM8994, in order to use the actual
570 functionaltiy of the device other drivers must be enabled.
573 tristate "Support for NXP PCF50633"
577 Say yes here if you have NXP PCF50633 chip on your board.
578 This core driver provides register access and IRQ handling
579 facilities, and registers devices for the various functions
580 so that function-specific drivers can bind to them.
583 tristate "Support for NXP PCF50633 ADC"
584 depends on MFD_PCF50633
586 Say yes here if you want to include support for ADC in the
590 tristate "Support for NXP PCF50633 GPIO"
591 depends on MFD_PCF50633
593 Say yes here if you want to include support GPIO for pins on
600 tristate "Support Freescale MC13783 and MC13892"
601 depends on SPI_MASTER
605 Support for the Freescale (Atlas) PMIC and audio CODECs
607 This driver provides common support for accessing the device,
608 additional drivers must be enabled in order to use the
609 functionality of the device.
612 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
613 default y if ARCH_U300 || ARCH_U8500
615 Say yes here if you have the ABX500 Mixed Signal IC family
616 chips. This core driver expose register access functions.
617 Functionality specific drivers using these functions can
618 remain unchanged when IC changes. Binding of the functions to
619 actual register access is done by the IC core driver.
622 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
623 depends on I2C=y && ABX500_CORE
625 default y if ARCH_U300
627 Select this to enable the AB3100 Mixed Signal IC core
628 functionality. This connects to a AB3100 on the I2C bus
629 and expose a number of symbols needed for dependent devices
630 to read and write registers and subscribe to events from
631 this multi-functional IC. This is needed to use other features
632 of the AB3100 such as battery-backed RTC, charging control,
633 LEDs, vibrator, system power and temperature, power management
637 tristate "ST-Ericsson AB3100 OTP functions"
638 depends on AB3100_CORE
639 default y if AB3100_CORE
641 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
642 programmable memory) support. This exposes a sysfs file to read
647 depends on GENERIC_HARDIRQS && SPI_MASTER
649 This enables the PCAP ASIC present on EZX Phones. This is
650 needed for MMC, TouchScreen, Sound, USB, etc..
653 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
654 depends on GENERIC_HARDIRQS && ABX500_CORE
657 Select this option to enable access to AB8500 power management
658 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
659 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
660 the irq_chip parts for handling the Mixed Signal chip events.
661 This chip embeds various other multimedia funtionalities as well.
663 config AB8500_I2C_CORE
664 bool "AB8500 register access via PRCMU I2C"
665 depends on AB8500_CORE && MFD_DB8500_PRCMU
668 This enables register access to the AB8500 chip via PRCMU I2C.
669 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
670 the I2C bus is connected to the Power Reset
671 and Mangagement Unit, PRCMU.
674 bool "Enable debug info via debugfs"
675 depends on AB8500_CORE && DEBUG_FS
676 default y if DEBUG_FS
678 Select this option if you want debug information using the debug
682 bool "AB8500 GPADC driver"
683 depends on AB8500_CORE && REGULATOR_AB8500
686 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
688 config MFD_DB8500_PRCMU
689 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
690 depends on UX500_SOC_DB8500
693 Select this option to enable support for the DB8500 Power Reset
694 and Control Management Unit. This is basically an autonomous
695 system controller running an XP70 microprocessor, which is accessed
696 through a register map.
699 tristate "Support for CS5535 and CS5536 southbridge core functions"
701 depends on PCI && X86
703 This is the core driver for CS5535/CS5536 MFD functions. This is
704 necessary for using the board's GPIO and MFGPT functionality.
706 config MFD_TIMBERDALE
707 tristate "Support for the Timberdale FPGA"
709 depends on PCI && GPIOLIB
711 This is the core driver for the timberdale FPGA. This device is a
712 multifunction device which exposes numerous platform devices.
714 The timberdale FPGA can be found on the Intel Atom development board
715 for in-vehicle infontainment, called Russellville.
718 tristate "Intel SCH LPC"
722 LPC bridge function of the Intel SCH provides support for
723 System Management Bus and General Purpose I/O.
726 tristate "Support for RDC-R321x southbridge"
730 Say yes here if you want to have support for the RDC R-321x SoC
731 southbridge which provides access to GPIOs and Watchdog using the
732 southbridge PCI device configuration space.
734 config MFD_JANZ_CMODIO
735 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
739 This is the core driver for the Janz CMOD-IO PCI MODULbus
740 carrier board. This device is a PCI to MODULbus bridge which may
741 host many different types of MODULbus daughterboards, including
742 CAN and GPIO controllers.
744 config MFD_JZ4740_ADC
745 bool "Support for the JZ4740 SoC ADC core"
747 select GENERIC_IRQ_CHIP
748 depends on MACH_JZ4740
750 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
751 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
754 tristate "Support for VIA VX855/VX875 integrated south bridge"
758 Say yes here to enable support for various functions of the
759 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
760 and/or vx855_gpio drivers for this to do anything useful.
762 config MFD_WL1273_CORE
763 tristate "Support for TI WL1273 FM radio."
768 This is the core driver for the TI WL1273 FM radio. This MFD
769 driver connects the radio-wl1273 V4L2 module and the wl1273
772 config MFD_OMAP_USB_HOST
773 bool "Support OMAP USBHS core driver"
774 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
777 This is the core driver for the OAMP EHCI and OHCI drivers.
778 This MFD driver does the required setup functionalities for
779 OMAP USB Host drivers.
784 config MFD_PM8921_CORE
785 tristate "Qualcomm PM8921 PMIC chip"
790 If you say yes to this option, support will be included for the
791 built-in PM8921 PMIC chip.
793 This is required if your board has a PM8921 and uses its features,
794 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
796 Say M here if you want to include support for PM8921 chip as a module.
797 This will build a module called "pm8921-core".
799 config MFD_PM8XXX_IRQ
800 bool "Support for Qualcomm PM8xxx IRQ features"
801 depends on MFD_PM8XXX
802 default y if MFD_PM8XXX
804 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
806 This is required to use certain other PM 8xxx features, such as GPIO
809 config TPS65911_COMPARATOR
813 bool "TPS65090 Power Management chips"
814 depends on I2C=y && GENERIC_HARDIRQS
818 If you say yes here you get support for the TPS65090 series of
819 Power Management chips.
820 This driver provides common support for accessing the device,
821 additional drivers must be enabled in order to use the
822 functionality of the device.
824 config MFD_AAT2870_CORE
825 bool "Support for the AnalogicTech AAT2870"
827 depends on I2C=y && GPIOLIB
829 If you say yes here you get support for the AAT2870.
830 This driver provides common support for accessing the device,
831 additional drivers must be enabled in order to use the
832 functionality of the device.
834 config MFD_INTEL_MSIC
835 bool "Support for Intel MSIC"
836 depends on INTEL_SCU_IPC
839 Select this option to enable access to Intel MSIC (Avatele
840 Passage) chip. This chip embeds audio, battery, GPIO, etc.
841 devices used in Intel Medfield platforms.
844 bool "Ricoh RC5T583 Power Management system device"
845 depends on I2C=y && GENERIC_HARDIRQS
849 Select this option to get support for the RICOH583 Power
850 Management system device.
851 This driver provides common support for accessing the device
852 through i2c interface. The device supports multiple sub-devices
853 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
854 Additional drivers must be enabled in order to use the
855 different functionality of the device.
858 bool "Support for Freescale i.MX on-chip ANATOP controller"
861 Select this option to enable Freescale i.MX on-chip ANATOP
862 MFD controller. This controller embeds regulator and
863 thermal devices for Freescale i.MX platforms.
866 bool "Support for the TI Palmas series chips"
872 If you say yes here you get support for the Palmas
873 series of PMIC chips from Texas Instruments.
878 menu "Multimedia Capabilities Port drivers"
879 depends on ARCH_SA1100
886 tristate "Support SA11x0 MCP interface"
887 depends on ARCH_SA1100
892 bool "Support for UCB1200 / UCB1300"
893 depends on MCP_SA11X0
896 config MCP_UCB1200_TS
897 tristate "Touchscreen interface support"
898 depends on MCP_UCB1200 && INPUT