2 # Multifunction miscellaneous devices
5 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
17 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
18 This includes the I2C driver and the core APIs _only_, you have to
19 select individual components like voltage regulators, RTC and
20 battery-charger under the corresponding menus.
23 tristate "Support for Silicon Motion SM501"
25 This is the core driver for the Silicon Motion SM501 multimedia
26 companion chip. This device is a multifunction device which may
27 provide numerous interfaces including USB host controller, USB gadget,
28 asynchronous serial ports, audio functions, and a dual display video
29 interface. The device may be connected by PCI or local bus with
30 varying functions enabled.
33 bool "Export GPIO via GPIO layer"
34 depends on MFD_SM501 && GPIOLIB
36 This option uses the gpio library layer to export the 64 GPIO
37 lines on the SM501. The platform data is used to supply the
38 base number for the first GPIO line to register.
41 bool "Support for Compaq ASIC3"
42 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
45 This driver supports the ASIC3 multifunction chip found on many
46 PDAs (mainly iPAQ and HTC based ones)
48 config MFD_SH_MOBILE_SDHI
49 bool "Support for SuperH Mobile SDHI"
50 depends on SUPERH || ARCH_SHMOBILE
54 This driver supports the SDHI hardware block found in many
57 config MFD_DAVINCI_VOICECODEC
61 config MFD_DM355EVM_MSP
62 bool "DaVinci DM355 EVM microcontroller"
63 depends on I2C && MACH_DAVINCI_DM355_EVM
65 This driver supports the MSP430 microcontroller used on these
66 boards. MSP430 firmware manages resets and power sequencing,
67 inputs from buttons and the IR remote, LEDs, an RTC, and more.
70 bool "HTC EGPIO support"
71 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
73 This driver supports the CPLD egpio chip present on
74 several HTC phones. It provides basic support for input
75 pins, output pins, and irqs.
78 tristate "HTC PASIC3 LED/DS1WM chip support"
81 This core driver provides register access for the LED/DS1WM
82 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
83 HTC Magician devices, respectively. Actual functionality is
84 handled by the leds-pasic3 and ds1wm drivers.
87 bool "HTC I2C PLD chip support"
88 depends on I2C=y && GPIOLIB
90 If you say yes here you get support for the supposed CPLD
91 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
92 This device provides input and output GPIOs through an I2C
93 interface to one or more sub-chips.
96 tristate "Philips UCB1400 Core driver"
100 This enables support for the Philips UCB1400 core functions.
101 The UCB1400 is an AC97 audio codec.
103 To compile this driver as a module, choose M here: the
104 module will be called ucb1400_core.
107 tristate "TPS6501x Power Management chips"
108 depends on I2C && GPIOLIB
109 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
111 If you say yes here you get support for the TPS6501x series of
112 Power Management chips. These include voltage regulators,
113 lithium ion/polymer battery charging, and other features that
114 are often used in portable devices like cell phones and cameras.
116 This driver can also be built as a module. If so, the module
117 will be called tps65010.
120 tristate "TPS6507x Power Management / Touch Screen chips"
124 If you say yes here you get support for the TPS6507x series of
125 Power Management / Touch Screen chips. These include voltage
126 regulators, lithium ion/polymer battery charging, touch screen
127 and other features that are often used in portable devices.
128 This driver can also be built as a module. If so, the module
129 will be called tps6507x.
132 bool "Texas Instruments TWL92330/Menelaus PM chip"
133 depends on I2C=y && ARCH_OMAP2
135 If you say yes here you get support for the Texas Instruments
136 TWL92330/Menelaus Power Management chip. This include voltage
137 regulators, Dual slot memory card transceivers, real-time clock
138 and other features that are often used in portable devices like
139 cell phones and PDAs.
142 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
143 depends on I2C=y && GENERIC_HARDIRQS
145 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
146 This core driver provides register access and IRQ handling
147 facilities, and registers devices for the various functions
148 so that function-specific drivers can bind to them.
150 These multi-function chips are found on many OMAP2 and OMAP3
151 boards, providing power management, RTC, GPIO, keypad, a
152 high speed USB OTG transceiver, an audio codec (on most
153 versions) and many other features.
156 bool "Support power resources on TWL4030 family chips"
157 depends on TWL4030_CORE && ARM
159 Say yes here if you want to use the power resources on the
160 TWL4030 family chips. Most of these resources are regulators,
161 which have a separate driver; some are control signals, such
162 as clock request handshaking.
164 This driver uses board-specific data to initialize the resources
165 and load scripts controling which resources are switched off/on
166 or reset when a sleep, wakeup or warm reset event occurs.
170 depends on TWL4030_CORE
184 bool "Support Toshiba T7L66XB"
185 depends on ARM && HAVE_CLK
189 Support for Toshiba Mobile IO Controller T7L66XB
192 bool "Support Toshiba TC6387XB"
193 depends on ARM && HAVE_CLK
197 Support for Toshiba Mobile IO Controller TC6387XB
200 bool "Support Toshiba TC6393XB"
201 depends on GPIOLIB && ARM
205 Support for Toshiba Mobile IO Controller TC6393XB
208 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
211 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
212 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
213 usually found on PXA processors-based platforms. This includes
214 the I2C driver and the core APIs _only_, you have to select
215 individual components like LCD backlight, voltage regulators,
216 LEDs and battery-charger under the corresponding menus.
219 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
222 Say yes here to add support for Analog Devices AD5520 and ADP5501,
223 Multifunction Power Management IC. This includes
224 the I2C driver and the core APIs _only_, you have to select
225 individual components like LCD backlight, LEDs, GPIOs and Kepad
226 under the corresponding menus.
229 bool "Maxim Semiconductor MAX8925 PMIC Support"
230 depends on I2C=y && GENERIC_HARDIRQS
233 Say yes here to support for Maxim Semiconductor MAX8925. This is
234 a Power Management IC. This driver provies common support for
235 accessing the device, additional drivers must be enabled in order
236 to use the functionality of the device.
239 tristate "Support Wolfson Microelectronics WM8400"
243 Support for the Wolfson Microelecronics WM8400 PMIC and audio
244 CODEC. This driver provides common support for accessing
245 the device, additional drivers must be enabled in order to use
246 the functionality of the device.
249 bool "Support Wolfson Microelectronics WM831x/2x PMICs"
251 depends on I2C=y && GENERIC_HARDIRQS
253 Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
254 This driver provides common support for accessing the device,
255 additional drivers must be enabled in order to use the
256 functionality of the device.
260 depends on GENERIC_HARDIRQS
262 config MFD_WM8350_CONFIG_MODE_0
264 depends on MFD_WM8350
266 config MFD_WM8350_CONFIG_MODE_1
268 depends on MFD_WM8350
270 config MFD_WM8350_CONFIG_MODE_2
272 depends on MFD_WM8350
274 config MFD_WM8350_CONFIG_MODE_3
276 depends on MFD_WM8350
278 config MFD_WM8351_CONFIG_MODE_0
280 depends on MFD_WM8350
282 config MFD_WM8351_CONFIG_MODE_1
284 depends on MFD_WM8350
286 config MFD_WM8351_CONFIG_MODE_2
288 depends on MFD_WM8350
290 config MFD_WM8351_CONFIG_MODE_3
292 depends on MFD_WM8350
294 config MFD_WM8352_CONFIG_MODE_0
296 depends on MFD_WM8350
298 config MFD_WM8352_CONFIG_MODE_1
300 depends on MFD_WM8350
302 config MFD_WM8352_CONFIG_MODE_2
304 depends on MFD_WM8350
306 config MFD_WM8352_CONFIG_MODE_3
308 depends on MFD_WM8350
310 config MFD_WM8350_I2C
311 bool "Support Wolfson Microelectronics WM8350 with I2C"
313 depends on I2C=y && GENERIC_HARDIRQS
315 The WM8350 is an integrated audio and power management
316 subsystem with watchdog and RTC functionality for embedded
317 systems. This option enables core support for the WM8350 with
318 I2C as the control interface. Additional options must be
319 selected to enable support for the functionality of the chip.
322 bool "Support Wolfson Microelectronics WM8994"
324 depends on I2C=y && GENERIC_HARDIRQS
326 The WM8994 is a highly integrated hi-fi CODEC designed for
327 smartphone applicatiosn. As well as audio functionality it
328 has on board GPIO and regulator functionality which is
329 supported via the relevant subsystems. This driver provides
330 core support for the WM8994, in order to use the actual
331 functionaltiy of the device other drivers must be enabled.
334 tristate "Support for NXP PCF50633"
337 Say yes here if you have NXP PCF50633 chip on your board.
338 This core driver provides register access and IRQ handling
339 facilities, and registers devices for the various functions
340 so that function-specific drivers can bind to them.
343 tristate "Support Freescale MC13783"
344 depends on SPI_MASTER
347 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
348 This driver provides common support for accessing the device,
349 additional drivers must be enabled in order to use the
350 functionality of the device.
353 tristate "Support for NXP PCF50633 ADC"
354 depends on MFD_PCF50633
356 Say yes here if you want to include support for ADC in the
360 tristate "Support for NXP PCF50633 GPIO"
361 depends on MFD_PCF50633
363 Say yes here if you want to include support GPIO for pins on
367 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
369 default y if ARCH_U300
371 Select this to enable the AB3100 Mixed Signal IC core
372 functionality. This connects to a AB3100 on the I2C bus
373 and expose a number of symbols needed for dependent devices
374 to read and write registers and subscribe to events from
375 this multi-functional IC. This is needed to use other features
376 of the AB3100 such as battery-backed RTC, charging control,
377 LEDs, vibrator, system power and temperature, power management
381 tristate "ST-Ericsson AB3100 OTP functions"
382 depends on AB3100_CORE
383 default y if AB3100_CORE
385 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
386 programmable memory) support. This exposes a sysfs file to read
391 depends on GENERIC_HARDIRQS && SPI_MASTER
393 This enables the PCAP ASIC present on EZX Phones. This is
394 needed for MMC, TouchScreen, Sound, USB, etc..
397 tristate "ST-Ericsson's AB4500 Mixed Signal Power management chip"
400 Select this option to enable access to AB4500 power management
401 chip. This connects to U8500 on the SSP/SPI bus and exports
402 read/write functions for the devices to get access to this chip.
403 This chip embeds various other multimedia funtionalities as well.
405 config MFD_TIMBERDALE
406 tristate "Support for the Timberdale FPGA"
408 depends on PCI && GPIOLIB
410 This is the core driver for the timberdale FPGA. This device is a
411 multifunction device which exposes numerous platform devices.
413 The timberdale FPGA can be found on the Intel Atom development board
414 for in-vehicle infontainment, called Russellville.
417 tristate "Intel SCH LPC"
421 LPC bridge function of the Intel SCH provides support for
422 System Management Bus and General Purpose I/O.
425 tristate "Support for RDC-R321x southbridge"
429 Say yes here if you want to have support for the RDC R-321x SoC
430 southbridge which provides access to GPIOs and Watchdog using the
431 southbridge PCI device configuration space.
433 config MFD_JANZ_CMODIO
434 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
438 This is the core driver for the Janz CMOD-IO PCI MODULbus
439 carrier board. This device is a PCI to MODULbus bridge which may
440 host many different types of MODULbus daughterboards, including
441 CAN and GPIO controllers.
445 menu "Multimedia Capabilities Port drivers"
446 depends on ARCH_SA1100
453 tristate "Support SA11x0 MCP interface"
454 depends on ARCH_SA1100
459 tristate "Support for UCB1200 / UCB1300"
462 config MCP_UCB1200_TS
463 tristate "Touchscreen interface support"
464 depends on MCP_UCB1200 && INPUT