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_SH_MOBILE_SDHI
64 bool "Support for SuperH Mobile SDHI"
65 depends on SUPERH || ARCH_SHMOBILE
69 This driver supports the SDHI hardware block found in many
72 config MFD_DAVINCI_VOICECODEC
76 config MFD_DM355EVM_MSP
77 bool "DaVinci DM355 EVM microcontroller"
78 depends on I2C=y && MACH_DAVINCI_DM355_EVM
80 This driver supports the MSP430 microcontroller used on these
81 boards. MSP430 firmware manages resets and power sequencing,
82 inputs from buttons and the IR remote, LEDs, an RTC, and more.
85 tristate "TI Sequencer Serial Port support"
86 depends on ARCH_DAVINCI_TNETV107X
89 Say Y here if you want support for the Sequencer Serial Port
90 in a Texas Instruments TNETV107X SoC.
92 To compile this driver as a module, choose M here: the
93 module will be called ti-ssp.
96 bool "HTC EGPIO support"
97 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
99 This driver supports the CPLD egpio chip present on
100 several HTC phones. It provides basic support for input
101 pins, output pins, and irqs.
104 tristate "HTC PASIC3 LED/DS1WM chip support"
107 This core driver provides register access for the LED/DS1WM
108 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
109 HTC Magician devices, respectively. Actual functionality is
110 handled by the leds-pasic3 and ds1wm drivers.
113 bool "HTC I2C PLD chip support"
114 depends on I2C=y && GPIOLIB
116 If you say yes here you get support for the supposed CPLD
117 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
118 This device provides input and output GPIOs through an I2C
119 interface to one or more sub-chips.
122 tristate "Philips UCB1400 Core driver"
126 This enables support for the Philips UCB1400 core functions.
127 The UCB1400 is an AC97 audio codec.
129 To compile this driver as a module, choose M here: the
130 module will be called ucb1400_core.
133 tristate "TPS6501x Power Management chips"
134 depends on I2C && GPIOLIB
135 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
137 If you say yes here you get support for the TPS6501x series of
138 Power Management chips. These include voltage regulators,
139 lithium ion/polymer battery charging, and other features that
140 are often used in portable devices like cell phones and cameras.
142 This driver can also be built as a module. If so, the module
143 will be called tps65010.
146 tristate "TPS6507x Power Management / Touch Screen chips"
150 If you say yes here you get support for the TPS6507x series of
151 Power Management / Touch Screen chips. These include voltage
152 regulators, lithium ion/polymer battery charging, touch screen
153 and other features that are often used in portable devices.
154 This driver can also be built as a module. If so, the module
155 will be called tps6507x.
158 bool "Texas Instruments TWL92330/Menelaus PM chip"
159 depends on I2C=y && ARCH_OMAP2
161 If you say yes here you get support for the Texas Instruments
162 TWL92330/Menelaus Power Management chip. This include voltage
163 regulators, Dual slot memory card transceivers, real-time clock
164 and other features that are often used in portable devices like
165 cell phones and PDAs.
168 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
169 depends on I2C=y && GENERIC_HARDIRQS
171 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
172 This core driver provides register access and IRQ handling
173 facilities, and registers devices for the various functions
174 so that function-specific drivers can bind to them.
176 These multi-function chips are found on many OMAP2 and OMAP3
177 boards, providing power management, RTC, GPIO, keypad, a
178 high speed USB OTG transceiver, an audio codec (on most
179 versions) and many other features.
182 tristate "Texas Instruments TWL4030 MADC"
183 depends on TWL4030_CORE
185 This driver provides support for triton TWL4030-MADC. The
186 driver supports both RT and SW conversion methods.
188 This driver can be built as a module. If so it will be
192 bool "Support power resources on TWL4030 family chips"
193 depends on TWL4030_CORE && ARM
195 Say yes here if you want to use the power resources on the
196 TWL4030 family chips. Most of these resources are regulators,
197 which have a separate driver; some are control signals, such
198 as clock request handshaking.
200 This driver uses board-specific data to initialize the resources
201 and load scripts controling which resources are switched off/on
202 or reset when a sleep, wakeup or warm reset event occurs.
206 depends on TWL4030_CORE
211 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
212 depends on TWL4030_CORE
216 Say yes here if you want support for TWL6030 PWM.
217 This is used to control charging LED brightness.
220 bool "Support STMicroelectronics STMPE"
221 depends on I2C=y && GENERIC_HARDIRQS
224 Support for the STMPE family of I/O Expanders from
227 Currently supported devices are:
229 STMPE811: GPIO, Touchscreen
230 STMPE1601: GPIO, Keypad
231 STMPE2401: GPIO, Keypad
232 STMPE2403: GPIO, Keypad
234 This driver provides common support for accessing the device,
235 additional drivers must be enabled in order to use the functionality
236 of the device. Currently available sub drivers are:
240 Touchscreen: stmpe-ts
243 bool "Support Toshiba TC35892 and variants"
244 depends on I2C=y && GENERIC_HARDIRQS
247 Support for the Toshiba TC35892 and variants I/O Expander.
249 This driver provides common support for accessing the device,
250 additional drivers must be enabled in order to use the
251 functionality of the device.
263 bool "Support Toshiba T7L66XB"
264 depends on ARM && HAVE_CLK
268 Support for Toshiba Mobile IO Controller T7L66XB
271 bool "Support Toshiba TC6387XB"
272 depends on ARM && HAVE_CLK
276 Support for Toshiba Mobile IO Controller TC6387XB
279 bool "Support Toshiba TC6393XB"
280 depends on GPIOLIB && ARM
284 Support for Toshiba Mobile IO Controller TC6393XB
287 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
290 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
291 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
292 usually found on PXA processors-based platforms. This includes
293 the I2C driver and the core APIs _only_, you have to select
294 individual components like LCD backlight, voltage regulators,
295 LEDs and battery-charger under the corresponding menus.
298 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
301 Say yes here to add support for Analog Devices AD5520 and ADP5501,
302 Multifunction Power Management IC. This includes
303 the I2C driver and the core APIs _only_, you have to select
304 individual components like LCD backlight, LEDs, GPIOs and Kepad
305 under the corresponding menus.
308 bool "Maxim Semiconductor MAX8925 PMIC Support"
309 depends on I2C=y && GENERIC_HARDIRQS
312 Say yes here to support for Maxim Semiconductor MAX8925. This is
313 a Power Management IC. This driver provies common support for
314 accessing the device, additional drivers must be enabled in order
315 to use the functionality of the device.
318 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
319 depends on I2C=y && GENERIC_HARDIRQS
322 Say yes here to support for Maxim Semiconductor MAX8998 and
323 National Semiconductor LP3974. This is a Power Management IC.
324 This driver provies common support for accessing the device,
325 additional drivers must be enabled in order to use the functionality
329 tristate "Support Wolfson Microelectronics WM8400"
333 Support for the Wolfson Microelecronics WM8400 PMIC and audio
334 CODEC. This driver provides common support for accessing
335 the device, additional drivers must be enabled in order to use
336 the functionality of the device.
340 depends on GENERIC_HARDIRQS
342 config MFD_WM831X_I2C
343 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
346 depends on I2C=y && GENERIC_HARDIRQS
348 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
349 when controlled using I2C. This driver provides common support
350 for accessing the device, additional drivers must be enabled in
351 order to use the functionality of the device.
353 config MFD_WM831X_SPI
354 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
357 depends on SPI_MASTER && GENERIC_HARDIRQS
359 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
360 when controlled using SPI. This driver provides common support
361 for accessing the device, additional drivers must be enabled in
362 order to use the functionality of the device.
366 depends on GENERIC_HARDIRQS
368 config MFD_WM8350_CONFIG_MODE_0
370 depends on MFD_WM8350
372 config MFD_WM8350_CONFIG_MODE_1
374 depends on MFD_WM8350
376 config MFD_WM8350_CONFIG_MODE_2
378 depends on MFD_WM8350
380 config MFD_WM8350_CONFIG_MODE_3
382 depends on MFD_WM8350
384 config MFD_WM8351_CONFIG_MODE_0
386 depends on MFD_WM8350
388 config MFD_WM8351_CONFIG_MODE_1
390 depends on MFD_WM8350
392 config MFD_WM8351_CONFIG_MODE_2
394 depends on MFD_WM8350
396 config MFD_WM8351_CONFIG_MODE_3
398 depends on MFD_WM8350
400 config MFD_WM8352_CONFIG_MODE_0
402 depends on MFD_WM8350
404 config MFD_WM8352_CONFIG_MODE_1
406 depends on MFD_WM8350
408 config MFD_WM8352_CONFIG_MODE_2
410 depends on MFD_WM8350
412 config MFD_WM8352_CONFIG_MODE_3
414 depends on MFD_WM8350
416 config MFD_WM8350_I2C
417 bool "Support Wolfson Microelectronics WM8350 with I2C"
419 depends on I2C=y && GENERIC_HARDIRQS
421 The WM8350 is an integrated audio and power management
422 subsystem with watchdog and RTC functionality for embedded
423 systems. This option enables core support for the WM8350 with
424 I2C as the control interface. Additional options must be
425 selected to enable support for the functionality of the chip.
428 bool "Support Wolfson Microelectronics WM8994"
430 depends on I2C=y && GENERIC_HARDIRQS
432 The WM8994 is a highly integrated hi-fi CODEC designed for
433 smartphone applicatiosn. As well as audio functionality it
434 has on board GPIO and regulator functionality which is
435 supported via the relevant subsystems. This driver provides
436 core support for the WM8994, in order to use the actual
437 functionaltiy of the device other drivers must be enabled.
440 tristate "Support for NXP PCF50633"
443 Say yes here if you have NXP PCF50633 chip on your board.
444 This core driver provides register access and IRQ handling
445 facilities, and registers devices for the various functions
446 so that function-specific drivers can bind to them.
452 tristate "Support Freescale MC13783 and MC13892"
453 depends on SPI_MASTER
457 Support for the Freescale (Atlas) PMIC and audio CODECs
459 This driver provides common support for accessing the device,
460 additional drivers must be enabled in order to use the
461 functionality of the device.
464 tristate "Support for NXP PCF50633 ADC"
465 depends on MFD_PCF50633
467 Say yes here if you want to include support for ADC in the
471 tristate "Support for NXP PCF50633 GPIO"
472 depends on MFD_PCF50633
474 Say yes here if you want to include support GPIO for pins on
478 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
479 default y if ARCH_U300 || ARCH_U8500
481 Say yes here if you have the ABX500 Mixed Signal IC family
482 chips. This core driver expose register access functions.
483 Functionality specific drivers using these functions can
484 remain unchanged when IC changes. Binding of the functions to
485 actual register access is done by the IC core driver.
488 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
489 depends on I2C=y && ABX500_CORE
491 default y if ARCH_U300
493 Select this to enable the AB3100 Mixed Signal IC core
494 functionality. This connects to a AB3100 on the I2C bus
495 and expose a number of symbols needed for dependent devices
496 to read and write registers and subscribe to events from
497 this multi-functional IC. This is needed to use other features
498 of the AB3100 such as battery-backed RTC, charging control,
499 LEDs, vibrator, system power and temperature, power management
503 tristate "ST-Ericsson AB3100 OTP functions"
504 depends on AB3100_CORE
505 default y if AB3100_CORE
507 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
508 programmable memory) support. This exposes a sysfs file to read
513 depends on GENERIC_HARDIRQS && SPI_MASTER
515 This enables the PCAP ASIC present on EZX Phones. This is
516 needed for MMC, TouchScreen, Sound, USB, etc..
519 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
520 depends on GENERIC_HARDIRQS && ABX500_CORE
523 Select this option to enable access to AB8500 power management
524 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
525 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
526 the irq_chip parts for handling the Mixed Signal chip events.
527 This chip embeds various other multimedia funtionalities as well.
529 config AB8500_I2C_CORE
530 bool "AB8500 register access via PRCMU I2C"
531 depends on AB8500_CORE && UX500_SOC_DB8500
534 This enables register access to the AB8500 chip via PRCMU I2C.
535 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
536 the I2C bus is connected to the Power Reset
537 and Mangagement Unit, PRCMU.
540 bool "Enable debug info via debugfs"
541 depends on AB8500_CORE && DEBUG_FS
542 default y if DEBUG_FS
544 Select this option if you want debug information using the debug
548 bool "AB8500 GPADC driver"
549 depends on AB8500_CORE && REGULATOR_AB8500
552 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
555 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
557 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
559 Select this to enable the AB3550 Mixed Signal IC core
560 functionality. This connects to a AB3550 on the I2C bus
561 and expose a number of symbols needed for dependent devices
562 to read and write registers and subscribe to events from
563 this multi-functional IC. This is needed to use other features
564 of the AB3550 such as battery-backed RTC, charging control,
565 LEDs, vibrator, system power and temperature, power management
569 tristate "Support for CS5535 and CS5536 southbridge core functions"
573 This is the core driver for CS5535/CS5536 MFD functions. This is
574 necessary for using the board's GPIO and MFGPT functionality.
576 config MFD_TIMBERDALE
577 tristate "Support for the Timberdale FPGA"
579 depends on PCI && GPIOLIB
581 This is the core driver for the timberdale FPGA. This device is a
582 multifunction device which exposes numerous platform devices.
584 The timberdale FPGA can be found on the Intel Atom development board
585 for in-vehicle infontainment, called Russellville.
588 tristate "Intel SCH LPC"
592 LPC bridge function of the Intel SCH provides support for
593 System Management Bus and General Purpose I/O.
596 tristate "Support for RDC-R321x southbridge"
600 Say yes here if you want to have support for the RDC R-321x SoC
601 southbridge which provides access to GPIOs and Watchdog using the
602 southbridge PCI device configuration space.
604 config MFD_JANZ_CMODIO
605 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
609 This is the core driver for the Janz CMOD-IO PCI MODULbus
610 carrier board. This device is a PCI to MODULbus bridge which may
611 host many different types of MODULbus daughterboards, including
612 CAN and GPIO controllers.
614 config MFD_JZ4740_ADC
615 tristate "Support for the JZ4740 SoC ADC core"
617 depends on MACH_JZ4740
619 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
620 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
623 bool "TPS6586x Power Management chips"
624 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
627 If you say yes here you get support for the TPS6586X series of
628 Power Management chips.
629 This driver provides common support for accessing the device,
630 additional drivers must be enabled in order to use the
631 functionality of the device.
633 This driver can also be built as a module. If so, the module
634 will be called tps6586x.
637 tristate "Support for VIA VX855/VX875 integrated south bridge"
641 Say yes here to enable support for various functions of the
642 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
643 and/or vx855_gpio drivers for this to do anything useful.
645 config MFD_WL1273_CORE
651 This is the core driver for the TI WL1273 FM radio. This MFD
652 driver connects the radio-wl1273 V4L2 module and the wl1273
655 config MFD_OMAP_USB_HOST
656 bool "Support OMAP USBHS core driver"
657 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
660 This is the core driver for the OAMP EHCI and OHCI drivers.
661 This MFD driver does the required setup functionalities for
662 OMAP USB Host drivers.
666 menu "Multimedia Capabilities Port drivers"
667 depends on ARCH_SA1100
674 tristate "Support SA11x0 MCP interface"
675 depends on ARCH_SA1100
680 tristate "Support for UCB1200 / UCB1300"
683 config MCP_UCB1200_TS
684 tristate "Touchscreen interface support"
685 depends on MCP_UCB1200 && INPUT