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.
185 depends on TWL4030_CORE
190 bool "Support Toshiba TC35892"
191 depends on I2C=y && GENERIC_HARDIRQS
194 Support for the Toshiba TC35892 I/O Expander.
196 This driver provides common support for accessing the device,
197 additional drivers must be enabled in order to use the
198 functionality of the device.
210 bool "Support Toshiba T7L66XB"
211 depends on ARM && HAVE_CLK
215 Support for Toshiba Mobile IO Controller T7L66XB
218 bool "Support Toshiba TC6387XB"
219 depends on ARM && HAVE_CLK
223 Support for Toshiba Mobile IO Controller TC6387XB
226 bool "Support Toshiba TC6393XB"
227 depends on GPIOLIB && ARM
231 Support for Toshiba Mobile IO Controller TC6393XB
234 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
237 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
238 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
239 usually found on PXA processors-based platforms. This includes
240 the I2C driver and the core APIs _only_, you have to select
241 individual components like LCD backlight, voltage regulators,
242 LEDs and battery-charger under the corresponding menus.
245 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
248 Say yes here to add support for Analog Devices AD5520 and ADP5501,
249 Multifunction Power Management IC. This includes
250 the I2C driver and the core APIs _only_, you have to select
251 individual components like LCD backlight, LEDs, GPIOs and Kepad
252 under the corresponding menus.
255 bool "Maxim Semiconductor MAX8925 PMIC Support"
256 depends on I2C=y && GENERIC_HARDIRQS
259 Say yes here to support for Maxim Semiconductor MAX8925. This is
260 a Power Management IC. This driver provies common support for
261 accessing the device, additional drivers must be enabled in order
262 to use the functionality of the device.
265 tristate "Support Wolfson Microelectronics WM8400"
269 Support for the Wolfson Microelecronics WM8400 PMIC and audio
270 CODEC. This driver provides common support for accessing
271 the device, additional drivers must be enabled in order to use
272 the functionality of the device.
275 bool "Support Wolfson Microelectronics WM831x/2x PMICs"
277 depends on I2C=y && GENERIC_HARDIRQS
279 Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
280 This driver provides common support for accessing the device,
281 additional drivers must be enabled in order to use the
282 functionality of the device.
286 depends on GENERIC_HARDIRQS
288 config MFD_WM8350_CONFIG_MODE_0
290 depends on MFD_WM8350
292 config MFD_WM8350_CONFIG_MODE_1
294 depends on MFD_WM8350
296 config MFD_WM8350_CONFIG_MODE_2
298 depends on MFD_WM8350
300 config MFD_WM8350_CONFIG_MODE_3
302 depends on MFD_WM8350
304 config MFD_WM8351_CONFIG_MODE_0
306 depends on MFD_WM8350
308 config MFD_WM8351_CONFIG_MODE_1
310 depends on MFD_WM8350
312 config MFD_WM8351_CONFIG_MODE_2
314 depends on MFD_WM8350
316 config MFD_WM8351_CONFIG_MODE_3
318 depends on MFD_WM8350
320 config MFD_WM8352_CONFIG_MODE_0
322 depends on MFD_WM8350
324 config MFD_WM8352_CONFIG_MODE_1
326 depends on MFD_WM8350
328 config MFD_WM8352_CONFIG_MODE_2
330 depends on MFD_WM8350
332 config MFD_WM8352_CONFIG_MODE_3
334 depends on MFD_WM8350
336 config MFD_WM8350_I2C
337 bool "Support Wolfson Microelectronics WM8350 with I2C"
339 depends on I2C=y && GENERIC_HARDIRQS
341 The WM8350 is an integrated audio and power management
342 subsystem with watchdog and RTC functionality for embedded
343 systems. This option enables core support for the WM8350 with
344 I2C as the control interface. Additional options must be
345 selected to enable support for the functionality of the chip.
348 bool "Support Wolfson Microelectronics WM8994"
350 depends on I2C=y && GENERIC_HARDIRQS
352 The WM8994 is a highly integrated hi-fi CODEC designed for
353 smartphone applicatiosn. As well as audio functionality it
354 has on board GPIO and regulator functionality which is
355 supported via the relevant subsystems. This driver provides
356 core support for the WM8994, in order to use the actual
357 functionaltiy of the device other drivers must be enabled.
360 tristate "Support for NXP PCF50633"
363 Say yes here if you have NXP PCF50633 chip on your board.
364 This core driver provides register access and IRQ handling
365 facilities, and registers devices for the various functions
366 so that function-specific drivers can bind to them.
369 tristate "Support Freescale MC13783"
370 depends on SPI_MASTER
373 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
374 This driver provides common support for accessing the device,
375 additional drivers must be enabled in order to use the
376 functionality of the device.
379 tristate "Support for NXP PCF50633 ADC"
380 depends on MFD_PCF50633
382 Say yes here if you want to include support for ADC in the
386 tristate "Support for NXP PCF50633 GPIO"
387 depends on MFD_PCF50633
389 Say yes here if you want to include support GPIO for pins on
393 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
394 default y if ARCH_U300
396 Say yes here if you have the ABX500 Mixed Signal IC family
397 chips. This core driver expose register access functions.
398 Functionality specific drivers using these functions can
399 remain unchanged when IC changes. Binding of the functions to
400 actual register access is done by the IC core driver.
403 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
404 depends on I2C=y && ABX500_CORE
405 default y if ARCH_U300
407 Select this to enable the AB3100 Mixed Signal IC core
408 functionality. This connects to a AB3100 on the I2C bus
409 and expose a number of symbols needed for dependent devices
410 to read and write registers and subscribe to events from
411 this multi-functional IC. This is needed to use other features
412 of the AB3100 such as battery-backed RTC, charging control,
413 LEDs, vibrator, system power and temperature, power management
417 tristate "ST-Ericsson AB3100 OTP functions"
418 depends on AB3100_CORE
419 default y if AB3100_CORE
421 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
422 programmable memory) support. This exposes a sysfs file to read
427 depends on GENERIC_HARDIRQS && SPI_MASTER
429 This enables the PCAP ASIC present on EZX Phones. This is
430 needed for MMC, TouchScreen, Sound, USB, etc..
433 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
434 depends on SPI=y && GENERIC_HARDIRQS
437 Select this option to enable access to AB8500 power management
438 chip. This connects to U8500 on the SSP/SPI bus and exports
439 read/write functions for the devices to get access to this chip.
440 This chip embeds various other multimedia funtionalities as well.
443 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
445 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
447 Select this to enable the AB3550 Mixed Signal IC core
448 functionality. This connects to a AB3550 on the I2C bus
449 and expose a number of symbols needed for dependent devices
450 to read and write registers and subscribe to events from
451 this multi-functional IC. This is needed to use other features
452 of the AB3550 such as battery-backed RTC, charging control,
453 LEDs, vibrator, system power and temperature, power management
456 config MFD_TIMBERDALE
457 tristate "Support for the Timberdale FPGA"
459 depends on PCI && GPIOLIB
461 This is the core driver for the timberdale FPGA. This device is a
462 multifunction device which exposes numerous platform devices.
464 The timberdale FPGA can be found on the Intel Atom development board
465 for in-vehicle infontainment, called Russellville.
468 tristate "Intel SCH LPC"
472 LPC bridge function of the Intel SCH provides support for
473 System Management Bus and General Purpose I/O.
476 tristate "Support for RDC-R321x southbridge"
480 Say yes here if you want to have support for the RDC R-321x SoC
481 southbridge which provides access to GPIOs and Watchdog using the
482 southbridge PCI device configuration space.
484 config MFD_JANZ_CMODIO
485 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
489 This is the core driver for the Janz CMOD-IO PCI MODULbus
490 carrier board. This device is a PCI to MODULbus bridge which may
491 host many different types of MODULbus daughterboards, including
492 CAN and GPIO controllers.
496 menu "Multimedia Capabilities Port drivers"
497 depends on ARCH_SA1100
504 tristate "Support SA11x0 MCP interface"
505 depends on ARCH_SA1100
510 tristate "Support for UCB1200 / UCB1300"
513 config MCP_UCB1200_TS
514 tristate "Touchscreen interface support"
515 depends on MCP_UCB1200 && INPUT