1# 2# Touchscreen driver configuration 3# 4menuconfig INPUT_TOUCHSCREEN 5 bool "Touchscreens" 6 help 7 Say Y here, and a list of supported touchscreens will be displayed. 8 This option doesn't affect the kernel. 9 10 If unsure, say Y. 11 12if INPUT_TOUCHSCREEN 13 14config TOUCHSCREEN_88PM860X 15 tristate "Marvell 88PM860x touchscreen" 16 depends on MFD_88PM860X 17 help 18 Say Y here if you have a 88PM860x PMIC and want to enable 19 support for the built-in touchscreen. 20 21 If unsure, say N. 22 23 To compile this driver as a module, choose M here: the 24 module will be called 88pm860x-ts. 25 26config TOUCHSCREEN_ADS7846 27 tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens" 28 depends on SPI_MASTER 29 depends on HWMON = n || HWMON 30 help 31 Say Y here if you have a touchscreen interface using the 32 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller, 33 and your board-specific setup code includes that in its 34 table of SPI devices. 35 36 If HWMON is selected, and the driver is told the reference voltage 37 on your board, you will also get hwmon interfaces for the voltage 38 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip. 39 40 If unsure, say N (but it's safe to say "Y"). 41 42 To compile this driver as a module, choose M here: the 43 module will be called ads7846. 44 45config TOUCHSCREEN_AD7877 46 tristate "AD7877 based touchscreens" 47 depends on SPI_MASTER 48 help 49 Say Y here if you have a touchscreen interface using the 50 AD7877 controller, and your board-specific initialization 51 code includes that in its table of SPI devices. 52 53 If unsure, say N (but it's safe to say "Y"). 54 55 To compile this driver as a module, choose M here: the 56 module will be called ad7877. 57 58config TOUCHSCREEN_AD7879 59 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface" 60 help 61 Say Y here if you want to support a touchscreen interface using 62 the AD7879-1/AD7889-1 controller. 63 64 You should select a bus connection too. 65 66 To compile this driver as a module, choose M here: the 67 module will be called ad7879. 68 69config TOUCHSCREEN_AD7879_I2C 70 tristate "support I2C bus connection" 71 depends on TOUCHSCREEN_AD7879 && I2C 72 help 73 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus. 74 75 To compile this driver as a module, choose M here: the 76 module will be called ad7879-i2c. 77 78config TOUCHSCREEN_AD7879_SPI 79 tristate "support SPI bus connection" 80 depends on TOUCHSCREEN_AD7879 && SPI_MASTER 81 help 82 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus. 83 84 If unsure, say N (but it's safe to say "Y"). 85 86 To compile this driver as a module, choose M here: the 87 module will be called ad7879-spi. 88 89config TOUCHSCREEN_ATMEL_MXT 90 tristate "Atmel mXT I2C Touchscreen" 91 depends on I2C 92 help 93 Say Y here if you have Atmel mXT series I2C touchscreen, 94 such as AT42QT602240/ATMXT224, connected to your system. 95 96 If unsure, say N. 97 98 To compile this driver as a module, choose M here: the 99 module will be called atmel_mxt_ts. 100 101config TOUCHSCREEN_BITSY 102 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" 103 depends on SA1100_BITSY 104 select SERIO 105 help 106 Say Y here if you have the h3600 (Bitsy) touchscreen. 107 108 If unsure, say N. 109 110 To compile this driver as a module, choose M here: the 111 module will be called h3600_ts_input. 112 113config TOUCHSCREEN_BU21013 114 tristate "BU21013 based touch panel controllers" 115 depends on I2C 116 help 117 Say Y here if you have a bu21013 touchscreen connected to 118 your system. 119 120 If unsure, say N. 121 122 To compile this driver as a module, choose M here: the 123 module will be called bu21013_ts. 124 125config TOUCHSCREEN_CY8CTMG110 126 tristate "cy8ctmg110 touchscreen" 127 depends on I2C 128 depends on GPIOLIB 129 130 help 131 Say Y here if you have a cy8ctmg110 capacitive touchscreen on 132 an AAVA device. 133 134 If unsure, say N. 135 136 To compile this driver as a module, choose M here: the 137 module will be called cy8ctmg110_ts. 138 139config TOUCHSCREEN_DA9034 140 tristate "Touchscreen support for Dialog Semiconductor DA9034" 141 depends on PMIC_DA903X 142 default y 143 help 144 Say Y here to enable the support for the touchscreen found 145 on Dialog Semiconductor DA9034 PMIC. 146 147config TOUCHSCREEN_DYNAPRO 148 tristate "Dynapro serial touchscreen" 149 select SERIO 150 help 151 Say Y here if you have a Dynapro serial touchscreen connected to 152 your system. 153 154 If unsure, say N. 155 156 To compile this driver as a module, choose M here: the 157 module will be called dynapro. 158 159config TOUCHSCREEN_HAMPSHIRE 160 tristate "Hampshire serial touchscreen" 161 select SERIO 162 help 163 Say Y here if you have a Hampshire serial touchscreen connected to 164 your system. 165 166 If unsure, say N. 167 168 To compile this driver as a module, choose M here: the 169 module will be called hampshire. 170 171config TOUCHSCREEN_EETI 172 tristate "EETI touchscreen panel support" 173 depends on I2C 174 help 175 Say Y here to enable support for I2C connected EETI touch panels. 176 177 To compile this driver as a module, choose M here: the 178 module will be called eeti_ts. 179 180config TOUCHSCREEN_FUJITSU 181 tristate "Fujitsu serial touchscreen" 182 select SERIO 183 help 184 Say Y here if you have the Fujitsu touchscreen (such as one 185 installed in Lifebook P series laptop) connected to your 186 system. 187 188 If unsure, say N. 189 190 To compile this driver as a module, choose M here: the 191 module will be called fujitsu-ts. 192 193config TOUCHSCREEN_S3C2410 194 tristate "Samsung S3C2410/generic touchscreen input driver" 195 depends on ARCH_S3C2410 || SAMSUNG_DEV_TS 196 select S3C_ADC 197 help 198 Say Y here if you have the s3c2410 touchscreen. 199 200 If unsure, say N. 201 202 To compile this driver as a module, choose M here: the 203 module will be called s3c2410_ts. 204 205config TOUCHSCREEN_GUNZE 206 tristate "Gunze AHL-51S touchscreen" 207 select SERIO 208 help 209 Say Y here if you have the Gunze AHL-51 touchscreen connected to 210 your system. 211 212 If unsure, say N. 213 214 To compile this driver as a module, choose M here: the 215 module will be called gunze. 216 217config TOUCHSCREEN_ELO 218 tristate "Elo serial touchscreens" 219 select SERIO 220 help 221 Say Y here if you have an Elo serial touchscreen connected to 222 your system. 223 224 If unsure, say N. 225 226 To compile this driver as a module, choose M here: the 227 module will be called elo. 228 229config TOUCHSCREEN_WACOM_W8001 230 tristate "Wacom W8001 penabled serial touchscreen" 231 select SERIO 232 help 233 Say Y here if you have an Wacom W8001 penabled serial touchscreen 234 connected to your system. 235 236 If unsure, say N. 237 238 To compile this driver as a module, choose M here: the 239 module will be called wacom_w8001. 240 241config TOUCHSCREEN_LPC32XX 242 tristate "LPC32XX touchscreen controller" 243 depends on ARCH_LPC32XX 244 help 245 Say Y here if you have a LPC32XX device and want 246 to support the built-in touchscreen. 247 248 To compile this driver as a module, choose M here: the 249 module will be called lpc32xx_ts. 250 251config TOUCHSCREEN_MAX11801 252 tristate "MAX11801 based touchscreens" 253 depends on I2C 254 help 255 Say Y here if you have a MAX11801 based touchscreen 256 controller. 257 258 If unsure, say N. 259 260 To compile this driver as a module, choose M here: the 261 module will be called max11801_ts. 262 263config TOUCHSCREEN_MCS5000 264 tristate "MELFAS MCS-5000 touchscreen" 265 depends on I2C 266 help 267 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 268 chip in your system. 269 270 If unsure, say N. 271 272 To compile this driver as a module, choose M here: the 273 module will be called mcs5000_ts. 274 275config TOUCHSCREEN_MTOUCH 276 tristate "MicroTouch serial touchscreens" 277 select SERIO 278 help 279 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 280 your system. 281 282 If unsure, say N. 283 284 To compile this driver as a module, choose M here: the 285 module will be called mtouch. 286 287config TOUCHSCREEN_INEXIO 288 tristate "iNexio serial touchscreens" 289 select SERIO 290 help 291 Say Y here if you have an iNexio serial touchscreen connected to 292 your system. 293 294 If unsure, say N. 295 296 To compile this driver as a module, choose M here: the 297 module will be called inexio. 298 299config TOUCHSCREEN_INTEL_MID 300 tristate "Intel MID platform resistive touchscreen" 301 depends on INTEL_SCU_IPC 302 help 303 Say Y here if you have a Intel MID based touchscreen in 304 your system. 305 306 If unsure, say N. 307 308 To compile this driver as a module, choose M here: the 309 module will be called intel_mid_touch. 310 311config TOUCHSCREEN_MK712 312 tristate "ICS MicroClock MK712 touchscreen" 313 help 314 Say Y here if you have the ICS MicroClock MK712 touchscreen 315 controller chip in your system. 316 317 If unsure, say N. 318 319 To compile this driver as a module, choose M here: the 320 module will be called mk712. 321 322config TOUCHSCREEN_HP600 323 tristate "HP Jornada 6xx touchscreen" 324 depends on SH_HP6XX && SH_ADC 325 help 326 Say Y here if you have a HP Jornada 620/660/680/690 and want to 327 support the built-in touchscreen. 328 329 To compile this driver as a module, choose M here: the 330 module will be called hp680_ts_input. 331 332config TOUCHSCREEN_HP7XX 333 tristate "HP Jornada 7xx touchscreen" 334 depends on SA1100_JORNADA720_SSP 335 help 336 Say Y here if you have a HP Jornada 710/720/728 and want 337 to support the built-in touchscreen. 338 339 To compile this driver as a module, choose M here: the 340 module will be called jornada720_ts. 341 342config TOUCHSCREEN_HTCPEN 343 tristate "HTC Shift X9500 touchscreen" 344 depends on ISA 345 help 346 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 347 Clio / Shangrila and want to support the built-in touchscreen. 348 349 If unsure, say N. 350 351 To compile this driver as a module, choose M here: the 352 module will be called htcpen. 353 354config TOUCHSCREEN_PENMOUNT 355 tristate "Penmount serial touchscreen" 356 select SERIO 357 help 358 Say Y here if you have a Penmount serial touchscreen connected to 359 your system. 360 361 If unsure, say N. 362 363 To compile this driver as a module, choose M here: the 364 module will be called penmount. 365 366config TOUCHSCREEN_MIGOR 367 tristate "Renesas MIGO-R touchscreen" 368 depends on SH_MIGOR && I2C 369 help 370 Say Y here to enable MIGO-R touchscreen support. 371 372 If unsure, say N. 373 374 To compile this driver as a module, choose M here: the 375 module will be called migor_ts. 376 377config TOUCHSCREEN_TNETV107X 378 tristate "TI TNETV107X touchscreen support" 379 depends on ARCH_DAVINCI_TNETV107X 380 help 381 Say Y here if you want to use the TNETV107X touchscreen. 382 383 To compile this driver as a module, choose M here: the 384 module will be called tnetv107x-ts. 385 386config TOUCHSCREEN_TOUCHRIGHT 387 tristate "Touchright serial touchscreen" 388 select SERIO 389 help 390 Say Y here if you have a Touchright serial touchscreen connected to 391 your system. 392 393 If unsure, say N. 394 395 To compile this driver as a module, choose M here: the 396 module will be called touchright. 397 398config TOUCHSCREEN_TOUCHWIN 399 tristate "Touchwin serial touchscreen" 400 select SERIO 401 help 402 Say Y here if you have a Touchwin serial touchscreen connected to 403 your system. 404 405 If unsure, say N. 406 407 To compile this driver as a module, choose M here: the 408 module will be called touchwin. 409 410config TOUCHSCREEN_ATMEL_TSADCC 411 tristate "Atmel Touchscreen Interface" 412 depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 413 help 414 Say Y here if you have a 4-wire touchscreen connected to the 415 ADC Controller on your Atmel SoC (such as the AT91SAM9RL). 416 417 If unsure, say N. 418 419 To compile this driver as a module, choose M here: the 420 module will be called atmel_tsadcc. 421 422config TOUCHSCREEN_UCB1400 423 tristate "Philips UCB1400 touchscreen" 424 depends on AC97_BUS 425 depends on UCB1400_CORE 426 help 427 This enables support for the Philips UCB1400 touchscreen interface. 428 The UCB1400 is an AC97 audio codec. The touchscreen interface 429 will be initialized only after the ALSA subsystem has been 430 brought up and the UCB1400 detected. You therefore have to 431 configure ALSA support as well (either built-in or modular, 432 independently of whether this driver is itself built-in or 433 modular) for this driver to work. 434 435 To compile this driver as a module, choose M here: the 436 module will be called ucb1400_ts. 437 438config TOUCHSCREEN_WM831X 439 tristate "Support for WM831x touchscreen controllers" 440 depends on MFD_WM831X 441 help 442 This enables support for the touchscreen controller on the WM831x 443 series of PMICs. 444 445 To compile this driver as a module, choose M here: the 446 module will be called wm831x-ts. 447 448config TOUCHSCREEN_WM97XX 449 tristate "Support for WM97xx AC97 touchscreen controllers" 450 depends on AC97_BUS 451 help 452 Say Y here if you have a Wolfson Microelectronics WM97xx 453 touchscreen connected to your system. Note that this option 454 only enables core driver, you will also need to select 455 support for appropriate chip below. 456 457 If unsure, say N. 458 459 To compile this driver as a module, choose M here: the 460 module will be called wm97xx-ts. 461 462config TOUCHSCREEN_WM9705 463 bool "WM9705 Touchscreen interface support" 464 depends on TOUCHSCREEN_WM97XX 465 default y 466 help 467 Say Y here to enable support for the Wolfson Microelectronics 468 WM9705 touchscreen controller. 469 470config TOUCHSCREEN_WM9712 471 bool "WM9712 Touchscreen interface support" 472 depends on TOUCHSCREEN_WM97XX 473 default y 474 help 475 Say Y here to enable support for the Wolfson Microelectronics 476 WM9712 touchscreen controller. 477 478config TOUCHSCREEN_WM9713 479 bool "WM9713 Touchscreen interface support" 480 depends on TOUCHSCREEN_WM97XX 481 default y 482 help 483 Say Y here to enable support for the Wolfson Microelectronics 484 WM9713 touchscreen controller. 485 486config TOUCHSCREEN_WM97XX_ATMEL 487 tristate "WM97xx Atmel accelerated touch" 488 depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91) 489 help 490 Say Y here for support for streaming mode with WM97xx touchscreens 491 on Atmel AT91 or AVR32 systems with an AC97C module. 492 493 Be aware that this will use channel B in the controller for 494 streaming data, this must not conflict with other AC97C drivers. 495 496 If unsure, say N. 497 498 To compile this driver as a module, choose M here: the module will 499 be called atmel-wm97xx. 500 501config TOUCHSCREEN_WM97XX_MAINSTONE 502 tristate "WM97xx Mainstone/Palm accelerated touch" 503 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 504 help 505 Say Y here for support for streaming mode with WM97xx touchscreens 506 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 507 508 If unsure, say N. 509 510 To compile this driver as a module, choose M here: the 511 module will be called mainstone-wm97xx. 512 513config TOUCHSCREEN_WM97XX_ZYLONITE 514 tristate "Zylonite accelerated touch" 515 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 516 select TOUCHSCREEN_WM9713 517 help 518 Say Y here for support for streaming mode with the touchscreen 519 on Zylonite systems. 520 521 If unsure, say N. 522 523 To compile this driver as a module, choose M here: the 524 module will be called zylonite-wm97xx. 525 526config TOUCHSCREEN_USB_COMPOSITE 527 tristate "USB Touchscreen Driver" 528 depends on USB_ARCH_HAS_HCD 529 select USB 530 help 531 USB Touchscreen driver for: 532 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 533 - PanJit TouchSet USB 534 - 3M MicroTouch USB (EX II series) 535 - ITM 536 - some other eTurboTouch 537 - Gunze AHL61 538 - DMC TSC-10/25 539 - IRTOUCHSYSTEMS/UNITOP 540 - IdealTEK URTC1000 541 - GoTop Super_Q2/GogoPen/PenPower tablets 542 - JASTEC USB Touch Controller/DigiTech DTR-02U 543 - Zytronic controllers 544 545 Have a look at <http://linux.chapter7.ch/touchkit/> for 546 a usage description and the required user-space stuff. 547 548 To compile this driver as a module, choose M here: the 549 module will be called usbtouchscreen. 550 551config TOUCHSCREEN_MC13783 552 tristate "Freescale MC13783 touchscreen input driver" 553 depends on MFD_MC13783 554 help 555 Say Y here if you have an Freescale MC13783 PMIC on your 556 board and want to use its touchscreen 557 558 If unsure, say N. 559 560 To compile this driver as a module, choose M here: the 561 module will be called mc13783_ts. 562 563config TOUCHSCREEN_USB_EGALAX 564 default y 565 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT 566 depends on TOUCHSCREEN_USB_COMPOSITE 567 568config TOUCHSCREEN_USB_PANJIT 569 default y 570 bool "PanJit device support" if EXPERT 571 depends on TOUCHSCREEN_USB_COMPOSITE 572 573config TOUCHSCREEN_USB_3M 574 default y 575 bool "3M/Microtouch EX II series device support" if EXPERT 576 depends on TOUCHSCREEN_USB_COMPOSITE 577 578config TOUCHSCREEN_USB_ITM 579 default y 580 bool "ITM device support" if EXPERT 581 depends on TOUCHSCREEN_USB_COMPOSITE 582 583config TOUCHSCREEN_USB_ETURBO 584 default y 585 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT 586 depends on TOUCHSCREEN_USB_COMPOSITE 587 588config TOUCHSCREEN_USB_GUNZE 589 default y 590 bool "Gunze AHL61 device support" if EXPERT 591 depends on TOUCHSCREEN_USB_COMPOSITE 592 593config TOUCHSCREEN_USB_DMC_TSC10 594 default y 595 bool "DMC TSC-10/25 device support" if EXPERT 596 depends on TOUCHSCREEN_USB_COMPOSITE 597 598config TOUCHSCREEN_USB_IRTOUCH 599 default y 600 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT 601 depends on TOUCHSCREEN_USB_COMPOSITE 602 603config TOUCHSCREEN_USB_IDEALTEK 604 default y 605 bool "IdealTEK URTC1000 device support" if EXPERT 606 depends on TOUCHSCREEN_USB_COMPOSITE 607 608config TOUCHSCREEN_USB_GENERAL_TOUCH 609 default y 610 bool "GeneralTouch Touchscreen device support" if EXPERT 611 depends on TOUCHSCREEN_USB_COMPOSITE 612 613config TOUCHSCREEN_USB_GOTOP 614 default y 615 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT 616 depends on TOUCHSCREEN_USB_COMPOSITE 617 618config TOUCHSCREEN_USB_JASTEC 619 default y 620 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT 621 depends on TOUCHSCREEN_USB_COMPOSITE 622 623config TOUCHSCREEN_USB_E2I 624 default y 625 bool "e2i Touchscreen controller (e.g. from Mimo 740)" 626 depends on TOUCHSCREEN_USB_COMPOSITE 627 628config TOUCHSCREEN_USB_ZYTRONIC 629 default y 630 bool "Zytronic controller" if EXPERT 631 depends on TOUCHSCREEN_USB_COMPOSITE 632 633config TOUCHSCREEN_USB_ETT_TC45USB 634 default y 635 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT 636 depends on TOUCHSCREEN_USB_COMPOSITE 637 638config TOUCHSCREEN_USB_NEXIO 639 default y 640 bool "NEXIO/iNexio device support" if EXPERT 641 depends on TOUCHSCREEN_USB_COMPOSITE 642 643config TOUCHSCREEN_TOUCHIT213 644 tristate "Sahara TouchIT-213 touchscreen" 645 select SERIO 646 help 647 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 648 649 If unsure, say N. 650 651 To compile this driver as a module, choose M here: the 652 module will be called touchit213. 653 654config TOUCHSCREEN_TSC_SERIO 655 tristate "TSC-10/25/40 serial touchscreen support" 656 select SERIO 657 help 658 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected 659 to your system. 660 661 If unsure, say N. 662 663 To compile this driver as a module, choose M here: the 664 module will be called tsc40. 665 666config TOUCHSCREEN_TSC2005 667 tristate "TSC2005 based touchscreens" 668 depends on SPI_MASTER && GENERIC_HARDIRQS 669 help 670 Say Y here if you have a TSC2005 based touchscreen. 671 672 If unsure, say N. 673 674 To compile this driver as a module, choose M here: the 675 module will be called tsc2005. 676 677config TOUCHSCREEN_TSC2007 678 tristate "TSC2007 based touchscreens" 679 depends on I2C 680 help 681 Say Y here if you have a TSC2007 based touchscreen. 682 683 If unsure, say N. 684 685 To compile this driver as a module, choose M here: the 686 module will be called tsc2007. 687 688config TOUCHSCREEN_W90X900 689 tristate "W90P910 touchscreen driver" 690 depends on HAVE_CLK 691 help 692 Say Y here if you have a W90P910 based touchscreen. 693 694 To compile this driver as a module, choose M here: the 695 module will be called w90p910_ts. 696 697config TOUCHSCREEN_PCAP 698 tristate "Motorola PCAP touchscreen" 699 depends on EZX_PCAP 700 help 701 Say Y here if you have a Motorola EZX telephone and 702 want to enable support for the built-in touchscreen. 703 704 To compile this driver as a module, choose M here: the 705 module will be called pcap_ts. 706 707config TOUCHSCREEN_ST1232 708 tristate "Sitronix ST1232 touchscreen controllers" 709 depends on I2C 710 help 711 Say Y here if you want to support Sitronix ST1232 712 touchscreen controller. 713 714 If unsure, say N. 715 716 To compile this driver as a module, choose M here: the 717 module will be called st1232_ts. 718 719config TOUCHSCREEN_STMPE 720 tristate "STMicroelectronics STMPE touchscreens" 721 depends on MFD_STMPE 722 help 723 Say Y here if you want support for STMicroelectronics 724 STMPE touchscreen controllers. 725 726 To compile this driver as a module, choose M here: the 727 module will be called stmpe-ts. 728 729config TOUCHSCREEN_TPS6507X 730 tristate "TPS6507x based touchscreens" 731 depends on I2C 732 help 733 Say Y here if you have a TPS6507x based touchscreen 734 controller. 735 736 If unsure, say N. 737 738 To compile this driver as a module, choose M here: the 739 module will be called tps6507x_ts. 740 741endif 742