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 bool "TPS6586x Power Management chips"
148 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
151 If you say yes here you get support for the TPS6586X series of
152 Power Management chips.
153 This driver provides common support for accessing the device,
154 additional drivers must be enabled in order to use the
155 functionality of the device.
157 This driver can also be built as a module. If so, the module
158 will be called tps6586x.
161 bool "TPS65910 Power Management chip"
162 depends on I2C=y && GPIOLIB
166 if you say yes here you get support for the TPS65910 series of
167 Power Management chips.
173 config MFD_TPS65912_I2C
174 bool "TPS95612 Power Management chip with I2C"
177 depends on I2C=y && GPIOLIB
179 If you say yes here you get support for the TPS65912 series of
180 PM chips with I2C interface.
182 config MFD_TPS65912_SPI
183 bool "TPS65912 Power Management chip with SPI"
186 depends on SPI_MASTER && GPIOLIB
188 If you say yes here you get support for the TPS65912 series of
189 PM chips with SPI interface.
192 bool "Texas Instruments TWL92330/Menelaus PM chip"
193 depends on I2C=y && ARCH_OMAP2
195 If you say yes here you get support for the Texas Instruments
196 TWL92330/Menelaus Power Management chip. This include voltage
197 regulators, Dual slot memory card transceivers, real-time clock
198 and other features that are often used in portable devices like
199 cell phones and PDAs.
202 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
203 depends on I2C=y && GENERIC_HARDIRQS
206 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
207 This core driver provides register access and IRQ handling
208 facilities, and registers devices for the various functions
209 so that function-specific drivers can bind to them.
211 These multi-function chips are found on many OMAP2 and OMAP3
212 boards, providing power management, RTC, GPIO, keypad, a
213 high speed USB OTG transceiver, an audio codec (on most
214 versions) and many other features.
217 tristate "Texas Instruments TWL4030 MADC"
218 depends on TWL4030_CORE
220 This driver provides support for triton TWL4030-MADC. The
221 driver supports both RT and SW conversion methods.
223 This driver can be built as a module. If so it will be
227 bool "Support power resources on TWL4030 family chips"
228 depends on TWL4030_CORE && ARM
230 Say yes here if you want to use the power resources on the
231 TWL4030 family chips. Most of these resources are regulators,
232 which have a separate driver; some are control signals, such
233 as clock request handshaking.
235 This driver uses board-specific data to initialize the resources
236 and load scripts controlling which resources are switched off/on
237 or reset when a sleep, wakeup or warm reset event occurs.
239 config MFD_TWL4030_AUDIO
241 depends on TWL4030_CORE
246 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
247 depends on TWL4030_CORE
251 Say yes here if you want support for TWL6030 PWM.
252 This is used to control charging LED brightness.
256 depends on TWL4030_CORE && GENERIC_HARDIRQS
261 bool "Support STMicroelectronics STMPE"
262 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
265 Support for the STMPE family of I/O Expanders from
268 Currently supported devices are:
270 STMPE811: GPIO, Touchscreen
271 STMPE1601: GPIO, Keypad
272 STMPE2401: GPIO, Keypad
273 STMPE2403: GPIO, Keypad
275 This driver provides common support for accessing the device,
276 additional drivers must be enabled in order to use the functionality
277 of the device. Currently available sub drivers are:
281 Touchscreen: stmpe-ts
283 menu "STMPE Interface Drivers"
287 bool "STMPE I2C Inteface"
291 This is used to enable I2C interface of STMPE
294 bool "STMPE SPI Inteface"
295 depends on SPI_MASTER
297 This is used to enable SPI interface of STMPE
301 bool "Support Toshiba TC35892 and variants"
302 depends on I2C=y && GENERIC_HARDIRQS
305 Support for the Toshiba TC35892 and variants I/O Expander.
307 This driver provides common support for accessing the device,
308 additional drivers must be enabled in order to use the
309 functionality of the device.
316 bool "Support Toshiba T7L66XB"
317 depends on ARM && HAVE_CLK
321 Support for Toshiba Mobile IO Controller T7L66XB
324 bool "Support Toshiba TC6387XB"
325 depends on ARM && HAVE_CLK
329 Support for Toshiba Mobile IO Controller TC6387XB
332 bool "Support Toshiba TC6393XB"
333 depends on GPIOLIB && ARM && HAVE_CLK
337 Support for Toshiba Mobile IO Controller TC6393XB
340 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
343 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
344 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
345 usually found on PXA processors-based platforms. This includes
346 the I2C driver and the core APIs _only_, you have to select
347 individual components like LCD backlight, voltage regulators,
348 LEDs and battery-charger under the corresponding menus.
354 config MFD_DA9052_SPI
355 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
359 depends on SPI_MASTER=y
361 Support for the Dialog Semiconductor DA9052 PMIC
362 when controlled using SPI. This driver provides common support
363 for accessing the device, additional drivers must be enabled in
364 order to use the functionality of the device.
366 config MFD_DA9052_I2C
367 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
373 Support for the Dialog Semiconductor DA9052 PMIC
374 when controlled using I2C. This driver provides common support
375 for accessing the device, additional drivers must be enabled in
376 order to use the functionality of the device.
379 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
382 Say yes here to add support for Analog Devices AD5520 and ADP5501,
383 Multifunction Power Management IC. This includes
384 the I2C driver and the core APIs _only_, you have to select
385 individual components like LCD backlight, LEDs, GPIOs and Kepad
386 under the corresponding menus.
389 bool "Maxim Semiconductor MAX8925 PMIC Support"
390 depends on I2C=y && GENERIC_HARDIRQS
393 Say yes here to support for Maxim Semiconductor MAX8925. This is
394 a Power Management IC. This driver provies common support for
395 accessing the device, additional drivers must be enabled in order
396 to use the functionality of the device.
399 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
400 depends on I2C=y && GENERIC_HARDIRQS
403 Say yes here to support for Maxim Semiconductor MAX8998/8966.
404 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
405 MUIC controls on chip.
406 This driver provides common support for accessing the device;
407 additional drivers must be enabled in order to use the functionality
411 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
412 depends on I2C=y && GENERIC_HARDIRQS
415 Say yes here to support for Maxim Semiconductor MAX8998 and
416 National Semiconductor LP3974. This is a Power Management IC.
417 This driver provies common support for accessing the device,
418 additional drivers must be enabled in order to use the functionality
422 bool "SAMSUNG S5M Series Support"
423 depends on I2C=y && GENERIC_HARDIRQS
427 Support for the Samsung Electronics S5M MFD series.
428 This driver provies common support for accessing the device,
429 additional drivers must be enabled in order to use the functionality
433 tristate "Support Wolfson Microelectronics WM8400"
438 Support for the Wolfson Microelecronics WM8400 PMIC and audio
439 CODEC. This driver provides common support for accessing
440 the device, additional drivers must be enabled in order to use
441 the functionality of the device.
445 depends on GENERIC_HARDIRQS
447 config MFD_WM831X_I2C
448 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
452 depends on I2C=y && GENERIC_HARDIRQS
454 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
455 when controlled using I2C. This driver provides common support
456 for accessing the device, additional drivers must be enabled in
457 order to use the functionality of the device.
459 config MFD_WM831X_SPI
460 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
464 depends on SPI_MASTER && GENERIC_HARDIRQS
466 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
467 when controlled using SPI. This driver provides common support
468 for accessing the device, additional drivers must be enabled in
469 order to use the functionality of the device.
473 depends on GENERIC_HARDIRQS
475 config MFD_WM8350_CONFIG_MODE_0
477 depends on MFD_WM8350
479 config MFD_WM8350_CONFIG_MODE_1
481 depends on MFD_WM8350
483 config MFD_WM8350_CONFIG_MODE_2
485 depends on MFD_WM8350
487 config MFD_WM8350_CONFIG_MODE_3
489 depends on MFD_WM8350
491 config MFD_WM8351_CONFIG_MODE_0
493 depends on MFD_WM8350
495 config MFD_WM8351_CONFIG_MODE_1
497 depends on MFD_WM8350
499 config MFD_WM8351_CONFIG_MODE_2
501 depends on MFD_WM8350
503 config MFD_WM8351_CONFIG_MODE_3
505 depends on MFD_WM8350
507 config MFD_WM8352_CONFIG_MODE_0
509 depends on MFD_WM8350
511 config MFD_WM8352_CONFIG_MODE_1
513 depends on MFD_WM8350
515 config MFD_WM8352_CONFIG_MODE_2
517 depends on MFD_WM8350
519 config MFD_WM8352_CONFIG_MODE_3
521 depends on MFD_WM8350
523 config MFD_WM8350_I2C
524 bool "Support Wolfson Microelectronics WM8350 with I2C"
526 depends on I2C=y && GENERIC_HARDIRQS
528 The WM8350 is an integrated audio and power management
529 subsystem with watchdog and RTC functionality for embedded
530 systems. This option enables core support for the WM8350 with
531 I2C as the control interface. Additional options must be
532 selected to enable support for the functionality of the chip.
535 bool "Support Wolfson Microelectronics WM8994"
539 depends on I2C=y && GENERIC_HARDIRQS
541 The WM8994 is a highly integrated hi-fi CODEC designed for
542 smartphone applicatiosn. As well as audio functionality it
543 has on board GPIO and regulator functionality which is
544 supported via the relevant subsystems. This driver provides
545 core support for the WM8994, in order to use the actual
546 functionaltiy of the device other drivers must be enabled.
549 tristate "Support for NXP PCF50633"
553 Say yes here if you have NXP PCF50633 chip on your board.
554 This core driver provides register access and IRQ handling
555 facilities, and registers devices for the various functions
556 so that function-specific drivers can bind to them.
559 tristate "Support for NXP PCF50633 ADC"
560 depends on MFD_PCF50633
562 Say yes here if you want to include support for ADC in the
566 tristate "Support for NXP PCF50633 GPIO"
567 depends on MFD_PCF50633
569 Say yes here if you want to include support GPIO for pins on
576 tristate "Support Freescale MC13783 and MC13892"
577 depends on SPI_MASTER
581 Support for the Freescale (Atlas) PMIC and audio CODECs
583 This driver provides common support for accessing the device,
584 additional drivers must be enabled in order to use the
585 functionality of the device.
588 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
589 default y if ARCH_U300 || ARCH_U8500
591 Say yes here if you have the ABX500 Mixed Signal IC family
592 chips. This core driver expose register access functions.
593 Functionality specific drivers using these functions can
594 remain unchanged when IC changes. Binding of the functions to
595 actual register access is done by the IC core driver.
598 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
599 depends on I2C=y && ABX500_CORE
601 default y if ARCH_U300
603 Select this to enable the AB3100 Mixed Signal IC core
604 functionality. This connects to a AB3100 on the I2C bus
605 and expose a number of symbols needed for dependent devices
606 to read and write registers and subscribe to events from
607 this multi-functional IC. This is needed to use other features
608 of the AB3100 such as battery-backed RTC, charging control,
609 LEDs, vibrator, system power and temperature, power management
613 tristate "ST-Ericsson AB3100 OTP functions"
614 depends on AB3100_CORE
615 default y if AB3100_CORE
617 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
618 programmable memory) support. This exposes a sysfs file to read
623 depends on GENERIC_HARDIRQS && SPI_MASTER
625 This enables the PCAP ASIC present on EZX Phones. This is
626 needed for MMC, TouchScreen, Sound, USB, etc..
629 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
630 depends on ABX500_CORE && MFD_DB5500_PRCMU
633 Select this option to enable access to AB5500 power management
634 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
635 This chip embeds various other multimedia funtionalities as well.
638 bool "Enable debug info via debugfs"
639 depends on AB5500_CORE && DEBUG_FS
640 default y if DEBUG_FS
642 Select this option if you want debug information from the AB5500
643 using the debug filesystem, debugfs.
646 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
647 depends on GENERIC_HARDIRQS && ABX500_CORE
650 Select this option to enable access to AB8500 power management
651 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
652 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
653 the irq_chip parts for handling the Mixed Signal chip events.
654 This chip embeds various other multimedia funtionalities as well.
656 config AB8500_I2C_CORE
657 bool "AB8500 register access via PRCMU I2C"
658 depends on AB8500_CORE && MFD_DB8500_PRCMU
661 This enables register access to the AB8500 chip via PRCMU I2C.
662 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
663 the I2C bus is connected to the Power Reset
664 and Mangagement Unit, PRCMU.
667 bool "Enable debug info via debugfs"
668 depends on AB8500_CORE && DEBUG_FS
669 default y if DEBUG_FS
671 Select this option if you want debug information using the debug
675 bool "AB8500 GPADC driver"
676 depends on AB8500_CORE && REGULATOR_AB8500
679 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
681 config MFD_DB8500_PRCMU
682 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
683 depends on UX500_SOC_DB8500
686 Select this option to enable support for the DB8500 Power Reset
687 and Control Management Unit. This is basically an autonomous
688 system controller running an XP70 microprocessor, which is accessed
689 through a register map.
691 config MFD_DB5500_PRCMU
692 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
693 depends on UX500_SOC_DB5500
696 Select this option to enable support for the DB5500 Power Reset
697 and Control Management Unit. This is basically an autonomous
698 system controller running an XP70 microprocessor, which is accessed
699 through a register map.
702 tristate "Support for CS5535 and CS5536 southbridge core functions"
704 depends on PCI && X86
706 This is the core driver for CS5535/CS5536 MFD functions. This is
707 necessary for using the board's GPIO and MFGPT functionality.
709 config MFD_TIMBERDALE
710 tristate "Support for the Timberdale FPGA"
712 depends on PCI && GPIOLIB
714 This is the core driver for the timberdale FPGA. This device is a
715 multifunction device which exposes numerous platform devices.
717 The timberdale FPGA can be found on the Intel Atom development board
718 for in-vehicle infontainment, called Russellville.
721 tristate "Intel SCH LPC"
725 LPC bridge function of the Intel SCH provides support for
726 System Management Bus and General Purpose I/O.
729 tristate "Support for RDC-R321x southbridge"
733 Say yes here if you want to have support for the RDC R-321x SoC
734 southbridge which provides access to GPIOs and Watchdog using the
735 southbridge PCI device configuration space.
737 config MFD_JANZ_CMODIO
738 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
742 This is the core driver for the Janz CMOD-IO PCI MODULbus
743 carrier board. This device is a PCI to MODULbus bridge which may
744 host many different types of MODULbus daughterboards, including
745 CAN and GPIO controllers.
747 config MFD_JZ4740_ADC
748 bool "Support for the JZ4740 SoC ADC core"
750 select GENERIC_IRQ_CHIP
751 depends on MACH_JZ4740
753 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
754 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
757 tristate "Support for VIA VX855/VX875 integrated south bridge"
761 Say yes here to enable support for various functions of the
762 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
763 and/or vx855_gpio drivers for this to do anything useful.
765 config MFD_WL1273_CORE
766 tristate "Support for TI WL1273 FM radio."
771 This is the core driver for the TI WL1273 FM radio. This MFD
772 driver connects the radio-wl1273 V4L2 module and the wl1273
775 config MFD_OMAP_USB_HOST
776 bool "Support OMAP USBHS core driver"
777 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
780 This is the core driver for the OAMP EHCI and OHCI drivers.
781 This MFD driver does the required setup functionalities for
782 OMAP USB Host drivers.
787 config MFD_PM8921_CORE
788 tristate "Qualcomm PM8921 PMIC chip"
793 If you say yes to this option, support will be included for the
794 built-in PM8921 PMIC chip.
796 This is required if your board has a PM8921 and uses its features,
797 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
799 Say M here if you want to include support for PM8921 chip as a module.
800 This will build a module called "pm8921-core".
802 config MFD_PM8XXX_IRQ
803 bool "Support for Qualcomm PM8xxx IRQ features"
804 depends on MFD_PM8XXX
805 default y if MFD_PM8XXX
807 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
809 This is required to use certain other PM 8xxx features, such as GPIO
812 config TPS65911_COMPARATOR
815 config MFD_AAT2870_CORE
816 bool "Support for the AnalogicTech AAT2870"
818 depends on I2C=y && GPIOLIB
820 If you say yes here you get support for the AAT2870.
821 This driver provides common support for accessing the device,
822 additional drivers must be enabled in order to use the
823 functionality of the device.
825 config MFD_INTEL_MSIC
826 bool "Support for Intel MSIC"
827 depends on INTEL_SCU_IPC
830 Select this option to enable access to Intel MSIC (Avatele
831 Passage) chip. This chip embeds audio, battery, GPIO, etc.
832 devices used in Intel Medfield platforms.
837 menu "Multimedia Capabilities Port drivers"
838 depends on ARCH_SA1100
845 tristate "Support SA11x0 MCP interface"
846 depends on ARCH_SA1100
851 tristate "Support for UCB1200 / UCB1300"
854 config MCP_UCB1200_TS
855 tristate "Touchscreen interface support"
856 depends on MCP_UCB1200 && INPUT