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