2 # Multifunction miscellaneous devices
6 bool "Multifunction device drivers"
10 Multifunction devices embed several functions (e.g. GPIOs,
11 touchscreens, keyboards, current regulators, power management chips,
12 etc...) in one single integrated circuit. They usually talk to the
13 main CPU through one or more IRQ lines and low speed data busses (SPI,
14 I2C, etc..). They appear as one single device to the main system
15 through the data bus and the MFD framework allows for sub devices
16 (a.k.a. functions) to appear as discrete platform devices.
17 MFDs are typically found on embedded platforms.
19 This option alone does not add any kernel code.
28 bool "Support Marvell 88PM8606/88PM8607"
29 depends on I2C=y && GENERIC_HARDIRQS
32 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
33 This includes the I2C driver and the core APIs _only_, you have to
34 select individual components like voltage regulators, RTC and
35 battery-charger under the corresponding menus.
38 tristate "Support for Silicon Motion SM501"
40 This is the core driver for the Silicon Motion SM501 multimedia
41 companion chip. This device is a multifunction device which may
42 provide numerous interfaces including USB host controller, USB gadget,
43 asynchronous serial ports, audio functions, and a dual display video
44 interface. The device may be connected by PCI or local bus with
45 varying functions enabled.
48 bool "Export GPIO via GPIO layer"
49 depends on MFD_SM501 && GPIOLIB
51 This option uses the gpio library layer to export the 64 GPIO
52 lines on the SM501. The platform data is used to supply the
53 base number for the first GPIO line to register.
56 bool "Support for Compaq ASIC3"
57 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
60 This driver supports the ASIC3 multifunction chip found on many
61 PDAs (mainly iPAQ and HTC based ones)
63 config MFD_DAVINCI_VOICECODEC
67 config MFD_DM355EVM_MSP
68 bool "DaVinci DM355 EVM microcontroller"
69 depends on I2C=y && MACH_DAVINCI_DM355_EVM
71 This driver supports the MSP430 microcontroller used on these
72 boards. MSP430 firmware manages resets and power sequencing,
73 inputs from buttons and the IR remote, LEDs, an RTC, and more.
76 tristate "TI Sequencer Serial Port support"
77 depends on ARCH_DAVINCI_TNETV107X
80 Say Y here if you want support for the Sequencer Serial Port
81 in a Texas Instruments TNETV107X SoC.
83 To compile this driver as a module, choose M here: the
84 module will be called ti-ssp.
87 bool "HTC EGPIO support"
88 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
90 This driver supports the CPLD egpio chip present on
91 several HTC phones. It provides basic support for input
92 pins, output pins, and irqs.
95 tristate "HTC PASIC3 LED/DS1WM chip support"
98 This core driver provides register access for the LED/DS1WM
99 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
100 HTC Magician devices, respectively. Actual functionality is
101 handled by the leds-pasic3 and ds1wm drivers.
104 bool "HTC I2C PLD chip support"
105 depends on I2C=y && GPIOLIB
107 If you say yes here you get support for the supposed CPLD
108 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
109 This device provides input and output GPIOs through an I2C
110 interface to one or more sub-chips.
113 tristate "Philips UCB1400 Core driver"
117 This enables support for the Philips UCB1400 core functions.
118 The UCB1400 is an AC97 audio codec.
120 To compile this driver as a module, choose M here: the
121 module will be called ucb1400_core.
124 tristate "TPS61050/61052 Boost Converters"
128 select REGULATOR_FIXED_VOLTAGE
130 This option enables a driver for the TP61050/TPS61052
131 high-power "white LED driver". This boost converter is
132 sometimes used for other things than white LEDs, and
133 also contains a GPIO pin.
136 tristate "TPS6501x Power Management chips"
137 depends on I2C && GPIOLIB
138 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
140 If you say yes here you get support for the TPS6501x series of
141 Power Management chips. These include voltage regulators,
142 lithium ion/polymer battery charging, and other features that
143 are often used in portable devices like cell phones and cameras.
145 This driver can also be built as a module. If so, the module
146 will be called tps65010.
149 tristate "TPS6507x Power Management / Touch Screen chips"
153 If you say yes here you get support for the TPS6507x series of
154 Power Management / Touch Screen chips. These include voltage
155 regulators, lithium ion/polymer battery charging, touch screen
156 and other features that are often used in portable devices.
157 This driver can also be built as a module. If so, the module
158 will be called tps6507x.
161 bool "TPS6586x Power Management chips"
162 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
165 If you say yes here you get support for the TPS6586X series of
166 Power Management chips.
167 This driver provides common support for accessing the device,
168 additional drivers must be enabled in order to use the
169 functionality of the device.
171 This driver can also be built as a module. If so, the module
172 will be called tps6586x.
175 bool "TPS65910 Power Management chip"
176 depends on I2C=y && GPIOLIB
181 if you say yes here you get support for the TPS65910 series of
182 Power Management chips.
188 config MFD_TPS65912_I2C
189 bool "TPS65912 Power Management chip with I2C"
192 depends on I2C=y && GPIOLIB
194 If you say yes here you get support for the TPS65912 series of
195 PM chips with I2C interface.
197 config MFD_TPS65912_SPI
198 bool "TPS65912 Power Management chip with SPI"
201 depends on SPI_MASTER && GPIOLIB
203 If you say yes here you get support for the TPS65912 series of
204 PM chips with SPI interface.
206 bool "Texas Instruments TWL92330/Menelaus PM chip"
207 depends on I2C=y && ARCH_OMAP2
209 If you say yes here you get support for the Texas Instruments
210 TWL92330/Menelaus Power Management chip. This include voltage
211 regulators, Dual slot memory card transceivers, real-time clock
212 and other features that are often used in portable devices like
213 cell phones and PDAs.
216 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
217 depends on I2C=y && GENERIC_HARDIRQS
219 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
220 This core driver provides register access and IRQ handling
221 facilities, and registers devices for the various functions
222 so that function-specific drivers can bind to them.
224 These multi-function chips are found on many OMAP2 and OMAP3
225 boards, providing power management, RTC, GPIO, keypad, a
226 high speed USB OTG transceiver, an audio codec (on most
227 versions) and many other features.
230 bool "Support power resources on TWL6030 family chips"
231 depends on TWL4030_CORE
233 Say yes here if you want to use the power resources on the
234 TWL6030 family chips. Most of these resources are regulators,
235 which have a separate driver; some are control signals, such
236 as clock request handshaking.
238 This driver defaults to assuming only APPs processor uses
239 the resource, it can however be overridden by board file
242 tristate "Texas Instruments TWL4030 MADC"
243 depends on TWL4030_CORE
245 This driver provides support for triton TWL4030-MADC. The
246 driver supports both RT and SW conversion methods.
248 This driver can be built as a module. If so it will be
252 bool "Support power resources on TWL4030 family chips"
253 depends on TWL4030_CORE && ARM
255 Say yes here if you want to use the power resources on the
256 TWL4030 family chips. Most of these resources are regulators,
257 which have a separate driver; some are control signals, such
258 as clock request handshaking.
260 This driver uses board-specific data to initialize the resources
261 and load scripts controlling which resources are switched off/on
262 or reset when a sleep, wakeup or warm reset event occurs.
266 depends on TWL4030_CORE
271 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
272 depends on TWL4030_CORE
276 Say yes here if you want support for TWL6030 PWM.
277 This is used to control charging LED brightness.
279 config TWL6030_POWEROFF
280 bool "TWL6030 device poweroff"
281 depends on TWL4030_CORE
284 tristate "Texas Instruments TWL6030 MADC"
285 depends on TWL4030_CORE
287 This driver provides support for TWL6030-MADC. The
288 driver supports both RT and SW conversion methods.
290 This driver can be built as a module. If so it will be
294 tristate "TWL6030 GPADC (General Purpose A/D Convertor) Support"
295 depends on TWL4030_CORE
298 Say yes here if you want support for the TWL6030 General Purpose
302 bool "Support TI Codec Aic3262"
307 bool "Support STMicroelectronics STMPE"
308 depends on I2C=y && GENERIC_HARDIRQS
311 Support for the STMPE family of I/O Expanders from
314 Currently supported devices are:
316 STMPE811: GPIO, Touchscreen
317 STMPE1601: GPIO, Keypad
318 STMPE2401: GPIO, Keypad
319 STMPE2403: GPIO, Keypad
321 This driver provides common support for accessing the device,
322 additional drivers must be enabled in order to use the functionality
323 of the device. Currently available sub drivers are:
327 Touchscreen: stmpe-ts
330 bool "Support Toshiba TC35892 and variants"
331 depends on I2C=y && GENERIC_HARDIRQS
334 Support for the Toshiba TC35892 and variants I/O Expander.
336 This driver provides common support for accessing the device,
337 additional drivers must be enabled in order to use the
338 functionality of the device.
345 bool "Support Toshiba T7L66XB"
346 depends on ARM && HAVE_CLK
350 Support for Toshiba Mobile IO Controller T7L66XB
353 bool "Support Toshiba TC6387XB"
354 depends on ARM && HAVE_CLK
358 Support for Toshiba Mobile IO Controller TC6387XB
361 bool "Support Toshiba TC6393XB"
362 depends on GPIOLIB && ARM
366 Support for Toshiba Mobile IO Controller TC6393XB
369 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
372 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
373 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
374 usually found on PXA processors-based platforms. This includes
375 the I2C driver and the core APIs _only_, you have to select
376 individual components like LCD backlight, voltage regulators,
377 LEDs and battery-charger under the corresponding menus.
380 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
383 Say yes here to add support for Analog Devices AD5520 and ADP5501,
384 Multifunction Power Management IC. This includes
385 the I2C driver and the core APIs _only_, you have to select
386 individual components like LCD backlight, LEDs, GPIOs and Kepad
387 under the corresponding menus.
390 bool "Maxim Semiconductor MAX8925 PMIC Support"
391 depends on I2C=y && GENERIC_HARDIRQS
394 Say yes here to support for Maxim Semiconductor MAX8925. This is
395 a Power Management IC. This driver provies common support for
396 accessing the device, additional drivers must be enabled in order
397 to use the functionality of the device.
400 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
401 depends on I2C=y && GENERIC_HARDIRQS
404 Say yes here to support for Maxim Semiconductor MAX8998/8966.
405 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
406 MUIC controls on chip.
407 This driver provides common support for accessing the device;
408 additional drivers must be enabled in order to use the functionality
412 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
413 depends on I2C=y && GENERIC_HARDIRQS
416 Say yes here to support for Maxim Semiconductor MAX8998 and
417 National Semiconductor LP3974. This is a Power Management IC.
418 This driver provies common support for accessing the device,
419 additional drivers must be enabled in order to use the functionality
423 tristate "Support Wolfson Microelectronics WM8400"
427 Support for the Wolfson Microelecronics WM8400 PMIC and audio
428 CODEC. This driver provides common support for accessing
429 the device, additional drivers must be enabled in order to use
430 the functionality of the device.
434 depends on GENERIC_HARDIRQS
436 config MFD_WM831X_I2C
437 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
440 depends on I2C=y && GENERIC_HARDIRQS
442 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
443 when controlled using I2C. This driver provides common support
444 for accessing the device, additional drivers must be enabled in
445 order to use the functionality of the device.
447 config MFD_WM831X_SPI
448 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
451 depends on SPI_MASTER && GENERIC_HARDIRQS
453 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
454 when controlled using SPI. This driver provides common support
455 for accessing the device, additional drivers must be enabled in
456 order to use the functionality of the device.
458 config MFD_WM831X_SPI_A22
459 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI for A22"
462 depends on SPI_MASTER && GENERIC_HARDIRQS
464 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
465 when controlled using SPI. This driver provides common support
466 for accessing the device, additional drivers must be enabled in
467 order to use the functionality of the device.
471 depends on GENERIC_HARDIRQS
473 config MFD_WM8350_CONFIG_MODE_0
475 depends on MFD_WM8350
477 config MFD_WM8350_CONFIG_MODE_1
479 depends on MFD_WM8350
481 config MFD_WM8350_CONFIG_MODE_2
483 depends on MFD_WM8350
485 config MFD_WM8350_CONFIG_MODE_3
487 depends on MFD_WM8350
489 config MFD_WM8351_CONFIG_MODE_0
491 depends on MFD_WM8350
493 config MFD_WM8351_CONFIG_MODE_1
495 depends on MFD_WM8350
497 config MFD_WM8351_CONFIG_MODE_2
499 depends on MFD_WM8350
501 config MFD_WM8351_CONFIG_MODE_3
503 depends on MFD_WM8350
505 config MFD_WM8352_CONFIG_MODE_0
507 depends on MFD_WM8350
509 config MFD_WM8352_CONFIG_MODE_1
511 depends on MFD_WM8350
513 config MFD_WM8352_CONFIG_MODE_2
515 depends on MFD_WM8350
517 config MFD_WM8352_CONFIG_MODE_3
519 depends on MFD_WM8350
521 config MFD_WM8350_I2C
522 bool "Support Wolfson Microelectronics WM8350 with I2C"
524 depends on I2C=y && GENERIC_HARDIRQS
526 The WM8350 is an integrated audio and power management
527 subsystem with watchdog and RTC functionality for embedded
528 systems. This option enables core support for the WM8350 with
529 I2C as the control interface. Additional options must be
530 selected to enable support for the functionality of the chip.
533 bool "Support Wolfson Microelectronics WM8994"
535 depends on I2C=y && GENERIC_HARDIRQS
537 The WM8994 is a highly integrated hi-fi CODEC designed for
538 smartphone applicatiosn. As well as audio functionality it
539 has on board GPIO and regulator functionality which is
540 supported via the relevant subsystems. This driver provides
541 core support for the WM8994, in order to use the actual
542 functionaltiy of the device other drivers must be enabled.
545 tristate "Support for NXP PCF50633"
548 Say yes here if you have NXP PCF50633 chip on your board.
549 This core driver provides register access and IRQ handling
550 facilities, and registers devices for the various functions
551 so that function-specific drivers can bind to them.
554 tristate "Support for NXP PCF50633 ADC"
555 depends on MFD_PCF50633
557 Say yes here if you want to include support for ADC in the
561 tristate "Support for NXP PCF50633 GPIO"
562 depends on MFD_PCF50633
564 Say yes here if you want to include support GPIO for pins on
571 tristate "Support Freescale MC13783 and MC13892"
572 depends on SPI_MASTER
576 Support for the Freescale (Atlas) PMIC and audio CODECs
578 This driver provides common support for accessing the device,
579 additional drivers must be enabled in order to use the
580 functionality of the device.
583 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
584 default y if ARCH_U300 || ARCH_U8500
586 Say yes here if you have the ABX500 Mixed Signal IC family
587 chips. This core driver expose register access functions.
588 Functionality specific drivers using these functions can
589 remain unchanged when IC changes. Binding of the functions to
590 actual register access is done by the IC core driver.
593 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
594 depends on I2C=y && ABX500_CORE
596 default y if ARCH_U300
598 Select this to enable the AB3100 Mixed Signal IC core
599 functionality. This connects to a AB3100 on the I2C bus
600 and expose a number of symbols needed for dependent devices
601 to read and write registers and subscribe to events from
602 this multi-functional IC. This is needed to use other features
603 of the AB3100 such as battery-backed RTC, charging control,
604 LEDs, vibrator, system power and temperature, power management
608 tristate "ST-Ericsson AB3100 OTP functions"
609 depends on AB3100_CORE
610 default y if AB3100_CORE
612 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
613 programmable memory) support. This exposes a sysfs file to read
618 depends on GENERIC_HARDIRQS && SPI_MASTER
620 This enables the PCAP ASIC present on EZX Phones. This is
621 needed for MMC, TouchScreen, Sound, USB, etc..
624 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
625 depends on GENERIC_HARDIRQS && ABX500_CORE
628 Select this option to enable access to AB8500 power management
629 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
630 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
631 the irq_chip parts for handling the Mixed Signal chip events.
632 This chip embeds various other multimedia funtionalities as well.
634 config AB8500_I2C_CORE
635 bool "AB8500 register access via PRCMU I2C"
636 depends on AB8500_CORE && MFD_DB8500_PRCMU
639 This enables register access to the AB8500 chip via PRCMU I2C.
640 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
641 the I2C bus is connected to the Power Reset
642 and Mangagement Unit, PRCMU.
645 bool "Enable debug info via debugfs"
646 depends on AB8500_CORE && DEBUG_FS
647 default y if DEBUG_FS
649 Select this option if you want debug information using the debug
653 bool "AB8500 GPADC driver"
654 depends on AB8500_CORE && REGULATOR_AB8500
657 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
660 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
662 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
664 Select this to enable the AB3550 Mixed Signal IC core
665 functionality. This connects to a AB3550 on the I2C bus
666 and expose a number of symbols needed for dependent devices
667 to read and write registers and subscribe to events from
668 this multi-functional IC. This is needed to use other features
669 of the AB3550 such as battery-backed RTC, charging control,
670 LEDs, vibrator, system power and temperature, power management
673 config MFD_DB8500_PRCMU
674 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
675 depends on UX500_SOC_DB8500
678 Select this option to enable support for the DB8500 Power Reset
679 and Control Management Unit. This is basically an autonomous
680 system controller running an XP70 microprocessor, which is accessed
681 through a register map.
683 config MFD_DB5500_PRCMU
684 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
685 depends on UX500_SOC_DB5500
688 Select this option to enable support for the DB5500 Power Reset
689 and Control Management Unit. This is basically an autonomous
690 system controller running an XP70 microprocessor, which is accessed
691 through a register map.
694 tristate "Support for CS5535 and CS5536 southbridge core functions"
696 depends on PCI && X86
698 This is the core driver for CS5535/CS5536 MFD functions. This is
699 necessary for using the board's GPIO and MFGPT functionality.
701 config MFD_TIMBERDALE
702 tristate "Support for the Timberdale FPGA"
704 depends on PCI && GPIOLIB
706 This is the core driver for the timberdale FPGA. This device is a
707 multifunction device which exposes numerous platform devices.
709 The timberdale FPGA can be found on the Intel Atom development board
710 for in-vehicle infontainment, called Russellville.
713 tristate "Intel SCH LPC"
717 LPC bridge function of the Intel SCH provides support for
718 System Management Bus and General Purpose I/O.
721 tristate "Support for RDC-R321x southbridge"
725 Say yes here if you want to have support for the RDC R-321x SoC
726 southbridge which provides access to GPIOs and Watchdog using the
727 southbridge PCI device configuration space.
729 config MFD_JANZ_CMODIO
730 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
734 This is the core driver for the Janz CMOD-IO PCI MODULbus
735 carrier board. This device is a PCI to MODULbus bridge which may
736 host many different types of MODULbus daughterboards, including
737 CAN and GPIO controllers.
739 config MFD_JZ4740_ADC
740 tristate "Support for the JZ4740 SoC ADC core"
742 depends on MACH_JZ4740
744 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
745 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
748 tristate "Support for VIA VX855/VX875 integrated south bridge"
752 Say yes here to enable support for various functions of the
753 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
754 and/or vx855_gpio drivers for this to do anything useful.
756 config MFD_WL1273_CORE
757 tristate "Support for TI WL1273 FM radio."
762 This is the core driver for the TI WL1273 FM radio. This MFD
763 driver connects the radio-wl1273 V4L2 module and the wl1273
766 config MFD_OMAP_USB_HOST
767 bool "Support OMAP USBHS core driver"
768 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
771 This is the core driver for the OAMP EHCI and OHCI drivers.
772 This MFD driver does the required setup functionalities for
773 OMAP USB Host drivers.
778 config MFD_PM8921_CORE
779 tristate "Qualcomm PM8921 PMIC chip"
784 If you say yes to this option, support will be included for the
785 built-in PM8921 PMIC chip.
787 This is required if your board has a PM8921 and uses its features,
788 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
790 Say M here if you want to include support for PM8921 chip as a module.
791 This will build a module called "pm8921-core".
793 config MFD_PM8XXX_IRQ
794 bool "Support for Qualcomm PM8xxx IRQ features"
795 depends on MFD_PM8XXX
796 default y if MFD_PM8XXX
798 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
800 This is required to use certain other PM 8xxx features, such as GPIO
803 config TPS65911_COMPARATOR
807 bool "TPS65090 Power Management chips"
808 depends on I2C=y && GENERIC_HARDIRQS
812 If you say yes here you get support for the TPS65090 series of
813 Power Management chips.
814 This driver provides common support for accessing the device,
815 additional drivers must be enabled in order to use the
816 functionality of the device.
819 bool "RK610(Jetta) Multimedia support"
820 depends on I2C=y && GPIOLIB
823 if you say yes here you get support for the RK610, with func as
824 HDMI LCD LVDS TVOUT CODEC.
827 menu "Multimedia Capabilities Port drivers"
828 depends on ARCH_SA1100
835 tristate "Support SA11x0 MCP interface"
836 depends on ARCH_SA1100
841 tristate "Support for UCB1200 / UCB1300"
844 config MCP_UCB1200_TS
845 tristate "Touchscreen interface support"
846 depends on MCP_UCB1200 && INPUT