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 tristate "Texas Instruments TWL4030 MADC"
200 depends on TWL4030_CORE
202 This driver provides support for triton TWL4030-MADC. The
203 driver supports both RT and SW conversion methods.
205 This driver can be built as a module. If so it will be
209 bool "Support power resources on TWL4030 family chips"
210 depends on TWL4030_CORE && ARM
212 Say yes here if you want to use the power resources on the
213 TWL4030 family chips. Most of these resources are regulators,
214 which have a separate driver; some are control signals, such
215 as clock request handshaking.
217 This driver uses board-specific data to initialize the resources
218 and load scripts controlling which resources are switched off/on
219 or reset when a sleep, wakeup or warm reset event occurs.
221 config MFD_TWL4030_AUDIO
223 depends on TWL4030_CORE
228 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
229 depends on TWL4030_CORE
233 Say yes here if you want support for TWL6030 PWM.
234 This is used to control charging LED brightness.
238 depends on TWL4030_CORE && GENERIC_HARDIRQS
243 bool "Support STMicroelectronics STMPE"
244 depends on I2C=y && GENERIC_HARDIRQS
247 Support for the STMPE family of I/O Expanders from
250 Currently supported devices are:
252 STMPE811: GPIO, Touchscreen
253 STMPE1601: GPIO, Keypad
254 STMPE2401: GPIO, Keypad
255 STMPE2403: GPIO, Keypad
257 This driver provides common support for accessing the device,
258 additional drivers must be enabled in order to use the functionality
259 of the device. Currently available sub drivers are:
263 Touchscreen: stmpe-ts
266 bool "Support Toshiba TC35892 and variants"
267 depends on I2C=y && GENERIC_HARDIRQS
270 Support for the Toshiba TC35892 and variants I/O Expander.
272 This driver provides common support for accessing the device,
273 additional drivers must be enabled in order to use the
274 functionality of the device.
281 bool "Support Toshiba T7L66XB"
282 depends on ARM && HAVE_CLK
286 Support for Toshiba Mobile IO Controller T7L66XB
289 bool "Support Toshiba TC6387XB"
290 depends on ARM && HAVE_CLK
294 Support for Toshiba Mobile IO Controller TC6387XB
297 bool "Support Toshiba TC6393XB"
298 depends on GPIOLIB && ARM
302 Support for Toshiba Mobile IO Controller TC6393XB
305 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
308 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
309 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
310 usually found on PXA processors-based platforms. This includes
311 the I2C driver and the core APIs _only_, you have to select
312 individual components like LCD backlight, voltage regulators,
313 LEDs and battery-charger under the corresponding menus.
316 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
319 Say yes here to add support for Analog Devices AD5520 and ADP5501,
320 Multifunction Power Management IC. This includes
321 the I2C driver and the core APIs _only_, you have to select
322 individual components like LCD backlight, LEDs, GPIOs and Kepad
323 under the corresponding menus.
326 bool "Maxim Semiconductor MAX8925 PMIC Support"
327 depends on I2C=y && GENERIC_HARDIRQS
330 Say yes here to support for Maxim Semiconductor MAX8925. This is
331 a Power Management IC. This driver provies common support for
332 accessing the device, additional drivers must be enabled in order
333 to use the functionality of the device.
336 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
337 depends on I2C=y && GENERIC_HARDIRQS
340 Say yes here to support for Maxim Semiconductor MAX8998/8966.
341 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
342 MUIC controls on chip.
343 This driver provides common support for accessing the device;
344 additional drivers must be enabled in order to use the functionality
348 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
349 depends on I2C=y && GENERIC_HARDIRQS
352 Say yes here to support for Maxim Semiconductor MAX8998 and
353 National Semiconductor LP3974. This is a Power Management IC.
354 This driver provies common support for accessing the device,
355 additional drivers must be enabled in order to use the functionality
359 tristate "Support Wolfson Microelectronics WM8400"
363 Support for the Wolfson Microelecronics WM8400 PMIC and audio
364 CODEC. This driver provides common support for accessing
365 the device, additional drivers must be enabled in order to use
366 the functionality of the device.
370 depends on GENERIC_HARDIRQS
372 config MFD_WM831X_I2C
373 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
376 depends on I2C=y && GENERIC_HARDIRQS
378 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
379 when controlled using I2C. This driver provides common support
380 for accessing the device, additional drivers must be enabled in
381 order to use the functionality of the device.
383 config MFD_WM831X_SPI
384 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
387 depends on SPI_MASTER && GENERIC_HARDIRQS
389 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
390 when controlled using SPI. This driver provides common support
391 for accessing the device, additional drivers must be enabled in
392 order to use the functionality of the device.
396 depends on GENERIC_HARDIRQS
398 config MFD_WM8350_CONFIG_MODE_0
400 depends on MFD_WM8350
402 config MFD_WM8350_CONFIG_MODE_1
404 depends on MFD_WM8350
406 config MFD_WM8350_CONFIG_MODE_2
408 depends on MFD_WM8350
410 config MFD_WM8350_CONFIG_MODE_3
412 depends on MFD_WM8350
414 config MFD_WM8351_CONFIG_MODE_0
416 depends on MFD_WM8350
418 config MFD_WM8351_CONFIG_MODE_1
420 depends on MFD_WM8350
422 config MFD_WM8351_CONFIG_MODE_2
424 depends on MFD_WM8350
426 config MFD_WM8351_CONFIG_MODE_3
428 depends on MFD_WM8350
430 config MFD_WM8352_CONFIG_MODE_0
432 depends on MFD_WM8350
434 config MFD_WM8352_CONFIG_MODE_1
436 depends on MFD_WM8350
438 config MFD_WM8352_CONFIG_MODE_2
440 depends on MFD_WM8350
442 config MFD_WM8352_CONFIG_MODE_3
444 depends on MFD_WM8350
446 config MFD_WM8350_I2C
447 bool "Support Wolfson Microelectronics WM8350 with I2C"
449 depends on I2C=y && GENERIC_HARDIRQS
451 The WM8350 is an integrated audio and power management
452 subsystem with watchdog and RTC functionality for embedded
453 systems. This option enables core support for the WM8350 with
454 I2C as the control interface. Additional options must be
455 selected to enable support for the functionality of the chip.
458 bool "Support Wolfson Microelectronics WM8994"
460 depends on I2C=y && GENERIC_HARDIRQS
462 The WM8994 is a highly integrated hi-fi CODEC designed for
463 smartphone applicatiosn. As well as audio functionality it
464 has on board GPIO and regulator functionality which is
465 supported via the relevant subsystems. This driver provides
466 core support for the WM8994, in order to use the actual
467 functionaltiy of the device other drivers must be enabled.
470 tristate "Support for NXP PCF50633"
473 Say yes here if you have NXP PCF50633 chip on your board.
474 This core driver provides register access and IRQ handling
475 facilities, and registers devices for the various functions
476 so that function-specific drivers can bind to them.
479 tristate "Support for NXP PCF50633 ADC"
480 depends on MFD_PCF50633
482 Say yes here if you want to include support for ADC in the
486 tristate "Support for NXP PCF50633 GPIO"
487 depends on MFD_PCF50633
489 Say yes here if you want to include support GPIO for pins on
496 tristate "Support Freescale MC13783 and MC13892"
497 depends on SPI_MASTER
501 Support for the Freescale (Atlas) PMIC and audio CODECs
503 This driver provides common support for accessing the device,
504 additional drivers must be enabled in order to use the
505 functionality of the device.
508 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
509 default y if ARCH_U300 || ARCH_U8500
511 Say yes here if you have the ABX500 Mixed Signal IC family
512 chips. This core driver expose register access functions.
513 Functionality specific drivers using these functions can
514 remain unchanged when IC changes. Binding of the functions to
515 actual register access is done by the IC core driver.
518 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
519 depends on I2C=y && ABX500_CORE
521 default y if ARCH_U300
523 Select this to enable the AB3100 Mixed Signal IC core
524 functionality. This connects to a AB3100 on the I2C bus
525 and expose a number of symbols needed for dependent devices
526 to read and write registers and subscribe to events from
527 this multi-functional IC. This is needed to use other features
528 of the AB3100 such as battery-backed RTC, charging control,
529 LEDs, vibrator, system power and temperature, power management
533 tristate "ST-Ericsson AB3100 OTP functions"
534 depends on AB3100_CORE
535 default y if AB3100_CORE
537 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
538 programmable memory) support. This exposes a sysfs file to read
543 depends on GENERIC_HARDIRQS && SPI_MASTER
545 This enables the PCAP ASIC present on EZX Phones. This is
546 needed for MMC, TouchScreen, Sound, USB, etc..
549 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
550 depends on GENERIC_HARDIRQS && ABX500_CORE
553 Select this option to enable access to AB8500 power management
554 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
555 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
556 the irq_chip parts for handling the Mixed Signal chip events.
557 This chip embeds various other multimedia funtionalities as well.
559 config AB8500_I2C_CORE
560 bool "AB8500 register access via PRCMU I2C"
561 depends on AB8500_CORE && MFD_DB8500_PRCMU
564 This enables register access to the AB8500 chip via PRCMU I2C.
565 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
566 the I2C bus is connected to the Power Reset
567 and Mangagement Unit, PRCMU.
570 bool "Enable debug info via debugfs"
571 depends on AB8500_CORE && DEBUG_FS
572 default y if DEBUG_FS
574 Select this option if you want debug information using the debug
578 bool "AB8500 GPADC driver"
579 depends on AB8500_CORE && REGULATOR_AB8500
582 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
585 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
587 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
589 Select this to enable the AB3550 Mixed Signal IC core
590 functionality. This connects to a AB3550 on the I2C bus
591 and expose a number of symbols needed for dependent devices
592 to read and write registers and subscribe to events from
593 this multi-functional IC. This is needed to use other features
594 of the AB3550 such as battery-backed RTC, charging control,
595 LEDs, vibrator, system power and temperature, power management
598 config MFD_DB8500_PRCMU
599 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
600 depends on UX500_SOC_DB8500
603 Select this option to enable support for the DB8500 Power Reset
604 and Control Management Unit. This is basically an autonomous
605 system controller running an XP70 microprocessor, which is accessed
606 through a register map.
608 config MFD_DB5500_PRCMU
609 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
610 depends on UX500_SOC_DB5500
613 Select this option to enable support for the DB5500 Power Reset
614 and Control Management Unit. This is basically an autonomous
615 system controller running an XP70 microprocessor, which is accessed
616 through a register map.
619 tristate "Support for CS5535 and CS5536 southbridge core functions"
621 depends on PCI && X86
623 This is the core driver for CS5535/CS5536 MFD functions. This is
624 necessary for using the board's GPIO and MFGPT functionality.
626 config MFD_TIMBERDALE
627 tristate "Support for the Timberdale FPGA"
629 depends on PCI && GPIOLIB
631 This is the core driver for the timberdale FPGA. This device is a
632 multifunction device which exposes numerous platform devices.
634 The timberdale FPGA can be found on the Intel Atom development board
635 for in-vehicle infontainment, called Russellville.
638 tristate "Intel SCH LPC"
642 LPC bridge function of the Intel SCH provides support for
643 System Management Bus and General Purpose I/O.
646 tristate "Support for RDC-R321x southbridge"
650 Say yes here if you want to have support for the RDC R-321x SoC
651 southbridge which provides access to GPIOs and Watchdog using the
652 southbridge PCI device configuration space.
654 config MFD_JANZ_CMODIO
655 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
659 This is the core driver for the Janz CMOD-IO PCI MODULbus
660 carrier board. This device is a PCI to MODULbus bridge which may
661 host many different types of MODULbus daughterboards, including
662 CAN and GPIO controllers.
664 config MFD_JZ4740_ADC
665 tristate "Support for the JZ4740 SoC ADC core"
667 depends on MACH_JZ4740
669 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
670 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
673 tristate "Support for VIA VX855/VX875 integrated south bridge"
677 Say yes here to enable support for various functions of the
678 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
679 and/or vx855_gpio drivers for this to do anything useful.
681 config MFD_WL1273_CORE
682 tristate "Support for TI WL1273 FM radio."
687 This is the core driver for the TI WL1273 FM radio. This MFD
688 driver connects the radio-wl1273 V4L2 module and the wl1273
691 config MFD_OMAP_USB_HOST
692 bool "Support OMAP USBHS core driver"
693 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
696 This is the core driver for the OAMP EHCI and OHCI drivers.
697 This MFD driver does the required setup functionalities for
698 OMAP USB Host drivers.
703 config MFD_PM8921_CORE
704 tristate "Qualcomm PM8921 PMIC chip"
709 If you say yes to this option, support will be included for the
710 built-in PM8921 PMIC chip.
712 This is required if your board has a PM8921 and uses its features,
713 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
715 Say M here if you want to include support for PM8921 chip as a module.
716 This will build a module called "pm8921-core".
718 config MFD_PM8XXX_IRQ
719 bool "Support for Qualcomm PM8xxx IRQ features"
720 depends on MFD_PM8XXX
721 default y if MFD_PM8XXX
723 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
725 This is required to use certain other PM 8xxx features, such as GPIO
729 bool "TPS65910 Power Management chip"
730 depends on I2C=y && GPIOLIB
734 if you say yes here you get support for the TPS65910 series of
735 Power Management chips.
737 config TPS65911_COMPARATOR
742 menu "Multimedia Capabilities Port drivers"
743 depends on ARCH_SA1100
750 tristate "Support SA11x0 MCP interface"
751 depends on ARCH_SA1100
756 tristate "Support for UCB1200 / UCB1300"
759 config MCP_UCB1200_TS
760 tristate "Touchscreen interface support"
761 depends on MCP_UCB1200 && INPUT