2 # Multifunction miscellaneous devices
5 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
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"
53 This driver supports the SDHI hardware block found in many
56 config MFD_DM355EVM_MSP
57 bool "DaVinci DM355 EVM microcontroller"
58 depends on I2C && MACH_DAVINCI_DM355_EVM
60 This driver supports the MSP430 microcontroller used on these
61 boards. MSP430 firmware manages resets and power sequencing,
62 inputs from buttons and the IR remote, LEDs, an RTC, and more.
65 bool "HTC EGPIO support"
66 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
68 This driver supports the CPLD egpio chip present on
69 several HTC phones. It provides basic support for input
70 pins, output pins, and irqs.
73 tristate "HTC PASIC3 LED/DS1WM chip support"
76 This core driver provides register access for the LED/DS1WM
77 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
78 HTC Magician devices, respectively. Actual functionality is
79 handled by the leds-pasic3 and ds1wm drivers.
82 tristate "Philips UCB1400 Core driver"
86 This enables support for the Philips UCB1400 core functions.
87 The UCB1400 is an AC97 audio codec.
89 To compile this driver as a module, choose M here: the
90 module will be called ucb1400_core.
93 tristate "TPS6501x Power Management chips"
94 depends on I2C && GPIOLIB
95 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
97 If you say yes here you get support for the TPS6501x series of
98 Power Management chips. These include voltage regulators,
99 lithium ion/polymer battery charging, and other features that
100 are often used in portable devices like cell phones and cameras.
102 This driver can also be built as a module. If so, the module
103 will be called tps65010.
106 bool "Texas Instruments TWL92330/Menelaus PM chip"
107 depends on I2C=y && ARCH_OMAP2
109 If you say yes here you get support for the Texas Instruments
110 TWL92330/Menelaus Power Management chip. This include voltage
111 regulators, Dual slot memory card transceivers, real-time clock
112 and other features that are often used in portable devices like
113 cell phones and PDAs.
116 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
117 depends on I2C=y && GENERIC_HARDIRQS
119 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
120 This core driver provides register access and IRQ handling
121 facilities, and registers devices for the various functions
122 so that function-specific drivers can bind to them.
124 These multi-function chips are found on many OMAP2 and OMAP3
125 boards, providing power management, RTC, GPIO, keypad, a
126 high speed USB OTG transceiver, an audio codec (on most
127 versions) and many other features.
130 bool "Support power resources on TWL4030 family chips"
131 depends on TWL4030_CORE && ARM
133 Say yes here if you want to use the power resources on the
134 TWL4030 family chips. Most of these resources are regulators,
135 which have a separate driver; some are control signals, such
136 as clock request handshaking.
138 This driver uses board-specific data to initialize the resources
139 and load scripts controling which resources are switched off/on
140 or reset when a sleep, wakeup or warm reset event occurs.
144 depends on TWL4030_CORE
153 bool "Support Toshiba T7L66XB"
154 depends on ARM && HAVE_CLK
158 Support for Toshiba Mobile IO Controller T7L66XB
161 bool "Support Toshiba TC6387XB"
162 depends on ARM && HAVE_CLK
166 Support for Toshiba Mobile IO Controller TC6387XB
169 bool "Support Toshiba TC6393XB"
170 depends on GPIOLIB && ARM
174 Support for Toshiba Mobile IO Controller TC6393XB
177 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
180 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
181 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
182 usually found on PXA processors-based platforms. This includes
183 the I2C driver and the core APIs _only_, you have to select
184 individual components like LCD backlight, voltage regulators,
185 LEDs and battery-charger under the corresponding menus.
188 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
191 Say yes here to add support for Analog Devices AD5520 and ADP5501,
192 Multifunction Power Management IC. This includes
193 the I2C driver and the core APIs _only_, you have to select
194 individual components like LCD backlight, LEDs, GPIOs and Kepad
195 under the corresponding menus.
198 tristate "Maxim Semiconductor MAX8925 PMIC Support"
202 Say yes here to support for Maxim Semiconductor MAX8925. This is
203 a Power Management IC. This driver provies common support for
204 accessing the device, additional drivers must be enabled in order
205 to use the functionality of the device.
208 tristate "Support Wolfson Microelectronics WM8400"
212 Support for the Wolfson Microelecronics WM8400 PMIC and audio
213 CODEC. This driver provides common support for accessing
214 the device, additional drivers must be enabled in order to use
215 the functionality of the device.
218 bool "Support Wolfson Microelectronics WM831x/2x PMICs"
222 Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
223 This driver provides common support for accessing the device,
224 additional drivers must be enabled in order to use the
225 functionality of the device.
230 config MFD_WM8350_CONFIG_MODE_0
232 depends on MFD_WM8350
234 config MFD_WM8350_CONFIG_MODE_1
236 depends on MFD_WM8350
238 config MFD_WM8350_CONFIG_MODE_2
240 depends on MFD_WM8350
242 config MFD_WM8350_CONFIG_MODE_3
244 depends on MFD_WM8350
246 config MFD_WM8351_CONFIG_MODE_0
248 depends on MFD_WM8350
250 config MFD_WM8351_CONFIG_MODE_1
252 depends on MFD_WM8350
254 config MFD_WM8351_CONFIG_MODE_2
256 depends on MFD_WM8350
258 config MFD_WM8351_CONFIG_MODE_3
260 depends on MFD_WM8350
262 config MFD_WM8352_CONFIG_MODE_0
264 depends on MFD_WM8350
266 config MFD_WM8352_CONFIG_MODE_1
268 depends on MFD_WM8350
270 config MFD_WM8352_CONFIG_MODE_2
272 depends on MFD_WM8350
274 config MFD_WM8352_CONFIG_MODE_3
276 depends on MFD_WM8350
278 config MFD_WM8350_I2C
279 bool "Support Wolfson Microelectronics WM8350 with I2C"
283 The WM8350 is an integrated audio and power management
284 subsystem with watchdog and RTC functionality for embedded
285 systems. This option enables core support for the WM8350 with
286 I2C as the control interface. Additional options must be
287 selected to enable support for the functionality of the chip.
290 tristate "Support for NXP PCF50633"
293 Say yes here if you have NXP PCF50633 chip on your board.
294 This core driver provides register access and IRQ handling
295 facilities, and registers devices for the various functions
296 so that function-specific drivers can bind to them.
299 tristate "Support Freescale MC13783"
300 depends on SPI_MASTER
303 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
304 This driver provides common support for accessing the device,
305 additional drivers must be enabled in order to use the
306 functionality of the device.
309 tristate "Support for NXP PCF50633 ADC"
310 depends on MFD_PCF50633
312 Say yes here if you want to include support for ADC in the
316 tristate "Support for NXP PCF50633 GPIO"
317 depends on MFD_PCF50633
319 Say yes here if you want to include support GPIO for pins on
323 tristate "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
325 default y if ARCH_U300
327 Select this to enable the AB3100 Mixed Signal IC core
328 functionality. This connects to a AB3100 on the I2C bus
329 and expose a number of symbols needed for dependent devices
330 to read and write registers and subscribe to events from
331 this multi-functional IC. This is needed to use other features
332 of the AB3100 such as battery-backed RTC, charging control,
333 LEDs, vibrator, system power and temperature, power management
337 tristate "ST-Ericsson AB3100 OTP functions"
338 depends on AB3100_CORE
339 default y if AB3100_CORE
341 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
342 programmable memory) support. This exposes a sysfs file to read
347 depends on GENERIC_HARDIRQS && SPI_MASTER
349 This enables the PCAP ASIC present on EZX Phones. This is
350 needed for MMC, TouchScreen, Sound, USB, etc..
353 tristate "ST-Ericsson's AB4500 Mixed Signal Power management chip"
356 Select this option to enable access to AB4500 power management
357 chip. This connects to U8500 on the SSP/SPI bus and exports
358 read/write functions for the devices to get access to this chip.
359 This chip embeds various other multimedia funtionalities as well.
361 config MFD_TIMBERDALE
362 tristate "Support for the Timberdale FPGA"
364 depends on PCI && GPIOLIB
366 This is the core driver for the timberdale FPGA. This device is a
367 multifunction device which exposes numerous platform devices.
369 The timberdale FPGA can be found on the Intel Atom development board
370 for in-vehicle infontainment, called Russellville.
373 menu "Multimedia Capabilities Port drivers"
374 depends on ARCH_SA1100
381 tristate "Support SA11x0 MCP interface"
382 depends on ARCH_SA1100
387 tristate "Support for UCB1200 / UCB1300"
390 config MCP_UCB1200_TS
391 tristate "Touchscreen interface support"
392 depends on MCP_UCB1200 && INPUT