2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
17 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
18 This includes the I2C driver and the core APIs _only_, you have to
19 select individual components like voltage regulators, RTC and
20 battery-charger under the corresponding menus.
23 tristate "Support for Silicon Motion SM501"
25 This is the core driver for the Silicon Motion SM501 multimedia
26 companion chip. This device is a multifunction device which may
27 provide numerous interfaces including USB host controller, USB gadget,
28 asynchronous serial ports, audio functions, and a dual display video
29 interface. The device may be connected by PCI or local bus with
30 varying functions enabled.
33 bool "Export GPIO via GPIO layer"
34 depends on MFD_SM501 && GPIOLIB
36 This option uses the gpio library layer to export the 64 GPIO
37 lines on the SM501. The platform data is used to supply the
38 base number for the first GPIO line to register.
41 bool "Support for Compaq ASIC3"
42 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
45 This driver supports the ASIC3 multifunction chip found on many
46 PDAs (mainly iPAQ and HTC based ones)
48 config MFD_DAVINCI_VOICECODEC
52 config MFD_DM355EVM_MSP
53 bool "DaVinci DM355 EVM microcontroller"
54 depends on I2C=y && MACH_DAVINCI_DM355_EVM
56 This driver supports the MSP430 microcontroller used on these
57 boards. MSP430 firmware manages resets and power sequencing,
58 inputs from buttons and the IR remote, LEDs, an RTC, and more.
61 tristate "TI Sequencer Serial Port support"
62 depends on ARCH_DAVINCI_TNETV107X
65 Say Y here if you want support for the Sequencer Serial Port
66 in a Texas Instruments TNETV107X SoC.
68 To compile this driver as a module, choose M here: the
69 module will be called ti-ssp.
72 bool "HTC EGPIO support"
73 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
75 This driver supports the CPLD egpio chip present on
76 several HTC phones. It provides basic support for input
77 pins, output pins, and irqs.
80 tristate "HTC PASIC3 LED/DS1WM chip support"
83 This core driver provides register access for the LED/DS1WM
84 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
85 HTC Magician devices, respectively. Actual functionality is
86 handled by the leds-pasic3 and ds1wm drivers.
89 bool "HTC I2C PLD chip support"
90 depends on I2C=y && GPIOLIB
92 If you say yes here you get support for the supposed CPLD
93 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
94 This device provides input and output GPIOs through an I2C
95 interface to one or more sub-chips.
98 tristate "Philips UCB1400 Core driver"
102 This enables support for the Philips UCB1400 core functions.
103 The UCB1400 is an AC97 audio codec.
105 To compile this driver as a module, choose M here: the
106 module will be called ucb1400_core.
109 tristate "TPS61050/61052 Boost Converters"
113 select REGULATOR_FIXED_VOLTAGE
115 This option enables a driver for the TP61050/TPS61052
116 high-power "white LED driver". This boost converter is
117 sometimes used for other things than white LEDs, and
118 also contains a GPIO pin.
121 tristate "TPS6501x Power Management chips"
122 depends on I2C && GPIOLIB
123 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
125 If you say yes here you get support for the TPS6501x series of
126 Power Management chips. These include voltage regulators,
127 lithium ion/polymer battery charging, and other features that
128 are often used in portable devices like cell phones and cameras.
130 This driver can also be built as a module. If so, the module
131 will be called tps65010.
134 tristate "TPS6507x Power Management / Touch Screen chips"
138 If you say yes here you get support for the TPS6507x series of
139 Power Management / Touch Screen chips. These include voltage
140 regulators, lithium ion/polymer battery charging, touch screen
141 and other features that are often used in portable devices.
142 This driver can also be built as a module. If so, the module
143 will be called tps6507x.
146 bool "TPS6586x Power Management chips"
147 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
150 If you say yes here you get support for the TPS6586X series of
151 Power Management chips.
152 This driver provides common support for accessing the device,
153 additional drivers must be enabled in order to use the
154 functionality of the device.
156 This driver can also be built as a module. If so, the module
157 will be called tps6586x.
160 bool "TPS65910 Power Management chip"
161 depends on I2C=y && GPIOLIB
165 if you say yes here you get support for the TPS65910 series of
166 Power Management chips.
172 config MFD_TPS65912_I2C
173 bool "TPS95612 Power Management chip with I2C"
176 depends on I2C=y && GPIOLIB
178 If you say yes here you get support for the TPS65912 series of
179 PM chips with I2C interface.
181 config MFD_TPS65912_SPI
182 bool "TPS65912 Power Management chip with SPI"
185 depends on SPI_MASTER && GPIOLIB
187 If you say yes here you get support for the TPS65912 series of
188 PM chips with SPI interface.
191 bool "Texas Instruments TWL92330/Menelaus PM chip"
192 depends on I2C=y && ARCH_OMAP2
194 If you say yes here you get support for the Texas Instruments
195 TWL92330/Menelaus Power Management chip. This include voltage
196 regulators, Dual slot memory card transceivers, real-time clock
197 and other features that are often used in portable devices like
198 cell phones and PDAs.
201 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
202 depends on I2C=y && GENERIC_HARDIRQS
204 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
205 This core driver provides register access and IRQ handling
206 facilities, and registers devices for the various functions
207 so that function-specific drivers can bind to them.
209 These multi-function chips are found on many OMAP2 and OMAP3
210 boards, providing power management, RTC, GPIO, keypad, a
211 high speed USB OTG transceiver, an audio codec (on most
212 versions) and many other features.
215 tristate "Texas Instruments TWL4030 MADC"
216 depends on TWL4030_CORE
218 This driver provides support for triton TWL4030-MADC. The
219 driver supports both RT and SW conversion methods.
221 This driver can be built as a module. If so it will be
225 bool "Support power resources on TWL4030 family chips"
226 depends on TWL4030_CORE && ARM
228 Say yes here if you want to use the power resources on the
229 TWL4030 family chips. Most of these resources are regulators,
230 which have a separate driver; some are control signals, such
231 as clock request handshaking.
233 This driver uses board-specific data to initialize the resources
234 and load scripts controlling which resources are switched off/on
235 or reset when a sleep, wakeup or warm reset event occurs.
237 config MFD_TWL4030_AUDIO
239 depends on TWL4030_CORE
244 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
245 depends on TWL4030_CORE
249 Say yes here if you want support for TWL6030 PWM.
250 This is used to control charging LED brightness.
254 depends on TWL4030_CORE && GENERIC_HARDIRQS
259 bool "Support STMicroelectronics STMPE"
260 depends on I2C=y && GENERIC_HARDIRQS
263 Support for the STMPE family of I/O Expanders from
266 Currently supported devices are:
268 STMPE811: GPIO, Touchscreen
269 STMPE1601: GPIO, Keypad
270 STMPE2401: GPIO, Keypad
271 STMPE2403: GPIO, Keypad
273 This driver provides common support for accessing the device,
274 additional drivers must be enabled in order to use the functionality
275 of the device. Currently available sub drivers are:
279 Touchscreen: stmpe-ts
282 bool "Support Toshiba TC35892 and variants"
283 depends on I2C=y && GENERIC_HARDIRQS
286 Support for the Toshiba TC35892 and variants I/O Expander.
288 This driver provides common support for accessing the device,
289 additional drivers must be enabled in order to use the
290 functionality of the device.
297 bool "Support Toshiba T7L66XB"
298 depends on ARM && HAVE_CLK
302 Support for Toshiba Mobile IO Controller T7L66XB
305 bool "Support Toshiba TC6387XB"
306 depends on ARM && HAVE_CLK
310 Support for Toshiba Mobile IO Controller TC6387XB
313 bool "Support Toshiba TC6393XB"
314 depends on GPIOLIB && ARM
318 Support for Toshiba Mobile IO Controller TC6393XB
321 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
324 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
325 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
326 usually found on PXA processors-based platforms. This includes
327 the I2C driver and the core APIs _only_, you have to select
328 individual components like LCD backlight, voltage regulators,
329 LEDs and battery-charger under the corresponding menus.
335 config MFD_DA9052_SPI
336 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
340 depends on SPI_MASTER=y
342 Support for the Dialog Semiconductor DA9052 PMIC
343 when controlled using SPI. This driver provides common support
344 for accessing the device, additional drivers must be enabled in
345 order to use the functionality of the device.
347 config MFD_DA9052_I2C
348 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
354 Support for the Dialog Semiconductor DA9052 PMIC
355 when controlled using I2C. This driver provides common support
356 for accessing the device, additional drivers must be enabled in
357 order to use the functionality of the device.
360 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
363 Say yes here to add support for Analog Devices AD5520 and ADP5501,
364 Multifunction Power Management IC. This includes
365 the I2C driver and the core APIs _only_, you have to select
366 individual components like LCD backlight, LEDs, GPIOs and Kepad
367 under the corresponding menus.
370 bool "Maxim Semiconductor MAX8925 PMIC Support"
371 depends on I2C=y && GENERIC_HARDIRQS
374 Say yes here to support for Maxim Semiconductor MAX8925. This is
375 a Power Management IC. This driver provies common support for
376 accessing the device, additional drivers must be enabled in order
377 to use the functionality of the device.
380 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
381 depends on I2C=y && GENERIC_HARDIRQS
384 Say yes here to support for Maxim Semiconductor MAX8998/8966.
385 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
386 MUIC controls on chip.
387 This driver provides common support for accessing the device;
388 additional drivers must be enabled in order to use the functionality
392 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
393 depends on I2C=y && GENERIC_HARDIRQS
396 Say yes here to support for Maxim Semiconductor MAX8998 and
397 National Semiconductor LP3974. This is a Power Management IC.
398 This driver provies common support for accessing the device,
399 additional drivers must be enabled in order to use the functionality
403 tristate "Support Wolfson Microelectronics WM8400"
408 Support for the Wolfson Microelecronics WM8400 PMIC and audio
409 CODEC. This driver provides common support for accessing
410 the device, additional drivers must be enabled in order to use
411 the functionality of the device.
415 depends on GENERIC_HARDIRQS
417 config MFD_WM831X_I2C
418 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
422 depends on I2C=y && GENERIC_HARDIRQS
424 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
425 when controlled using I2C. This driver provides common support
426 for accessing the device, additional drivers must be enabled in
427 order to use the functionality of the device.
429 config MFD_WM831X_SPI
430 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
434 depends on SPI_MASTER && GENERIC_HARDIRQS
436 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
437 when controlled using SPI. This driver provides common support
438 for accessing the device, additional drivers must be enabled in
439 order to use the functionality of the device.
443 depends on GENERIC_HARDIRQS
445 config MFD_WM8350_CONFIG_MODE_0
447 depends on MFD_WM8350
449 config MFD_WM8350_CONFIG_MODE_1
451 depends on MFD_WM8350
453 config MFD_WM8350_CONFIG_MODE_2
455 depends on MFD_WM8350
457 config MFD_WM8350_CONFIG_MODE_3
459 depends on MFD_WM8350
461 config MFD_WM8351_CONFIG_MODE_0
463 depends on MFD_WM8350
465 config MFD_WM8351_CONFIG_MODE_1
467 depends on MFD_WM8350
469 config MFD_WM8351_CONFIG_MODE_2
471 depends on MFD_WM8350
473 config MFD_WM8351_CONFIG_MODE_3
475 depends on MFD_WM8350
477 config MFD_WM8352_CONFIG_MODE_0
479 depends on MFD_WM8350
481 config MFD_WM8352_CONFIG_MODE_1
483 depends on MFD_WM8350
485 config MFD_WM8352_CONFIG_MODE_2
487 depends on MFD_WM8350
489 config MFD_WM8352_CONFIG_MODE_3
491 depends on MFD_WM8350
493 config MFD_WM8350_I2C
494 bool "Support Wolfson Microelectronics WM8350 with I2C"
496 depends on I2C=y && GENERIC_HARDIRQS
498 The WM8350 is an integrated audio and power management
499 subsystem with watchdog and RTC functionality for embedded
500 systems. This option enables core support for the WM8350 with
501 I2C as the control interface. Additional options must be
502 selected to enable support for the functionality of the chip.
505 bool "Support Wolfson Microelectronics WM8994"
508 depends on I2C=y && GENERIC_HARDIRQS
510 The WM8994 is a highly integrated hi-fi CODEC designed for
511 smartphone applicatiosn. As well as audio functionality it
512 has on board GPIO and regulator functionality which is
513 supported via the relevant subsystems. This driver provides
514 core support for the WM8994, in order to use the actual
515 functionaltiy of the device other drivers must be enabled.
518 tristate "Support for NXP PCF50633"
522 Say yes here if you have NXP PCF50633 chip on your board.
523 This core driver provides register access and IRQ handling
524 facilities, and registers devices for the various functions
525 so that function-specific drivers can bind to them.
528 tristate "Support for NXP PCF50633 ADC"
529 depends on MFD_PCF50633
531 Say yes here if you want to include support for ADC in the
535 tristate "Support for NXP PCF50633 GPIO"
536 depends on MFD_PCF50633
538 Say yes here if you want to include support GPIO for pins on
545 tristate "Support Freescale MC13783 and MC13892"
546 depends on SPI_MASTER
550 Support for the Freescale (Atlas) PMIC and audio CODECs
552 This driver provides common support for accessing the device,
553 additional drivers must be enabled in order to use the
554 functionality of the device.
557 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
558 default y if ARCH_U300 || ARCH_U8500
560 Say yes here if you have the ABX500 Mixed Signal IC family
561 chips. This core driver expose register access functions.
562 Functionality specific drivers using these functions can
563 remain unchanged when IC changes. Binding of the functions to
564 actual register access is done by the IC core driver.
567 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
568 depends on I2C=y && ABX500_CORE
570 default y if ARCH_U300
572 Select this to enable the AB3100 Mixed Signal IC core
573 functionality. This connects to a AB3100 on the I2C bus
574 and expose a number of symbols needed for dependent devices
575 to read and write registers and subscribe to events from
576 this multi-functional IC. This is needed to use other features
577 of the AB3100 such as battery-backed RTC, charging control,
578 LEDs, vibrator, system power and temperature, power management
582 tristate "ST-Ericsson AB3100 OTP functions"
583 depends on AB3100_CORE
584 default y if AB3100_CORE
586 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
587 programmable memory) support. This exposes a sysfs file to read
592 depends on GENERIC_HARDIRQS && SPI_MASTER
594 This enables the PCAP ASIC present on EZX Phones. This is
595 needed for MMC, TouchScreen, Sound, USB, etc..
598 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
599 depends on ABX500_CORE && MFD_DB5500_PRCMU
602 Select this option to enable access to AB5500 power management
603 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
604 This chip embeds various other multimedia funtionalities as well.
607 bool "Enable debug info via debugfs"
608 depends on AB5500_CORE && DEBUG_FS
609 default y if DEBUG_FS
611 Select this option if you want debug information from the AB5500
612 using the debug filesystem, debugfs.
615 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
616 depends on GENERIC_HARDIRQS && ABX500_CORE
619 Select this option to enable access to AB8500 power management
620 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
621 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
622 the irq_chip parts for handling the Mixed Signal chip events.
623 This chip embeds various other multimedia funtionalities as well.
625 config AB8500_I2C_CORE
626 bool "AB8500 register access via PRCMU I2C"
627 depends on AB8500_CORE && MFD_DB8500_PRCMU
630 This enables register access to the AB8500 chip via PRCMU I2C.
631 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
632 the I2C bus is connected to the Power Reset
633 and Mangagement Unit, PRCMU.
636 bool "Enable debug info via debugfs"
637 depends on AB8500_CORE && DEBUG_FS
638 default y if DEBUG_FS
640 Select this option if you want debug information using the debug
644 bool "AB8500 GPADC driver"
645 depends on AB8500_CORE && REGULATOR_AB8500
648 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
650 config MFD_DB8500_PRCMU
651 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
652 depends on UX500_SOC_DB8500
655 Select this option to enable support for the DB8500 Power Reset
656 and Control Management Unit. This is basically an autonomous
657 system controller running an XP70 microprocessor, which is accessed
658 through a register map.
660 config MFD_DB5500_PRCMU
661 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
662 depends on UX500_SOC_DB5500
665 Select this option to enable support for the DB5500 Power Reset
666 and Control Management Unit. This is basically an autonomous
667 system controller running an XP70 microprocessor, which is accessed
668 through a register map.
671 tristate "Support for CS5535 and CS5536 southbridge core functions"
673 depends on PCI && X86
675 This is the core driver for CS5535/CS5536 MFD functions. This is
676 necessary for using the board's GPIO and MFGPT functionality.
678 config MFD_TIMBERDALE
679 tristate "Support for the Timberdale FPGA"
681 depends on PCI && GPIOLIB
683 This is the core driver for the timberdale FPGA. This device is a
684 multifunction device which exposes numerous platform devices.
686 The timberdale FPGA can be found on the Intel Atom development board
687 for in-vehicle infontainment, called Russellville.
690 tristate "Intel SCH LPC"
694 LPC bridge function of the Intel SCH provides support for
695 System Management Bus and General Purpose I/O.
698 tristate "Support for RDC-R321x southbridge"
702 Say yes here if you want to have support for the RDC R-321x SoC
703 southbridge which provides access to GPIOs and Watchdog using the
704 southbridge PCI device configuration space.
706 config MFD_JANZ_CMODIO
707 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
711 This is the core driver for the Janz CMOD-IO PCI MODULbus
712 carrier board. This device is a PCI to MODULbus bridge which may
713 host many different types of MODULbus daughterboards, including
714 CAN and GPIO controllers.
716 config MFD_JZ4740_ADC
717 bool "Support for the JZ4740 SoC ADC core"
719 select GENERIC_IRQ_CHIP
720 depends on MACH_JZ4740
722 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
723 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
726 tristate "Support for VIA VX855/VX875 integrated south bridge"
730 Say yes here to enable support for various functions of the
731 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
732 and/or vx855_gpio drivers for this to do anything useful.
734 config MFD_WL1273_CORE
735 tristate "Support for TI WL1273 FM radio."
740 This is the core driver for the TI WL1273 FM radio. This MFD
741 driver connects the radio-wl1273 V4L2 module and the wl1273
744 config MFD_OMAP_USB_HOST
745 bool "Support OMAP USBHS core driver"
746 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
749 This is the core driver for the OAMP EHCI and OHCI drivers.
750 This MFD driver does the required setup functionalities for
751 OMAP USB Host drivers.
756 config MFD_PM8921_CORE
757 tristate "Qualcomm PM8921 PMIC chip"
762 If you say yes to this option, support will be included for the
763 built-in PM8921 PMIC chip.
765 This is required if your board has a PM8921 and uses its features,
766 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
768 Say M here if you want to include support for PM8921 chip as a module.
769 This will build a module called "pm8921-core".
771 config MFD_PM8XXX_IRQ
772 bool "Support for Qualcomm PM8xxx IRQ features"
773 depends on MFD_PM8XXX
774 default y if MFD_PM8XXX
776 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
778 This is required to use certain other PM 8xxx features, such as GPIO
781 config TPS65911_COMPARATOR
784 config MFD_AAT2870_CORE
785 bool "Support for the AnalogicTech AAT2870"
787 depends on I2C=y && GPIOLIB
789 If you say yes here you get support for the AAT2870.
790 This driver provides common support for accessing the device,
791 additional drivers must be enabled in order to use the
792 functionality of the device.
794 config MFD_INTEL_MSIC
795 bool "Support for Intel MSIC"
796 depends on INTEL_SCU_IPC
799 Select this option to enable access to Intel MSIC (Avatele
800 Passage) chip. This chip embeds audio, battery, GPIO, etc.
801 devices used in Intel Medfield platforms.
806 menu "Multimedia Capabilities Port drivers"
807 depends on ARCH_SA1100
814 tristate "Support SA11x0 MCP interface"
815 depends on ARCH_SA1100
820 tristate "Support for UCB1200 / UCB1300"
823 config MCP_UCB1200_TS
824 tristate "Touchscreen interface support"
825 depends on MCP_UCB1200 && INPUT