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