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 && 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 bool "HTC EGPIO support"
86 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
88 This driver supports the CPLD egpio chip present on
89 several HTC phones. It provides basic support for input
90 pins, output pins, and irqs.
93 tristate "HTC PASIC3 LED/DS1WM chip support"
96 This core driver provides register access for the LED/DS1WM
97 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
98 HTC Magician devices, respectively. Actual functionality is
99 handled by the leds-pasic3 and ds1wm drivers.
102 bool "HTC I2C PLD chip support"
103 depends on I2C=y && GPIOLIB
105 If you say yes here you get support for the supposed CPLD
106 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
107 This device provides input and output GPIOs through an I2C
108 interface to one or more sub-chips.
111 tristate "Philips UCB1400 Core driver"
115 This enables support for the Philips UCB1400 core functions.
116 The UCB1400 is an AC97 audio codec.
118 To compile this driver as a module, choose M here: the
119 module will be called ucb1400_core.
122 tristate "TPS6501x Power Management chips"
123 depends on I2C && GPIOLIB
124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
126 If you say yes here you get support for the TPS6501x series of
127 Power Management chips. These include voltage regulators,
128 lithium ion/polymer battery charging, and other features that
129 are often used in portable devices like cell phones and cameras.
131 This driver can also be built as a module. If so, the module
132 will be called tps65010.
135 tristate "TPS6507x Power Management / Touch Screen chips"
139 If you say yes here you get support for the TPS6507x series of
140 Power Management / Touch Screen chips. These include voltage
141 regulators, lithium ion/polymer battery charging, touch screen
142 and other features that are often used in portable devices.
143 This driver can also be built as a module. If so, the module
144 will be called tps6507x.
147 bool "Texas Instruments TWL92330/Menelaus PM chip"
148 depends on I2C=y && ARCH_OMAP2
150 If you say yes here you get support for the Texas Instruments
151 TWL92330/Menelaus Power Management chip. This include voltage
152 regulators, Dual slot memory card transceivers, real-time clock
153 and other features that are often used in portable devices like
154 cell phones and PDAs.
157 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
158 depends on I2C=y && GENERIC_HARDIRQS
160 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
161 This core driver provides register access and IRQ handling
162 facilities, and registers devices for the various functions
163 so that function-specific drivers can bind to them.
165 These multi-function chips are found on many OMAP2 and OMAP3
166 boards, providing power management, RTC, GPIO, keypad, a
167 high speed USB OTG transceiver, an audio codec (on most
168 versions) and many other features.
171 bool "Support power resources on TWL4030 family chips"
172 depends on TWL4030_CORE && ARM
174 Say yes here if you want to use the power resources on the
175 TWL4030 family chips. Most of these resources are regulators,
176 which have a separate driver; some are control signals, such
177 as clock request handshaking.
179 This driver uses board-specific data to initialize the resources
180 and load scripts controling which resources are switched off/on
181 or reset when a sleep, wakeup or warm reset event occurs.
184 bool "Texas Instruments TPS65910 Support"
185 depends on I2C=y && GENERIC_HARDIRQS
187 Say yes here if you have TPS65910 family chip on your board.
188 This core driver provides register access and registers devices
189 for the various functions so that function-specific drivers can
192 These multi-function chips are found on many AM35xx boards,
193 providing power management, RTC, GPIO features.
197 depends on TWL4030_CORE
202 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
203 depends on TWL4030_CORE
207 Say yes here if you want support for TWL6030 PWM.
208 This is used to control charging LED brightness.
211 bool "Support STMicroelectronics STMPE"
212 depends on I2C=y && GENERIC_HARDIRQS
215 Support for the STMPE family of I/O Expanders from
218 Currently supported devices are:
220 STMPE811: GPIO, Touchscreen
221 STMPE1601: GPIO, Keypad
222 STMPE2401: GPIO, Keypad
223 STMPE2403: GPIO, Keypad
225 This driver provides common support for accessing the device,
226 additional drivers must be enabled in order to use the functionality
227 of the device. Currently available sub drivers are:
231 Touchscreen: stmpe-ts
234 bool "Support Toshiba TC35892"
235 depends on I2C=y && GENERIC_HARDIRQS
238 Support for the Toshiba TC35892 I/O Expander.
240 This driver provides common support for accessing the device,
241 additional drivers must be enabled in order to use the
242 functionality of the device.
254 bool "Support Toshiba T7L66XB"
255 depends on ARM && HAVE_CLK
259 Support for Toshiba Mobile IO Controller T7L66XB
262 bool "Support Toshiba TC6387XB"
263 depends on ARM && HAVE_CLK
267 Support for Toshiba Mobile IO Controller TC6387XB
270 bool "Support Toshiba TC6393XB"
271 depends on GPIOLIB && ARM
275 Support for Toshiba Mobile IO Controller TC6393XB
278 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
281 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
282 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
283 usually found on PXA processors-based platforms. This includes
284 the I2C driver and the core APIs _only_, you have to select
285 individual components like LCD backlight, voltage regulators,
286 LEDs and battery-charger under the corresponding menus.
289 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
292 Say yes here to add support for Analog Devices AD5520 and ADP5501,
293 Multifunction Power Management IC. This includes
294 the I2C driver and the core APIs _only_, you have to select
295 individual components like LCD backlight, LEDs, GPIOs and Kepad
296 under the corresponding menus.
299 bool "Maxim Semiconductor MAX8925 PMIC Support"
300 depends on I2C=y && GENERIC_HARDIRQS
303 Say yes here to support for Maxim Semiconductor MAX8925. This is
304 a Power Management IC. This driver provies common support for
305 accessing the device, additional drivers must be enabled in order
306 to use the functionality of the device.
309 bool "Maxim Semiconductor MAX8998 PMIC Support"
313 Say yes here to support for Maxim Semiconductor MAX8998. This is
314 a Power Management IC. This driver provies common support for
315 accessing the device, additional drivers must be enabled in order
316 to use the functionality of the device.
319 tristate "Support Wolfson Microelectronics WM8400"
323 Support for the Wolfson Microelecronics WM8400 PMIC and audio
324 CODEC. This driver provides common support for accessing
325 the device, additional drivers must be enabled in order to use
326 the functionality of the device.
330 depends on GENERIC_HARDIRQS
332 config MFD_WM831X_I2C
333 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
336 depends on I2C=y && GENERIC_HARDIRQS
338 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
339 when controlled using I2C. This driver provides common support
340 for accessing the device, additional drivers must be enabled in
341 order to use the functionality of the device.
343 config MFD_WM831X_SPI
344 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
347 depends on SPI_MASTER && GENERIC_HARDIRQS
349 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
350 when controlled using SPI. This driver provides common support
351 for accessing the device, additional drivers must be enabled in
352 order to use the functionality of the device.
354 config MFD_WM831X_SPI_A22
355 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI for A22"
358 depends on SPI_MASTER && GENERIC_HARDIRQS
360 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
361 when controlled using SPI. This driver provides common support
362 for accessing the device, additional drivers must be enabled in
363 order to use the functionality of the device.
367 depends on GENERIC_HARDIRQS
369 config MFD_WM8350_CONFIG_MODE_0
371 depends on MFD_WM8350
373 config MFD_WM8350_CONFIG_MODE_1
375 depends on MFD_WM8350
377 config MFD_WM8350_CONFIG_MODE_2
379 depends on MFD_WM8350
381 config MFD_WM8350_CONFIG_MODE_3
383 depends on MFD_WM8350
385 config MFD_WM8351_CONFIG_MODE_0
387 depends on MFD_WM8350
389 config MFD_WM8351_CONFIG_MODE_1
391 depends on MFD_WM8350
393 config MFD_WM8351_CONFIG_MODE_2
395 depends on MFD_WM8350
397 config MFD_WM8351_CONFIG_MODE_3
399 depends on MFD_WM8350
401 config MFD_WM8352_CONFIG_MODE_0
403 depends on MFD_WM8350
405 config MFD_WM8352_CONFIG_MODE_1
407 depends on MFD_WM8350
409 config MFD_WM8352_CONFIG_MODE_2
411 depends on MFD_WM8350
413 config MFD_WM8352_CONFIG_MODE_3
415 depends on MFD_WM8350
417 config MFD_WM8350_I2C
418 bool "Support Wolfson Microelectronics WM8350 with I2C"
420 depends on I2C=y && GENERIC_HARDIRQS
422 The WM8350 is an integrated audio and power management
423 subsystem with watchdog and RTC functionality for embedded
424 systems. This option enables core support for the WM8350 with
425 I2C as the control interface. Additional options must be
426 selected to enable support for the functionality of the chip.
429 bool "Support Wolfson Microelectronics WM8994"
431 depends on I2C=y && GENERIC_HARDIRQS
433 The WM8994 is a highly integrated hi-fi CODEC designed for
434 smartphone applicatiosn. As well as audio functionality it
435 has on board GPIO and regulator functionality which is
436 supported via the relevant subsystems. This driver provides
437 core support for the WM8994, in order to use the actual
438 functionaltiy of the device other drivers must be enabled.
441 tristate "Support for NXP PCF50633"
444 Say yes here if you have NXP PCF50633 chip on your board.
445 This core driver provides register access and IRQ handling
446 facilities, and registers devices for the various functions
447 so that function-specific drivers can bind to them.
450 tristate "Support Freescale MC13783"
451 depends on SPI_MASTER
454 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
455 This driver provides common support for accessing the device,
456 additional drivers must be enabled in order to use the
457 functionality of the device.
460 tristate "Support for NXP PCF50633 ADC"
461 depends on MFD_PCF50633
463 Say yes here if you want to include support for ADC in the
467 tristate "Support for NXP PCF50633 GPIO"
468 depends on MFD_PCF50633
470 Say yes here if you want to include support GPIO for pins on
474 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
475 default y if ARCH_U300
477 Say yes here if you have the ABX500 Mixed Signal IC family
478 chips. This core driver expose register access functions.
479 Functionality specific drivers using these functions can
480 remain unchanged when IC changes. Binding of the functions to
481 actual register access is done by the IC core driver.
484 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
485 depends on I2C=y && ABX500_CORE
486 default y if ARCH_U300
488 Select this to enable the AB3100 Mixed Signal IC core
489 functionality. This connects to a AB3100 on the I2C bus
490 and expose a number of symbols needed for dependent devices
491 to read and write registers and subscribe to events from
492 this multi-functional IC. This is needed to use other features
493 of the AB3100 such as battery-backed RTC, charging control,
494 LEDs, vibrator, system power and temperature, power management
498 tristate "ST-Ericsson AB3100 OTP functions"
499 depends on AB3100_CORE
500 default y if AB3100_CORE
502 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
503 programmable memory) support. This exposes a sysfs file to read
508 depends on GENERIC_HARDIRQS && SPI_MASTER
510 This enables the PCAP ASIC present on EZX Phones. This is
511 needed for MMC, TouchScreen, Sound, USB, etc..
514 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
515 depends on SPI=y && GENERIC_HARDIRQS
518 Select this option to enable access to AB8500 power management
519 chip. This connects to U8500 on the SSP/SPI bus and exports
520 read/write functions for the devices to get access to this chip.
521 This chip embeds various other multimedia funtionalities as well.
524 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
526 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
528 Select this to enable the AB3550 Mixed Signal IC core
529 functionality. This connects to a AB3550 on the I2C bus
530 and expose a number of symbols needed for dependent devices
531 to read and write registers and subscribe to events from
532 this multi-functional IC. This is needed to use other features
533 of the AB3550 such as battery-backed RTC, charging control,
534 LEDs, vibrator, system power and temperature, power management
537 config MFD_TIMBERDALE
538 tristate "Support for the Timberdale FPGA"
540 depends on PCI && GPIOLIB
542 This is the core driver for the timberdale FPGA. This device is a
543 multifunction device which exposes numerous platform devices.
545 The timberdale FPGA can be found on the Intel Atom development board
546 for in-vehicle infontainment, called Russellville.
549 tristate "Intel SCH LPC"
553 LPC bridge function of the Intel SCH provides support for
554 System Management Bus and General Purpose I/O.
557 tristate "Support for RDC-R321x southbridge"
561 Say yes here if you want to have support for the RDC R-321x SoC
562 southbridge which provides access to GPIOs and Watchdog using the
563 southbridge PCI device configuration space.
566 tristate "Support for CPCAP"
567 depends on SPI && FIRMWARE_IN_KERNEL
569 Say yes here if you want to include drivers for the CPCAP chip.
571 config MFD_JANZ_CMODIO
572 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
576 This is the core driver for the Janz CMOD-IO PCI MODULbus
577 carrier board. This device is a PCI to MODULbus bridge which may
578 host many different types of MODULbus daughterboards, including
579 CAN and GPIO controllers.
581 config MFD_JZ4740_ADC
582 tristate "Support for the JZ4740 SoC ADC core"
584 depends on MACH_JZ4740
586 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
587 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
590 bool "TPS6586x Power Management chips"
591 depends on I2C && GPIOLIB && GENERIC_HARDIRQS
594 If you say yes here you get support for the TPS6586X series of
595 Power Management chips.
596 This driver provides common support for accessing the device,
597 additional drivers must be enabled in order to use the
598 functionality of the device.
600 This driver can also be built as a module. If so, the module
601 will be called tps6586x.
605 menu "Multimedia Capabilities Port drivers"
606 depends on ARCH_SA1100
613 tristate "Support SA11x0 MCP interface"
614 depends on ARCH_SA1100
619 tristate "Support for UCB1200 / UCB1300"
622 config MCP_UCB1200_TS
623 tristate "Touchscreen interface support"
624 depends on MCP_UCB1200 && INPUT