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