mfd: Add MODULE_DEVICE_TABLE to rdc321x-southbridge
[linux-2.6-block.git] / drivers / mfd / Kconfig
CommitLineData
a4e137ab
RK
1#
2# Multifunction miscellaneous devices
3#
4
38270644
RD
5menuconfig MFD_SUPPORT
6 bool "Multifunction device drivers"
e25df120 7 depends on HAS_IOMEM
38270644
RD
8 default y
9 help
15742c8a
SO
10 Multifunction devices embed several functions (e.g. GPIOs,
11 touchscreens, keyboards, current regulators, power management chips,
12 etc...) in one single integrated circuit. They usually talk to the
13 main CPU through one or more IRQ lines and low speed data busses (SPI,
14 I2C, etc..). They appear as one single device to the main system
15 through the data bus and the MFD framework allows for sub devices
16 (a.k.a. functions) to appear as discrete platform devices.
17 MFDs are typically found on embedded platforms.
18
19 This option alone does not add any kernel code.
38270644
RD
20
21if MFD_SUPPORT
b6d6454f 22
aa613de6
DB
23config MFD_CORE
24 tristate
25 default n
26
2cc50bee
HZ
27config MFD_88PM860X
28 bool "Support Marvell 88PM8606/88PM8607"
8d002bdc 29 depends on I2C=y && GENERIC_HARDIRQS
2cc50bee
HZ
30 select MFD_CORE
31 help
32 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
33 This includes the I2C driver and the core APIs _only_, you have to
34 select individual components like voltage regulators, RTC and
35 battery-charger under the corresponding menus.
36
b6d6454f
BD
37config MFD_SM501
38 tristate "Support for Silicon Motion SM501"
39 ---help---
40 This is the core driver for the Silicon Motion SM501 multimedia
41 companion chip. This device is a multifunction device which may
01dd2fbf
ML
42 provide numerous interfaces including USB host controller, USB gadget,
43 asynchronous serial ports, audio functions, and a dual display video
b6d6454f
BD
44 interface. The device may be connected by PCI or local bus with
45 varying functions enabled.
46
f61be273
BD
47config MFD_SM501_GPIO
48 bool "Export GPIO via GPIO layer"
2eedd604 49 depends on MFD_SM501 && GPIOLIB
f61be273
BD
50 ---help---
51 This option uses the gpio library layer to export the 64 GPIO
52 lines on the SM501. The platform data is used to supply the
53 base number for the first GPIO line to register.
54
fa9ff4b1
SO
55config MFD_ASIC3
56 bool "Support for Compaq ASIC3"
2eedd604 57 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
9461f65a 58 select MFD_CORE
fa9ff4b1
SO
59 ---help---
60 This driver supports the ASIC3 multifunction chip found on many
61 PDAs (mainly iPAQ and HTC based ones)
62
a87d5638
MD
63config MFD_SH_MOBILE_SDHI
64 bool "Support for SuperH Mobile SDHI"
3d8ca8c0 65 depends on SUPERH || ARCH_SHMOBILE
a87d5638 66 select MFD_CORE
311f3ac7 67 select TMIO_MMC_DMA
a87d5638
MD
68 ---help---
69 This driver supports the SDHI hardware block found in many
70 SuperH Mobile SoCs.
71
ca26308c
MA
72config MFD_DAVINCI_VOICECODEC
73 tristate
74 select MFD_CORE
75
0931a4c6
DB
76config MFD_DM355EVM_MSP
77 bool "DaVinci DM355 EVM microcontroller"
1819ebcf 78 depends on I2C=y && MACH_DAVINCI_DM355_EVM
0931a4c6
DB
79 help
80 This driver supports the MSP430 microcontroller used on these
81 boards. MSP430 firmware manages resets and power sequencing,
82 inputs from buttons and the IR remote, LEDs, an RTC, and more.
83
03df0f62
CC
84config MFD_TI_SSP
85 tristate "TI Sequencer Serial Port support"
86 depends on ARCH_DAVINCI_TNETV107X
87 select MFD_CORE
88 ---help---
89 Say Y here if you want support for the Sequencer Serial Port
90 in a Texas Instruments TNETV107X SoC.
91
92 To compile this driver as a module, choose M here: the
93 module will be called ti-ssp.
94
a1635b8f
PZ
95config HTC_EGPIO
96 bool "HTC EGPIO support"
7444a72e 97 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
a1635b8f
PZ
98 help
99 This driver supports the CPLD egpio chip present on
100 several HTC phones. It provides basic support for input
101 pins, output pins, and irqs.
102
5dc3339a
PZ
103config HTC_PASIC3
104 tristate "HTC PASIC3 LED/DS1WM chip support"
0254a8f4 105 select MFD_CORE
5dc3339a
PZ
106 help
107 This core driver provides register access for the LED/DS1WM
108 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
109 HTC Magician devices, respectively. Actual functionality is
110 handled by the leds-pasic3 and ds1wm drivers.
111
6048a3dd
CM
112config HTC_I2CPLD
113 bool "HTC I2C PLD chip support"
bef3e20c 114 depends on I2C=y && GPIOLIB
6048a3dd
CM
115 help
116 If you say yes here you get support for the supposed CPLD
117 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
118 This device provides input and output GPIOs through an I2C
119 interface to one or more sub-chips.
120
d9105c2b
MV
121config UCB1400_CORE
122 tristate "Philips UCB1400 Core driver"
e4831802 123 depends on AC97_BUS
5a49a540 124 depends on GPIOLIB
d9105c2b
MV
125 help
126 This enables support for the Philips UCB1400 core functions.
127 The UCB1400 is an AC97 audio codec.
128
129 To compile this driver as a module, choose M here: the
130 module will be called ucb1400_core.
131
798a8eee
LW
132config TPS6105X
133 tristate "TPS61050/61052 Boost Converters"
134 depends on I2C
2edd3b69
LW
135 select REGULATOR
136 select REGULATOR_FIXED_VOLTAGE
798a8eee
LW
137 help
138 This option enables a driver for the TP61050/TPS61052
139 high-power "white LED driver". This boost converter is
140 sometimes used for other things than white LEDs, and
141 also contains a GPIO pin.
142
87c13493
DB
143config TPS65010
144 tristate "TPS6501x Power Management chips"
145 depends on I2C && GPIOLIB
146 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
147 help
148 If you say yes here you get support for the TPS6501x series of
149 Power Management chips. These include voltage regulators,
150 lithium ion/polymer battery charging, and other features that
151 are often used in portable devices like cell phones and cameras.
152
153 This driver can also be built as a module. If so, the module
154 will be called tps65010.
155
31dd6a26
TF
156config TPS6507X
157 tristate "TPS6507x Power Management / Touch Screen chips"
158 select MFD_CORE
159 depends on I2C
160 help
161 If you say yes here you get support for the TPS6507x series of
162 Power Management / Touch Screen chips. These include voltage
163 regulators, lithium ion/polymer battery charging, touch screen
164 and other features that are often used in portable devices.
165 This driver can also be built as a module. If so, the module
166 will be called tps6507x.
167
88e75cc3
DB
168config MENELAUS
169 bool "Texas Instruments TWL92330/Menelaus PM chip"
088ef950 170 depends on I2C=y && ARCH_OMAP2
88e75cc3
DB
171 help
172 If you say yes here you get support for the Texas Instruments
173 TWL92330/Menelaus Power Management chip. This include voltage
692105b8 174 regulators, Dual slot memory card transceivers, real-time clock
88e75cc3
DB
175 and other features that are often used in portable devices like
176 cell phones and PDAs.
177
a603a7fa 178config TWL4030_CORE
e8deb28c 179 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
67460a7c 180 depends on I2C=y && GENERIC_HARDIRQS
a603a7fa 181 help
e8deb28c 182 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
a603a7fa
DB
183 This core driver provides register access and IRQ handling
184 facilities, and registers devices for the various functions
185 so that function-specific drivers can bind to them.
186
187 These multi-function chips are found on many OMAP2 and OMAP3
188 boards, providing power management, RTC, GPIO, keypad, a
189 high speed USB OTG transceiver, an audio codec (on most
190 versions) and many other features.
191
f99c1d4f
K
192config TWL4030_MADC
193 tristate "Texas Instruments TWL4030 MADC"
194 depends on TWL4030_CORE
195 help
196 This driver provides support for triton TWL4030-MADC. The
197 driver supports both RT and SW conversion methods.
198
199 This driver can be built as a module. If so it will be
200 named twl4030-madc
201
ebf0bd36
AK
202config TWL4030_POWER
203 bool "Support power resources on TWL4030 family chips"
204 depends on TWL4030_CORE && ARM
205 help
206 Say yes here if you want to use the power resources on the
207 TWL4030 family chips. Most of these resources are regulators,
208 which have a separate driver; some are control signals, such
209 as clock request handshaking.
210
211 This driver uses board-specific data to initialize the resources
212 and load scripts controling which resources are switched off/on
213 or reset when a sleep, wakeup or warm reset event occurs.
214
0b83ddeb
PU
215config TWL4030_CODEC
216 bool
217 depends on TWL4030_CORE
218 select MFD_CORE
219 default n
220
31fc03df
H
221config TWL6030_PWM
222 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
223 depends on TWL4030_CORE
224 select HAVE_PWM
225 default n
226 help
227 Say yes here if you want support for TWL6030 PWM.
228 This is used to control charging LED brightness.
229
27e34995
RV
230config MFD_STMPE
231 bool "Support STMicroelectronics STMPE"
232 depends on I2C=y && GENERIC_HARDIRQS
233 select MFD_CORE
234 help
235 Support for the STMPE family of I/O Expanders from
236 STMicroelectronics.
237
238 Currently supported devices are:
239
240 STMPE811: GPIO, Touchscreen
241 STMPE1601: GPIO, Keypad
242 STMPE2401: GPIO, Keypad
243 STMPE2403: GPIO, Keypad
244
245 This driver provides common support for accessing the device,
246 additional drivers must be enabled in order to use the functionality
247 of the device. Currently available sub drivers are:
248
249 GPIO: stmpe-gpio
250 Keypad: stmpe-keypad
251 Touchscreen: stmpe-ts
252
f4e8afdc
SI
253config MFD_TC3589X
254 bool "Support Toshiba TC35892 and variants"
b4ecd326
RV
255 depends on I2C=y && GENERIC_HARDIRQS
256 select MFD_CORE
257 help
f4e8afdc 258 Support for the Toshiba TC35892 and variants I/O Expander.
b4ecd326
RV
259
260 This driver provides common support for accessing the device,
261 additional drivers must be enabled in order to use the
262 functionality of the device.
263
1c2c30ac
SO
264config MFD_TMIO
265 bool
266 default n
267
311f3ac7
GL
268config TMIO_MMC_DMA
269 bool
270 select DMA_ENGINE
271 select DMADEVICES
272
1f192015
IM
273config MFD_T7L66XB
274 bool "Support Toshiba T7L66XB"
9ca68233 275 depends on ARM && HAVE_CLK
1f192015 276 select MFD_CORE
1c2c30ac 277 select MFD_TMIO
1f192015
IM
278 help
279 Support for Toshiba Mobile IO Controller T7L66XB
280
cbdfb426
IM
281config MFD_TC6387XB
282 bool "Support Toshiba TC6387XB"
9ca68233 283 depends on ARM && HAVE_CLK
cbdfb426 284 select MFD_CORE
1c2c30ac 285 select MFD_TMIO
cbdfb426
IM
286 help
287 Support for Toshiba Mobile IO Controller TC6387XB
288
d6315949
DB
289config MFD_TC6393XB
290 bool "Support Toshiba TC6393XB"
8d25b36b 291 depends on GPIOLIB && ARM
f024ff10 292 select MFD_CORE
1c2c30ac 293 select MFD_TMIO
d6315949
DB
294 help
295 Support for Toshiba Mobile IO Controller TC6393XB
296
8e2eaabf
SO
297config PMIC_DA903X
298 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
299 depends on I2C=y
300 help
301 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
302 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
303 usually found on PXA processors-based platforms. This includes
304 the I2C driver and the core APIs _only_, you have to select
305 individual components like LCD backlight, voltage regulators,
306 LEDs and battery-charger under the corresponding menus.
a5736e0b
MH
307
308config PMIC_ADP5520
309 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
310 depends on I2C=y
311 help
312 Say yes here to add support for Analog Devices AD5520 and ADP5501,
313 Multifunction Power Management IC. This includes
314 the I2C driver and the core APIs _only_, you have to select
315 individual components like LCD backlight, LEDs, GPIOs and Kepad
316 under the corresponding menus.
8e2eaabf 317
d50f8f33 318config MFD_MAX8925
1f1cf8f9 319 bool "Maxim Semiconductor MAX8925 PMIC Support"
8d002bdc 320 depends on I2C=y && GENERIC_HARDIRQS
1ad99893 321 select MFD_CORE
d50f8f33
HZ
322 help
323 Say yes here to support for Maxim Semiconductor MAX8925. This is
324 a Power Management IC. This driver provies common support for
325 accessing the device, additional drivers must be enabled in order
326 to use the functionality of the device.
327
527e7e9a
MH
328config MFD_MAX8997
329 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
330 depends on I2C=y && GENERIC_HARDIRQS
331 select MFD_CORE
332 help
333 Say yes here to support for Maxim Semiconductor MAX8998/8966.
334 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
335 MUIC controls on chip.
d7e8c01a 336 This driver provides common support for accessing the device;
527e7e9a
MH
337 additional drivers must be enabled in order to use the functionality
338 of the device.
339
156f2528 340config MFD_MAX8998
f8539ddc 341 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
2c7e6f57 342 depends on I2C=y && GENERIC_HARDIRQS
156f2528
KP
343 select MFD_CORE
344 help
f8539ddc
KP
345 Say yes here to support for Maxim Semiconductor MAX8998 and
346 National Semiconductor LP3974. This is a Power Management IC.
347 This driver provies common support for accessing the device,
348 additional drivers must be enabled in order to use the functionality
349 of the device.
156f2528 350
1d9f9f04
MB
351config MFD_WM8400
352 tristate "Support Wolfson Microelectronics WM8400"
b8380c1a 353 select MFD_CORE
9c366452 354 depends on I2C
1d9f9f04
MB
355 help
356 Support for the Wolfson Microelecronics WM8400 PMIC and audio
9e5aca58 357 CODEC. This driver provides common support for accessing
1d9f9f04
MB
358 the device, additional drivers must be enabled in order to use
359 the functionality of the device.
360
b11062b9 361config MFD_WM831X
e5b48684
MB
362 bool
363 depends on GENERIC_HARDIRQS
364
365config MFD_WM831X_I2C
366 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
b11062b9 367 select MFD_CORE
e5b48684 368 select MFD_WM831X
8d002bdc 369 depends on I2C=y && GENERIC_HARDIRQS
b11062b9 370 help
e5b48684
MB
371 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
372 when controlled using I2C. This driver provides common support
373 for accessing the device, additional drivers must be enabled in
374 order to use the functionality of the device.
b11062b9 375
2aa13b9e
MB
376config MFD_WM831X_SPI
377 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
378 select MFD_CORE
379 select MFD_WM831X
380 depends on SPI_MASTER && GENERIC_HARDIRQS
381 help
382 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
383 when controlled using SPI. This driver provides common support
384 for accessing the device, additional drivers must be enabled in
385 order to use the functionality of the device.
386
89b4012b 387config MFD_WM8350
ecf926bc 388 bool
8d002bdc 389 depends on GENERIC_HARDIRQS
89b4012b
MB
390
391config MFD_WM8350_CONFIG_MODE_0
392 bool
393 depends on MFD_WM8350
394
395config MFD_WM8350_CONFIG_MODE_1
396 bool
397 depends on MFD_WM8350
398
399config MFD_WM8350_CONFIG_MODE_2
400 bool
401 depends on MFD_WM8350
402
403config MFD_WM8350_CONFIG_MODE_3
404 bool
405 depends on MFD_WM8350
406
ca23f8c1
MB
407config MFD_WM8351_CONFIG_MODE_0
408 bool
409 depends on MFD_WM8350
410
411config MFD_WM8351_CONFIG_MODE_1
412 bool
413 depends on MFD_WM8350
414
415config MFD_WM8351_CONFIG_MODE_2
416 bool
417 depends on MFD_WM8350
418
419config MFD_WM8351_CONFIG_MODE_3
420 bool
421 depends on MFD_WM8350
422
96920630
MB
423config MFD_WM8352_CONFIG_MODE_0
424 bool
425 depends on MFD_WM8350
426
427config MFD_WM8352_CONFIG_MODE_1
428 bool
429 depends on MFD_WM8350
430
431config MFD_WM8352_CONFIG_MODE_2
432 bool
433 depends on MFD_WM8350
434
435config MFD_WM8352_CONFIG_MODE_3
436 bool
437 depends on MFD_WM8350
438
c661a0b9 439config MFD_WM8350_I2C
ecf926bc 440 bool "Support Wolfson Microelectronics WM8350 with I2C"
c661a0b9 441 select MFD_WM8350
8d002bdc 442 depends on I2C=y && GENERIC_HARDIRQS
c661a0b9
MB
443 help
444 The WM8350 is an integrated audio and power management
445 subsystem with watchdog and RTC functionality for embedded
446 systems. This option enables core support for the WM8350 with
447 I2C as the control interface. Additional options must be
448 selected to enable support for the functionality of the chip.
449
9e501086 450config MFD_WM8994
c9fbf7e0 451 bool "Support Wolfson Microelectronics WM8994"
9e501086 452 select MFD_CORE
c9fbf7e0 453 depends on I2C=y && GENERIC_HARDIRQS
9e501086
MB
454 help
455 The WM8994 is a highly integrated hi-fi CODEC designed for
456 smartphone applicatiosn. As well as audio functionality it
457 has on board GPIO and regulator functionality which is
458 supported via the relevant subsystems. This driver provides
459 core support for the WM8994, in order to use the actual
460 functionaltiy of the device other drivers must be enabled.
461
f52046b1
BR
462config MFD_PCF50633
463 tristate "Support for NXP PCF50633"
464 depends on I2C
465 help
466 Say yes here if you have NXP PCF50633 chip on your board.
467 This core driver provides register access and IRQ handling
468 facilities, and registers devices for the various functions
469 so that function-specific drivers can bind to them.
470
8238addc 471config MFD_MC13783
8e005935
UKK
472 tristate
473
474config MFD_MC13XXX
475 tristate "Support Freescale MC13783 and MC13892"
8238addc
SH
476 depends on SPI_MASTER
477 select MFD_CORE
8e005935 478 select MFD_MC13783
8238addc 479 help
8e005935
UKK
480 Support for the Freescale (Atlas) PMIC and audio CODECs
481 MC13783 and MC13892.
8238addc
SH
482 This driver provides common support for accessing the device,
483 additional drivers must be enabled in order to use the
484 functionality of the device.
485
08c3e06a
BR
486config PCF50633_ADC
487 tristate "Support for NXP PCF50633 ADC"
488 depends on MFD_PCF50633
489 help
490 Say yes here if you want to include support for ADC in the
491 NXP PCF50633 chip.
492
6a3d119b
BR
493config PCF50633_GPIO
494 tristate "Support for NXP PCF50633 GPIO"
495 depends on MFD_PCF50633
496 help
497 Say yes here if you want to include support GPIO for pins on
498 the PCF50633 chip.
499
fa661258
MW
500config ABX500_CORE
501 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
47c16975 502 default y if ARCH_U300 || ARCH_U8500
fa661258
MW
503 help
504 Say yes here if you have the ABX500 Mixed Signal IC family
505 chips. This core driver expose register access functions.
506 Functionality specific drivers using these functions can
507 remain unchanged when IC changes. Binding of the functions to
508 actual register access is done by the IC core driver.
509
14fa5691 510config AB3100_CORE
2071db48 511 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
fa661258 512 depends on I2C=y && ABX500_CORE
8c96aefb 513 select MFD_CORE
14fa5691
LW
514 default y if ARCH_U300
515 help
516 Select this to enable the AB3100 Mixed Signal IC core
517 functionality. This connects to a AB3100 on the I2C bus
518 and expose a number of symbols needed for dependent devices
519 to read and write registers and subscribe to events from
520 this multi-functional IC. This is needed to use other features
521 of the AB3100 such as battery-backed RTC, charging control,
522 LEDs, vibrator, system power and temperature, power management
523 and ALSA sound.
524
12992dd8
LW
525config AB3100_OTP
526 tristate "ST-Ericsson AB3100 OTP functions"
527 depends on AB3100_CORE
528 default y if AB3100_CORE
529 help
530 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
531 programmable memory) support. This exposes a sysfs file to read
532 out OTP values.
533
13a09f93
DR
534config EZX_PCAP
535 bool "PCAP Support"
536 depends on GENERIC_HARDIRQS && SPI_MASTER
537 help
538 This enables the PCAP ASIC present on EZX Phones. This is
539 needed for MMC, TouchScreen, Sound, USB, etc..
540
62579266
RV
541config AB8500_CORE
542 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
6680d940 543 depends on GENERIC_HARDIRQS && ABX500_CORE
62579266 544 select MFD_CORE
0c41839e 545 help
62579266 546 Select this option to enable access to AB8500 power management
6680d940
SI
547 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
548 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
549 the irq_chip parts for handling the Mixed Signal chip events.
0c41839e
SK
550 This chip embeds various other multimedia funtionalities as well.
551
39368eda
MW
552config AB8500_I2C_CORE
553 bool "AB8500 register access via PRCMU I2C"
554 depends on AB8500_CORE && UX500_SOC_DB8500
555 default y
556 help
557 This enables register access to the AB8500 chip via PRCMU I2C.
558 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
559 the I2C bus is connected to the Power Reset
560 and Mangagement Unit, PRCMU.
561
5814fc35
MW
562config AB8500_DEBUG
563 bool "Enable debug info via debugfs"
564 depends on AB8500_CORE && DEBUG_FS
565 default y if DEBUG_FS
566 help
567 Select this option if you want debug information using the debug
568 filesystem, debugfs.
dae2db30
AM
569
570config AB8500_GPADC
571 bool "AB8500 GPADC driver"
572 depends on AB8500_CORE && REGULATOR_AB8500
573 default y
574 help
575 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
5814fc35 576
09bcb3f3
MW
577config AB3550_CORE
578 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
579 select MFD_CORE
580 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
581 help
582 Select this to enable the AB3550 Mixed Signal IC core
583 functionality. This connects to a AB3550 on the I2C bus
584 and expose a number of symbols needed for dependent devices
585 to read and write registers and subscribe to events from
586 this multi-functional IC. This is needed to use other features
587 of the AB3550 such as battery-backed RTC, charging control,
588 LEDs, vibrator, system power and temperature, power management
589 and ALSA sound.
590
f71e1afd
AS
591config MFD_CS5535
592 tristate "Support for CS5535 and CS5536 southbridge core functions"
593 select MFD_CORE
594 depends on PCI
595 ---help---
596 This is the core driver for CS5535/CS5536 MFD functions. This is
597 necessary for using the board's GPIO and MFGPT functionality.
598
8edbede9
RR
599config MFD_TIMBERDALE
600 tristate "Support for the Timberdale FPGA"
601 select MFD_CORE
546e29b6 602 depends on PCI && GPIOLIB
8edbede9
RR
603 ---help---
604 This is the core driver for the timberdale FPGA. This device is a
605 multifunction device which exposes numerous platform devices.
606
607 The timberdale FPGA can be found on the Intel Atom development board
608 for in-vehicle infontainment, called Russellville.
e82c60ae
DT
609
610config LPC_SCH
611 tristate "Intel SCH LPC"
612 depends on PCI
613 select MFD_CORE
614 help
615 LPC bridge function of the Intel SCH provides support for
616 System Management Bus and General Purpose I/O.
617
e090d506
FF
618config MFD_RDC321X
619 tristate "Support for RDC-R321x southbridge"
620 select MFD_CORE
621 depends on PCI
622 help
623 Say yes here if you want to have support for the RDC R-321x SoC
624 southbridge which provides access to GPIOs and Watchdog using the
625 southbridge PCI device configuration space.
626
bd358132
IS
627config MFD_JANZ_CMODIO
628 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
629 select MFD_CORE
630 depends on PCI
631 help
632 This is the core driver for the Janz CMOD-IO PCI MODULbus
633 carrier board. This device is a PCI to MODULbus bridge which may
634 host many different types of MODULbus daughterboards, including
635 CAN and GPIO controllers.
636
91f4debf
LPC
637config MFD_JZ4740_ADC
638 tristate "Support for the JZ4740 SoC ADC core"
639 select MFD_CORE
640 depends on MACH_JZ4740
641 help
642 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
643 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
644
c6c19332 645config MFD_TPS6586X
c26448c4
GK
646 bool "TPS6586x Power Management chips"
647 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
c6c19332
MR
648 select MFD_CORE
649 help
650 If you say yes here you get support for the TPS6586X series of
651 Power Management chips.
652 This driver provides common support for accessing the device,
653 additional drivers must be enabled in order to use the
654 functionality of the device.
655
656 This driver can also be built as a module. If so, the module
657 will be called tps6586x.
658
375fc77b
DD
659config MFD_VX855
660 tristate "Support for VIA VX855/VX875 integrated south bridge"
661 depends on PCI
662 select MFD_CORE
663 help
664 Say yes here to enable support for various functions of the
665 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
666 and/or vx855_gpio drivers for this to do anything useful.
667
383268a8 668config MFD_WL1273_CORE
94fd5b74 669 tristate "Support for TI WL1273 FM radio."
383268a8
MA
670 depends on I2C
671 select MFD_CORE
672 default n
673 help
674 This is the core driver for the TI WL1273 FM radio. This MFD
675 driver connects the radio-wl1273 V4L2 module and the wl1273
676 audio codec.
677
17cdd29d
KM
678config MFD_OMAP_USB_HOST
679 bool "Support OMAP USBHS core driver"
680 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
681 default y
682 help
683 This is the core driver for the OAMP EHCI and OHCI drivers.
684 This MFD driver does the required setup functionalities for
685 OMAP USB Host drivers.
686
38270644 687endif # MFD_SUPPORT
b6d6454f 688
a4e137ab 689menu "Multimedia Capabilities Port drivers"
f751d50f 690 depends on ARCH_SA1100
a4e137ab
RK
691
692config MCP
693 tristate
694
5e742ad6
RK
695# Interface drivers
696config MCP_SA11X0
697 tristate "Support SA11x0 MCP interface"
698 depends on ARCH_SA1100
699 select MCP
700
05c45ca9
RK
701# Chip drivers
702config MCP_UCB1200
703 tristate "Support for UCB1200 / UCB1300"
704 depends on MCP
705
acb45439
RK
706config MCP_UCB1200_TS
707 tristate "Touchscreen interface support"
708 depends on MCP_UCB1200 && INPUT
709
a4e137ab 710endmenu