2 # Multifunction miscellaneous devices
5 menu "Multifunction device drivers"
13 tristate "Support for Silicon Motion SM501"
15 This is the core driver for the Silicon Motion SM501 multimedia
16 companion chip. This device is a multifunction device which may
17 provide numerous interfaces including USB host controller, USB gadget,
18 asynchronous serial ports, audio functions, and a dual display video
19 interface. The device may be connected by PCI or local bus with
20 varying functions enabled.
23 bool "Export GPIO via GPIO layer"
24 depends on MFD_SM501 && GPIOLIB
26 This option uses the gpio library layer to export the 64 GPIO
27 lines on the SM501. The platform data is used to supply the
28 base number for the first GPIO line to register.
31 bool "Support for Compaq ASIC3"
32 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
35 This driver supports the ASIC3 multifunction chip found on many
36 PDAs (mainly iPAQ and HTC based ones)
38 config MFD_DM355EVM_MSP
39 bool "DaVinci DM355 EVM microcontroller"
40 depends on I2C && MACH_DAVINCI_DM355_EVM
42 This driver supports the MSP430 microcontroller used on these
43 boards. MSP430 firmware manages resets and power sequencing,
44 inputs from buttons and the IR remote, LEDs, an RTC, and more.
47 bool "HTC EGPIO support"
48 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
50 This driver supports the CPLD egpio chip present on
51 several HTC phones. It provides basic support for input
52 pins, output pins, and irqs.
55 tristate "HTC PASIC3 LED/DS1WM chip support"
58 This core driver provides register access for the LED/DS1WM
59 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
60 HTC Magician devices, respectively. Actual functionality is
61 handled by the leds-pasic3 and ds1wm drivers.
64 tristate "Philips UCB1400 Core driver"
68 This enables support for the Philips UCB1400 core functions.
69 The UCB1400 is an AC97 audio codec.
71 To compile this driver as a module, choose M here: the
72 module will be called ucb1400_core.
75 tristate "TPS6501x Power Management chips"
76 depends on I2C && GPIOLIB
77 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
79 If you say yes here you get support for the TPS6501x series of
80 Power Management chips. These include voltage regulators,
81 lithium ion/polymer battery charging, and other features that
82 are often used in portable devices like cell phones and cameras.
84 This driver can also be built as a module. If so, the module
85 will be called tps65010.
88 bool "Texas Instruments TWL92330/Menelaus PM chip"
89 depends on I2C=y && ARCH_OMAP24XX
91 If you say yes here you get support for the Texas Instruments
92 TWL92330/Menelaus Power Management chip. This include voltage
93 regulators, Dual slot memory card transceivers, real-time clock
94 and other features that are often used in portable devices like
98 bool "Texas Instruments TWL4030/TPS659x0 Support"
99 depends on I2C=y && GENERIC_HARDIRQS
101 Say yes here if you have TWL4030 family chip on your board.
102 This core driver provides register access and IRQ handling
103 facilities, and registers devices for the various functions
104 so that function-specific drivers can bind to them.
106 These multi-function chips are found on many OMAP2 and OMAP3
107 boards, providing power management, RTC, GPIO, keypad, a
108 high speed USB OTG transceiver, an audio codec (on most
109 versions) and many other features.
112 bool "Support power resources on TWL4030 family chips"
113 depends on TWL4030_CORE && ARM
115 Say yes here if you want to use the power resources on the
116 TWL4030 family chips. Most of these resources are regulators,
117 which have a separate driver; some are control signals, such
118 as clock request handshaking.
120 This driver uses board-specific data to initialize the resources
121 and load scripts controling which resources are switched off/on
122 or reset when a sleep, wakeup or warm reset event occurs.
125 bool "Texas Instruments TPS65910 Support"
126 depends on I2C=y && GENERIC_HARDIRQS
128 Say yes here if you have TPS65910 family chip on your board.
129 This core driver provides register access and registers devices
130 for the various functions so that function-specific drivers can
133 These multi-function chips are found on many AM35xx boards,
134 providing power management, RTC, GPIO features.
141 bool "Support Toshiba T7L66XB"
142 depends on ARM && HAVE_CLK
146 Support for Toshiba Mobile IO Controller T7L66XB
149 bool "Support Toshiba TC6387XB"
150 depends on ARM && HAVE_CLK
154 Support for Toshiba Mobile IO Controller TC6387XB
157 bool "Support Toshiba TC6393XB"
158 depends on GPIOLIB && ARM
162 Support for Toshiba Mobile IO Controller TC6393XB
165 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
168 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
169 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
170 usually found on PXA processors-based platforms. This includes
171 the I2C driver and the core APIs _only_, you have to select
172 individual components like LCD backlight, voltage regulators,
173 LEDs and battery-charger under the corresponding menus.
176 tristate "Support Wolfson Microelectronics WM8994"
180 The WM8994 is a highly integrated hi-fi CODEC designed for
181 smartphone applicatiosn. As well as audio functionality it
182 has on board GPIO and regulator functionality which is
183 supported via the relevant subsystems. This driver provides
184 core support for the WM8994, in order to use the actual
185 functionaltiy of the device other drivers must be enabled.
188 tristate "Support Wolfson Microelectronics WM8400"
192 Support for the Wolfson Microelecronics WM8400 PMIC and audio
193 CODEC. This driver provides common support for accessing
194 the device, additional drivers must be enabled in order to use
195 the functionality of the device.
199 depends on GENERIC_HARDIRQS
201 config MFD_WM831X_I2C
202 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
205 depends on I2C=y && GENERIC_HARDIRQS
207 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
208 when controlled using I2C. This driver provides common support
209 for accessing the device, additional drivers must be enabled in
210 order to use the functionality of the device.
212 config MFD_WM831X_SPI
213 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
216 depends on SPI_MASTER && GENERIC_HARDIRQS
218 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
219 when controlled using SPI. This driver provides common support
220 for accessing the device, additional drivers must be enabled in
221 order to use the functionality of the device.
223 config MFD_WM831X_SPI_A22
224 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI for A22"
227 depends on SPI_MASTER && GENERIC_HARDIRQS
229 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
230 when controlled using SPI. This driver provides common support
231 for accessing the device, additional drivers must be enabled in
232 order to use the functionality of the device.
237 config MFD_WM8350_CONFIG_MODE_0
239 depends on MFD_WM8350
241 config MFD_WM8350_CONFIG_MODE_1
243 depends on MFD_WM8350
245 config MFD_WM8350_CONFIG_MODE_2
247 depends on MFD_WM8350
249 config MFD_WM8350_CONFIG_MODE_3
251 depends on MFD_WM8350
253 config MFD_WM8351_CONFIG_MODE_0
255 depends on MFD_WM8350
257 config MFD_WM8351_CONFIG_MODE_1
259 depends on MFD_WM8350
261 config MFD_WM8351_CONFIG_MODE_2
263 depends on MFD_WM8350
265 config MFD_WM8351_CONFIG_MODE_3
267 depends on MFD_WM8350
269 config MFD_WM8352_CONFIG_MODE_0
271 depends on MFD_WM8350
273 config MFD_WM8352_CONFIG_MODE_1
275 depends on MFD_WM8350
277 config MFD_WM8352_CONFIG_MODE_2
279 depends on MFD_WM8350
281 config MFD_WM8352_CONFIG_MODE_3
283 depends on MFD_WM8350
285 config MFD_WM8350_I2C
286 tristate "Support Wolfson Microelectronics WM8350 with I2C"
290 The WM8350 is an integrated audio and power management
291 subsystem with watchdog and RTC functionality for embedded
292 systems. This option enables core support for the WM8350 with
293 I2C as the control interface. Additional options must be
294 selected to enable support for the functionality of the chip.
297 tristate "Support for NXP PCF50633"
300 Say yes here if you have NXP PCF50633 chip on your board.
301 This core driver provides register access and IRQ handling
302 facilities, and registers devices for the various functions
303 so that function-specific drivers can bind to them.
306 tristate "Support Freescale MC13783"
307 depends on SPI_MASTER
310 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
311 This driver provides common support for accessing the device,
312 additional drivers must be enabled in order to use the
313 functionality of the device.
316 tristate "Support for NXP PCF50633 ADC"
317 depends on MFD_PCF50633
319 Say yes here if you want to include support for ADC in the
323 tristate "Support for NXP PCF50633 GPIO"
324 depends on MFD_PCF50633
326 Say yes here if you want to include support GPIO for pins on
330 tristate "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
332 default y if ARCH_U300
334 Select this to enable the AB3100 Mixed Signal IC core
335 functionality. This connects to a AB3100 on the I2C bus
336 and expose a number of symbols needed for dependent devices
337 to read and write registers and subscribe to events from
338 this multi-functional IC. This is needed to use other features
339 of the AB3100 such as battery-backed RTC, charging control,
340 LEDs, vibrator, system power and temperature, power management
344 tristate "ST-Ericsson AB3100 OTP functions"
345 depends on AB3100_CORE
346 default y if AB3100_CORE
348 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
349 programmable memory) support. This exposes a sysfs file to read
354 depends on GENERIC_HARDIRQS && SPI_MASTER
356 This enables the PCAP ASIC present on EZX Phones. This is
357 needed for MMC, TouchScreen, Sound, USB, etc..
361 menu "Multimedia Capabilities Port drivers"
362 depends on ARCH_SA1100
369 tristate "Support SA11x0 MCP interface"
370 depends on ARCH_SA1100
375 tristate "Support for UCB1200 / UCB1300"
378 config MCP_UCB1200_TS
379 tristate "Touchscreen interface support"
380 depends on MCP_UCB1200 && INPUT