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_ADS7846 15 tristate "ADS7846/TSC2046 and ADS7843 based touchscreens" 16 depends on SPI_MASTER 17 depends on HWMON = n || HWMON 18 help 19 Say Y here if you have a touchscreen interface using the 20 ADS7846/TSC2046 or ADS7843 controller, and your board-specific 21 setup code includes that in its table of SPI devices. 22 23 If HWMON is selected, and the driver is told the reference voltage 24 on your board, you will also get hwmon interfaces for the voltage 25 (and on ads7846/tsc2046, temperature) sensors of this chip. 26 27 If unsure, say N (but it's safe to say "Y"). 28 29 To compile this driver as a module, choose M here: the 30 module will be called ads7846. 31 32config TOUCHSCREEN_AD7877 33 tristate "AD7877 based touchscreens" 34 depends on SPI_MASTER 35 help 36 Say Y here if you have a touchscreen interface using the 37 AD7877 controller, and your board-specific initialization 38 code includes that in its table of SPI devices. 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 ad7877. 44 45config TOUCHSCREEN_AD7879_I2C 46 tristate "AD7879 based touchscreens: AD7879-1 I2C Interface" 47 depends on I2C 48 select TOUCHSCREEN_AD7879 49 help 50 Say Y here if you have a touchscreen interface using the 51 AD7879-1/AD7889-1 controller, and your board-specific 52 initialization code includes that in its table of I2C devices. 53 54 If unsure, say N (but it's safe to say "Y"). 55 56 To compile this driver as a module, choose M here: the 57 module will be called ad7879. 58 59config TOUCHSCREEN_AD7879_SPI 60 tristate "AD7879 based touchscreens: AD7879 SPI Interface" 61 depends on SPI_MASTER && TOUCHSCREEN_AD7879_I2C = n 62 select TOUCHSCREEN_AD7879 63 help 64 Say Y here if you have a touchscreen interface using the 65 AD7879/AD7889 controller, and your board-specific initialization 66 code includes that in its table of SPI devices. 67 68 If unsure, say N (but it's safe to say "Y"). 69 70 To compile this driver as a module, choose M here: the 71 module will be called ad7879. 72 73config TOUCHSCREEN_AD7879 74 tristate 75 default n 76 77config TOUCHSCREEN_BITSY 78 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" 79 depends on SA1100_BITSY 80 select SERIO 81 help 82 Say Y here if you have the h3600 (Bitsy) touchscreen. 83 84 If unsure, say N. 85 86 To compile this driver as a module, choose M here: the 87 module will be called h3600_ts_input. 88 89config TOUCHSCREEN_CORGI 90 tristate "SharpSL (Corgi and Spitz series) touchscreen driver (DEPRECATED)" 91 depends on PXA_SHARPSL 92 select CORGI_SSP_DEPRECATED 93 help 94 Say Y here to enable the driver for the touchscreen on the 95 Sharp SL-C7xx and SL-Cxx00 series of PDAs. 96 97 If unsure, say N. 98 99 To compile this driver as a module, choose M here: the 100 module will be called corgi_ts. 101 102 NOTE: this driver is deprecated, try enable SPI and generic 103 ADS7846-based touchscreen driver. 104 105config TOUCHSCREEN_DA9034 106 tristate "Touchscreen support for Dialog Semiconductor DA9034" 107 depends on PMIC_DA903X 108 default y 109 help 110 Say Y here to enable the support for the touchscreen found 111 on Dialog Semiconductor DA9034 PMIC. 112 113config TOUCHSCREEN_DYNAPRO 114 tristate "Dynapro serial touchscreen" 115 select SERIO 116 help 117 Say Y here if you have a Dynapro serial 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 dynapro. 124 125config TOUCHSCREEN_EETI 126 tristate "EETI touchscreen panel support" 127 depends on I2C 128 help 129 Say Y here to enable support for I2C connected EETI touch panels. 130 131 To compile this driver as a module, choose M here: the 132 module will be called eeti_ts. 133 134config TOUCHSCREEN_FUJITSU 135 tristate "Fujitsu serial touchscreen" 136 select SERIO 137 help 138 Say Y here if you have the Fujitsu touchscreen (such as one 139 installed in Lifebook P series laptop) connected to your 140 system. 141 142 If unsure, say N. 143 144 To compile this driver as a module, choose M here: the 145 module will be called fujitsu-ts. 146 147config TOUCHSCREEN_S3C2410 148 tristate "Samsung S3C2410 touchscreen input driver" 149 depends on ARCH_S3C2410 150 select S3C24XX_ADC 151 help 152 Say Y here if you have the s3c2410 touchscreen. 153 154 If unsure, say N. 155 156 To compile this driver as a module, choose M here: the 157 module will be called s3c2410_ts. 158 159config TOUCHSCREEN_GUNZE 160 tristate "Gunze AHL-51S touchscreen" 161 select SERIO 162 help 163 Say Y here if you have the Gunze AHL-51 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 gunze. 170 171config TOUCHSCREEN_ELO 172 tristate "Elo serial touchscreens" 173 select SERIO 174 help 175 Say Y here if you have an Elo serial touchscreen connected to 176 your system. 177 178 If unsure, say N. 179 180 To compile this driver as a module, choose M here: the 181 module will be called elo. 182 183config TOUCHSCREEN_WACOM_W8001 184 tristate "Wacom W8001 penabled serial touchscreen" 185 select SERIO 186 help 187 Say Y here if you have an Wacom W8001 penabled serial touchscreen 188 connected to your system. 189 190 If unsure, say N. 191 192 To compile this driver as a module, choose M here: the 193 module will be called wacom_w8001. 194 195config TOUCHSCREEN_MCS5000 196 tristate "MELFAS MCS-5000 touchscreen" 197 depends on I2C 198 help 199 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 200 chip in your system. 201 202 If unsure, say N. 203 204 To compile this driver as a module, choose M here: the 205 module will be called mcs5000_ts. 206 207config TOUCHSCREEN_MTOUCH 208 tristate "MicroTouch serial touchscreens" 209 select SERIO 210 help 211 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 212 your system. 213 214 If unsure, say N. 215 216 To compile this driver as a module, choose M here: the 217 module will be called mtouch. 218 219config TOUCHSCREEN_INEXIO 220 tristate "iNexio serial touchscreens" 221 select SERIO 222 help 223 Say Y here if you have an iNexio serial touchscreen connected to 224 your system. 225 226 If unsure, say N. 227 228 To compile this driver as a module, choose M here: the 229 module will be called inexio. 230 231config TOUCHSCREEN_MK712 232 tristate "ICS MicroClock MK712 touchscreen" 233 help 234 Say Y here if you have the ICS MicroClock MK712 touchscreen 235 controller chip in your system. 236 237 If unsure, say N. 238 239 To compile this driver as a module, choose M here: the 240 module will be called mk712. 241 242config TOUCHSCREEN_HP600 243 tristate "HP Jornada 6xx touchscreen" 244 depends on SH_HP6XX && SH_ADC 245 help 246 Say Y here if you have a HP Jornada 620/660/680/690 and want to 247 support the built-in touchscreen. 248 249 To compile this driver as a module, choose M here: the 250 module will be called hp680_ts_input. 251 252config TOUCHSCREEN_HP7XX 253 tristate "HP Jornada 7xx touchscreen" 254 depends on SA1100_JORNADA720_SSP 255 help 256 Say Y here if you have a HP Jornada 710/720/728 and want 257 to support the built-in touchscreen. 258 259 To compile this driver as a module, choose M here: the 260 module will be called jornada720_ts. 261 262config TOUCHSCREEN_HTCPEN 263 tristate "HTC Shift X9500 touchscreen" 264 depends on ISA 265 help 266 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 267 Clio / Shangrila and want to support the built-in touchscreen. 268 269 If unsure, say N. 270 271 To compile this driver as a module, choose M here: the 272 module will be called htcpen. 273 274config TOUCHSCREEN_PENMOUNT 275 tristate "Penmount serial touchscreen" 276 select SERIO 277 help 278 Say Y here if you have a Penmount serial touchscreen connected to 279 your system. 280 281 If unsure, say N. 282 283 To compile this driver as a module, choose M here: the 284 module will be called penmount. 285 286config TOUCHSCREEN_MIGOR 287 tristate "Renesas MIGO-R touchscreen" 288 depends on SH_MIGOR && I2C 289 help 290 Say Y here to enable MIGO-R touchscreen support. 291 292 If unsure, say N. 293 294 To compile this driver as a module, choose M here: the 295 module will be called migor_ts. 296 297config TOUCHSCREEN_TOUCHRIGHT 298 tristate "Touchright serial touchscreen" 299 select SERIO 300 help 301 Say Y here if you have a Touchright serial touchscreen connected to 302 your system. 303 304 If unsure, say N. 305 306 To compile this driver as a module, choose M here: the 307 module will be called touchright. 308 309config TOUCHSCREEN_TOUCHWIN 310 tristate "Touchwin serial touchscreen" 311 select SERIO 312 help 313 Say Y here if you have a Touchwin serial touchscreen connected to 314 your system. 315 316 If unsure, say N. 317 318 To compile this driver as a module, choose M here: the 319 module will be called touchwin. 320 321config TOUCHSCREEN_ATMEL_TSADCC 322 tristate "Atmel Touchscreen Interface" 323 depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 324 help 325 Say Y here if you have a 4-wire touchscreen connected to the 326 ADC Controller on your Atmel SoC (such as the AT91SAM9RL). 327 328 If unsure, say N. 329 330 To compile this driver as a module, choose M here: the 331 module will be called atmel_tsadcc. 332 333config TOUCHSCREEN_UCB1400 334 tristate "Philips UCB1400 touchscreen" 335 depends on AC97_BUS 336 depends on UCB1400_CORE 337 help 338 This enables support for the Philips UCB1400 touchscreen interface. 339 The UCB1400 is an AC97 audio codec. The touchscreen interface 340 will be initialized only after the ALSA subsystem has been 341 brought up and the UCB1400 detected. You therefore have to 342 configure ALSA support as well (either built-in or modular, 343 independently of whether this driver is itself built-in or 344 modular) for this driver to work. 345 346 To compile this driver as a module, choose M here: the 347 module will be called ucb1400_ts. 348 349config TOUCHSCREEN_WM97XX 350 tristate "Support for WM97xx AC97 touchscreen controllers" 351 depends on AC97_BUS 352 help 353 Say Y here if you have a Wolfson Microelectronics WM97xx 354 touchscreen connected to your system. Note that this option 355 only enables core driver, you will also need to select 356 support for appropriate chip below. 357 358 If unsure, say N. 359 360 To compile this driver as a module, choose M here: the 361 module will be called wm97xx-ts. 362 363config TOUCHSCREEN_WM9705 364 bool "WM9705 Touchscreen interface support" 365 depends on TOUCHSCREEN_WM97XX 366 default y 367 help 368 Say Y here to enable support for the Wolfson Microelectronics 369 WM9705 touchscreen controller. 370 371config TOUCHSCREEN_WM9712 372 bool "WM9712 Touchscreen interface support" 373 depends on TOUCHSCREEN_WM97XX 374 default y 375 help 376 Say Y here to enable support for the Wolfson Microelectronics 377 WM9712 touchscreen controller. 378 379config TOUCHSCREEN_WM9713 380 bool "WM9713 Touchscreen interface support" 381 depends on TOUCHSCREEN_WM97XX 382 default y 383 help 384 Say Y here to enable support for the Wolfson Microelectronics 385 WM9713 touchscreen controller. 386 387config TOUCHSCREEN_WM97XX_ATMEL 388 tristate "WM97xx Atmel accelerated touch" 389 depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91) 390 help 391 Say Y here for support for streaming mode with WM97xx touchscreens 392 on Atmel AT91 or AVR32 systems with an AC97C module. 393 394 Be aware that this will use channel B in the controller for 395 streaming data, this must not conflict with other AC97C drivers. 396 397 If unsure, say N. 398 399 To compile this driver as a module, choose M here: the module will 400 be called atmel-wm97xx. 401 402config TOUCHSCREEN_WM97XX_MAINSTONE 403 tristate "WM97xx Mainstone/Palm accelerated touch" 404 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 405 help 406 Say Y here for support for streaming mode with WM97xx touchscreens 407 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 408 409 If unsure, say N. 410 411 To compile this driver as a module, choose M here: the 412 module will be called mainstone-wm97xx. 413 414config TOUCHSCREEN_WM97XX_ZYLONITE 415 tristate "Zylonite accelerated touch" 416 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 417 select TOUCHSCREEN_WM9713 418 help 419 Say Y here for support for streaming mode with the touchscreen 420 on Zylonite systems. 421 422 If unsure, say N. 423 424 To compile this driver as a module, choose M here: the 425 module will be called zylonite-wm97xx. 426 427config TOUCHSCREEN_USB_COMPOSITE 428 tristate "USB Touchscreen Driver" 429 depends on USB_ARCH_HAS_HCD 430 select USB 431 help 432 USB Touchscreen driver for: 433 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 434 - PanJit TouchSet USB 435 - 3M MicroTouch USB (EX II series) 436 - ITM 437 - some other eTurboTouch 438 - Gunze AHL61 439 - DMC TSC-10/25 440 - IRTOUCHSYSTEMS/UNITOP 441 - IdealTEK URTC1000 442 - GoTop Super_Q2/GogoPen/PenPower tablets 443 - JASTEC USB Touch Controller/DigiTech DTR-02U 444 - Zytronic controllers 445 446 Have a look at <http://linux.chapter7.ch/touchkit/> for 447 a usage description and the required user-space stuff. 448 449 To compile this driver as a module, choose M here: the 450 module will be called usbtouchscreen. 451 452config TOUCHSCREEN_MC13783 453 tristate "Freescale MC13783 touchscreen input driver" 454 depends on MFD_MC13783 455 help 456 Say Y here if you have an Freescale MC13783 PMIC on your 457 board and want to use its touchscreen 458 459 If unsure, say N. 460 461 To compile this driver as a module, choose M here: the 462 module will be called mc13783_ts. 463 464config TOUCHSCREEN_USB_EGALAX 465 default y 466 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED 467 depends on TOUCHSCREEN_USB_COMPOSITE 468 469config TOUCHSCREEN_USB_PANJIT 470 default y 471 bool "PanJit device support" if EMBEDDED 472 depends on TOUCHSCREEN_USB_COMPOSITE 473 474config TOUCHSCREEN_USB_3M 475 default y 476 bool "3M/Microtouch EX II series device support" if EMBEDDED 477 depends on TOUCHSCREEN_USB_COMPOSITE 478 479config TOUCHSCREEN_USB_ITM 480 default y 481 bool "ITM device support" if EMBEDDED 482 depends on TOUCHSCREEN_USB_COMPOSITE 483 484config TOUCHSCREEN_USB_ETURBO 485 default y 486 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED 487 depends on TOUCHSCREEN_USB_COMPOSITE 488 489config TOUCHSCREEN_USB_GUNZE 490 default y 491 bool "Gunze AHL61 device support" if EMBEDDED 492 depends on TOUCHSCREEN_USB_COMPOSITE 493 494config TOUCHSCREEN_USB_DMC_TSC10 495 default y 496 bool "DMC TSC-10/25 device support" if EMBEDDED 497 depends on TOUCHSCREEN_USB_COMPOSITE 498 499config TOUCHSCREEN_USB_IRTOUCH 500 default y 501 bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED 502 depends on TOUCHSCREEN_USB_COMPOSITE 503 504config TOUCHSCREEN_USB_IDEALTEK 505 default y 506 bool "IdealTEK URTC1000 device support" if EMBEDDED 507 depends on TOUCHSCREEN_USB_COMPOSITE 508 509config TOUCHSCREEN_USB_GENERAL_TOUCH 510 default y 511 bool "GeneralTouch Touchscreen device support" if EMBEDDED 512 depends on TOUCHSCREEN_USB_COMPOSITE 513 514config TOUCHSCREEN_USB_GOTOP 515 default y 516 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED 517 depends on TOUCHSCREEN_USB_COMPOSITE 518 519config TOUCHSCREEN_USB_JASTEC 520 default y 521 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED 522 depends on TOUCHSCREEN_USB_COMPOSITE 523 524config TOUCHSCREEN_USB_E2I 525 default y 526 bool "e2i Touchscreen controller (e.g. from Mimo 740)" 527 depends on TOUCHSCREEN_USB_COMPOSITE 528 529config TOUCHSCREEN_USB_ZYTRONIC 530 default y 531 bool "Zytronic controller" if EMBEDDED 532 depends on TOUCHSCREEN_USB_COMPOSITE 533 534config TOUCHSCREEN_USB_ETT_TC5UH 535 default y 536 bool "ET&T TC5UH touchscreen controler support" if EMBEDDED 537 depends on TOUCHSCREEN_USB_COMPOSITE 538 539config TOUCHSCREEN_USB_NEXIO 540 default y 541 bool "NEXIO/iNexio device support" if EMBEDDED 542 depends on TOUCHSCREEN_USB_COMPOSITE 543 544config TOUCHSCREEN_TOUCHIT213 545 tristate "Sahara TouchIT-213 touchscreen" 546 select SERIO 547 help 548 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 549 550 If unsure, say N. 551 552 To compile this driver as a module, choose M here: the 553 module will be called touchit213. 554 555config TOUCHSCREEN_TSC2007 556 tristate "TSC2007 based touchscreens" 557 depends on I2C 558 help 559 Say Y here if you have a TSC2007 based touchscreen. 560 561 If unsure, say N. 562 563 To compile this driver as a module, choose M here: the 564 module will be called tsc2007. 565 566config TOUCHSCREEN_W90X900 567 tristate "W90P910 touchscreen driver" 568 depends on HAVE_CLK 569 help 570 Say Y here if you have a W90P910 based touchscreen. 571 572 To compile this driver as a module, choose M here: the 573 module will be called w90p910_ts. 574 575config TOUCHSCREEN_PCAP 576 tristate "Motorola PCAP touchscreen" 577 depends on EZX_PCAP 578 help 579 Say Y here if you have a Motorola EZX telephone and 580 want to enable support for the built-in touchscreen. 581 582 To compile this driver as a module, choose M here: the 583 module will be called pcap_ts. 584endif 585