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 "Texas Instruments TWL92330/Menelaus PM chip"
162 depends on I2C=y && ARCH_OMAP2
164 If you say yes here you get support for the Texas Instruments
165 TWL92330/Menelaus Power Management chip. This include voltage
166 regulators, Dual slot memory card transceivers, real-time clock
167 and other features that are often used in portable devices like
168 cell phones and PDAs.
171 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
172 depends on I2C=y && GENERIC_HARDIRQS
174 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
175 This core driver provides register access and IRQ handling
176 facilities, and registers devices for the various functions
177 so that function-specific drivers can bind to them.
179 These multi-function chips are found on many OMAP2 and OMAP3
180 boards, providing power management, RTC, GPIO, keypad, a
181 high speed USB OTG transceiver, an audio codec (on most
182 versions) and many other features.
185 tristate "Texas Instruments TWL4030 MADC"
186 depends on TWL4030_CORE
188 This driver provides support for triton TWL4030-MADC. The
189 driver supports both RT and SW conversion methods.
191 This driver can be built as a module. If so it will be
195 bool "Support power resources on TWL4030 family chips"
196 depends on TWL4030_CORE && ARM
198 Say yes here if you want to use the power resources on the
199 TWL4030 family chips. Most of these resources are regulators,
200 which have a separate driver; some are control signals, such
201 as clock request handshaking.
203 This driver uses board-specific data to initialize the resources
204 and load scripts controlling which resources are switched off/on
205 or reset when a sleep, wakeup or warm reset event occurs.
209 depends on TWL4030_CORE
213 config TWL4030_POWEROFF
214 bool "TWL4030 Allow power-off on shutdown"
215 depends on TWL4030_CORE
217 Enables the CPU to power-off the system on shutdown
220 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
221 depends on TWL4030_CORE
225 Say yes here if you want support for TWL6030 PWM.
226 This is used to control charging LED brightness.
229 bool "Support STMicroelectronics STMPE"
230 depends on I2C=y && GENERIC_HARDIRQS
233 Support for the STMPE family of I/O Expanders from
236 Currently supported devices are:
238 STMPE811: GPIO, Touchscreen
239 STMPE1601: GPIO, Keypad
240 STMPE2401: GPIO, Keypad
241 STMPE2403: GPIO, Keypad
243 This driver provides common support for accessing the device,
244 additional drivers must be enabled in order to use the functionality
245 of the device. Currently available sub drivers are:
249 Touchscreen: stmpe-ts
252 bool "Support Toshiba TC35892 and variants"
253 depends on I2C=y && GENERIC_HARDIRQS
256 Support for the Toshiba TC35892 and variants I/O Expander.
258 This driver provides common support for accessing the device,
259 additional drivers must be enabled in order to use the
260 functionality of the device.
267 bool "Support Toshiba T7L66XB"
268 depends on ARM && HAVE_CLK
272 Support for Toshiba Mobile IO Controller T7L66XB
275 bool "Support Toshiba TC6387XB"
276 depends on ARM && HAVE_CLK
280 Support for Toshiba Mobile IO Controller TC6387XB
283 bool "Support Toshiba TC6393XB"
284 depends on GPIOLIB && ARM
288 Support for Toshiba Mobile IO Controller TC6393XB
291 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
294 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
295 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
296 usually found on PXA processors-based platforms. This includes
297 the I2C driver and the core APIs _only_, you have to select
298 individual components like LCD backlight, voltage regulators,
299 LEDs and battery-charger under the corresponding menus.
302 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
305 Say yes here to add support for Analog Devices AD5520 and ADP5501,
306 Multifunction Power Management IC. This includes
307 the I2C driver and the core APIs _only_, you have to select
308 individual components like LCD backlight, LEDs, GPIOs and Kepad
309 under the corresponding menus.
312 bool "Maxim Semiconductor MAX8925 PMIC Support"
313 depends on I2C=y && GENERIC_HARDIRQS
316 Say yes here to support for Maxim Semiconductor MAX8925. This is
317 a Power Management IC. This driver provies common support for
318 accessing the device, additional drivers must be enabled in order
319 to use the functionality of the device.
322 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
323 depends on I2C=y && GENERIC_HARDIRQS
326 Say yes here to support for Maxim Semiconductor MAX8998/8966.
327 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
328 MUIC controls on chip.
329 This driver provides common support for accessing the device;
330 additional drivers must be enabled in order to use the functionality
334 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
335 depends on I2C=y && GENERIC_HARDIRQS
338 Say yes here to support for Maxim Semiconductor MAX8998 and
339 National Semiconductor LP3974. This is a Power Management IC.
340 This driver provies common support for accessing the device,
341 additional drivers must be enabled in order to use the functionality
345 tristate "Support Wolfson Microelectronics WM8400"
349 Support for the Wolfson Microelecronics WM8400 PMIC and audio
350 CODEC. This driver provides common support for accessing
351 the device, additional drivers must be enabled in order to use
352 the functionality of the device.
356 depends on GENERIC_HARDIRQS
358 config MFD_WM831X_I2C
359 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
362 depends on I2C=y && GENERIC_HARDIRQS
364 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
365 when controlled using I2C. This driver provides common support
366 for accessing the device, additional drivers must be enabled in
367 order to use the functionality of the device.
369 config MFD_WM831X_SPI
370 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
373 depends on SPI_MASTER && GENERIC_HARDIRQS
375 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
376 when controlled using SPI. This driver provides common support
377 for accessing the device, additional drivers must be enabled in
378 order to use the functionality of the device.
382 depends on GENERIC_HARDIRQS
384 config MFD_WM8350_CONFIG_MODE_0
386 depends on MFD_WM8350
388 config MFD_WM8350_CONFIG_MODE_1
390 depends on MFD_WM8350
392 config MFD_WM8350_CONFIG_MODE_2
394 depends on MFD_WM8350
396 config MFD_WM8350_CONFIG_MODE_3
398 depends on MFD_WM8350
400 config MFD_WM8351_CONFIG_MODE_0
402 depends on MFD_WM8350
404 config MFD_WM8351_CONFIG_MODE_1
406 depends on MFD_WM8350
408 config MFD_WM8351_CONFIG_MODE_2
410 depends on MFD_WM8350
412 config MFD_WM8351_CONFIG_MODE_3
414 depends on MFD_WM8350
416 config MFD_WM8352_CONFIG_MODE_0
418 depends on MFD_WM8350
420 config MFD_WM8352_CONFIG_MODE_1
422 depends on MFD_WM8350
424 config MFD_WM8352_CONFIG_MODE_2
426 depends on MFD_WM8350
428 config MFD_WM8352_CONFIG_MODE_3
430 depends on MFD_WM8350
432 config MFD_WM8350_I2C
433 bool "Support Wolfson Microelectronics WM8350 with I2C"
435 depends on I2C=y && GENERIC_HARDIRQS
437 The WM8350 is an integrated audio and power management
438 subsystem with watchdog and RTC functionality for embedded
439 systems. This option enables core support for the WM8350 with
440 I2C as the control interface. Additional options must be
441 selected to enable support for the functionality of the chip.
444 bool "Support Wolfson Microelectronics WM8994"
446 depends on I2C=y && GENERIC_HARDIRQS
448 The WM8994 is a highly integrated hi-fi CODEC designed for
449 smartphone applicatiosn. As well as audio functionality it
450 has on board GPIO and regulator functionality which is
451 supported via the relevant subsystems. This driver provides
452 core support for the WM8994, in order to use the actual
453 functionaltiy of the device other drivers must be enabled.
456 tristate "Support for NXP PCF50633"
459 Say yes here if you have NXP PCF50633 chip on your board.
460 This core driver provides register access and IRQ handling
461 facilities, and registers devices for the various functions
462 so that function-specific drivers can bind to them.
468 tristate "Support Freescale MC13783 and MC13892"
469 depends on SPI_MASTER
473 Support for the Freescale (Atlas) PMIC and audio CODECs
475 This driver provides common support for accessing the device,
476 additional drivers must be enabled in order to use the
477 functionality of the device.
480 tristate "Support for NXP PCF50633 ADC"
481 depends on MFD_PCF50633
483 Say yes here if you want to include support for ADC in the
487 tristate "Support for NXP PCF50633 GPIO"
488 depends on MFD_PCF50633
490 Say yes here if you want to include support GPIO for pins on
494 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
495 default y if ARCH_U300 || ARCH_U8500
497 Say yes here if you have the ABX500 Mixed Signal IC family
498 chips. This core driver expose register access functions.
499 Functionality specific drivers using these functions can
500 remain unchanged when IC changes. Binding of the functions to
501 actual register access is done by the IC core driver.
504 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
505 depends on I2C=y && ABX500_CORE
507 default y if ARCH_U300
509 Select this to enable the AB3100 Mixed Signal IC core
510 functionality. This connects to a AB3100 on the I2C bus
511 and expose a number of symbols needed for dependent devices
512 to read and write registers and subscribe to events from
513 this multi-functional IC. This is needed to use other features
514 of the AB3100 such as battery-backed RTC, charging control,
515 LEDs, vibrator, system power and temperature, power management
519 tristate "ST-Ericsson AB3100 OTP functions"
520 depends on AB3100_CORE
521 default y if AB3100_CORE
523 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
524 programmable memory) support. This exposes a sysfs file to read
529 depends on GENERIC_HARDIRQS && SPI_MASTER
531 This enables the PCAP ASIC present on EZX Phones. This is
532 needed for MMC, TouchScreen, Sound, USB, etc..
535 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
536 depends on GENERIC_HARDIRQS && ABX500_CORE
539 Select this option to enable access to AB8500 power management
540 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
541 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
542 the irq_chip parts for handling the Mixed Signal chip events.
543 This chip embeds various other multimedia funtionalities as well.
545 config AB8500_I2C_CORE
546 bool "AB8500 register access via PRCMU I2C"
547 depends on AB8500_CORE && UX500_SOC_DB8500
550 This enables register access to the AB8500 chip via PRCMU I2C.
551 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
552 the I2C bus is connected to the Power Reset
553 and Mangagement Unit, PRCMU.
556 bool "Enable debug info via debugfs"
557 depends on AB8500_CORE && DEBUG_FS
558 default y if DEBUG_FS
560 Select this option if you want debug information using the debug
564 bool "AB8500 GPADC driver"
565 depends on AB8500_CORE && REGULATOR_AB8500
568 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
571 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
573 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
575 Select this to enable the AB3550 Mixed Signal IC core
576 functionality. This connects to a AB3550 on the I2C bus
577 and expose a number of symbols needed for dependent devices
578 to read and write registers and subscribe to events from
579 this multi-functional IC. This is needed to use other features
580 of the AB3550 such as battery-backed RTC, charging control,
581 LEDs, vibrator, system power and temperature, power management
585 tristate "Support for CS5535 and CS5536 southbridge core functions"
587 depends on PCI && X86
589 This is the core driver for CS5535/CS5536 MFD functions. This is
590 necessary for using the board's GPIO and MFGPT functionality.
592 config MFD_TIMBERDALE
593 tristate "Support for the Timberdale FPGA"
595 depends on PCI && GPIOLIB
597 This is the core driver for the timberdale FPGA. This device is a
598 multifunction device which exposes numerous platform devices.
600 The timberdale FPGA can be found on the Intel Atom development board
601 for in-vehicle infontainment, called Russellville.
604 tristate "Intel SCH LPC"
608 LPC bridge function of the Intel SCH provides support for
609 System Management Bus and General Purpose I/O.
612 tristate "Support for RDC-R321x southbridge"
616 Say yes here if you want to have support for the RDC R-321x SoC
617 southbridge which provides access to GPIOs and Watchdog using the
618 southbridge PCI device configuration space.
620 config MFD_JANZ_CMODIO
621 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
625 This is the core driver for the Janz CMOD-IO PCI MODULbus
626 carrier board. This device is a PCI to MODULbus bridge which may
627 host many different types of MODULbus daughterboards, including
628 CAN and GPIO controllers.
630 config MFD_JZ4740_ADC
631 tristate "Support for the JZ4740 SoC ADC core"
633 depends on MACH_JZ4740
635 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
636 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
639 bool "TPS6586x Power Management chips"
640 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
643 If you say yes here you get support for the TPS6586X series of
644 Power Management chips.
645 This driver provides common support for accessing the device,
646 additional drivers must be enabled in order to use the
647 functionality of the device.
649 This driver can also be built as a module. If so, the module
650 will be called tps6586x.
653 tristate "Support for VIA VX855/VX875 integrated south bridge"
657 Say yes here to enable support for various functions of the
658 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
659 and/or vx855_gpio drivers for this to do anything useful.
661 config MFD_WL1273_CORE
662 tristate "Support for TI WL1273 FM radio."
667 This is the core driver for the TI WL1273 FM radio. This MFD
668 driver connects the radio-wl1273 V4L2 module and the wl1273
671 config MFD_OMAP_USB_HOST
672 bool "Support OMAP USBHS core driver"
673 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
676 This is the core driver for the OAMP EHCI and OHCI drivers.
677 This MFD driver does the required setup functionalities for
678 OMAP USB Host drivers.
682 menu "Multimedia Capabilities Port drivers"
683 depends on ARCH_SA1100
690 tristate "Support SA11x0 MCP interface"
691 depends on ARCH_SA1100
696 tristate "Support for UCB1200 / UCB1300"
699 config MCP_UCB1200_TS
700 tristate "Touchscreen interface support"
701 depends on MCP_UCB1200 && INPUT