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_MCS5000 252 tristate "MELFAS MCS-5000 touchscreen" 253 depends on I2C 254 help 255 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 256 chip in your system. 257 258 If unsure, say N. 259 260 To compile this driver as a module, choose M here: the 261 module will be called mcs5000_ts. 262 263config TOUCHSCREEN_MTOUCH 264 tristate "MicroTouch serial touchscreens" 265 select SERIO 266 help 267 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 268 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 mtouch. 274 275config TOUCHSCREEN_INEXIO 276 tristate "iNexio serial touchscreens" 277 select SERIO 278 help 279 Say Y here if you have an iNexio 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 inexio. 286 287config TOUCHSCREEN_INTEL_MID 288 tristate "Intel MID platform resistive touchscreen" 289 depends on INTEL_SCU_IPC 290 help 291 Say Y here if you have a Intel MID based touchscreen in 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 intel_mid_touch. 298 299config TOUCHSCREEN_MK712 300 tristate "ICS MicroClock MK712 touchscreen" 301 help 302 Say Y here if you have the ICS MicroClock MK712 touchscreen 303 controller chip in your system. 304 305 If unsure, say N. 306 307 To compile this driver as a module, choose M here: the 308 module will be called mk712. 309 310config TOUCHSCREEN_HP600 311 tristate "HP Jornada 6xx touchscreen" 312 depends on SH_HP6XX && SH_ADC 313 help 314 Say Y here if you have a HP Jornada 620/660/680/690 and want to 315 support the built-in touchscreen. 316 317 To compile this driver as a module, choose M here: the 318 module will be called hp680_ts_input. 319 320config TOUCHSCREEN_HP7XX 321 tristate "HP Jornada 7xx touchscreen" 322 depends on SA1100_JORNADA720_SSP 323 help 324 Say Y here if you have a HP Jornada 710/720/728 and want 325 to support the built-in touchscreen. 326 327 To compile this driver as a module, choose M here: the 328 module will be called jornada720_ts. 329 330config TOUCHSCREEN_HTCPEN 331 tristate "HTC Shift X9500 touchscreen" 332 depends on ISA 333 help 334 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 335 Clio / Shangrila and want to support the built-in touchscreen. 336 337 If unsure, say N. 338 339 To compile this driver as a module, choose M here: the 340 module will be called htcpen. 341 342config TOUCHSCREEN_PENMOUNT 343 tristate "Penmount serial touchscreen" 344 select SERIO 345 help 346 Say Y here if you have a Penmount serial touchscreen connected to 347 your system. 348 349 If unsure, say N. 350 351 To compile this driver as a module, choose M here: the 352 module will be called penmount. 353 354config TOUCHSCREEN_MIGOR 355 tristate "Renesas MIGO-R touchscreen" 356 depends on SH_MIGOR && I2C 357 help 358 Say Y here to enable MIGO-R touchscreen support. 359 360 If unsure, say N. 361 362 To compile this driver as a module, choose M here: the 363 module will be called migor_ts. 364 365config TOUCHSCREEN_TNETV107X 366 tristate "TI TNETV107X touchscreen support" 367 depends on ARCH_DAVINCI_TNETV107X 368 help 369 Say Y here if you want to use the TNETV107X touchscreen. 370 371 To compile this driver as a module, choose M here: the 372 module will be called tnetv107x-ts. 373 374config TOUCHSCREEN_TOUCHRIGHT 375 tristate "Touchright serial touchscreen" 376 select SERIO 377 help 378 Say Y here if you have a Touchright serial touchscreen connected to 379 your system. 380 381 If unsure, say N. 382 383 To compile this driver as a module, choose M here: the 384 module will be called touchright. 385 386config TOUCHSCREEN_TOUCHWIN 387 tristate "Touchwin serial touchscreen" 388 select SERIO 389 help 390 Say Y here if you have a Touchwin 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 touchwin. 397 398config TOUCHSCREEN_ATMEL_TSADCC 399 tristate "Atmel Touchscreen Interface" 400 depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 401 help 402 Say Y here if you have a 4-wire touchscreen connected to the 403 ADC Controller on your Atmel SoC (such as the AT91SAM9RL). 404 405 If unsure, say N. 406 407 To compile this driver as a module, choose M here: the 408 module will be called atmel_tsadcc. 409 410config TOUCHSCREEN_UCB1400 411 tristate "Philips UCB1400 touchscreen" 412 depends on AC97_BUS 413 depends on UCB1400_CORE 414 help 415 This enables support for the Philips UCB1400 touchscreen interface. 416 The UCB1400 is an AC97 audio codec. The touchscreen interface 417 will be initialized only after the ALSA subsystem has been 418 brought up and the UCB1400 detected. You therefore have to 419 configure ALSA support as well (either built-in or modular, 420 independently of whether this driver is itself built-in or 421 modular) for this driver to work. 422 423 To compile this driver as a module, choose M here: the 424 module will be called ucb1400_ts. 425 426config TOUCHSCREEN_WM831X 427 tristate "Support for WM831x touchscreen controllers" 428 depends on MFD_WM831X 429 help 430 This enables support for the touchscreen controller on the WM831x 431 series of PMICs. 432 433 To compile this driver as a module, choose M here: the 434 module will be called wm831x-ts. 435 436config TOUCHSCREEN_WM97XX 437 tristate "Support for WM97xx AC97 touchscreen controllers" 438 depends on AC97_BUS 439 help 440 Say Y here if you have a Wolfson Microelectronics WM97xx 441 touchscreen connected to your system. Note that this option 442 only enables core driver, you will also need to select 443 support for appropriate chip below. 444 445 If unsure, say N. 446 447 To compile this driver as a module, choose M here: the 448 module will be called wm97xx-ts. 449 450config TOUCHSCREEN_WM9705 451 bool "WM9705 Touchscreen interface support" 452 depends on TOUCHSCREEN_WM97XX 453 default y 454 help 455 Say Y here to enable support for the Wolfson Microelectronics 456 WM9705 touchscreen controller. 457 458config TOUCHSCREEN_WM9712 459 bool "WM9712 Touchscreen interface support" 460 depends on TOUCHSCREEN_WM97XX 461 default y 462 help 463 Say Y here to enable support for the Wolfson Microelectronics 464 WM9712 touchscreen controller. 465 466config TOUCHSCREEN_WM9713 467 bool "WM9713 Touchscreen interface support" 468 depends on TOUCHSCREEN_WM97XX 469 default y 470 help 471 Say Y here to enable support for the Wolfson Microelectronics 472 WM9713 touchscreen controller. 473 474config TOUCHSCREEN_WM97XX_ATMEL 475 tristate "WM97xx Atmel accelerated touch" 476 depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91) 477 help 478 Say Y here for support for streaming mode with WM97xx touchscreens 479 on Atmel AT91 or AVR32 systems with an AC97C module. 480 481 Be aware that this will use channel B in the controller for 482 streaming data, this must not conflict with other AC97C drivers. 483 484 If unsure, say N. 485 486 To compile this driver as a module, choose M here: the module will 487 be called atmel-wm97xx. 488 489config TOUCHSCREEN_WM97XX_MAINSTONE 490 tristate "WM97xx Mainstone/Palm accelerated touch" 491 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 492 help 493 Say Y here for support for streaming mode with WM97xx touchscreens 494 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 495 496 If unsure, say N. 497 498 To compile this driver as a module, choose M here: the 499 module will be called mainstone-wm97xx. 500 501config TOUCHSCREEN_WM97XX_ZYLONITE 502 tristate "Zylonite accelerated touch" 503 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 504 select TOUCHSCREEN_WM9713 505 help 506 Say Y here for support for streaming mode with the touchscreen 507 on Zylonite systems. 508 509 If unsure, say N. 510 511 To compile this driver as a module, choose M here: the 512 module will be called zylonite-wm97xx. 513 514config TOUCHSCREEN_USB_COMPOSITE 515 tristate "USB Touchscreen Driver" 516 depends on USB_ARCH_HAS_HCD 517 select USB 518 help 519 USB Touchscreen driver for: 520 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 521 - PanJit TouchSet USB 522 - 3M MicroTouch USB (EX II series) 523 - ITM 524 - some other eTurboTouch 525 - Gunze AHL61 526 - DMC TSC-10/25 527 - IRTOUCHSYSTEMS/UNITOP 528 - IdealTEK URTC1000 529 - GoTop Super_Q2/GogoPen/PenPower tablets 530 - JASTEC USB Touch Controller/DigiTech DTR-02U 531 - Zytronic controllers 532 533 Have a look at <http://linux.chapter7.ch/touchkit/> for 534 a usage description and the required user-space stuff. 535 536 To compile this driver as a module, choose M here: the 537 module will be called usbtouchscreen. 538 539config TOUCHSCREEN_MC13783 540 tristate "Freescale MC13783 touchscreen input driver" 541 depends on MFD_MC13783 542 help 543 Say Y here if you have an Freescale MC13783 PMIC on your 544 board and want to use its touchscreen 545 546 If unsure, say N. 547 548 To compile this driver as a module, choose M here: the 549 module will be called mc13783_ts. 550 551config TOUCHSCREEN_USB_EGALAX 552 default y 553 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT 554 depends on TOUCHSCREEN_USB_COMPOSITE 555 556config TOUCHSCREEN_USB_PANJIT 557 default y 558 bool "PanJit device support" if EXPERT 559 depends on TOUCHSCREEN_USB_COMPOSITE 560 561config TOUCHSCREEN_USB_3M 562 default y 563 bool "3M/Microtouch EX II series device support" if EXPERT 564 depends on TOUCHSCREEN_USB_COMPOSITE 565 566config TOUCHSCREEN_USB_ITM 567 default y 568 bool "ITM device support" if EXPERT 569 depends on TOUCHSCREEN_USB_COMPOSITE 570 571config TOUCHSCREEN_USB_ETURBO 572 default y 573 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT 574 depends on TOUCHSCREEN_USB_COMPOSITE 575 576config TOUCHSCREEN_USB_GUNZE 577 default y 578 bool "Gunze AHL61 device support" if EXPERT 579 depends on TOUCHSCREEN_USB_COMPOSITE 580 581config TOUCHSCREEN_USB_DMC_TSC10 582 default y 583 bool "DMC TSC-10/25 device support" if EXPERT 584 depends on TOUCHSCREEN_USB_COMPOSITE 585 586config TOUCHSCREEN_USB_IRTOUCH 587 default y 588 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT 589 depends on TOUCHSCREEN_USB_COMPOSITE 590 591config TOUCHSCREEN_USB_IDEALTEK 592 default y 593 bool "IdealTEK URTC1000 device support" if EXPERT 594 depends on TOUCHSCREEN_USB_COMPOSITE 595 596config TOUCHSCREEN_USB_GENERAL_TOUCH 597 default y 598 bool "GeneralTouch Touchscreen device support" if EXPERT 599 depends on TOUCHSCREEN_USB_COMPOSITE 600 601config TOUCHSCREEN_USB_GOTOP 602 default y 603 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT 604 depends on TOUCHSCREEN_USB_COMPOSITE 605 606config TOUCHSCREEN_USB_JASTEC 607 default y 608 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT 609 depends on TOUCHSCREEN_USB_COMPOSITE 610 611config TOUCHSCREEN_USB_E2I 612 default y 613 bool "e2i Touchscreen controller (e.g. from Mimo 740)" 614 depends on TOUCHSCREEN_USB_COMPOSITE 615 616config TOUCHSCREEN_USB_ZYTRONIC 617 default y 618 bool "Zytronic controller" if EXPERT 619 depends on TOUCHSCREEN_USB_COMPOSITE 620 621config TOUCHSCREEN_USB_ETT_TC45USB 622 default y 623 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT 624 depends on TOUCHSCREEN_USB_COMPOSITE 625 626config TOUCHSCREEN_USB_NEXIO 627 default y 628 bool "NEXIO/iNexio device support" if EXPERT 629 depends on TOUCHSCREEN_USB_COMPOSITE 630 631config TOUCHSCREEN_TOUCHIT213 632 tristate "Sahara TouchIT-213 touchscreen" 633 select SERIO 634 help 635 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 636 637 If unsure, say N. 638 639 To compile this driver as a module, choose M here: the 640 module will be called touchit213. 641 642config TOUCHSCREEN_TSC2005 643 tristate "TSC2005 based touchscreens" 644 depends on SPI_MASTER && GENERIC_HARDIRQS 645 help 646 Say Y here if you have a TSC2005 based touchscreen. 647 648 If unsure, say N. 649 650 To compile this driver as a module, choose M here: the 651 module will be called tsc2005. 652 653config TOUCHSCREEN_TSC2007 654 tristate "TSC2007 based touchscreens" 655 depends on I2C 656 help 657 Say Y here if you have a TSC2007 based touchscreen. 658 659 If unsure, say N. 660 661 To compile this driver as a module, choose M here: the 662 module will be called tsc2007. 663 664config TOUCHSCREEN_W90X900 665 tristate "W90P910 touchscreen driver" 666 depends on HAVE_CLK 667 help 668 Say Y here if you have a W90P910 based touchscreen. 669 670 To compile this driver as a module, choose M here: the 671 module will be called w90p910_ts. 672 673config TOUCHSCREEN_PCAP 674 tristate "Motorola PCAP touchscreen" 675 depends on EZX_PCAP 676 help 677 Say Y here if you have a Motorola EZX telephone and 678 want to enable support for the built-in touchscreen. 679 680 To compile this driver as a module, choose M here: the 681 module will be called pcap_ts. 682 683config TOUCHSCREEN_ST1232 684 tristate "Sitronix ST1232 touchscreen controllers" 685 depends on I2C 686 help 687 Say Y here if you want to support Sitronix ST1232 688 touchscreen controller. 689 690 If unsure, say N. 691 692 To compile this driver as a module, choose M here: the 693 module will be called st1232_ts. 694 695config TOUCHSCREEN_STMPE 696 tristate "STMicroelectronics STMPE touchscreens" 697 depends on MFD_STMPE 698 help 699 Say Y here if you want support for STMicroelectronics 700 STMPE touchscreen controllers. 701 702 To compile this driver as a module, choose M here: the 703 module will be called stmpe-ts. 704 705config TOUCHSCREEN_TPS6507X 706 tristate "TPS6507x based touchscreens" 707 depends on I2C 708 help 709 Say Y here if you have a TPS6507x based touchscreen 710 controller. 711 712 If unsure, say N. 713 714 To compile this driver as a module, choose M here: the 715 module will be called tps6507x_ts. 716 717endif 718