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 "RK808 Power Management chip"
307 if you say yes here you get support for the RK808 series of
308 Power Management chips.
311 bool "Support TI Codec Aic3262"
316 bool "Support STMicroelectronics STMPE"
317 depends on I2C=y && GENERIC_HARDIRQS
320 Support for the STMPE family of I/O Expanders from
323 Currently supported devices are:
325 STMPE811: GPIO, Touchscreen
326 STMPE1601: GPIO, Keypad
327 STMPE2401: GPIO, Keypad
328 STMPE2403: GPIO, Keypad
330 This driver provides common support for accessing the device,
331 additional drivers must be enabled in order to use the functionality
332 of the device. Currently available sub drivers are:
336 Touchscreen: stmpe-ts
339 bool "Support Toshiba TC35892 and variants"
340 depends on I2C=y && GENERIC_HARDIRQS
343 Support for the Toshiba TC35892 and variants I/O Expander.
345 This driver provides common support for accessing the device,
346 additional drivers must be enabled in order to use the
347 functionality of the device.
354 bool "Support Toshiba T7L66XB"
355 depends on ARM && HAVE_CLK
359 Support for Toshiba Mobile IO Controller T7L66XB
362 bool "Support Toshiba TC6387XB"
363 depends on ARM && HAVE_CLK
367 Support for Toshiba Mobile IO Controller TC6387XB
370 bool "Support Toshiba TC6393XB"
371 depends on GPIOLIB && ARM
375 Support for Toshiba Mobile IO Controller TC6393XB
378 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
381 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
382 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
383 usually found on PXA processors-based platforms. This includes
384 the I2C driver and the core APIs _only_, you have to select
385 individual components like LCD backlight, voltage regulators,
386 LEDs and battery-charger under the corresponding menus.
389 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
392 Say yes here to add support for Analog Devices AD5520 and ADP5501,
393 Multifunction Power Management IC. This includes
394 the I2C driver and the core APIs _only_, you have to select
395 individual components like LCD backlight, LEDs, GPIOs and Kepad
396 under the corresponding menus.
399 bool "Maxim Semiconductor MAX8925 PMIC Support"
400 depends on I2C=y && GENERIC_HARDIRQS
403 Say yes here to support for Maxim Semiconductor MAX8925. This is
404 a Power Management IC. This driver provies common support for
405 accessing the device, additional drivers must be enabled in order
406 to use the functionality of the device.
409 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
410 depends on I2C=y && GENERIC_HARDIRQS
413 Say yes here to support for Maxim Semiconductor MAX8998/8966.
414 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
415 MUIC controls on chip.
416 This driver provides common support for accessing the device;
417 additional drivers must be enabled in order to use the functionality
421 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
422 depends on I2C=y && GENERIC_HARDIRQS
425 Say yes here to support for Maxim Semiconductor MAX8998 and
426 National Semiconductor LP3974. This is a Power Management IC.
427 This driver provies common support for accessing the device,
428 additional drivers must be enabled in order to use the functionality
432 tristate "Support Wolfson Microelectronics WM8400"
436 Support for the Wolfson Microelecronics WM8400 PMIC and audio
437 CODEC. This driver provides common support for accessing
438 the device, additional drivers must be enabled in order to use
439 the functionality of the device.
443 depends on GENERIC_HARDIRQS
445 config MFD_WM831X_I2C
446 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
449 depends on I2C=y && GENERIC_HARDIRQS
451 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
452 when controlled using I2C. This driver provides common support
453 for accessing the device, additional drivers must be enabled in
454 order to use the functionality of the device.
456 config MFD_WM831X_SPI
457 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
460 depends on SPI_MASTER && GENERIC_HARDIRQS
462 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
463 when controlled using SPI. This driver provides common support
464 for accessing the device, additional drivers must be enabled in
465 order to use the functionality of the device.
467 config MFD_WM831X_SPI_A22
468 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI for A22"
471 depends on SPI_MASTER && GENERIC_HARDIRQS
473 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
474 when controlled using SPI. This driver provides common support
475 for accessing the device, additional drivers must be enabled in
476 order to use the functionality of the device.
480 depends on GENERIC_HARDIRQS
482 config MFD_WM8350_CONFIG_MODE_0
484 depends on MFD_WM8350
486 config MFD_WM8350_CONFIG_MODE_1
488 depends on MFD_WM8350
490 config MFD_WM8350_CONFIG_MODE_2
492 depends on MFD_WM8350
494 config MFD_WM8350_CONFIG_MODE_3
496 depends on MFD_WM8350
498 config MFD_WM8351_CONFIG_MODE_0
500 depends on MFD_WM8350
502 config MFD_WM8351_CONFIG_MODE_1
504 depends on MFD_WM8350
506 config MFD_WM8351_CONFIG_MODE_2
508 depends on MFD_WM8350
510 config MFD_WM8351_CONFIG_MODE_3
512 depends on MFD_WM8350
514 config MFD_WM8352_CONFIG_MODE_0
516 depends on MFD_WM8350
518 config MFD_WM8352_CONFIG_MODE_1
520 depends on MFD_WM8350
522 config MFD_WM8352_CONFIG_MODE_2
524 depends on MFD_WM8350
526 config MFD_WM8352_CONFIG_MODE_3
528 depends on MFD_WM8350
530 config MFD_WM8350_I2C
531 bool "Support Wolfson Microelectronics WM8350 with I2C"
533 depends on I2C=y && GENERIC_HARDIRQS
535 The WM8350 is an integrated audio and power management
536 subsystem with watchdog and RTC functionality for embedded
537 systems. This option enables core support for the WM8350 with
538 I2C as the control interface. Additional options must be
539 selected to enable support for the functionality of the chip.
542 bool "Support Wolfson Microelectronics WM8994"
544 depends on I2C=y && GENERIC_HARDIRQS
546 The WM8994 is a highly integrated hi-fi CODEC designed for
547 smartphone applicatiosn. As well as audio functionality it
548 has on board GPIO and regulator functionality which is
549 supported via the relevant subsystems. This driver provides
550 core support for the WM8994, in order to use the actual
551 functionaltiy of the device other drivers must be enabled.
554 tristate "Support for NXP PCF50633"
557 Say yes here if you have NXP PCF50633 chip on your board.
558 This core driver provides register access and IRQ handling
559 facilities, and registers devices for the various functions
560 so that function-specific drivers can bind to them.
563 tristate "Support for NXP PCF50633 ADC"
564 depends on MFD_PCF50633
566 Say yes here if you want to include support for ADC in the
570 tristate "Support for NXP PCF50633 GPIO"
571 depends on MFD_PCF50633
573 Say yes here if you want to include support GPIO for pins on
580 tristate "Support Freescale MC13783 and MC13892"
581 depends on SPI_MASTER
585 Support for the Freescale (Atlas) PMIC and audio CODECs
587 This driver provides common support for accessing the device,
588 additional drivers must be enabled in order to use the
589 functionality of the device.
592 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
593 default y if ARCH_U300 || ARCH_U8500
595 Say yes here if you have the ABX500 Mixed Signal IC family
596 chips. This core driver expose register access functions.
597 Functionality specific drivers using these functions can
598 remain unchanged when IC changes. Binding of the functions to
599 actual register access is done by the IC core driver.
602 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
603 depends on I2C=y && ABX500_CORE
605 default y if ARCH_U300
607 Select this to enable the AB3100 Mixed Signal IC core
608 functionality. This connects to a AB3100 on the I2C bus
609 and expose a number of symbols needed for dependent devices
610 to read and write registers and subscribe to events from
611 this multi-functional IC. This is needed to use other features
612 of the AB3100 such as battery-backed RTC, charging control,
613 LEDs, vibrator, system power and temperature, power management
617 tristate "ST-Ericsson AB3100 OTP functions"
618 depends on AB3100_CORE
619 default y if AB3100_CORE
621 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
622 programmable memory) support. This exposes a sysfs file to read
627 depends on GENERIC_HARDIRQS && SPI_MASTER
629 This enables the PCAP ASIC present on EZX Phones. This is
630 needed for MMC, TouchScreen, Sound, USB, etc..
633 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
634 depends on GENERIC_HARDIRQS && ABX500_CORE
637 Select this option to enable access to AB8500 power management
638 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
639 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
640 the irq_chip parts for handling the Mixed Signal chip events.
641 This chip embeds various other multimedia funtionalities as well.
643 config AB8500_I2C_CORE
644 bool "AB8500 register access via PRCMU I2C"
645 depends on AB8500_CORE && MFD_DB8500_PRCMU
648 This enables register access to the AB8500 chip via PRCMU I2C.
649 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
650 the I2C bus is connected to the Power Reset
651 and Mangagement Unit, PRCMU.
654 bool "Enable debug info via debugfs"
655 depends on AB8500_CORE && DEBUG_FS
656 default y if DEBUG_FS
658 Select this option if you want debug information using the debug
662 bool "AB8500 GPADC driver"
663 depends on AB8500_CORE && REGULATOR_AB8500
666 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
669 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
671 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
673 Select this to enable the AB3550 Mixed Signal IC core
674 functionality. This connects to a AB3550 on the I2C bus
675 and expose a number of symbols needed for dependent devices
676 to read and write registers and subscribe to events from
677 this multi-functional IC. This is needed to use other features
678 of the AB3550 such as battery-backed RTC, charging control,
679 LEDs, vibrator, system power and temperature, power management
682 config MFD_DB8500_PRCMU
683 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
684 depends on UX500_SOC_DB8500
687 Select this option to enable support for the DB8500 Power Reset
688 and Control Management Unit. This is basically an autonomous
689 system controller running an XP70 microprocessor, which is accessed
690 through a register map.
692 config MFD_DB5500_PRCMU
693 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
694 depends on UX500_SOC_DB5500
697 Select this option to enable support for the DB5500 Power Reset
698 and Control Management Unit. This is basically an autonomous
699 system controller running an XP70 microprocessor, which is accessed
700 through a register map.
703 tristate "Support for CS5535 and CS5536 southbridge core functions"
705 depends on PCI && X86
707 This is the core driver for CS5535/CS5536 MFD functions. This is
708 necessary for using the board's GPIO and MFGPT functionality.
710 config MFD_TIMBERDALE
711 tristate "Support for the Timberdale FPGA"
713 depends on PCI && GPIOLIB
715 This is the core driver for the timberdale FPGA. This device is a
716 multifunction device which exposes numerous platform devices.
718 The timberdale FPGA can be found on the Intel Atom development board
719 for in-vehicle infontainment, called Russellville.
722 tristate "Intel SCH LPC"
726 LPC bridge function of the Intel SCH provides support for
727 System Management Bus and General Purpose I/O.
730 tristate "Support for RDC-R321x southbridge"
734 Say yes here if you want to have support for the RDC R-321x SoC
735 southbridge which provides access to GPIOs and Watchdog using the
736 southbridge PCI device configuration space.
738 config MFD_JANZ_CMODIO
739 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
743 This is the core driver for the Janz CMOD-IO PCI MODULbus
744 carrier board. This device is a PCI to MODULbus bridge which may
745 host many different types of MODULbus daughterboards, including
746 CAN and GPIO controllers.
748 config MFD_JZ4740_ADC
749 tristate "Support for the JZ4740 SoC ADC core"
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
816 bool "TPS65090 Power Management chips"
817 depends on I2C=y && GENERIC_HARDIRQS
821 If you say yes here you get support for the TPS65090 series of
822 Power Management chips.
823 This driver provides common support for accessing the device,
824 additional drivers must be enabled in order to use the
825 functionality of the device.
828 bool "RK610(Jetta) Multimedia support"
829 depends on I2C=y && GPIOLIB
832 if you say yes here you get support for the RK610, with func as
833 HDMI LCD LVDS TVOUT CODEC.
836 menu "Multimedia Capabilities Port drivers"
837 depends on ARCH_SA1100
844 tristate "Support SA11x0 MCP interface"
845 depends on ARCH_SA1100
850 tristate "Support for UCB1200 / UCB1300"
853 config MCP_UCB1200_TS
854 tristate "Touchscreen interface support"
855 depends on MCP_UCB1200 && INPUT