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