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.
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.
237 bool "Support STMicroelectronics STMPE"
238 depends on I2C=y && GENERIC_HARDIRQS
241 Support for the STMPE family of I/O Expanders from
244 Currently supported devices are:
246 STMPE811: GPIO, Touchscreen
247 STMPE1601: GPIO, Keypad
248 STMPE2401: GPIO, Keypad
249 STMPE2403: GPIO, Keypad
251 This driver provides common support for accessing the device,
252 additional drivers must be enabled in order to use the functionality
253 of the device. Currently available sub drivers are:
257 Touchscreen: stmpe-ts
260 bool "Support Toshiba TC35892 and variants"
261 depends on I2C=y && GENERIC_HARDIRQS
264 Support for the Toshiba TC35892 and variants I/O Expander.
266 This driver provides common support for accessing the device,
267 additional drivers must be enabled in order to use the
268 functionality of the device.
275 bool "Support Toshiba T7L66XB"
276 depends on ARM && HAVE_CLK
280 Support for Toshiba Mobile IO Controller T7L66XB
283 bool "Support Toshiba TC6387XB"
284 depends on ARM && HAVE_CLK
288 Support for Toshiba Mobile IO Controller TC6387XB
291 bool "Support Toshiba TC6393XB"
292 depends on GPIOLIB && ARM
296 Support for Toshiba Mobile IO Controller TC6393XB
299 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
302 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
303 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
304 usually found on PXA processors-based platforms. This includes
305 the I2C driver and the core APIs _only_, you have to select
306 individual components like LCD backlight, voltage regulators,
307 LEDs and battery-charger under the corresponding menus.
310 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
313 Say yes here to add support for Analog Devices AD5520 and ADP5501,
314 Multifunction Power Management IC. This includes
315 the I2C driver and the core APIs _only_, you have to select
316 individual components like LCD backlight, LEDs, GPIOs and Kepad
317 under the corresponding menus.
320 bool "Maxim Semiconductor MAX8925 PMIC Support"
321 depends on I2C=y && GENERIC_HARDIRQS
324 Say yes here to support for Maxim Semiconductor MAX8925. This is
325 a Power Management IC. This driver provies common support for
326 accessing the device, additional drivers must be enabled in order
327 to use the functionality of the device.
330 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
331 depends on I2C=y && GENERIC_HARDIRQS
334 Say yes here to support for Maxim Semiconductor MAX8998/8966.
335 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
336 MUIC controls on chip.
337 This driver provides common support for accessing the device;
338 additional drivers must be enabled in order to use the functionality
342 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
343 depends on I2C=y && GENERIC_HARDIRQS
346 Say yes here to support for Maxim Semiconductor MAX8998 and
347 National Semiconductor LP3974. This is a Power Management IC.
348 This driver provies common support for accessing the device,
349 additional drivers must be enabled in order to use the functionality
353 tristate "Support Wolfson Microelectronics WM8400"
357 Support for the Wolfson Microelecronics WM8400 PMIC and audio
358 CODEC. This driver provides common support for accessing
359 the device, additional drivers must be enabled in order to use
360 the functionality of the device.
364 depends on GENERIC_HARDIRQS
366 config MFD_WM831X_I2C
367 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
370 depends on I2C=y && GENERIC_HARDIRQS
372 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
373 when controlled using I2C. This driver provides common support
374 for accessing the device, additional drivers must be enabled in
375 order to use the functionality of the device.
377 config MFD_WM831X_SPI
378 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
381 depends on SPI_MASTER && GENERIC_HARDIRQS
383 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
384 when controlled using SPI. This driver provides common support
385 for accessing the device, additional drivers must be enabled in
386 order to use the functionality of the device.
390 depends on GENERIC_HARDIRQS
392 config MFD_WM8350_CONFIG_MODE_0
394 depends on MFD_WM8350
396 config MFD_WM8350_CONFIG_MODE_1
398 depends on MFD_WM8350
400 config MFD_WM8350_CONFIG_MODE_2
402 depends on MFD_WM8350
404 config MFD_WM8350_CONFIG_MODE_3
406 depends on MFD_WM8350
408 config MFD_WM8351_CONFIG_MODE_0
410 depends on MFD_WM8350
412 config MFD_WM8351_CONFIG_MODE_1
414 depends on MFD_WM8350
416 config MFD_WM8351_CONFIG_MODE_2
418 depends on MFD_WM8350
420 config MFD_WM8351_CONFIG_MODE_3
422 depends on MFD_WM8350
424 config MFD_WM8352_CONFIG_MODE_0
426 depends on MFD_WM8350
428 config MFD_WM8352_CONFIG_MODE_1
430 depends on MFD_WM8350
432 config MFD_WM8352_CONFIG_MODE_2
434 depends on MFD_WM8350
436 config MFD_WM8352_CONFIG_MODE_3
438 depends on MFD_WM8350
440 config MFD_WM8350_I2C
441 bool "Support Wolfson Microelectronics WM8350 with I2C"
443 depends on I2C=y && GENERIC_HARDIRQS
445 The WM8350 is an integrated audio and power management
446 subsystem with watchdog and RTC functionality for embedded
447 systems. This option enables core support for the WM8350 with
448 I2C as the control interface. Additional options must be
449 selected to enable support for the functionality of the chip.
452 bool "Support Wolfson Microelectronics WM8994"
454 depends on I2C=y && GENERIC_HARDIRQS
456 The WM8994 is a highly integrated hi-fi CODEC designed for
457 smartphone applicatiosn. As well as audio functionality it
458 has on board GPIO and regulator functionality which is
459 supported via the relevant subsystems. This driver provides
460 core support for the WM8994, in order to use the actual
461 functionaltiy of the device other drivers must be enabled.
464 tristate "Support for NXP PCF50633"
467 Say yes here if you have NXP PCF50633 chip on your board.
468 This core driver provides register access and IRQ handling
469 facilities, and registers devices for the various functions
470 so that function-specific drivers can bind to them.
473 bool "Support Dialog Semiconductor PMIC"
478 Support for Dialog semiconductor PMIC chips.
479 Use the options provided to support the desired PMIC's.
482 depends on PMIC_DIALOG
484 bool "Support Dialog Semiconductor DA9052 PMIC"
486 Support for Dialog semiconductor DA9052 PMIC with inbuilt
487 SPI & I2C connectivities.
488 This driver provides common support for accessing the device,
489 additional drivers must be enabled in order to use the
490 functionality of the device.
492 bool "Support Dialog Semiconductor DA9053 AA PMIC"
494 Support for Dialog semiconductor DA9053 AA PMIC with inbuilt
495 SPI & I2C connectivities.
496 This driver provides common support for accessing the device,
497 additional drivers must be enabled in order to use the
498 functionality of the device.
500 bool "Support Dialog Semiconductor DA9053 BA/BB PMIC"
502 Support for Dialog semiconductor DA9053 BA/BB PMIC with inbuilt
503 SPI & I2C connectivities.
504 This driver provides common support for accessing the device,
505 additional drivers must be enabled in order to use the
506 functionality of the device.
511 tristate "Support for NXP PCF50633 ADC"
512 depends on MFD_PCF50633
514 Say yes here if you want to include support for ADC in the
518 tristate "Support for NXP PCF50633 GPIO"
519 depends on MFD_PCF50633
521 Say yes here if you want to include support GPIO for pins on
528 tristate "Support Freescale MC13783 and MC13892"
529 depends on SPI_MASTER
533 Support for the Freescale (Atlas) PMIC and audio CODECs
535 This driver provides common support for accessing the device,
536 additional drivers must be enabled in order to use the
537 functionality of the device.
540 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
541 default y if ARCH_U300 || ARCH_U8500
543 Say yes here if you have the ABX500 Mixed Signal IC family
544 chips. This core driver expose register access functions.
545 Functionality specific drivers using these functions can
546 remain unchanged when IC changes. Binding of the functions to
547 actual register access is done by the IC core driver.
550 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
551 depends on I2C=y && ABX500_CORE
553 default y if ARCH_U300
555 Select this to enable the AB3100 Mixed Signal IC core
556 functionality. This connects to a AB3100 on the I2C bus
557 and expose a number of symbols needed for dependent devices
558 to read and write registers and subscribe to events from
559 this multi-functional IC. This is needed to use other features
560 of the AB3100 such as battery-backed RTC, charging control,
561 LEDs, vibrator, system power and temperature, power management
565 tristate "ST-Ericsson AB3100 OTP functions"
566 depends on AB3100_CORE
567 default y if AB3100_CORE
569 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
570 programmable memory) support. This exposes a sysfs file to read
575 depends on GENERIC_HARDIRQS && SPI_MASTER
577 This enables the PCAP ASIC present on EZX Phones. This is
578 needed for MMC, TouchScreen, Sound, USB, etc..
581 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
582 depends on GENERIC_HARDIRQS && ABX500_CORE
585 Select this option to enable access to AB8500 power management
586 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
587 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
588 the irq_chip parts for handling the Mixed Signal chip events.
589 This chip embeds various other multimedia funtionalities as well.
591 config AB8500_I2C_CORE
592 bool "AB8500 register access via PRCMU I2C"
593 depends on AB8500_CORE && MFD_DB8500_PRCMU
596 This enables register access to the AB8500 chip via PRCMU I2C.
597 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
598 the I2C bus is connected to the Power Reset
599 and Mangagement Unit, PRCMU.
602 bool "Enable debug info via debugfs"
603 depends on AB8500_CORE && DEBUG_FS
604 default y if DEBUG_FS
606 Select this option if you want debug information using the debug
610 bool "AB8500 GPADC driver"
611 depends on AB8500_CORE && REGULATOR_AB8500
614 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
617 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
619 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
621 Select this to enable the AB3550 Mixed Signal IC core
622 functionality. This connects to a AB3550 on the I2C bus
623 and expose a number of symbols needed for dependent devices
624 to read and write registers and subscribe to events from
625 this multi-functional IC. This is needed to use other features
626 of the AB3550 such as battery-backed RTC, charging control,
627 LEDs, vibrator, system power and temperature, power management
630 config MFD_DB8500_PRCMU
631 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
632 depends on UX500_SOC_DB8500
635 Select this option to enable support for the DB8500 Power Reset
636 and Control Management Unit. This is basically an autonomous
637 system controller running an XP70 microprocessor, which is accessed
638 through a register map.
640 config MFD_DB5500_PRCMU
641 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
642 depends on UX500_SOC_DB5500
645 Select this option to enable support for the DB5500 Power Reset
646 and Control Management Unit. This is basically an autonomous
647 system controller running an XP70 microprocessor, which is accessed
648 through a register map.
651 tristate "Support for CS5535 and CS5536 southbridge core functions"
653 depends on PCI && X86
655 This is the core driver for CS5535/CS5536 MFD functions. This is
656 necessary for using the board's GPIO and MFGPT functionality.
658 config MFD_TIMBERDALE
659 tristate "Support for the Timberdale FPGA"
661 depends on PCI && GPIOLIB
663 This is the core driver for the timberdale FPGA. This device is a
664 multifunction device which exposes numerous platform devices.
666 The timberdale FPGA can be found on the Intel Atom development board
667 for in-vehicle infontainment, called Russellville.
670 tristate "Intel SCH LPC"
674 LPC bridge function of the Intel SCH provides support for
675 System Management Bus and General Purpose I/O.
678 tristate "Support for RDC-R321x southbridge"
682 Say yes here if you want to have support for the RDC R-321x SoC
683 southbridge which provides access to GPIOs and Watchdog using the
684 southbridge PCI device configuration space.
686 config MFD_JANZ_CMODIO
687 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
691 This is the core driver for the Janz CMOD-IO PCI MODULbus
692 carrier board. This device is a PCI to MODULbus bridge which may
693 host many different types of MODULbus daughterboards, including
694 CAN and GPIO controllers.
696 config MFD_JZ4740_ADC
697 tristate "Support for the JZ4740 SoC ADC core"
699 depends on MACH_JZ4740
701 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
702 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
705 tristate "Support for VIA VX855/VX875 integrated south bridge"
709 Say yes here to enable support for various functions of the
710 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
711 and/or vx855_gpio drivers for this to do anything useful.
713 config MFD_WL1273_CORE
714 tristate "Support for TI WL1273 FM radio."
719 This is the core driver for the TI WL1273 FM radio. This MFD
720 driver connects the radio-wl1273 V4L2 module and the wl1273
723 config MFD_OMAP_USB_HOST
724 bool "Support OMAP USBHS core driver"
725 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
728 This is the core driver for the OAMP EHCI and OHCI drivers.
729 This MFD driver does the required setup functionalities for
730 OMAP USB Host drivers.
735 config MFD_PM8921_CORE
736 tristate "Qualcomm PM8921 PMIC chip"
741 If you say yes to this option, support will be included for the
742 built-in PM8921 PMIC chip.
744 This is required if your board has a PM8921 and uses its features,
745 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
747 Say M here if you want to include support for PM8921 chip as a module.
748 This will build a module called "pm8921-core".
750 config MFD_PM8XXX_IRQ
751 bool "Support for Qualcomm PM8xxx IRQ features"
752 depends on MFD_PM8XXX
753 default y if MFD_PM8XXX
755 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
757 This is required to use certain other PM 8xxx features, such as GPIO
761 bool "TPS65910 Power Management chip"
762 depends on I2C=y && GPIOLIB
766 if you say yes here you get support for the TPS65910 series of
767 Power Management chips.
769 config TPS65911_COMPARATOR
773 tristate "MAX17135 PMIC core"
776 This is the MAX17135 PMIC support. It includes
777 core support for communication with the MAX17135 chip.
781 menu "Multimedia Capabilities Port drivers"
782 depends on ARCH_SA1100
789 tristate "Support SA11x0 MCP interface"
790 depends on ARCH_SA1100
795 tristate "Support for UCB1200 / UCB1300"
798 config MCP_UCB1200_TS
799 tristate "Touchscreen interface support"
800 depends on MCP_UCB1200 && INPUT