]> bbs.cooldavid.org Git - net-next-2.6.git/blame - drivers/mfd/Kconfig
mfd: Remove DEBUG defines from mc13xxx-core
[net-next-2.6.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
DES
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
a1635b8f
PZ
84config HTC_EGPIO
85 bool "HTC EGPIO support"
7444a72e 86 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
a1635b8f
PZ
87 help
88 This driver supports the CPLD egpio chip present on
89 several HTC phones. It provides basic support for input
90 pins, output pins, and irqs.
91
5dc3339a
PZ
92config HTC_PASIC3
93 tristate "HTC PASIC3 LED/DS1WM chip support"
0254a8f4 94 select MFD_CORE
5dc3339a
PZ
95 help
96 This core driver provides register access for the LED/DS1WM
97 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
98 HTC Magician devices, respectively. Actual functionality is
99 handled by the leds-pasic3 and ds1wm drivers.
100
6048a3dd
CM
101config HTC_I2CPLD
102 bool "HTC I2C PLD chip support"
bef3e20c 103 depends on I2C=y && GPIOLIB
6048a3dd
CM
104 help
105 If you say yes here you get support for the supposed CPLD
106 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
107 This device provides input and output GPIOs through an I2C
108 interface to one or more sub-chips.
109
d9105c2b
MV
110config UCB1400_CORE
111 tristate "Philips UCB1400 Core driver"
e4831802 112 depends on AC97_BUS
5a49a540 113 depends on GPIOLIB
d9105c2b
MV
114 help
115 This enables support for the Philips UCB1400 core functions.
116 The UCB1400 is an AC97 audio codec.
117
118 To compile this driver as a module, choose M here: the
119 module will be called ucb1400_core.
120
87c13493
DB
121config TPS65010
122 tristate "TPS6501x Power Management chips"
123 depends on I2C && GPIOLIB
124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
125 help
126 If you say yes here you get support for the TPS6501x series of
127 Power Management chips. These include voltage regulators,
128 lithium ion/polymer battery charging, and other features that
129 are often used in portable devices like cell phones and cameras.
130
131 This driver can also be built as a module. If so, the module
132 will be called tps65010.
133
31dd6a26
TF
134config TPS6507X
135 tristate "TPS6507x Power Management / Touch Screen chips"
136 select MFD_CORE
137 depends on I2C
138 help
139 If you say yes here you get support for the TPS6507x series of
140 Power Management / Touch Screen chips. These include voltage
141 regulators, lithium ion/polymer battery charging, touch screen
142 and other features that are often used in portable devices.
143 This driver can also be built as a module. If so, the module
144 will be called tps6507x.
145
88e75cc3
DB
146config MENELAUS
147 bool "Texas Instruments TWL92330/Menelaus PM chip"
088ef950 148 depends on I2C=y && ARCH_OMAP2
88e75cc3
DB
149 help
150 If you say yes here you get support for the Texas Instruments
151 TWL92330/Menelaus Power Management chip. This include voltage
692105b8 152 regulators, Dual slot memory card transceivers, real-time clock
88e75cc3
DB
153 and other features that are often used in portable devices like
154 cell phones and PDAs.
155
a603a7fa 156config TWL4030_CORE
e8deb28c 157 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
67460a7c 158 depends on I2C=y && GENERIC_HARDIRQS
a603a7fa 159 help
e8deb28c 160 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
a603a7fa
DB
161 This core driver provides register access and IRQ handling
162 facilities, and registers devices for the various functions
163 so that function-specific drivers can bind to them.
164
165 These multi-function chips are found on many OMAP2 and OMAP3
166 boards, providing power management, RTC, GPIO, keypad, a
167 high speed USB OTG transceiver, an audio codec (on most
168 versions) and many other features.
169
ebf0bd36
AK
170config TWL4030_POWER
171 bool "Support power resources on TWL4030 family chips"
172 depends on TWL4030_CORE && ARM
173 help
174 Say yes here if you want to use the power resources on the
175 TWL4030 family chips. Most of these resources are regulators,
176 which have a separate driver; some are control signals, such
177 as clock request handshaking.
178
179 This driver uses board-specific data to initialize the resources
180 and load scripts controling which resources are switched off/on
181 or reset when a sleep, wakeup or warm reset event occurs.
182
0b83ddeb
PU
183config TWL4030_CODEC
184 bool
185 depends on TWL4030_CORE
186 select MFD_CORE
187 default n
188
31fc03df
H
189config TWL6030_PWM
190 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
191 depends on TWL4030_CORE
192 select HAVE_PWM
193 default n
194 help
195 Say yes here if you want support for TWL6030 PWM.
196 This is used to control charging LED brightness.
197
27e34995
RV
198config MFD_STMPE
199 bool "Support STMicroelectronics STMPE"
200 depends on I2C=y && GENERIC_HARDIRQS
201 select MFD_CORE
202 help
203 Support for the STMPE family of I/O Expanders from
204 STMicroelectronics.
205
206 Currently supported devices are:
207
208 STMPE811: GPIO, Touchscreen
209 STMPE1601: GPIO, Keypad
210 STMPE2401: GPIO, Keypad
211 STMPE2403: GPIO, Keypad
212
213 This driver provides common support for accessing the device,
214 additional drivers must be enabled in order to use the functionality
215 of the device. Currently available sub drivers are:
216
217 GPIO: stmpe-gpio
218 Keypad: stmpe-keypad
219 Touchscreen: stmpe-ts
220
b4ecd326
RV
221config MFD_TC35892
222 bool "Support Toshiba TC35892"
223 depends on I2C=y && GENERIC_HARDIRQS
224 select MFD_CORE
225 help
226 Support for the Toshiba TC35892 I/O Expander.
227
228 This driver provides common support for accessing the device,
229 additional drivers must be enabled in order to use the
230 functionality of the device.
231
1c2c30ac
SO
232config MFD_TMIO
233 bool
234 default n
235
311f3ac7
GL
236config TMIO_MMC_DMA
237 bool
238 select DMA_ENGINE
239 select DMADEVICES
240
1f192015
IM
241config MFD_T7L66XB
242 bool "Support Toshiba T7L66XB"
9ca68233 243 depends on ARM && HAVE_CLK
1f192015 244 select MFD_CORE
1c2c30ac 245 select MFD_TMIO
1f192015
IM
246 help
247 Support for Toshiba Mobile IO Controller T7L66XB
248
cbdfb426
IM
249config MFD_TC6387XB
250 bool "Support Toshiba TC6387XB"
9ca68233 251 depends on ARM && HAVE_CLK
cbdfb426 252 select MFD_CORE
1c2c30ac 253 select MFD_TMIO
cbdfb426
IM
254 help
255 Support for Toshiba Mobile IO Controller TC6387XB
256
d6315949
DES
257config MFD_TC6393XB
258 bool "Support Toshiba TC6393XB"
8d25b36b 259 depends on GPIOLIB && ARM
f024ff10 260 select MFD_CORE
1c2c30ac 261 select MFD_TMIO
d6315949
DES
262 help
263 Support for Toshiba Mobile IO Controller TC6393XB
264
8e2eaabf
SO
265config PMIC_DA903X
266 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
267 depends on I2C=y
268 help
269 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
270 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
271 usually found on PXA processors-based platforms. This includes
272 the I2C driver and the core APIs _only_, you have to select
273 individual components like LCD backlight, voltage regulators,
274 LEDs and battery-charger under the corresponding menus.
a5736e0b
MH
275
276config PMIC_ADP5520
277 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
278 depends on I2C=y
279 help
280 Say yes here to add support for Analog Devices AD5520 and ADP5501,
281 Multifunction Power Management IC. This includes
282 the I2C driver and the core APIs _only_, you have to select
283 individual components like LCD backlight, LEDs, GPIOs and Kepad
284 under the corresponding menus.
8e2eaabf 285
d50f8f33 286config MFD_MAX8925
1f1cf8f9 287 bool "Maxim Semiconductor MAX8925 PMIC Support"
8d002bdc 288 depends on I2C=y && GENERIC_HARDIRQS
1ad99893 289 select MFD_CORE
d50f8f33
HZ
290 help
291 Say yes here to support for Maxim Semiconductor MAX8925. This is
292 a Power Management IC. This driver provies common support for
293 accessing the device, additional drivers must be enabled in order
294 to use the functionality of the device.
295
156f2528 296config MFD_MAX8998
f8539ddc 297 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
2c7e6f57 298 depends on I2C=y && GENERIC_HARDIRQS
156f2528
KP
299 select MFD_CORE
300 help
f8539ddc
KP
301 Say yes here to support for Maxim Semiconductor MAX8998 and
302 National Semiconductor LP3974. This is a Power Management IC.
303 This driver provies common support for accessing the device,
304 additional drivers must be enabled in order to use the functionality
305 of the device.
156f2528 306
1d9f9f04
MB
307config MFD_WM8400
308 tristate "Support Wolfson Microelectronics WM8400"
b8380c1a 309 select MFD_CORE
9c366452 310 depends on I2C
1d9f9f04
MB
311 help
312 Support for the Wolfson Microelecronics WM8400 PMIC and audio
9e5aca58 313 CODEC. This driver provides common support for accessing
1d9f9f04
MB
314 the device, additional drivers must be enabled in order to use
315 the functionality of the device.
316
b11062b9 317config MFD_WM831X
6e40173d 318 bool "Support Wolfson Microelectronics WM831x/2x PMICs"
b11062b9 319 select MFD_CORE
8d002bdc 320 depends on I2C=y && GENERIC_HARDIRQS
b11062b9 321 help
d4e0a89e
MB
322 Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
323 This driver provides common support for accessing the device,
b11062b9
MB
324 additional drivers must be enabled in order to use the
325 functionality of the device.
326
89b4012b 327config MFD_WM8350
ecf926bc 328 bool
8d002bdc 329 depends on GENERIC_HARDIRQS
89b4012b
MB
330
331config MFD_WM8350_CONFIG_MODE_0
332 bool
333 depends on MFD_WM8350
334
335config MFD_WM8350_CONFIG_MODE_1
336 bool
337 depends on MFD_WM8350
338
339config MFD_WM8350_CONFIG_MODE_2
340 bool
341 depends on MFD_WM8350
342
343config MFD_WM8350_CONFIG_MODE_3
344 bool
345 depends on MFD_WM8350
346
ca23f8c1
MB
347config MFD_WM8351_CONFIG_MODE_0
348 bool
349 depends on MFD_WM8350
350
351config MFD_WM8351_CONFIG_MODE_1
352 bool
353 depends on MFD_WM8350
354
355config MFD_WM8351_CONFIG_MODE_2
356 bool
357 depends on MFD_WM8350
358
359config MFD_WM8351_CONFIG_MODE_3
360 bool
361 depends on MFD_WM8350
362
96920630
MB
363config MFD_WM8352_CONFIG_MODE_0
364 bool
365 depends on MFD_WM8350
366
367config MFD_WM8352_CONFIG_MODE_1
368 bool
369 depends on MFD_WM8350
370
371config MFD_WM8352_CONFIG_MODE_2
372 bool
373 depends on MFD_WM8350
374
375config MFD_WM8352_CONFIG_MODE_3
376 bool
377 depends on MFD_WM8350
378
c661a0b9 379config MFD_WM8350_I2C
ecf926bc 380 bool "Support Wolfson Microelectronics WM8350 with I2C"
c661a0b9 381 select MFD_WM8350
8d002bdc 382 depends on I2C=y && GENERIC_HARDIRQS
c661a0b9
MB
383 help
384 The WM8350 is an integrated audio and power management
385 subsystem with watchdog and RTC functionality for embedded
386 systems. This option enables core support for the WM8350 with
387 I2C as the control interface. Additional options must be
388 selected to enable support for the functionality of the chip.
389
9e501086 390config MFD_WM8994
c9fbf7e0 391 bool "Support Wolfson Microelectronics WM8994"
9e501086 392 select MFD_CORE
c9fbf7e0 393 depends on I2C=y && GENERIC_HARDIRQS
9e501086
MB
394 help
395 The WM8994 is a highly integrated hi-fi CODEC designed for
396 smartphone applicatiosn. As well as audio functionality it
397 has on board GPIO and regulator functionality which is
398 supported via the relevant subsystems. This driver provides
399 core support for the WM8994, in order to use the actual
400 functionaltiy of the device other drivers must be enabled.
401
f52046b1
BR
402config MFD_PCF50633
403 tristate "Support for NXP PCF50633"
404 depends on I2C
405 help
406 Say yes here if you have NXP PCF50633 chip on your board.
407 This core driver provides register access and IRQ handling
408 facilities, and registers devices for the various functions
409 so that function-specific drivers can bind to them.
410
8238addc 411config MFD_MC13783
8e005935
UKK
412 tristate
413
414config MFD_MC13XXX
415 tristate "Support Freescale MC13783 and MC13892"
8238addc
SH
416 depends on SPI_MASTER
417 select MFD_CORE
8e005935 418 select MFD_MC13783
8238addc 419 help
8e005935
UKK
420 Support for the Freescale (Atlas) PMIC and audio CODECs
421 MC13783 and MC13892.
8238addc
SH
422 This driver provides common support for accessing the device,
423 additional drivers must be enabled in order to use the
424 functionality of the device.
425
08c3e06a
BR
426config PCF50633_ADC
427 tristate "Support for NXP PCF50633 ADC"
428 depends on MFD_PCF50633
429 help
430 Say yes here if you want to include support for ADC in the
431 NXP PCF50633 chip.
432
6a3d119b
BR
433config PCF50633_GPIO
434 tristate "Support for NXP PCF50633 GPIO"
435 depends on MFD_PCF50633
436 help
437 Say yes here if you want to include support GPIO for pins on
438 the PCF50633 chip.
439
fa661258
MW
440config ABX500_CORE
441 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
47c16975 442 default y if ARCH_U300 || ARCH_U8500
fa661258
MW
443 help
444 Say yes here if you have the ABX500 Mixed Signal IC family
445 chips. This core driver expose register access functions.
446 Functionality specific drivers using these functions can
447 remain unchanged when IC changes. Binding of the functions to
448 actual register access is done by the IC core driver.
449
14fa5691 450config AB3100_CORE
2071db48 451 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
fa661258 452 depends on I2C=y && ABX500_CORE
8c96aefb 453 select MFD_CORE
14fa5691
LW
454 default y if ARCH_U300
455 help
456 Select this to enable the AB3100 Mixed Signal IC core
457 functionality. This connects to a AB3100 on the I2C bus
458 and expose a number of symbols needed for dependent devices
459 to read and write registers and subscribe to events from
460 this multi-functional IC. This is needed to use other features
461 of the AB3100 such as battery-backed RTC, charging control,
462 LEDs, vibrator, system power and temperature, power management
463 and ALSA sound.
464
12992dd8
LW
465config AB3100_OTP
466 tristate "ST-Ericsson AB3100 OTP functions"
467 depends on AB3100_CORE
468 default y if AB3100_CORE
469 help
470 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
471 programmable memory) support. This exposes a sysfs file to read
472 out OTP values.
473
13a09f93
DR
474config EZX_PCAP
475 bool "PCAP Support"
476 depends on GENERIC_HARDIRQS && SPI_MASTER
477 help
478 This enables the PCAP ASIC present on EZX Phones. This is
479 needed for MMC, TouchScreen, Sound, USB, etc..
480
62579266
RV
481config AB8500_CORE
482 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
d5a0514e 483 depends on GENERIC_HARDIRQS && ABX500_CORE && SPI_MASTER && ARCH_U8500
62579266 484 select MFD_CORE
0c41839e 485 help
62579266 486 Select this option to enable access to AB8500 power management
39368eda
MW
487 chip. This connects to U8500 either on the SSP/SPI bus
488 or the I2C bus via PRCMU. It also adds the irq_chip
489 parts for handling the Mixed Signal chip events.
0c41839e
SK
490 This chip embeds various other multimedia funtionalities as well.
491
39368eda
MW
492config AB8500_I2C_CORE
493 bool "AB8500 register access via PRCMU I2C"
494 depends on AB8500_CORE && UX500_SOC_DB8500
495 default y
496 help
497 This enables register access to the AB8500 chip via PRCMU I2C.
498 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
499 the I2C bus is connected to the Power Reset
500 and Mangagement Unit, PRCMU.
501
5814fc35
MW
502config AB8500_DEBUG
503 bool "Enable debug info via debugfs"
504 depends on AB8500_CORE && DEBUG_FS
505 default y if DEBUG_FS
506 help
507 Select this option if you want debug information using the debug
508 filesystem, debugfs.
509
09bcb3f3
MW
510config AB3550_CORE
511 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
512 select MFD_CORE
513 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
514 help
515 Select this to enable the AB3550 Mixed Signal IC core
516 functionality. This connects to a AB3550 on the I2C bus
517 and expose a number of symbols needed for dependent devices
518 to read and write registers and subscribe to events from
519 this multi-functional IC. This is needed to use other features
520 of the AB3550 such as battery-backed RTC, charging control,
521 LEDs, vibrator, system power and temperature, power management
522 and ALSA sound.
523
8edbede9
RR
524config MFD_TIMBERDALE
525 tristate "Support for the Timberdale FPGA"
526 select MFD_CORE
546e29b6 527 depends on PCI && GPIOLIB
8edbede9
RR
528 ---help---
529 This is the core driver for the timberdale FPGA. This device is a
530 multifunction device which exposes numerous platform devices.
531
532 The timberdale FPGA can be found on the Intel Atom development board
533 for in-vehicle infontainment, called Russellville.
e82c60ae
DT
534
535config LPC_SCH
536 tristate "Intel SCH LPC"
537 depends on PCI
538 select MFD_CORE
539 help
540 LPC bridge function of the Intel SCH provides support for
541 System Management Bus and General Purpose I/O.
542
e090d506
FF
543config MFD_RDC321X
544 tristate "Support for RDC-R321x southbridge"
545 select MFD_CORE
546 depends on PCI
547 help
548 Say yes here if you want to have support for the RDC R-321x SoC
549 southbridge which provides access to GPIOs and Watchdog using the
550 southbridge PCI device configuration space.
551
bd358132
IS
552config MFD_JANZ_CMODIO
553 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
554 select MFD_CORE
555 depends on PCI
556 help
557 This is the core driver for the Janz CMOD-IO PCI MODULbus
558 carrier board. This device is a PCI to MODULbus bridge which may
559 host many different types of MODULbus daughterboards, including
560 CAN and GPIO controllers.
561
91f4debf
LPC
562config MFD_JZ4740_ADC
563 tristate "Support for the JZ4740 SoC ADC core"
564 select MFD_CORE
565 depends on MACH_JZ4740
566 help
567 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
568 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
569
c6c19332 570config MFD_TPS6586X
c26448c4
GK
571 bool "TPS6586x Power Management chips"
572 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
c6c19332
MR
573 select MFD_CORE
574 help
575 If you say yes here you get support for the TPS6586X series of
576 Power Management chips.
577 This driver provides common support for accessing the device,
578 additional drivers must be enabled in order to use the
579 functionality of the device.
580
581 This driver can also be built as a module. If so, the module
582 will be called tps6586x.
583
375fc77b
DD
584config MFD_VX855
585 tristate "Support for VIA VX855/VX875 integrated south bridge"
586 depends on PCI
587 select MFD_CORE
588 help
589 Say yes here to enable support for various functions of the
590 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
591 and/or vx855_gpio drivers for this to do anything useful.
592
38270644 593endif # MFD_SUPPORT
b6d6454f 594
a4e137ab 595menu "Multimedia Capabilities Port drivers"
f751d50f 596 depends on ARCH_SA1100
a4e137ab
RK
597
598config MCP
599 tristate
600
5e742ad6
RK
601# Interface drivers
602config MCP_SA11X0
603 tristate "Support SA11x0 MCP interface"
604 depends on ARCH_SA1100
605 select MCP
606
05c45ca9
RK
607# Chip drivers
608config MCP_UCB1200
609 tristate "Support for UCB1200 / UCB1300"
610 depends on MCP
611
acb45439
RK
612config MCP_UCB1200_TS
613 tristate "Touchscreen interface support"
614 depends on MCP_UCB1200 && INPUT
615
a4e137ab 616endmenu