2 # Multifunction miscellaneous devices
6 bool "Multifunction device drivers"
10 Configure MFD device drivers.
19 bool "Support Marvell 88PM8606/88PM8607"
20 depends on I2C=y && GENERIC_HARDIRQS
23 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
24 This includes the I2C driver and the core APIs _only_, you have to
25 select individual components like voltage regulators, RTC and
26 battery-charger under the corresponding menus.
29 tristate "Support for Silicon Motion SM501"
31 This is the core driver for the Silicon Motion SM501 multimedia
32 companion chip. This device is a multifunction device which may
33 provide numerous interfaces including USB host controller, USB gadget,
34 asynchronous serial ports, audio functions, and a dual display video
35 interface. The device may be connected by PCI or local bus with
36 varying functions enabled.
39 bool "Export GPIO via GPIO layer"
40 depends on MFD_SM501 && GPIOLIB
42 This option uses the gpio library layer to export the 64 GPIO
43 lines on the SM501. The platform data is used to supply the
44 base number for the first GPIO line to register.
47 bool "Support for Compaq ASIC3"
48 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
51 This driver supports the ASIC3 multifunction chip found on many
52 PDAs (mainly iPAQ and HTC based ones)
54 config MFD_SH_MOBILE_SDHI
55 bool "Support for SuperH Mobile SDHI"
56 depends on SUPERH || ARCH_SHMOBILE
60 This driver supports the SDHI hardware block found in many
63 config MFD_DAVINCI_VOICECODEC
67 config MFD_DM355EVM_MSP
68 bool "DaVinci DM355 EVM microcontroller"
69 depends on I2C && 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 bool "HTC EGPIO support"
77 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
79 This driver supports the CPLD egpio chip present on
80 several HTC phones. It provides basic support for input
81 pins, output pins, and irqs.
84 tristate "HTC PASIC3 LED/DS1WM chip support"
87 This core driver provides register access for the LED/DS1WM
88 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
89 HTC Magician devices, respectively. Actual functionality is
90 handled by the leds-pasic3 and ds1wm drivers.
93 bool "HTC I2C PLD chip support"
94 depends on I2C=y && GPIOLIB
96 If you say yes here you get support for the supposed CPLD
97 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
98 This device provides input and output GPIOs through an I2C
99 interface to one or more sub-chips.
102 tristate "Philips UCB1400 Core driver"
106 This enables support for the Philips UCB1400 core functions.
107 The UCB1400 is an AC97 audio codec.
109 To compile this driver as a module, choose M here: the
110 module will be called ucb1400_core.
113 tristate "TPS6501x Power Management chips"
114 depends on I2C && GPIOLIB
115 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
117 If you say yes here you get support for the TPS6501x series of
118 Power Management chips. These include voltage regulators,
119 lithium ion/polymer battery charging, and other features that
120 are often used in portable devices like cell phones and cameras.
122 This driver can also be built as a module. If so, the module
123 will be called tps65010.
126 tristate "TPS6507x Power Management / Touch Screen chips"
130 If you say yes here you get support for the TPS6507x series of
131 Power Management / Touch Screen chips. These include voltage
132 regulators, lithium ion/polymer battery charging, touch screen
133 and other features that are often used in portable devices.
134 This driver can also be built as a module. If so, the module
135 will be called tps6507x.
138 bool "Texas Instruments TWL92330/Menelaus PM chip"
139 depends on I2C=y && ARCH_OMAP2
141 If you say yes here you get support for the Texas Instruments
142 TWL92330/Menelaus Power Management chip. This include voltage
143 regulators, Dual slot memory card transceivers, real-time clock
144 and other features that are often used in portable devices like
145 cell phones and PDAs.
148 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
149 depends on I2C=y && GENERIC_HARDIRQS
151 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
152 This core driver provides register access and IRQ handling
153 facilities, and registers devices for the various functions
154 so that function-specific drivers can bind to them.
156 These multi-function chips are found on many OMAP2 and OMAP3
157 boards, providing power management, RTC, GPIO, keypad, a
158 high speed USB OTG transceiver, an audio codec (on most
159 versions) and many other features.
162 bool "Support power resources on TWL4030 family chips"
163 depends on TWL4030_CORE && ARM
165 Say yes here if you want to use the power resources on the
166 TWL4030 family chips. Most of these resources are regulators,
167 which have a separate driver; some are control signals, such
168 as clock request handshaking.
170 This driver uses board-specific data to initialize the resources
171 and load scripts controling which resources are switched off/on
172 or reset when a sleep, wakeup or warm reset event occurs.
176 depends on TWL4030_CORE
181 bool "Support Toshiba TC35892"
182 depends on I2C=y && GENERIC_HARDIRQS
185 Support for the Toshiba TC35892 I/O Expander.
187 This driver provides common support for accessing the device,
188 additional drivers must be enabled in order to use the
189 functionality of the device.
201 bool "Support Toshiba T7L66XB"
202 depends on ARM && HAVE_CLK
206 Support for Toshiba Mobile IO Controller T7L66XB
209 bool "Support Toshiba TC6387XB"
210 depends on ARM && HAVE_CLK
214 Support for Toshiba Mobile IO Controller TC6387XB
217 bool "Support Toshiba TC6393XB"
218 depends on GPIOLIB && ARM
222 Support for Toshiba Mobile IO Controller TC6393XB
225 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
228 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
229 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
230 usually found on PXA processors-based platforms. This includes
231 the I2C driver and the core APIs _only_, you have to select
232 individual components like LCD backlight, voltage regulators,
233 LEDs and battery-charger under the corresponding menus.
236 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
239 Say yes here to add support for Analog Devices AD5520 and ADP5501,
240 Multifunction Power Management IC. This includes
241 the I2C driver and the core APIs _only_, you have to select
242 individual components like LCD backlight, LEDs, GPIOs and Kepad
243 under the corresponding menus.
246 bool "Maxim Semiconductor MAX8925 PMIC Support"
247 depends on I2C=y && GENERIC_HARDIRQS
250 Say yes here to support for Maxim Semiconductor MAX8925. This is
251 a Power Management IC. This driver provies common support for
252 accessing the device, additional drivers must be enabled in order
253 to use the functionality of the device.
256 bool "Maxim Semiconductor MAX8998 PMIC Support"
260 Say yes here to support for Maxim Semiconductor MAX8998. This is
261 a Power Management IC. This driver provies common support for
262 accessing the device, additional drivers must be enabled in order
263 to use the functionality of the device.
266 tristate "Support Wolfson Microelectronics WM8400"
270 Support for the Wolfson Microelecronics WM8400 PMIC and audio
271 CODEC. This driver provides common support for accessing
272 the device, additional drivers must be enabled in order to use
273 the functionality of the device.
276 bool "Support Wolfson Microelectronics WM831x/2x PMICs"
278 depends on I2C=y && GENERIC_HARDIRQS
280 Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
281 This driver provides common support for accessing the device,
282 additional drivers must be enabled in order to use the
283 functionality of the device.
287 depends on GENERIC_HARDIRQS
289 config MFD_WM8350_CONFIG_MODE_0
291 depends on MFD_WM8350
293 config MFD_WM8350_CONFIG_MODE_1
295 depends on MFD_WM8350
297 config MFD_WM8350_CONFIG_MODE_2
299 depends on MFD_WM8350
301 config MFD_WM8350_CONFIG_MODE_3
303 depends on MFD_WM8350
305 config MFD_WM8351_CONFIG_MODE_0
307 depends on MFD_WM8350
309 config MFD_WM8351_CONFIG_MODE_1
311 depends on MFD_WM8350
313 config MFD_WM8351_CONFIG_MODE_2
315 depends on MFD_WM8350
317 config MFD_WM8351_CONFIG_MODE_3
319 depends on MFD_WM8350
321 config MFD_WM8352_CONFIG_MODE_0
323 depends on MFD_WM8350
325 config MFD_WM8352_CONFIG_MODE_1
327 depends on MFD_WM8350
329 config MFD_WM8352_CONFIG_MODE_2
331 depends on MFD_WM8350
333 config MFD_WM8352_CONFIG_MODE_3
335 depends on MFD_WM8350
337 config MFD_WM8350_I2C
338 bool "Support Wolfson Microelectronics WM8350 with I2C"
340 depends on I2C=y && GENERIC_HARDIRQS
342 The WM8350 is an integrated audio and power management
343 subsystem with watchdog and RTC functionality for embedded
344 systems. This option enables core support for the WM8350 with
345 I2C as the control interface. Additional options must be
346 selected to enable support for the functionality of the chip.
349 bool "Support Wolfson Microelectronics WM8994"
351 depends on I2C=y && GENERIC_HARDIRQS
353 The WM8994 is a highly integrated hi-fi CODEC designed for
354 smartphone applicatiosn. As well as audio functionality it
355 has on board GPIO and regulator functionality which is
356 supported via the relevant subsystems. This driver provides
357 core support for the WM8994, in order to use the actual
358 functionaltiy of the device other drivers must be enabled.
361 tristate "Support for NXP PCF50633"
364 Say yes here if you have NXP PCF50633 chip on your board.
365 This core driver provides register access and IRQ handling
366 facilities, and registers devices for the various functions
367 so that function-specific drivers can bind to them.
370 tristate "Support Freescale MC13783"
371 depends on SPI_MASTER
374 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
375 This driver provides common support for accessing the device,
376 additional drivers must be enabled in order to use the
377 functionality of the device.
380 tristate "Support for NXP PCF50633 ADC"
381 depends on MFD_PCF50633
383 Say yes here if you want to include support for ADC in the
387 tristate "Support for NXP PCF50633 GPIO"
388 depends on MFD_PCF50633
390 Say yes here if you want to include support GPIO for pins on
394 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
395 default y if ARCH_U300
397 Say yes here if you have the ABX500 Mixed Signal IC family
398 chips. This core driver expose register access functions.
399 Functionality specific drivers using these functions can
400 remain unchanged when IC changes. Binding of the functions to
401 actual register access is done by the IC core driver.
404 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
405 depends on I2C=y && ABX500_CORE
406 default y if ARCH_U300
408 Select this to enable the AB3100 Mixed Signal IC core
409 functionality. This connects to a AB3100 on the I2C bus
410 and expose a number of symbols needed for dependent devices
411 to read and write registers and subscribe to events from
412 this multi-functional IC. This is needed to use other features
413 of the AB3100 such as battery-backed RTC, charging control,
414 LEDs, vibrator, system power and temperature, power management
418 tristate "ST-Ericsson AB3100 OTP functions"
419 depends on AB3100_CORE
420 default y if AB3100_CORE
422 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
423 programmable memory) support. This exposes a sysfs file to read
428 depends on GENERIC_HARDIRQS && SPI_MASTER
430 This enables the PCAP ASIC present on EZX Phones. This is
431 needed for MMC, TouchScreen, Sound, USB, etc..
434 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
435 depends on SPI=y && GENERIC_HARDIRQS
438 Select this option to enable access to AB8500 power management
439 chip. This connects to U8500 on the SSP/SPI bus and exports
440 read/write functions for the devices to get access to this chip.
441 This chip embeds various other multimedia funtionalities as well.
444 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
446 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
448 Select this to enable the AB3550 Mixed Signal IC core
449 functionality. This connects to a AB3550 on the I2C bus
450 and expose a number of symbols needed for dependent devices
451 to read and write registers and subscribe to events from
452 this multi-functional IC. This is needed to use other features
453 of the AB3550 such as battery-backed RTC, charging control,
454 LEDs, vibrator, system power and temperature, power management
457 config MFD_TIMBERDALE
458 tristate "Support for the Timberdale FPGA"
460 depends on PCI && GPIOLIB
462 This is the core driver for the timberdale FPGA. This device is a
463 multifunction device which exposes numerous platform devices.
465 The timberdale FPGA can be found on the Intel Atom development board
466 for in-vehicle infontainment, called Russellville.
469 tristate "Intel SCH LPC"
473 LPC bridge function of the Intel SCH provides support for
474 System Management Bus and General Purpose I/O.
477 tristate "Support for RDC-R321x southbridge"
481 Say yes here if you want to have support for the RDC R-321x SoC
482 southbridge which provides access to GPIOs and Watchdog using the
483 southbridge PCI device configuration space.
485 config MFD_JANZ_CMODIO
486 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
490 This is the core driver for the Janz CMOD-IO PCI MODULbus
491 carrier board. This device is a PCI to MODULbus bridge which may
492 host many different types of MODULbus daughterboards, including
493 CAN and GPIO controllers.
497 menu "Multimedia Capabilities Port drivers"
498 depends on ARCH_SA1100
505 tristate "Support SA11x0 MCP interface"
506 depends on ARCH_SA1100
511 tristate "Support for UCB1200 / UCB1300"
514 config MCP_UCB1200_TS
515 tristate "Touchscreen interface support"
516 depends on MCP_UCB1200 && INPUT