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 "Texas Instruments TWL92330/Menelaus PM chip"
176 depends on I2C=y && ARCH_OMAP2
178 If you say yes here you get support for the Texas Instruments
179 TWL92330/Menelaus Power Management chip. This include voltage
180 regulators, Dual slot memory card transceivers, real-time clock
181 and other features that are often used in portable devices like
182 cell phones and PDAs.
185 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
186 depends on I2C=y && GENERIC_HARDIRQS
188 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
189 This core driver provides register access and IRQ handling
190 facilities, and registers devices for the various functions
191 so that function-specific drivers can bind to them.
193 These multi-function chips are found on many OMAP2 and OMAP3
194 boards, providing power management, RTC, GPIO, keypad, a
195 high speed USB OTG transceiver, an audio codec (on most
196 versions) and many other features.
199 bool "Support power resources on TWL6030 family chips"
200 depends on TWL4030_CORE
202 Say yes here if you want to use the power resources on the
203 TWL6030 family chips. Most of these resources are regulators,
204 which have a separate driver; some are control signals, such
205 as clock request handshaking.
207 This driver defaults to assuming only APPs processor uses
208 the resource, it can however be overridden by board file
211 tristate "Texas Instruments TWL4030 MADC"
212 depends on TWL4030_CORE
214 This driver provides support for triton TWL4030-MADC. The
215 driver supports both RT and SW conversion methods.
217 This driver can be built as a module. If so it will be
221 bool "Support power resources on TWL4030 family chips"
222 depends on TWL4030_CORE && ARM
224 Say yes here if you want to use the power resources on the
225 TWL4030 family chips. Most of these resources are regulators,
226 which have a separate driver; some are control signals, such
227 as clock request handshaking.
229 This driver uses board-specific data to initialize the resources
230 and load scripts controlling which resources are switched off/on
231 or reset when a sleep, wakeup or warm reset event occurs.
235 depends on TWL4030_CORE
240 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
241 depends on TWL4030_CORE
245 Say yes here if you want support for TWL6030 PWM.
246 This is used to control charging LED brightness.
248 config TWL6030_POWEROFF
249 bool "TWL6030 device poweroff"
250 depends on TWL4030_CORE
253 tristate "Texas Instruments TWL6030 MADC"
254 depends on TWL4030_CORE
256 This driver provides support for TWL6030-MADC. The
257 driver supports both RT and SW conversion methods.
259 This driver can be built as a module. If so it will be
263 tristate "TWL6030 GPADC (General Purpose A/D Convertor) Support"
264 depends on TWL4030_CORE
267 Say yes here if you want support for the TWL6030 General Purpose
271 bool "Support TI Codec Aic3262"
276 bool "Support STMicroelectronics STMPE"
277 depends on I2C=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
299 bool "Support Toshiba TC35892 and variants"
300 depends on I2C=y && GENERIC_HARDIRQS
303 Support for the Toshiba TC35892 and variants I/O Expander.
305 This driver provides common support for accessing the device,
306 additional drivers must be enabled in order to use the
307 functionality of the device.
314 bool "Support Toshiba T7L66XB"
315 depends on ARM && HAVE_CLK
319 Support for Toshiba Mobile IO Controller T7L66XB
322 bool "Support Toshiba TC6387XB"
323 depends on ARM && HAVE_CLK
327 Support for Toshiba Mobile IO Controller TC6387XB
330 bool "Support Toshiba TC6393XB"
331 depends on GPIOLIB && ARM
335 Support for Toshiba Mobile IO Controller TC6393XB
338 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
341 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
342 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
343 usually found on PXA processors-based platforms. This includes
344 the I2C driver and the core APIs _only_, you have to select
345 individual components like LCD backlight, voltage regulators,
346 LEDs and battery-charger under the corresponding menus.
349 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
352 Say yes here to add support for Analog Devices AD5520 and ADP5501,
353 Multifunction Power Management IC. This includes
354 the I2C driver and the core APIs _only_, you have to select
355 individual components like LCD backlight, LEDs, GPIOs and Kepad
356 under the corresponding menus.
359 bool "Maxim Semiconductor MAX8925 PMIC Support"
360 depends on I2C=y && GENERIC_HARDIRQS
363 Say yes here to support for Maxim Semiconductor MAX8925. This is
364 a Power Management IC. This driver provies common support for
365 accessing the device, additional drivers must be enabled in order
366 to use the functionality of the device.
369 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
370 depends on I2C=y && GENERIC_HARDIRQS
373 Say yes here to support for Maxim Semiconductor MAX8998/8966.
374 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
375 MUIC controls on chip.
376 This driver provides common support for accessing the device;
377 additional drivers must be enabled in order to use the functionality
381 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
382 depends on I2C=y && GENERIC_HARDIRQS
385 Say yes here to support for Maxim Semiconductor MAX8998 and
386 National Semiconductor LP3974. This is a Power Management IC.
387 This driver provies common support for accessing the device,
388 additional drivers must be enabled in order to use the functionality
392 tristate "Support Wolfson Microelectronics WM8400"
396 Support for the Wolfson Microelecronics WM8400 PMIC and audio
397 CODEC. This driver provides common support for accessing
398 the device, additional drivers must be enabled in order to use
399 the functionality of the device.
403 depends on GENERIC_HARDIRQS
405 config MFD_WM831X_I2C
406 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
409 depends on I2C=y && GENERIC_HARDIRQS
411 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
412 when controlled using I2C. This driver provides common support
413 for accessing the device, additional drivers must be enabled in
414 order to use the functionality of the device.
416 config MFD_WM831X_SPI
417 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
420 depends on SPI_MASTER && GENERIC_HARDIRQS
422 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
423 when controlled using SPI. This driver provides common support
424 for accessing the device, additional drivers must be enabled in
425 order to use the functionality of the device.
427 config MFD_WM831X_SPI_A22
428 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI for A22"
431 depends on SPI_MASTER && GENERIC_HARDIRQS
433 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
434 when controlled using SPI. This driver provides common support
435 for accessing the device, additional drivers must be enabled in
436 order to use the functionality of the device.
440 depends on GENERIC_HARDIRQS
442 config MFD_WM8350_CONFIG_MODE_0
444 depends on MFD_WM8350
446 config MFD_WM8350_CONFIG_MODE_1
448 depends on MFD_WM8350
450 config MFD_WM8350_CONFIG_MODE_2
452 depends on MFD_WM8350
454 config MFD_WM8350_CONFIG_MODE_3
456 depends on MFD_WM8350
458 config MFD_WM8351_CONFIG_MODE_0
460 depends on MFD_WM8350
462 config MFD_WM8351_CONFIG_MODE_1
464 depends on MFD_WM8350
466 config MFD_WM8351_CONFIG_MODE_2
468 depends on MFD_WM8350
470 config MFD_WM8351_CONFIG_MODE_3
472 depends on MFD_WM8350
474 config MFD_WM8352_CONFIG_MODE_0
476 depends on MFD_WM8350
478 config MFD_WM8352_CONFIG_MODE_1
480 depends on MFD_WM8350
482 config MFD_WM8352_CONFIG_MODE_2
484 depends on MFD_WM8350
486 config MFD_WM8352_CONFIG_MODE_3
488 depends on MFD_WM8350
490 config MFD_WM8350_I2C
491 bool "Support Wolfson Microelectronics WM8350 with I2C"
493 depends on I2C=y && GENERIC_HARDIRQS
495 The WM8350 is an integrated audio and power management
496 subsystem with watchdog and RTC functionality for embedded
497 systems. This option enables core support for the WM8350 with
498 I2C as the control interface. Additional options must be
499 selected to enable support for the functionality of the chip.
502 bool "Support Wolfson Microelectronics WM8994"
504 depends on I2C=y && GENERIC_HARDIRQS
506 The WM8994 is a highly integrated hi-fi CODEC designed for
507 smartphone applicatiosn. As well as audio functionality it
508 has on board GPIO and regulator functionality which is
509 supported via the relevant subsystems. This driver provides
510 core support for the WM8994, in order to use the actual
511 functionaltiy of the device other drivers must be enabled.
514 tristate "Support for NXP PCF50633"
517 Say yes here if you have NXP PCF50633 chip on your board.
518 This core driver provides register access and IRQ handling
519 facilities, and registers devices for the various functions
520 so that function-specific drivers can bind to them.
523 tristate "Support for NXP PCF50633 ADC"
524 depends on MFD_PCF50633
526 Say yes here if you want to include support for ADC in the
530 tristate "Support for NXP PCF50633 GPIO"
531 depends on MFD_PCF50633
533 Say yes here if you want to include support GPIO for pins on
540 tristate "Support Freescale MC13783 and MC13892"
541 depends on SPI_MASTER
545 Support for the Freescale (Atlas) PMIC and audio CODECs
547 This driver provides common support for accessing the device,
548 additional drivers must be enabled in order to use the
549 functionality of the device.
552 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
553 default y if ARCH_U300 || ARCH_U8500
555 Say yes here if you have the ABX500 Mixed Signal IC family
556 chips. This core driver expose register access functions.
557 Functionality specific drivers using these functions can
558 remain unchanged when IC changes. Binding of the functions to
559 actual register access is done by the IC core driver.
562 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
563 depends on I2C=y && ABX500_CORE
565 default y if ARCH_U300
567 Select this to enable the AB3100 Mixed Signal IC core
568 functionality. This connects to a AB3100 on the I2C bus
569 and expose a number of symbols needed for dependent devices
570 to read and write registers and subscribe to events from
571 this multi-functional IC. This is needed to use other features
572 of the AB3100 such as battery-backed RTC, charging control,
573 LEDs, vibrator, system power and temperature, power management
577 tristate "ST-Ericsson AB3100 OTP functions"
578 depends on AB3100_CORE
579 default y if AB3100_CORE
581 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
582 programmable memory) support. This exposes a sysfs file to read
587 depends on GENERIC_HARDIRQS && SPI_MASTER
589 This enables the PCAP ASIC present on EZX Phones. This is
590 needed for MMC, TouchScreen, Sound, USB, etc..
593 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
594 depends on GENERIC_HARDIRQS && ABX500_CORE
597 Select this option to enable access to AB8500 power management
598 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
599 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
600 the irq_chip parts for handling the Mixed Signal chip events.
601 This chip embeds various other multimedia funtionalities as well.
603 config AB8500_I2C_CORE
604 bool "AB8500 register access via PRCMU I2C"
605 depends on AB8500_CORE && MFD_DB8500_PRCMU
608 This enables register access to the AB8500 chip via PRCMU I2C.
609 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
610 the I2C bus is connected to the Power Reset
611 and Mangagement Unit, PRCMU.
614 bool "Enable debug info via debugfs"
615 depends on AB8500_CORE && DEBUG_FS
616 default y if DEBUG_FS
618 Select this option if you want debug information using the debug
622 bool "AB8500 GPADC driver"
623 depends on AB8500_CORE && REGULATOR_AB8500
626 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
629 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
631 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
633 Select this to enable the AB3550 Mixed Signal IC core
634 functionality. This connects to a AB3550 on the I2C bus
635 and expose a number of symbols needed for dependent devices
636 to read and write registers and subscribe to events from
637 this multi-functional IC. This is needed to use other features
638 of the AB3550 such as battery-backed RTC, charging control,
639 LEDs, vibrator, system power and temperature, power management
642 config MFD_DB8500_PRCMU
643 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
644 depends on UX500_SOC_DB8500
647 Select this option to enable support for the DB8500 Power Reset
648 and Control Management Unit. This is basically an autonomous
649 system controller running an XP70 microprocessor, which is accessed
650 through a register map.
652 config MFD_DB5500_PRCMU
653 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
654 depends on UX500_SOC_DB5500
657 Select this option to enable support for the DB5500 Power Reset
658 and Control Management Unit. This is basically an autonomous
659 system controller running an XP70 microprocessor, which is accessed
660 through a register map.
663 tristate "Support for CS5535 and CS5536 southbridge core functions"
665 depends on PCI && X86
667 This is the core driver for CS5535/CS5536 MFD functions. This is
668 necessary for using the board's GPIO and MFGPT functionality.
670 config MFD_TIMBERDALE
671 tristate "Support for the Timberdale FPGA"
673 depends on PCI && GPIOLIB
675 This is the core driver for the timberdale FPGA. This device is a
676 multifunction device which exposes numerous platform devices.
678 The timberdale FPGA can be found on the Intel Atom development board
679 for in-vehicle infontainment, called Russellville.
682 tristate "Intel SCH LPC"
686 LPC bridge function of the Intel SCH provides support for
687 System Management Bus and General Purpose I/O.
690 tristate "Support for RDC-R321x southbridge"
694 Say yes here if you want to have support for the RDC R-321x SoC
695 southbridge which provides access to GPIOs and Watchdog using the
696 southbridge PCI device configuration space.
698 config MFD_JANZ_CMODIO
699 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
703 This is the core driver for the Janz CMOD-IO PCI MODULbus
704 carrier board. This device is a PCI to MODULbus bridge which may
705 host many different types of MODULbus daughterboards, including
706 CAN and GPIO controllers.
708 config MFD_JZ4740_ADC
709 tristate "Support for the JZ4740 SoC ADC core"
711 depends on MACH_JZ4740
713 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
714 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
717 tristate "Support for VIA VX855/VX875 integrated south bridge"
721 Say yes here to enable support for various functions of the
722 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
723 and/or vx855_gpio drivers for this to do anything useful.
725 config MFD_WL1273_CORE
726 tristate "Support for TI WL1273 FM radio."
731 This is the core driver for the TI WL1273 FM radio. This MFD
732 driver connects the radio-wl1273 V4L2 module and the wl1273
735 config MFD_OMAP_USB_HOST
736 bool "Support OMAP USBHS core driver"
737 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
740 This is the core driver for the OAMP EHCI and OHCI drivers.
741 This MFD driver does the required setup functionalities for
742 OMAP USB Host drivers.
747 config MFD_PM8921_CORE
748 tristate "Qualcomm PM8921 PMIC chip"
753 If you say yes to this option, support will be included for the
754 built-in PM8921 PMIC chip.
756 This is required if your board has a PM8921 and uses its features,
757 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
759 Say M here if you want to include support for PM8921 chip as a module.
760 This will build a module called "pm8921-core".
762 config MFD_PM8XXX_IRQ
763 bool "Support for Qualcomm PM8xxx IRQ features"
764 depends on MFD_PM8XXX
765 default y if MFD_PM8XXX
767 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
769 This is required to use certain other PM 8xxx features, such as GPIO
773 bool "TPS65910 Power Management chip"
774 depends on I2C=y && GPIOLIB
778 if you say yes here you get support for the TPS65910 series of
779 Power Management chips.
781 config TPS65911_COMPARATOR
785 bool "RK610(Jetta) Multimedia support"
786 depends on I2C=y && GPIOLIB
789 if you say yes here you get support for the RK610, with func as
790 HDMI LCD LVDS TVOUT CODEC.
793 menu "Multimedia Capabilities Port drivers"
794 depends on ARCH_SA1100
801 tristate "Support SA11x0 MCP interface"
802 depends on ARCH_SA1100
807 tristate "Support for UCB1200 / UCB1300"
810 config MCP_UCB1200_TS
811 tristate "Touchscreen interface support"
812 depends on MCP_UCB1200 && INPUT