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