2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
18 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
19 This includes the I2C driver and the core APIs _only_, you have to
20 select individual components like voltage regulators, RTC and
21 battery-charger under the corresponding menus.
24 tristate "Support for Silicon Motion SM501"
26 This is the core driver for the Silicon Motion SM501 multimedia
27 companion chip. This device is a multifunction device which may
28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
34 bool "Export GPIO via GPIO layer"
35 depends on MFD_SM501 && GPIOLIB
37 This option uses the gpio library layer to export the 64 GPIO
38 lines on the SM501. The platform data is used to supply the
39 base number for the first GPIO line to register.
42 bool "Support for Compaq ASIC3"
43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
49 config MFD_DAVINCI_VOICECODEC
53 config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
57 This driver supports the MSP430 microcontroller used on these
58 boards. MSP430 firmware manages resets and power sequencing,
59 inputs from buttons and the IR remote, LEDs, an RTC, and more.
62 tristate "TI Sequencer Serial Port support"
63 depends on ARCH_DAVINCI_TNETV107X
66 Say Y here if you want support for the Sequencer Serial Port
67 in a Texas Instruments TNETV107X SoC.
69 To compile this driver as a module, choose M here: the
70 module will be called ti-ssp.
73 bool "HTC EGPIO support"
74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
76 This driver supports the CPLD egpio chip present on
77 several HTC phones. It provides basic support for input
78 pins, output pins, and irqs.
81 tristate "HTC PASIC3 LED/DS1WM chip support"
84 This core driver provides register access for the LED/DS1WM
85 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
86 HTC Magician devices, respectively. Actual functionality is
87 handled by the leds-pasic3 and ds1wm drivers.
90 bool "HTC I2C PLD chip support"
91 depends on I2C=y && GPIOLIB
93 If you say yes here you get support for the supposed CPLD
94 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
95 This device provides input and output GPIOs through an I2C
96 interface to one or more sub-chips.
99 tristate "Philips UCB1400 Core driver"
103 This enables support for the Philips UCB1400 core functions.
104 The UCB1400 is an AC97 audio codec.
106 To compile this driver as a module, choose M here: the
107 module will be called ucb1400_core.
110 tristate "TPS61050/61052 Boost Converters"
114 select REGULATOR_FIXED_VOLTAGE
116 This option enables a driver for the TP61050/TPS61052
117 high-power "white LED driver". This boost converter is
118 sometimes used for other things than white LEDs, and
119 also contains a GPIO pin.
122 tristate "TPS6501x Power Management chips"
123 depends on I2C && GPIOLIB
124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
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.
131 This driver can also be built as a module. If so, the module
132 will be called tps65010.
135 tristate "TPS6507x Power Management / Touch Screen chips"
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.
147 tristate "TPS65217 Power Management / White LED chips"
152 If you say yes here you get support for the TPS65217 series of
153 Power Management / White LED chips.
154 These include voltage regulators, lithium ion/polymer battery
155 charger, wled and other features that are often used in portable
158 This driver can also be built as a module. If so, the module
159 will be called tps65217.
162 bool "TPS6586x Power Management chips"
163 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
166 If you say yes here you get support for the TPS6586X series of
167 Power Management chips.
168 This driver provides common support for accessing the device,
169 additional drivers must be enabled in order to use the
170 functionality of the device.
172 This driver can also be built as a module. If so, the module
173 will be called tps6586x.
176 bool "TPS65910 Power Management chip"
177 depends on I2C=y && GPIOLIB
182 if you say yes here you get support for the TPS65910 series of
183 Power Management chips.
189 config MFD_TPS65912_I2C
190 bool "TPS65912 Power Management chip with I2C"
193 depends on I2C=y && GPIOLIB
195 If you say yes here you get support for the TPS65912 series of
196 PM chips with I2C interface.
198 config MFD_TPS65912_SPI
199 bool "TPS65912 Power Management chip with SPI"
202 depends on SPI_MASTER && GPIOLIB
204 If you say yes here you get support for the TPS65912 series of
205 PM chips with SPI interface.
208 bool "Texas Instruments TWL92330/Menelaus PM chip"
209 depends on I2C=y && ARCH_OMAP2
211 If you say yes here you get support for the Texas Instruments
212 TWL92330/Menelaus Power Management chip. This include voltage
213 regulators, Dual slot memory card transceivers, real-time clock
214 and other features that are often used in portable devices like
215 cell phones and PDAs.
218 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
219 depends on I2C=y && GENERIC_HARDIRQS
222 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
223 This core driver provides register access and IRQ handling
224 facilities, and registers devices for the various functions
225 so that function-specific drivers can bind to them.
227 These multi-function chips are found on many OMAP2 and OMAP3
228 boards, providing power management, RTC, GPIO, keypad, a
229 high speed USB OTG transceiver, an audio codec (on most
230 versions) and many other features.
233 tristate "Texas Instruments TWL4030 MADC"
234 depends on TWL4030_CORE
236 This driver provides support for triton TWL4030-MADC. The
237 driver supports both RT and SW conversion methods.
239 This driver can be built as a module. If so it will be
243 bool "Support power resources on TWL4030 family chips"
244 depends on TWL4030_CORE && ARM
246 Say yes here if you want to use the power resources on the
247 TWL4030 family chips. Most of these resources are regulators,
248 which have a separate driver; some are control signals, such
249 as clock request handshaking.
251 This driver uses board-specific data to initialize the resources
252 and load scripts controlling which resources are switched off/on
253 or reset when a sleep, wakeup or warm reset event occurs.
255 config MFD_TWL4030_AUDIO
257 depends on TWL4030_CORE
262 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
263 depends on TWL4030_CORE
267 Say yes here if you want support for TWL6030 PWM.
268 This is used to control charging LED brightness.
271 bool "Support for TWL6040 audio codec"
272 depends on I2C=y && GENERIC_HARDIRQS
277 Say yes here if you want support for Texas Instruments TWL6040 audio
279 This driver provides common support for accessing the device,
280 additional drivers must be enabled in order to use the
281 functionality of the device (audio, vibra).
284 bool "Support STMicroelectronics STMPE"
285 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
288 Support for the STMPE family of I/O Expanders from
291 Currently supported devices are:
293 STMPE811: GPIO, Touchscreen
294 STMPE1601: GPIO, Keypad
295 STMPE2401: GPIO, Keypad
296 STMPE2403: GPIO, Keypad
298 This driver provides common support for accessing the device,
299 additional drivers must be enabled in order to use the functionality
300 of the device. Currently available sub drivers are:
304 Touchscreen: stmpe-ts
306 menu "STMPE Interface Drivers"
310 bool "STMPE I2C Inteface"
314 This is used to enable I2C interface of STMPE
317 bool "STMPE SPI Inteface"
318 depends on SPI_MASTER
320 This is used to enable SPI interface of STMPE
324 bool "Support Toshiba TC35892 and variants"
325 depends on I2C=y && GENERIC_HARDIRQS
328 Support for the Toshiba TC35892 and variants I/O Expander.
330 This driver provides common support for accessing the device,
331 additional drivers must be enabled in order to use the
332 functionality of the device.
339 bool "Support Toshiba T7L66XB"
340 depends on ARM && HAVE_CLK
344 Support for Toshiba Mobile IO Controller T7L66XB
347 bool "Support Toshiba TC6387XB"
348 depends on ARM && HAVE_CLK
352 Support for Toshiba Mobile IO Controller TC6387XB
355 bool "Support Toshiba TC6393XB"
356 depends on GPIOLIB && ARM && HAVE_CLK
360 Support for Toshiba Mobile IO Controller TC6393XB
363 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
366 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
367 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
368 usually found on PXA processors-based platforms. This includes
369 the I2C driver and the core APIs _only_, you have to select
370 individual components like LCD backlight, voltage regulators,
371 LEDs and battery-charger under the corresponding menus.
377 config MFD_DA9052_SPI
378 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
383 depends on SPI_MASTER=y
385 Support for the Dialog Semiconductor DA9052 PMIC
386 when controlled using SPI. This driver provides common support
387 for accessing the device, additional drivers must be enabled in
388 order to use the functionality of the device.
390 config MFD_DA9052_I2C
391 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
398 Support for the Dialog Semiconductor DA9052 PMIC
399 when controlled using I2C. This driver provides common support
400 for accessing the device, additional drivers must be enabled in
401 order to use the functionality of the device.
404 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
407 Say yes here to add support for Analog Devices AD5520 and ADP5501,
408 Multifunction Power Management IC. This includes
409 the I2C driver and the core APIs _only_, you have to select
410 individual components like LCD backlight, LEDs, GPIOs and Kepad
411 under the corresponding menus.
414 bool "Maxim Semiconductor MAX8925 PMIC Support"
415 depends on I2C=y && GENERIC_HARDIRQS
418 Say yes here to support for Maxim Semiconductor MAX8925. This is
419 a Power Management IC. This driver provies common support for
420 accessing the device, additional drivers must be enabled in order
421 to use the functionality of the device.
424 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
425 depends on I2C=y && GENERIC_HARDIRQS
428 Say yes here to support for Maxim Semiconductor MAX8997/8966.
429 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
430 MUIC controls on chip.
431 This driver provides common support for accessing the device;
432 additional drivers must be enabled in order to use the functionality
436 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
437 depends on I2C=y && GENERIC_HARDIRQS
440 Say yes here to support for Maxim Semiconductor MAX8998 and
441 National Semiconductor LP3974. This is a Power Management IC.
442 This driver provies common support for accessing the device,
443 additional drivers must be enabled in order to use the functionality
447 bool "SAMSUNG S5M Series Support"
448 depends on I2C=y && GENERIC_HARDIRQS
452 Support for the Samsung Electronics S5M MFD series.
453 This driver provies common support for accessing the device,
454 additional drivers must be enabled in order to use the functionality
458 tristate "Support Wolfson Microelectronics WM8400"
463 Support for the Wolfson Microelecronics WM8400 PMIC and audio
464 CODEC. This driver provides common support for accessing
465 the device, additional drivers must be enabled in order to use
466 the functionality of the device.
470 depends on GENERIC_HARDIRQS
472 config MFD_WM831X_I2C
473 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
477 depends on I2C=y && GENERIC_HARDIRQS
479 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
480 when controlled using I2C. This driver provides common support
481 for accessing the device, additional drivers must be enabled in
482 order to use the functionality of the device.
484 config MFD_WM831X_SPI
485 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
489 depends on SPI_MASTER && GENERIC_HARDIRQS
491 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
492 when controlled using SPI. This driver provides common support
493 for accessing the device, additional drivers must be enabled in
494 order to use the functionality of the device.
498 depends on GENERIC_HARDIRQS
500 config MFD_WM8350_CONFIG_MODE_0
502 depends on MFD_WM8350
504 config MFD_WM8350_CONFIG_MODE_1
506 depends on MFD_WM8350
508 config MFD_WM8350_CONFIG_MODE_2
510 depends on MFD_WM8350
512 config MFD_WM8350_CONFIG_MODE_3
514 depends on MFD_WM8350
516 config MFD_WM8351_CONFIG_MODE_0
518 depends on MFD_WM8350
520 config MFD_WM8351_CONFIG_MODE_1
522 depends on MFD_WM8350
524 config MFD_WM8351_CONFIG_MODE_2
526 depends on MFD_WM8350
528 config MFD_WM8351_CONFIG_MODE_3
530 depends on MFD_WM8350
532 config MFD_WM8352_CONFIG_MODE_0
534 depends on MFD_WM8350
536 config MFD_WM8352_CONFIG_MODE_1
538 depends on MFD_WM8350
540 config MFD_WM8352_CONFIG_MODE_2
542 depends on MFD_WM8350
544 config MFD_WM8352_CONFIG_MODE_3
546 depends on MFD_WM8350
548 config MFD_WM8350_I2C
549 bool "Support Wolfson Microelectronics WM8350 with I2C"
551 depends on I2C=y && GENERIC_HARDIRQS
553 The WM8350 is an integrated audio and power management
554 subsystem with watchdog and RTC functionality for embedded
555 systems. This option enables core support for the WM8350 with
556 I2C as the control interface. Additional options must be
557 selected to enable support for the functionality of the chip.
560 bool "Support Wolfson Microelectronics WM8994"
565 depends on I2C=y && GENERIC_HARDIRQS
567 The WM8994 is a highly integrated hi-fi CODEC designed for
568 smartphone applicatiosn. As well as audio functionality it
569 has on board GPIO and regulator functionality which is
570 supported via the relevant subsystems. This driver provides
571 core support for the WM8994, in order to use the actual
572 functionaltiy of the device other drivers must be enabled.
575 tristate "Support for NXP PCF50633"
579 Say yes here if you have NXP PCF50633 chip on your board.
580 This core driver provides register access and IRQ handling
581 facilities, and registers devices for the various functions
582 so that function-specific drivers can bind to them.
585 tristate "Support for NXP PCF50633 ADC"
586 depends on MFD_PCF50633
588 Say yes here if you want to include support for ADC in the
592 tristate "Support for NXP PCF50633 GPIO"
593 depends on MFD_PCF50633
595 Say yes here if you want to include support GPIO for pins on
602 tristate "Support Freescale MC13783 and MC13892"
603 depends on SPI_MASTER
607 Support for the Freescale (Atlas) PMIC and audio CODECs
609 This driver provides common support for accessing the device,
610 additional drivers must be enabled in order to use the
611 functionality of the device.
614 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
615 default y if ARCH_U300 || ARCH_U8500
617 Say yes here if you have the ABX500 Mixed Signal IC family
618 chips. This core driver expose register access functions.
619 Functionality specific drivers using these functions can
620 remain unchanged when IC changes. Binding of the functions to
621 actual register access is done by the IC core driver.
624 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
625 depends on I2C=y && ABX500_CORE
627 default y if ARCH_U300
629 Select this to enable the AB3100 Mixed Signal IC core
630 functionality. This connects to a AB3100 on the I2C bus
631 and expose a number of symbols needed for dependent devices
632 to read and write registers and subscribe to events from
633 this multi-functional IC. This is needed to use other features
634 of the AB3100 such as battery-backed RTC, charging control,
635 LEDs, vibrator, system power and temperature, power management
639 tristate "ST-Ericsson AB3100 OTP functions"
640 depends on AB3100_CORE
641 default y if AB3100_CORE
643 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
644 programmable memory) support. This exposes a sysfs file to read
649 depends on GENERIC_HARDIRQS && SPI_MASTER
651 This enables the PCAP ASIC present on EZX Phones. This is
652 needed for MMC, TouchScreen, Sound, USB, etc..
655 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
656 depends on ABX500_CORE && MFD_DB5500_PRCMU
659 Select this option to enable access to AB5500 power management
660 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
661 This chip embeds various other multimedia funtionalities as well.
664 bool "Enable debug info via debugfs"
665 depends on AB5500_CORE && DEBUG_FS
666 default y if DEBUG_FS
668 Select this option if you want debug information from the AB5500
669 using the debug filesystem, debugfs.
672 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
673 depends on GENERIC_HARDIRQS && ABX500_CORE
676 Select this option to enable access to AB8500 power management
677 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
678 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
679 the irq_chip parts for handling the Mixed Signal chip events.
680 This chip embeds various other multimedia funtionalities as well.
682 config AB8500_I2C_CORE
683 bool "AB8500 register access via PRCMU I2C"
684 depends on AB8500_CORE && MFD_DB8500_PRCMU
687 This enables register access to the AB8500 chip via PRCMU I2C.
688 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
689 the I2C bus is connected to the Power Reset
690 and Mangagement Unit, PRCMU.
693 bool "Enable debug info via debugfs"
694 depends on AB8500_CORE && DEBUG_FS
695 default y if DEBUG_FS
697 Select this option if you want debug information using the debug
701 bool "AB8500 GPADC driver"
702 depends on AB8500_CORE && REGULATOR_AB8500
705 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
707 config MFD_DB8500_PRCMU
708 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
709 depends on UX500_SOC_DB8500
712 Select this option to enable support for the DB8500 Power Reset
713 and Control Management Unit. This is basically an autonomous
714 system controller running an XP70 microprocessor, which is accessed
715 through a register map.
717 config MFD_DB5500_PRCMU
718 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
719 depends on UX500_SOC_DB5500
722 Select this option to enable support for the DB5500 Power Reset
723 and Control Management Unit. This is basically an autonomous
724 system controller running an XP70 microprocessor, which is accessed
725 through a register map.
728 tristate "Support for CS5535 and CS5536 southbridge core functions"
730 depends on PCI && X86
732 This is the core driver for CS5535/CS5536 MFD functions. This is
733 necessary for using the board's GPIO and MFGPT functionality.
735 config MFD_TIMBERDALE
736 tristate "Support for the Timberdale FPGA"
738 depends on PCI && GPIOLIB
740 This is the core driver for the timberdale FPGA. This device is a
741 multifunction device which exposes numerous platform devices.
743 The timberdale FPGA can be found on the Intel Atom development board
744 for in-vehicle infontainment, called Russellville.
747 tristate "Intel SCH LPC"
751 LPC bridge function of the Intel SCH provides support for
752 System Management Bus and General Purpose I/O.
755 tristate "Support for RDC-R321x southbridge"
759 Say yes here if you want to have support for the RDC R-321x SoC
760 southbridge which provides access to GPIOs and Watchdog using the
761 southbridge PCI device configuration space.
763 config MFD_JANZ_CMODIO
764 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
768 This is the core driver for the Janz CMOD-IO PCI MODULbus
769 carrier board. This device is a PCI to MODULbus bridge which may
770 host many different types of MODULbus daughterboards, including
771 CAN and GPIO controllers.
773 config MFD_JZ4740_ADC
774 bool "Support for the JZ4740 SoC ADC core"
776 select GENERIC_IRQ_CHIP
777 depends on MACH_JZ4740
779 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
780 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
783 tristate "Support for VIA VX855/VX875 integrated south bridge"
787 Say yes here to enable support for various functions of the
788 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
789 and/or vx855_gpio drivers for this to do anything useful.
791 config MFD_WL1273_CORE
792 tristate "Support for TI WL1273 FM radio."
797 This is the core driver for the TI WL1273 FM radio. This MFD
798 driver connects the radio-wl1273 V4L2 module and the wl1273
801 config MFD_OMAP_USB_HOST
802 bool "Support OMAP USBHS core driver"
803 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
806 This is the core driver for the OAMP EHCI and OHCI drivers.
807 This MFD driver does the required setup functionalities for
808 OMAP USB Host drivers.
813 config MFD_PM8921_CORE
814 tristate "Qualcomm PM8921 PMIC chip"
819 If you say yes to this option, support will be included for the
820 built-in PM8921 PMIC chip.
822 This is required if your board has a PM8921 and uses its features,
823 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
825 Say M here if you want to include support for PM8921 chip as a module.
826 This will build a module called "pm8921-core".
828 config MFD_PM8XXX_IRQ
829 bool "Support for Qualcomm PM8xxx IRQ features"
830 depends on MFD_PM8XXX
831 default y if MFD_PM8XXX
833 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
835 This is required to use certain other PM 8xxx features, such as GPIO
838 config TPS65911_COMPARATOR
842 bool "TPS65090 Power Management chips"
843 depends on I2C=y && GENERIC_HARDIRQS
847 If you say yes here you get support for the TPS65090 series of
848 Power Management chips.
849 This driver provides common support for accessing the device,
850 additional drivers must be enabled in order to use the
851 functionality of the device.
853 config MFD_AAT2870_CORE
854 bool "Support for the AnalogicTech AAT2870"
856 depends on I2C=y && GPIOLIB
858 If you say yes here you get support for the AAT2870.
859 This driver provides common support for accessing the device,
860 additional drivers must be enabled in order to use the
861 functionality of the device.
863 config MFD_INTEL_MSIC
864 bool "Support for Intel MSIC"
865 depends on INTEL_SCU_IPC
868 Select this option to enable access to Intel MSIC (Avatele
869 Passage) chip. This chip embeds audio, battery, GPIO, etc.
870 devices used in Intel Medfield platforms.
873 bool "Ricoh RC5T583 Power Management system device"
874 depends on I2C=y && GENERIC_HARDIRQS
878 Select this option to get support for the RICOH583 Power
879 Management system device.
880 This driver provides common support for accessing the device
881 through i2c interface. The device supports multiple sub-devices
882 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
883 Additional drivers must be enabled in order to use the
884 different functionality of the device.
887 bool "Support for Freescale i.MX on-chip ANATOP controller"
890 Select this option to enable Freescale i.MX on-chip ANATOP
891 MFD controller. This controller embeds regulator and
892 thermal devices for Freescale i.MX platforms.
897 menu "Multimedia Capabilities Port drivers"
898 depends on ARCH_SA1100
905 tristate "Support SA11x0 MCP interface"
906 depends on ARCH_SA1100
911 bool "Support for UCB1200 / UCB1300"
912 depends on MCP_SA11X0
915 config MCP_UCB1200_TS
916 tristate "Touchscreen interface support"
917 depends on MCP_UCB1200 && INPUT