]> bbs.cooldavid.org Git - net-next-2.6.git/blame - drivers/mfd/Kconfig
ARM: AB3550 board configuration and irq for U300
[net-next-2.6.git] / drivers / mfd / Kconfig
CommitLineData
a4e137ab
RK
1#
2# Multifunction miscellaneous devices
3#
4
b6d6454f 5menu "Multifunction device drivers"
e25df120 6 depends on HAS_IOMEM
b6d6454f 7
aa613de6
DES
8config MFD_CORE
9 tristate
10 default n
11
2cc50bee
HZ
12config MFD_88PM860X
13 bool "Support Marvell 88PM8606/88PM8607"
8d002bdc 14 depends on I2C=y && GENERIC_HARDIRQS
2cc50bee
HZ
15 select MFD_CORE
16 help
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.
21
b6d6454f
BD
22config MFD_SM501
23 tristate "Support for Silicon Motion SM501"
24 ---help---
25 This is the core driver for the Silicon Motion SM501 multimedia
26 companion chip. This device is a multifunction device which may
01dd2fbf
ML
27 provide numerous interfaces including USB host controller, USB gadget,
28 asynchronous serial ports, audio functions, and a dual display video
b6d6454f
BD
29 interface. The device may be connected by PCI or local bus with
30 varying functions enabled.
31
f61be273
BD
32config MFD_SM501_GPIO
33 bool "Export GPIO via GPIO layer"
2eedd604 34 depends on MFD_SM501 && GPIOLIB
f61be273
BD
35 ---help---
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.
39
fa9ff4b1
SO
40config MFD_ASIC3
41 bool "Support for Compaq ASIC3"
2eedd604 42 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
9461f65a 43 select MFD_CORE
fa9ff4b1
SO
44 ---help---
45 This driver supports the ASIC3 multifunction chip found on many
46 PDAs (mainly iPAQ and HTC based ones)
47
a87d5638
MD
48config MFD_SH_MOBILE_SDHI
49 bool "Support for SuperH Mobile SDHI"
3d8ca8c0 50 depends on SUPERH || ARCH_SHMOBILE
a87d5638 51 select MFD_CORE
311f3ac7 52 select TMIO_MMC_DMA
a87d5638
MD
53 ---help---
54 This driver supports the SDHI hardware block found in many
55 SuperH Mobile SoCs.
56
ca26308c
MA
57config MFD_DAVINCI_VOICECODEC
58 tristate
59 select MFD_CORE
60
0931a4c6
DB
61config MFD_DM355EVM_MSP
62 bool "DaVinci DM355 EVM microcontroller"
63 depends on I2C && MACH_DAVINCI_DM355_EVM
64 help
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.
68
a1635b8f
PZ
69config HTC_EGPIO
70 bool "HTC EGPIO support"
7444a72e 71 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
a1635b8f
PZ
72 help
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.
76
5dc3339a
PZ
77config HTC_PASIC3
78 tristate "HTC PASIC3 LED/DS1WM chip support"
0254a8f4 79 select MFD_CORE
5dc3339a
PZ
80 help
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.
85
6048a3dd
CM
86config HTC_I2CPLD
87 bool "HTC I2C PLD chip support"
bef3e20c 88 depends on I2C=y && GPIOLIB
6048a3dd
CM
89 help
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.
94
d9105c2b
MV
95config UCB1400_CORE
96 tristate "Philips UCB1400 Core driver"
e4831802 97 depends on AC97_BUS
5a49a540 98 depends on GPIOLIB
d9105c2b
MV
99 help
100 This enables support for the Philips UCB1400 core functions.
101 The UCB1400 is an AC97 audio codec.
102
103 To compile this driver as a module, choose M here: the
104 module will be called ucb1400_core.
105
87c13493
DB
106config TPS65010
107 tristate "TPS6501x Power Management chips"
108 depends on I2C && GPIOLIB
109 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
110 help
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.
115
116 This driver can also be built as a module. If so, the module
117 will be called tps65010.
118
31dd6a26
TF
119config TPS6507X
120 tristate "TPS6507x Power Management / Touch Screen chips"
121 select MFD_CORE
122 depends on I2C
123 help
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.
130
88e75cc3
DB
131config MENELAUS
132 bool "Texas Instruments TWL92330/Menelaus PM chip"
088ef950 133 depends on I2C=y && ARCH_OMAP2
88e75cc3
DB
134 help
135 If you say yes here you get support for the Texas Instruments
136 TWL92330/Menelaus Power Management chip. This include voltage
692105b8 137 regulators, Dual slot memory card transceivers, real-time clock
88e75cc3
DB
138 and other features that are often used in portable devices like
139 cell phones and PDAs.
140
a603a7fa 141config TWL4030_CORE
e8deb28c 142 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
67460a7c 143 depends on I2C=y && GENERIC_HARDIRQS
a603a7fa 144 help
e8deb28c 145 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
a603a7fa
DB
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.
149
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.
154
ebf0bd36
AK
155config TWL4030_POWER
156 bool "Support power resources on TWL4030 family chips"
157 depends on TWL4030_CORE && ARM
158 help
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.
163
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.
167
0b83ddeb
PU
168config TWL4030_CODEC
169 bool
170 depends on TWL4030_CORE
171 select MFD_CORE
172 default n
173
b4ecd326
RV
174config MFD_TC35892
175 bool "Support Toshiba TC35892"
176 depends on I2C=y && GENERIC_HARDIRQS
177 select MFD_CORE
178 help
179 Support for the Toshiba TC35892 I/O Expander.
180
181 This driver provides common support for accessing the device,
182 additional drivers must be enabled in order to use the
183 functionality of the device.
184
1c2c30ac
SO
185config MFD_TMIO
186 bool
187 default n
188
311f3ac7
GL
189config TMIO_MMC_DMA
190 bool
191 select DMA_ENGINE
192 select DMADEVICES
193
1f192015
IM
194config MFD_T7L66XB
195 bool "Support Toshiba T7L66XB"
9ca68233 196 depends on ARM && HAVE_CLK
1f192015 197 select MFD_CORE
1c2c30ac 198 select MFD_TMIO
1f192015
IM
199 help
200 Support for Toshiba Mobile IO Controller T7L66XB
201
cbdfb426
IM
202config MFD_TC6387XB
203 bool "Support Toshiba TC6387XB"
9ca68233 204 depends on ARM && HAVE_CLK
cbdfb426 205 select MFD_CORE
1c2c30ac 206 select MFD_TMIO
cbdfb426
IM
207 help
208 Support for Toshiba Mobile IO Controller TC6387XB
209
d6315949
DES
210config MFD_TC6393XB
211 bool "Support Toshiba TC6393XB"
8d25b36b 212 depends on GPIOLIB && ARM
f024ff10 213 select MFD_CORE
1c2c30ac 214 select MFD_TMIO
d6315949
DES
215 help
216 Support for Toshiba Mobile IO Controller TC6393XB
217
8e2eaabf
SO
218config PMIC_DA903X
219 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
220 depends on I2C=y
221 help
222 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
223 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
224 usually found on PXA processors-based platforms. This includes
225 the I2C driver and the core APIs _only_, you have to select
226 individual components like LCD backlight, voltage regulators,
227 LEDs and battery-charger under the corresponding menus.
a5736e0b
MH
228
229config PMIC_ADP5520
230 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
231 depends on I2C=y
232 help
233 Say yes here to add support for Analog Devices AD5520 and ADP5501,
234 Multifunction Power Management IC. This includes
235 the I2C driver and the core APIs _only_, you have to select
236 individual components like LCD backlight, LEDs, GPIOs and Kepad
237 under the corresponding menus.
8e2eaabf 238
d50f8f33 239config MFD_MAX8925
1f1cf8f9 240 bool "Maxim Semiconductor MAX8925 PMIC Support"
8d002bdc 241 depends on I2C=y && GENERIC_HARDIRQS
1ad99893 242 select MFD_CORE
d50f8f33
HZ
243 help
244 Say yes here to support for Maxim Semiconductor MAX8925. This is
245 a Power Management IC. This driver provies common support for
246 accessing the device, additional drivers must be enabled in order
247 to use the functionality of the device.
248
1d9f9f04
MB
249config MFD_WM8400
250 tristate "Support Wolfson Microelectronics WM8400"
b8380c1a 251 select MFD_CORE
9c366452 252 depends on I2C
1d9f9f04
MB
253 help
254 Support for the Wolfson Microelecronics WM8400 PMIC and audio
9e5aca58 255 CODEC. This driver provides common support for accessing
1d9f9f04
MB
256 the device, additional drivers must be enabled in order to use
257 the functionality of the device.
258
b11062b9 259config MFD_WM831X
6e40173d 260 bool "Support Wolfson Microelectronics WM831x/2x PMICs"
b11062b9 261 select MFD_CORE
8d002bdc 262 depends on I2C=y && GENERIC_HARDIRQS
b11062b9 263 help
d4e0a89e
MB
264 Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
265 This driver provides common support for accessing the device,
b11062b9
MB
266 additional drivers must be enabled in order to use the
267 functionality of the device.
268
89b4012b 269config MFD_WM8350
ecf926bc 270 bool
8d002bdc 271 depends on GENERIC_HARDIRQS
89b4012b
MB
272
273config MFD_WM8350_CONFIG_MODE_0
274 bool
275 depends on MFD_WM8350
276
277config MFD_WM8350_CONFIG_MODE_1
278 bool
279 depends on MFD_WM8350
280
281config MFD_WM8350_CONFIG_MODE_2
282 bool
283 depends on MFD_WM8350
284
285config MFD_WM8350_CONFIG_MODE_3
286 bool
287 depends on MFD_WM8350
288
ca23f8c1
MB
289config MFD_WM8351_CONFIG_MODE_0
290 bool
291 depends on MFD_WM8350
292
293config MFD_WM8351_CONFIG_MODE_1
294 bool
295 depends on MFD_WM8350
296
297config MFD_WM8351_CONFIG_MODE_2
298 bool
299 depends on MFD_WM8350
300
301config MFD_WM8351_CONFIG_MODE_3
302 bool
303 depends on MFD_WM8350
304
96920630
MB
305config MFD_WM8352_CONFIG_MODE_0
306 bool
307 depends on MFD_WM8350
308
309config MFD_WM8352_CONFIG_MODE_1
310 bool
311 depends on MFD_WM8350
312
313config MFD_WM8352_CONFIG_MODE_2
314 bool
315 depends on MFD_WM8350
316
317config MFD_WM8352_CONFIG_MODE_3
318 bool
319 depends on MFD_WM8350
320
c661a0b9 321config MFD_WM8350_I2C
ecf926bc 322 bool "Support Wolfson Microelectronics WM8350 with I2C"
c661a0b9 323 select MFD_WM8350
8d002bdc 324 depends on I2C=y && GENERIC_HARDIRQS
c661a0b9
MB
325 help
326 The WM8350 is an integrated audio and power management
327 subsystem with watchdog and RTC functionality for embedded
328 systems. This option enables core support for the WM8350 with
329 I2C as the control interface. Additional options must be
330 selected to enable support for the functionality of the chip.
331
9e501086 332config MFD_WM8994
c9fbf7e0 333 bool "Support Wolfson Microelectronics WM8994"
9e501086 334 select MFD_CORE
c9fbf7e0 335 depends on I2C=y && GENERIC_HARDIRQS
9e501086
MB
336 help
337 The WM8994 is a highly integrated hi-fi CODEC designed for
338 smartphone applicatiosn. As well as audio functionality it
339 has on board GPIO and regulator functionality which is
340 supported via the relevant subsystems. This driver provides
341 core support for the WM8994, in order to use the actual
342 functionaltiy of the device other drivers must be enabled.
343
f52046b1
BR
344config MFD_PCF50633
345 tristate "Support for NXP PCF50633"
346 depends on I2C
347 help
348 Say yes here if you have NXP PCF50633 chip on your board.
349 This core driver provides register access and IRQ handling
350 facilities, and registers devices for the various functions
351 so that function-specific drivers can bind to them.
352
8238addc
SH
353config MFD_MC13783
354 tristate "Support Freescale MC13783"
355 depends on SPI_MASTER
356 select MFD_CORE
357 help
358 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
359 This driver provides common support for accessing the device,
360 additional drivers must be enabled in order to use the
361 functionality of the device.
362
08c3e06a
BR
363config PCF50633_ADC
364 tristate "Support for NXP PCF50633 ADC"
365 depends on MFD_PCF50633
366 help
367 Say yes here if you want to include support for ADC in the
368 NXP PCF50633 chip.
369
6a3d119b
BR
370config PCF50633_GPIO
371 tristate "Support for NXP PCF50633 GPIO"
372 depends on MFD_PCF50633
373 help
374 Say yes here if you want to include support GPIO for pins on
375 the PCF50633 chip.
376
fa661258
MW
377config ABX500_CORE
378 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
379 default y if ARCH_U300
380 help
381 Say yes here if you have the ABX500 Mixed Signal IC family
382 chips. This core driver expose register access functions.
383 Functionality specific drivers using these functions can
384 remain unchanged when IC changes. Binding of the functions to
385 actual register access is done by the IC core driver.
386
14fa5691 387config AB3100_CORE
2071db48 388 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
fa661258 389 depends on I2C=y && ABX500_CORE
14fa5691
LW
390 default y if ARCH_U300
391 help
392 Select this to enable the AB3100 Mixed Signal IC core
393 functionality. This connects to a AB3100 on the I2C bus
394 and expose a number of symbols needed for dependent devices
395 to read and write registers and subscribe to events from
396 this multi-functional IC. This is needed to use other features
397 of the AB3100 such as battery-backed RTC, charging control,
398 LEDs, vibrator, system power and temperature, power management
399 and ALSA sound.
400
12992dd8
LW
401config AB3100_OTP
402 tristate "ST-Ericsson AB3100 OTP functions"
403 depends on AB3100_CORE
404 default y if AB3100_CORE
405 help
406 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
407 programmable memory) support. This exposes a sysfs file to read
408 out OTP values.
409
13a09f93
DR
410config EZX_PCAP
411 bool "PCAP Support"
412 depends on GENERIC_HARDIRQS && SPI_MASTER
413 help
414 This enables the PCAP ASIC present on EZX Phones. This is
415 needed for MMC, TouchScreen, Sound, USB, etc..
416
0c41839e
SK
417config AB4500_CORE
418 tristate "ST-Ericsson's AB4500 Mixed Signal Power management chip"
419 depends on SPI
0c41839e
SK
420 help
421 Select this option to enable access to AB4500 power management
422 chip. This connects to U8500 on the SSP/SPI bus and exports
423 read/write functions for the devices to get access to this chip.
424 This chip embeds various other multimedia funtionalities as well.
425
09bcb3f3
MW
426config AB3550_CORE
427 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
428 select MFD_CORE
429 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
430 help
431 Select this to enable the AB3550 Mixed Signal IC core
432 functionality. This connects to a AB3550 on the I2C bus
433 and expose a number of symbols needed for dependent devices
434 to read and write registers and subscribe to events from
435 this multi-functional IC. This is needed to use other features
436 of the AB3550 such as battery-backed RTC, charging control,
437 LEDs, vibrator, system power and temperature, power management
438 and ALSA sound.
439
8edbede9
RR
440config MFD_TIMBERDALE
441 tristate "Support for the Timberdale FPGA"
442 select MFD_CORE
546e29b6 443 depends on PCI && GPIOLIB
8edbede9
RR
444 ---help---
445 This is the core driver for the timberdale FPGA. This device is a
446 multifunction device which exposes numerous platform devices.
447
448 The timberdale FPGA can be found on the Intel Atom development board
449 for in-vehicle infontainment, called Russellville.
e82c60ae
DT
450
451config LPC_SCH
452 tristate "Intel SCH LPC"
453 depends on PCI
454 select MFD_CORE
455 help
456 LPC bridge function of the Intel SCH provides support for
457 System Management Bus and General Purpose I/O.
458
e090d506
FF
459config MFD_RDC321X
460 tristate "Support for RDC-R321x southbridge"
461 select MFD_CORE
462 depends on PCI
463 help
464 Say yes here if you want to have support for the RDC R-321x SoC
465 southbridge which provides access to GPIOs and Watchdog using the
466 southbridge PCI device configuration space.
467
bd358132
IS
468config MFD_JANZ_CMODIO
469 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
470 select MFD_CORE
471 depends on PCI
472 help
473 This is the core driver for the Janz CMOD-IO PCI MODULbus
474 carrier board. This device is a PCI to MODULbus bridge which may
475 host many different types of MODULbus daughterboards, including
476 CAN and GPIO controllers.
477
b6d6454f
BD
478endmenu
479
a4e137ab 480menu "Multimedia Capabilities Port drivers"
f751d50f 481 depends on ARCH_SA1100
a4e137ab
RK
482
483config MCP
484 tristate
485
5e742ad6
RK
486# Interface drivers
487config MCP_SA11X0
488 tristate "Support SA11x0 MCP interface"
489 depends on ARCH_SA1100
490 select MCP
491
05c45ca9
RK
492# Chip drivers
493config MCP_UCB1200
494 tristate "Support for UCB1200 / UCB1300"
495 depends on MCP
496
acb45439
RK
497config MCP_UCB1200_TS
498 tristate "Touchscreen interface support"
499 depends on MCP_UCB1200 && INPUT
500
a4e137ab 501endmenu