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_PROPERTIES 15 def_tristate INPUT 16 depends on INPUT 17 18config TOUCHSCREEN_88PM860X 19 tristate "Marvell 88PM860x touchscreen" 20 depends on MFD_88PM860X 21 help 22 Say Y here if you have a 88PM860x PMIC and want to enable 23 support for the built-in touchscreen. 24 25 If unsure, say N. 26 27 To compile this driver as a module, choose M here: the 28 module will be called 88pm860x-ts. 29 30config TOUCHSCREEN_ADS7846 31 tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens" 32 depends on SPI_MASTER 33 depends on HWMON = n || HWMON 34 help 35 Say Y here if you have a touchscreen interface using the 36 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller, 37 and your board-specific setup code includes that in its 38 table of SPI devices. 39 40 If HWMON is selected, and the driver is told the reference voltage 41 on your board, you will also get hwmon interfaces for the voltage 42 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip. 43 44 If unsure, say N (but it's safe to say "Y"). 45 46 To compile this driver as a module, choose M here: the 47 module will be called ads7846. 48 49config TOUCHSCREEN_AD7877 50 tristate "AD7877 based touchscreens" 51 depends on SPI_MASTER 52 help 53 Say Y here if you have a touchscreen interface using the 54 AD7877 controller, and your board-specific initialization 55 code includes that in its table of SPI devices. 56 57 If unsure, say N (but it's safe to say "Y"). 58 59 To compile this driver as a module, choose M here: the 60 module will be called ad7877. 61 62config TOUCHSCREEN_AD7879 63 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface" 64 help 65 Say Y here if you want to support a touchscreen interface using 66 the AD7879-1/AD7889-1 controller. 67 68 You should select a bus connection too. 69 70 To compile this driver as a module, choose M here: the 71 module will be called ad7879. 72 73config TOUCHSCREEN_AD7879_I2C 74 tristate "support I2C bus connection" 75 depends on TOUCHSCREEN_AD7879 && I2C 76 help 77 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus. 78 79 To compile this driver as a module, choose M here: the 80 module will be called ad7879-i2c. 81 82config TOUCHSCREEN_AD7879_SPI 83 tristate "support SPI bus connection" 84 depends on TOUCHSCREEN_AD7879 && SPI_MASTER 85 help 86 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus. 87 88 If unsure, say N (but it's safe to say "Y"). 89 90 To compile this driver as a module, choose M here: the 91 module will be called ad7879-spi. 92 93config TOUCHSCREEN_AR1021_I2C 94 tristate "Microchip AR1021 i2c touchscreen" 95 depends on I2C && OF 96 help 97 Say Y here if you have the Microchip AR1021 touchscreen controller 98 chip in your system. 99 100 If unsure, say N. 101 102 To compile this driver as a module, choose M here: the 103 module will be called ar1021_i2c. 104 105config TOUCHSCREEN_ATMEL_MXT 106 tristate "Atmel mXT I2C Touchscreen" 107 depends on I2C 108 select FW_LOADER 109 help 110 Say Y here if you have Atmel mXT series I2C touchscreen, 111 such as AT42QT602240/ATMXT224, connected to your system. 112 113 If unsure, say N. 114 115 To compile this driver as a module, choose M here: the 116 module will be called atmel_mxt_ts. 117 118config TOUCHSCREEN_AUO_PIXCIR 119 tristate "AUO in-cell touchscreen using Pixcir ICs" 120 depends on I2C 121 depends on GPIOLIB || COMPILE_TEST 122 help 123 Say Y here if you have a AUO display with in-cell touchscreen 124 using Pixcir ICs. 125 126 If unsure, say N. 127 128 To compile this driver as a module, choose M here: the 129 module will be called auo-pixcir-ts. 130 131config TOUCHSCREEN_BU21013 132 tristate "BU21013 based touch panel controllers" 133 depends on I2C 134 help 135 Say Y here if you have a bu21013 touchscreen connected to 136 your system. 137 138 If unsure, say N. 139 140 To compile this driver as a module, choose M here: the 141 module will be called bu21013_ts. 142 143config TOUCHSCREEN_CHIPONE_ICN8318 144 tristate "chipone icn8318 touchscreen controller" 145 depends on GPIOLIB || COMPILE_TEST 146 depends on I2C 147 depends on OF 148 help 149 Say Y here if you have a ChipOne icn8318 based I2C 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 chipone_icn8318. 155 156config TOUCHSCREEN_CY8CTMG110 157 tristate "cy8ctmg110 touchscreen" 158 depends on I2C 159 depends on GPIOLIB || COMPILE_TEST 160 help 161 Say Y here if you have a cy8ctmg110 capacitive touchscreen on 162 an AAVA device. 163 164 If unsure, say N. 165 166 To compile this driver as a module, choose M here: the 167 module will be called cy8ctmg110_ts. 168 169config TOUCHSCREEN_CYTTSP_CORE 170 tristate "Cypress TTSP touchscreen" 171 help 172 Say Y here if you have a touchscreen using controller from 173 the Cypress TrueTouch(tm) Standard Product family connected 174 to your system. You will also need to select appropriate 175 bus connection below. 176 177 If unsure, say N. 178 179 To compile this driver as a module, choose M here: the 180 module will be called cyttsp_core. 181 182config TOUCHSCREEN_CYTTSP_I2C 183 tristate "support I2C bus connection" 184 depends on TOUCHSCREEN_CYTTSP_CORE && I2C 185 help 186 Say Y here if the touchscreen is connected via I2C bus. 187 188 To compile this driver as a module, choose M here: the 189 module will be called cyttsp_i2c. 190 191config TOUCHSCREEN_CYTTSP_SPI 192 tristate "support SPI bus connection" 193 depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER 194 help 195 Say Y here if the touchscreen is connected via SPI bus. 196 197 To compile this driver as a module, choose M here: the 198 module will be called cyttsp_spi. 199 200config TOUCHSCREEN_CYTTSP4_CORE 201 tristate "Cypress TrueTouch Gen4 Touchscreen Driver" 202 help 203 Core driver for Cypress TrueTouch(tm) Standard Product 204 Generation4 touchscreen controllers. 205 206 Say Y here if you have a Cypress Gen4 touchscreen. 207 208 If unsure, say N. 209 210 To compile this driver as a module, choose M here. 211 212config TOUCHSCREEN_CYTTSP4_I2C 213 tristate "support I2C bus connection" 214 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C 215 help 216 Say Y here if the touchscreen is connected via I2C bus. 217 218 To compile this driver as a module, choose M here: the 219 module will be called cyttsp4_i2c. 220 221config TOUCHSCREEN_CYTTSP4_SPI 222 tristate "support SPI bus connection" 223 depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER 224 help 225 Say Y here if the touchscreen is connected via SPI bus. 226 227 To compile this driver as a module, choose M here: the 228 module will be called cyttsp4_spi. 229 230config TOUCHSCREEN_DA9034 231 tristate "Touchscreen support for Dialog Semiconductor DA9034" 232 depends on PMIC_DA903X 233 default y 234 help 235 Say Y here to enable the support for the touchscreen found 236 on Dialog Semiconductor DA9034 PMIC. 237 238 If unsure, say N. 239 240 To compile this driver as a module, choose M here: the 241 module will be called da9034-ts. 242 243config TOUCHSCREEN_DA9052 244 tristate "Dialog DA9052/DA9053 TSI" 245 depends on PMIC_DA9052 246 help 247 Say Y here to support the touchscreen found on Dialog Semiconductor 248 DA9052-BC and DA9053-AA/Bx PMICs. 249 250 If unsure, say N. 251 252 To compile this driver as a module, choose M here: the 253 module will be called da9052_tsi. 254 255config TOUCHSCREEN_DYNAPRO 256 tristate "Dynapro serial touchscreen" 257 select SERIO 258 help 259 Say Y here if you have a Dynapro serial touchscreen connected to 260 your system. 261 262 If unsure, say N. 263 264 To compile this driver as a module, choose M here: the 265 module will be called dynapro. 266 267config TOUCHSCREEN_HAMPSHIRE 268 tristate "Hampshire serial touchscreen" 269 select SERIO 270 help 271 Say Y here if you have a Hampshire serial touchscreen connected to 272 your system. 273 274 If unsure, say N. 275 276 To compile this driver as a module, choose M here: the 277 module will be called hampshire. 278 279config TOUCHSCREEN_EETI 280 tristate "EETI touchscreen panel support" 281 depends on I2C 282 help 283 Say Y here to enable support for I2C connected EETI touch panels. 284 285 To compile this driver as a module, choose M here: the 286 module will be called eeti_ts. 287 288config TOUCHSCREEN_EGALAX 289 tristate "EETI eGalax multi-touch panel support" 290 depends on I2C && OF 291 help 292 Say Y here to enable support for I2C connected EETI 293 eGalax multi-touch panels. 294 295 To compile this driver as a module, choose M here: the 296 module will be called egalax_ts. 297 298config TOUCHSCREEN_FT6236 299 tristate "FT6236 I2C touchscreen" 300 depends on I2C 301 depends on GPIOLIB || COMPILE_TEST 302 help 303 Say Y here to enable support for the I2C connected FT6x06 and 304 FT6x36 family of capacitive touchscreen drivers. 305 306 If unsure, say N. 307 308 To compile this driver as a module, choose M here: the 309 module will be called ft6236. 310 311config TOUCHSCREEN_FUJITSU 312 tristate "Fujitsu serial touchscreen" 313 select SERIO 314 help 315 Say Y here if you have the Fujitsu touchscreen (such as one 316 installed in Lifebook P series laptop) connected to your 317 system. 318 319 If unsure, say N. 320 321 To compile this driver as a module, choose M here: the 322 module will be called fujitsu-ts. 323 324config TOUCHSCREEN_GOODIX 325 tristate "Goodix I2C touchscreen" 326 depends on I2C 327 help 328 Say Y here if you have the Goodix touchscreen (such as one 329 installed in Onda v975w tablets) connected to your 330 system. It also supports 5-finger chip models, which can be 331 found on ARM tablets, like Wexler TAB7200 and MSI Primo73. 332 333 If unsure, say N. 334 335 To compile this driver as a module, choose M here: the 336 module will be called goodix. 337 338config TOUCHSCREEN_ILI210X 339 tristate "Ilitek ILI210X based touchscreen" 340 depends on I2C 341 help 342 Say Y here if you have a ILI210X based touchscreen 343 controller. This driver supports models ILI2102, 344 ILI2102s, ILI2103, ILI2103s and ILI2105. 345 Such kind of chipsets can be found in Amazon Kindle Fire 346 touchscreens. 347 348 If unsure, say N. 349 350 To compile this driver as a module, choose M here: the 351 module will be called ili210x. 352 353config TOUCHSCREEN_IPROC 354 tristate "IPROC touch panel driver support" 355 depends on ARCH_BCM_IPROC || COMPILE_TEST 356 help 357 Say Y here if you want to add support for the IPROC touch 358 controller to your system. 359 360 If unsure, say N. 361 362 To compile this driver as a module, choose M here: the 363 module will be called bcm_iproc_tsc. 364 365config TOUCHSCREEN_S3C2410 366 tristate "Samsung S3C2410/generic touchscreen input driver" 367 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS 368 select S3C_ADC 369 help 370 Say Y here if you have the s3c2410 touchscreen. 371 372 If unsure, say N. 373 374 To compile this driver as a module, choose M here: the 375 module will be called s3c2410_ts. 376 377config TOUCHSCREEN_GUNZE 378 tristate "Gunze AHL-51S touchscreen" 379 select SERIO 380 help 381 Say Y here if you have the Gunze AHL-51 touchscreen connected to 382 your system. 383 384 If unsure, say N. 385 386 To compile this driver as a module, choose M here: the 387 module will be called gunze. 388 389config TOUCHSCREEN_ELAN 390 tristate "Elan eKTH I2C touchscreen" 391 depends on I2C 392 help 393 Say Y here if you have an Elan eKTH I2C touchscreen 394 connected to your system. 395 396 If unsure, say N. 397 398 To compile this driver as a module, choose M here: the 399 module will be called elants_i2c. 400 401config TOUCHSCREEN_ELO 402 tristate "Elo serial touchscreens" 403 select SERIO 404 help 405 Say Y here if you have an Elo serial touchscreen connected to 406 your system. 407 408 If unsure, say N. 409 410 To compile this driver as a module, choose M here: the 411 module will be called elo. 412 413config TOUCHSCREEN_WACOM_W8001 414 tristate "Wacom W8001 penabled serial touchscreen" 415 select SERIO 416 help 417 Say Y here if you have an Wacom W8001 penabled serial touchscreen 418 connected to your system. 419 420 If unsure, say N. 421 422 To compile this driver as a module, choose M here: the 423 module will be called wacom_w8001. 424 425config TOUCHSCREEN_WACOM_I2C 426 tristate "Wacom Tablet support (I2C)" 427 depends on I2C 428 help 429 Say Y here if you want to use the I2C version of the Wacom 430 Pen Tablet. 431 432 If unsure, say N. 433 434 To compile this driver as a module, choose M here: the module 435 will be called wacom_i2c. 436 437config TOUCHSCREEN_LPC32XX 438 tristate "LPC32XX touchscreen controller" 439 depends on ARCH_LPC32XX 440 help 441 Say Y here if you have a LPC32XX device and want 442 to support the built-in touchscreen. 443 444 To compile this driver as a module, choose M here: the 445 module will be called lpc32xx_ts. 446 447config TOUCHSCREEN_MAX11801 448 tristate "MAX11801 based touchscreens" 449 depends on I2C 450 help 451 Say Y here if you have a MAX11801 based touchscreen 452 controller. 453 454 If unsure, say N. 455 456 To compile this driver as a module, choose M here: the 457 module will be called max11801_ts. 458 459config TOUCHSCREEN_MCS5000 460 tristate "MELFAS MCS-5000 touchscreen" 461 depends on I2C 462 help 463 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 464 chip in your system. 465 466 If unsure, say N. 467 468 To compile this driver as a module, choose M here: the 469 module will be called mcs5000_ts. 470 471config TOUCHSCREEN_MMS114 472 tristate "MELFAS MMS114 touchscreen" 473 depends on I2C 474 help 475 Say Y here if you have the MELFAS MMS114 touchscreen controller 476 chip in your system. 477 478 If unsure, say N. 479 480 To compile this driver as a module, choose M here: the 481 module will be called mms114. 482 483config TOUCHSCREEN_MTOUCH 484 tristate "MicroTouch serial touchscreens" 485 select SERIO 486 help 487 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 488 your system. 489 490 If unsure, say N. 491 492 To compile this driver as a module, choose M here: the 493 module will be called mtouch. 494 495config TOUCHSCREEN_IMX6UL_TSC 496 tristate "Freescale i.MX6UL touchscreen controller" 497 depends on (OF && GPIOLIB) || COMPILE_TEST 498 help 499 Say Y here if you have a Freescale i.MX6UL, and want to 500 use the internal touchscreen controller. 501 502 If unsure, say N. 503 504 To compile this driver as a module, choose M here: the 505 module will be called imx6ul_tsc. 506 507config TOUCHSCREEN_INEXIO 508 tristate "iNexio serial touchscreens" 509 select SERIO 510 help 511 Say Y here if you have an iNexio serial touchscreen connected to 512 your system. 513 514 If unsure, say N. 515 516 To compile this driver as a module, choose M here: the 517 module will be called inexio. 518 519config TOUCHSCREEN_INTEL_MID 520 tristate "Intel MID platform resistive touchscreen" 521 depends on INTEL_SCU_IPC 522 help 523 Say Y here if you have a Intel MID based touchscreen in 524 your system. 525 526 If unsure, say N. 527 528 To compile this driver as a module, choose M here: the 529 module will be called intel_mid_touch. 530 531config TOUCHSCREEN_MK712 532 tristate "ICS MicroClock MK712 touchscreen" 533 help 534 Say Y here if you have the ICS MicroClock MK712 touchscreen 535 controller chip in your system. 536 537 If unsure, say N. 538 539 To compile this driver as a module, choose M here: the 540 module will be called mk712. 541 542config TOUCHSCREEN_HP600 543 tristate "HP Jornada 6xx touchscreen" 544 depends on SH_HP6XX && SH_ADC 545 help 546 Say Y here if you have a HP Jornada 620/660/680/690 and want to 547 support the built-in touchscreen. 548 549 To compile this driver as a module, choose M here: the 550 module will be called hp680_ts_input. 551 552config TOUCHSCREEN_HP7XX 553 tristate "HP Jornada 7xx touchscreen" 554 depends on SA1100_JORNADA720_SSP 555 help 556 Say Y here if you have a HP Jornada 710/720/728 and want 557 to support the built-in touchscreen. 558 559 To compile this driver as a module, choose M here: the 560 module will be called jornada720_ts. 561 562config TOUCHSCREEN_IPAQ_MICRO 563 tristate "HP iPAQ Atmel Micro ASIC touchscreen" 564 depends on MFD_IPAQ_MICRO 565 help 566 Say Y here to enable support for the touchscreen attached to 567 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700 568 569 If unsure, say N. 570 571 To compile this driver as a module, choose M here: the 572 module will be called ipaq-micro-ts. 573 574config TOUCHSCREEN_HTCPEN 575 tristate "HTC Shift X9500 touchscreen" 576 depends on ISA 577 help 578 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 579 Clio / Shangrila and want to support the built-in touchscreen. 580 581 If unsure, say N. 582 583 To compile this driver as a module, choose M here: the 584 module will be called htcpen. 585 586config TOUCHSCREEN_PENMOUNT 587 tristate "Penmount serial touchscreen" 588 select SERIO 589 help 590 Say Y here if you have a Penmount serial touchscreen connected to 591 your system. 592 593 If unsure, say N. 594 595 To compile this driver as a module, choose M here: the 596 module will be called penmount. 597 598config TOUCHSCREEN_EDT_FT5X06 599 tristate "EDT FocalTech FT5x06 I2C Touchscreen support" 600 depends on I2C 601 help 602 Say Y here if you have an EDT "Polytouch" touchscreen based 603 on the FocalTech FT5x06 family of controllers connected to 604 your system. 605 606 If unsure, say N. 607 608 To compile this driver as a module, choose M here: the 609 module will be called edt-ft5x06. 610 611config TOUCHSCREEN_MIGOR 612 tristate "Renesas MIGO-R touchscreen" 613 depends on SH_MIGOR && I2C 614 help 615 Say Y here to enable MIGO-R touchscreen support. 616 617 If unsure, say N. 618 619 To compile this driver as a module, choose M here: the 620 module will be called migor_ts. 621 622config TOUCHSCREEN_TOUCHRIGHT 623 tristate "Touchright serial touchscreen" 624 select SERIO 625 help 626 Say Y here if you have a Touchright serial touchscreen connected to 627 your system. 628 629 If unsure, say N. 630 631 To compile this driver as a module, choose M here: the 632 module will be called touchright. 633 634config TOUCHSCREEN_TOUCHWIN 635 tristate "Touchwin serial touchscreen" 636 select SERIO 637 help 638 Say Y here if you have a Touchwin serial touchscreen connected to 639 your system. 640 641 If unsure, say N. 642 643 To compile this driver as a module, choose M here: the 644 module will be called touchwin. 645 646config TOUCHSCREEN_TI_AM335X_TSC 647 tristate "TI Touchscreen Interface" 648 depends on MFD_TI_AM335X_TSCADC 649 help 650 Say Y here if you have 4/5/8 wire touchscreen controller 651 to be connected to the ADC controller on your TI AM335x SoC. 652 653 If unsure, say N. 654 655 To compile this driver as a module, choose M here: the 656 module will be called ti_am335x_tsc. 657 658config TOUCHSCREEN_UCB1400 659 tristate "Philips UCB1400 touchscreen" 660 depends on AC97_BUS 661 depends on UCB1400_CORE 662 help 663 This enables support for the Philips UCB1400 touchscreen interface. 664 The UCB1400 is an AC97 audio codec. The touchscreen interface 665 will be initialized only after the ALSA subsystem has been 666 brought up and the UCB1400 detected. You therefore have to 667 configure ALSA support as well (either built-in or modular, 668 independently of whether this driver is itself built-in or 669 modular) for this driver to work. 670 671 To compile this driver as a module, choose M here: the 672 module will be called ucb1400_ts. 673 674config TOUCHSCREEN_PIXCIR 675 tristate "PIXCIR I2C touchscreens" 676 depends on I2C 677 help 678 Say Y here if you have a pixcir i2c touchscreen 679 controller. 680 681 If unsure, say N. 682 683 To compile this driver as a module, choose M here: the 684 module will be called pixcir_i2c_ts. 685 686config TOUCHSCREEN_WDT87XX_I2C 687 tristate "Weida HiTech I2C touchscreen" 688 depends on I2C 689 help 690 Say Y here if you have a Weida WDT87XX I2C touchscreen 691 connected to your system. 692 693 If unsure, say N. 694 695 To compile this driver as a module, choose M here: the 696 module will be called wdt87xx_i2c. 697 698config TOUCHSCREEN_WM831X 699 tristate "Support for WM831x touchscreen controllers" 700 depends on MFD_WM831X 701 help 702 This enables support for the touchscreen controller on the WM831x 703 series of PMICs. 704 705 To compile this driver as a module, choose M here: the 706 module will be called wm831x-ts. 707 708config TOUCHSCREEN_WM97XX 709 tristate "Support for WM97xx AC97 touchscreen controllers" 710 depends on AC97_BUS 711 help 712 Say Y here if you have a Wolfson Microelectronics WM97xx 713 touchscreen connected to your system. Note that this option 714 only enables core driver, you will also need to select 715 support for appropriate chip below. 716 717 If unsure, say N. 718 719 To compile this driver as a module, choose M here: the 720 module will be called wm97xx-ts. 721 722config TOUCHSCREEN_WM9705 723 bool "WM9705 Touchscreen interface support" 724 depends on TOUCHSCREEN_WM97XX 725 default y 726 help 727 Say Y here to enable support for the Wolfson Microelectronics 728 WM9705 touchscreen controller. 729 730config TOUCHSCREEN_WM9712 731 bool "WM9712 Touchscreen interface support" 732 depends on TOUCHSCREEN_WM97XX 733 default y 734 help 735 Say Y here to enable support for the Wolfson Microelectronics 736 WM9712 touchscreen controller. 737 738config TOUCHSCREEN_WM9713 739 bool "WM9713 Touchscreen interface support" 740 depends on TOUCHSCREEN_WM97XX 741 default y 742 help 743 Say Y here to enable support for the Wolfson Microelectronics 744 WM9713 touchscreen controller. 745 746config TOUCHSCREEN_WM97XX_ATMEL 747 tristate "WM97xx Atmel accelerated touch" 748 depends on TOUCHSCREEN_WM97XX && AVR32 749 help 750 Say Y here for support for streaming mode with WM97xx touchscreens 751 on Atmel AT91 or AVR32 systems with an AC97C module. 752 753 Be aware that this will use channel B in the controller for 754 streaming data, this must not conflict with other AC97C drivers. 755 756 If unsure, say N. 757 758 To compile this driver as a module, choose M here: the module will 759 be called atmel-wm97xx. 760 761config TOUCHSCREEN_WM97XX_MAINSTONE 762 tristate "WM97xx Mainstone/Palm accelerated touch" 763 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 764 help 765 Say Y here for support for streaming mode with WM97xx touchscreens 766 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 767 768 If unsure, say N. 769 770 To compile this driver as a module, choose M here: the 771 module will be called mainstone-wm97xx. 772 773config TOUCHSCREEN_WM97XX_ZYLONITE 774 tristate "Zylonite accelerated touch" 775 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 776 select TOUCHSCREEN_WM9713 777 help 778 Say Y here for support for streaming mode with the touchscreen 779 on Zylonite systems. 780 781 If unsure, say N. 782 783 To compile this driver as a module, choose M here: the 784 module will be called zylonite-wm97xx. 785 786config TOUCHSCREEN_USB_COMPOSITE 787 tristate "USB Touchscreen Driver" 788 depends on USB_ARCH_HAS_HCD 789 select USB 790 help 791 USB Touchscreen driver for: 792 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 793 - PanJit TouchSet USB 794 - 3M MicroTouch USB (EX II series) 795 - ITM 796 - some other eTurboTouch 797 - Gunze AHL61 798 - DMC TSC-10/25 799 - IRTOUCHSYSTEMS/UNITOP 800 - IdealTEK URTC1000 801 - GoTop Super_Q2/GogoPen/PenPower tablets 802 - JASTEC USB Touch Controller/DigiTech DTR-02U 803 - Zytronic controllers 804 - Elo TouchSystems 2700 IntelliTouch 805 - EasyTouch USB Touch Controller from Data Modul 806 - e2i (Mimo monitors) 807 808 Have a look at <http://linux.chapter7.ch/touchkit/> for 809 a usage description and the required user-space stuff. 810 811 To compile this driver as a module, choose M here: the 812 module will be called usbtouchscreen. 813 814config TOUCHSCREEN_MC13783 815 tristate "Freescale MC13783 touchscreen input driver" 816 depends on MFD_MC13XXX 817 help 818 Say Y here if you have an Freescale MC13783 PMIC on your 819 board and want to use its touchscreen 820 821 If unsure, say N. 822 823 To compile this driver as a module, choose M here: the 824 module will be called mc13783_ts. 825 826config TOUCHSCREEN_USB_EGALAX 827 default y 828 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT 829 depends on TOUCHSCREEN_USB_COMPOSITE 830 831config TOUCHSCREEN_USB_PANJIT 832 default y 833 bool "PanJit device support" if EXPERT 834 depends on TOUCHSCREEN_USB_COMPOSITE 835 836config TOUCHSCREEN_USB_3M 837 default y 838 bool "3M/Microtouch EX II series device support" if EXPERT 839 depends on TOUCHSCREEN_USB_COMPOSITE 840 841config TOUCHSCREEN_USB_ITM 842 default y 843 bool "ITM device support" if EXPERT 844 depends on TOUCHSCREEN_USB_COMPOSITE 845 846config TOUCHSCREEN_USB_ETURBO 847 default y 848 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT 849 depends on TOUCHSCREEN_USB_COMPOSITE 850 851config TOUCHSCREEN_USB_GUNZE 852 default y 853 bool "Gunze AHL61 device support" if EXPERT 854 depends on TOUCHSCREEN_USB_COMPOSITE 855 856config TOUCHSCREEN_USB_DMC_TSC10 857 default y 858 bool "DMC TSC-10/25 device support" if EXPERT 859 depends on TOUCHSCREEN_USB_COMPOSITE 860 861config TOUCHSCREEN_USB_IRTOUCH 862 default y 863 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT 864 depends on TOUCHSCREEN_USB_COMPOSITE 865 866config TOUCHSCREEN_USB_IDEALTEK 867 default y 868 bool "IdealTEK URTC1000 device support" if EXPERT 869 depends on TOUCHSCREEN_USB_COMPOSITE 870 871config TOUCHSCREEN_USB_GENERAL_TOUCH 872 default y 873 bool "GeneralTouch Touchscreen device support" if EXPERT 874 depends on TOUCHSCREEN_USB_COMPOSITE 875 876config TOUCHSCREEN_USB_GOTOP 877 default y 878 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT 879 depends on TOUCHSCREEN_USB_COMPOSITE 880 881config TOUCHSCREEN_USB_JASTEC 882 default y 883 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT 884 depends on TOUCHSCREEN_USB_COMPOSITE 885 886config TOUCHSCREEN_USB_ELO 887 default y 888 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT 889 depends on TOUCHSCREEN_USB_COMPOSITE 890 891config TOUCHSCREEN_USB_E2I 892 default y 893 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT 894 depends on TOUCHSCREEN_USB_COMPOSITE 895 896config TOUCHSCREEN_USB_ZYTRONIC 897 default y 898 bool "Zytronic controller" if EXPERT 899 depends on TOUCHSCREEN_USB_COMPOSITE 900 901config TOUCHSCREEN_USB_ETT_TC45USB 902 default y 903 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT 904 depends on TOUCHSCREEN_USB_COMPOSITE 905 906config TOUCHSCREEN_USB_NEXIO 907 default y 908 bool "NEXIO/iNexio device support" if EXPERT 909 depends on TOUCHSCREEN_USB_COMPOSITE 910 911config TOUCHSCREEN_USB_EASYTOUCH 912 default y 913 bool "EasyTouch USB Touch controller device support" if EMBEDDED 914 depends on TOUCHSCREEN_USB_COMPOSITE 915 help 916 Say Y here if you have an EasyTouch USB Touch controller. 917 If unsure, say N. 918 919config TOUCHSCREEN_TOUCHIT213 920 tristate "Sahara TouchIT-213 touchscreen" 921 select SERIO 922 help 923 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 924 925 If unsure, say N. 926 927 To compile this driver as a module, choose M here: the 928 module will be called touchit213. 929 930config TOUCHSCREEN_TSC_SERIO 931 tristate "TSC-10/25/40 serial touchscreen support" 932 select SERIO 933 help 934 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected 935 to your system. 936 937 If unsure, say N. 938 939 To compile this driver as a module, choose M here: the 940 module will be called tsc40. 941 942config TOUCHSCREEN_TSC200X_CORE 943 tristate 944 945config TOUCHSCREEN_TSC2004 946 tristate "TSC2004 based touchscreens" 947 depends on I2C 948 select REGMAP_I2C 949 select TOUCHSCREEN_TSC200X_CORE 950 help 951 Say Y here if you have a TSC2004 based touchscreen. 952 953 If unsure, say N. 954 955 To compile this driver as a module, choose M here: the 956 module will be called tsc2004. 957 958config TOUCHSCREEN_TSC2005 959 tristate "TSC2005 based touchscreens" 960 depends on SPI_MASTER 961 select REGMAP_SPI 962 select TOUCHSCREEN_TSC200X_CORE 963 help 964 Say Y here if you have a TSC2005 based touchscreen. 965 966 If unsure, say N. 967 968 To compile this driver as a module, choose M here: the 969 module will be called tsc2005. 970 971config TOUCHSCREEN_TSC2007 972 tristate "TSC2007 based touchscreens" 973 depends on I2C 974 help 975 Say Y here if you have a TSC2007 based touchscreen. 976 977 If unsure, say N. 978 979 To compile this driver as a module, choose M here: the 980 module will be called tsc2007. 981 982config TOUCHSCREEN_W90X900 983 tristate "W90P910 touchscreen driver" 984 depends on ARCH_W90X900 985 help 986 Say Y here if you have a W90P910 based touchscreen. 987 988 To compile this driver as a module, choose M here: the 989 module will be called w90p910_ts. 990 991config TOUCHSCREEN_PCAP 992 tristate "Motorola PCAP touchscreen" 993 depends on EZX_PCAP 994 help 995 Say Y here if you have a Motorola EZX telephone and 996 want to enable support for the built-in touchscreen. 997 998 To compile this driver as a module, choose M here: the 999 module will be called pcap_ts. 1000 1001config TOUCHSCREEN_ST1232 1002 tristate "Sitronix ST1232 touchscreen controllers" 1003 depends on I2C 1004 help 1005 Say Y here if you want to support Sitronix ST1232 1006 touchscreen controller. 1007 1008 If unsure, say N. 1009 1010 To compile this driver as a module, choose M here: the 1011 module will be called st1232_ts. 1012 1013config TOUCHSCREEN_STMPE 1014 tristate "STMicroelectronics STMPE touchscreens" 1015 depends on MFD_STMPE 1016 depends on (OF || COMPILE_TEST) 1017 help 1018 Say Y here if you want support for STMicroelectronics 1019 STMPE touchscreen controllers. 1020 1021 To compile this driver as a module, choose M here: the 1022 module will be called stmpe-ts. 1023 1024config TOUCHSCREEN_SUN4I 1025 tristate "Allwinner sun4i resistive touchscreen controller support" 1026 depends on ARCH_SUNXI || COMPILE_TEST 1027 depends on HWMON 1028 depends on THERMAL || !THERMAL_OF 1029 help 1030 This selects support for the resistive touchscreen controller 1031 found on Allwinner sunxi SoCs. 1032 1033 To compile this driver as a module, choose M here: the 1034 module will be called sun4i-ts. 1035 1036config TOUCHSCREEN_SUR40 1037 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen" 1038 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA 1039 depends on VIDEO_V4L2 1040 select INPUT_POLLDEV 1041 select VIDEOBUF2_DMA_SG 1042 help 1043 Say Y here if you want support for the Samsung SUR40 touchscreen 1044 (also known as Microsoft Surface 2.0 or Microsoft PixelSense). 1045 1046 To compile this driver as a module, choose M here: the 1047 module will be called sur40. 1048 1049config TOUCHSCREEN_SX8654 1050 tristate "Semtech SX8654 touchscreen" 1051 depends on I2C 1052 help 1053 Say Y here if you have a Semtech SX8654 touchscreen controller. 1054 1055 If unsure, say N 1056 1057 To compile this driver as a module, choose M here: the 1058 module will be called sx8654. 1059 1060config TOUCHSCREEN_TPS6507X 1061 tristate "TPS6507x based touchscreens" 1062 depends on I2C 1063 select INPUT_POLLDEV 1064 help 1065 Say Y here if you have a TPS6507x based touchscreen 1066 controller. 1067 1068 If unsure, say N. 1069 1070 To compile this driver as a module, choose M here: the 1071 module will be called tps6507x_ts. 1072 1073config TOUCHSCREEN_ZFORCE 1074 tristate "Neonode zForce infrared touchscreens" 1075 depends on I2C 1076 depends on GPIOLIB || COMPILE_TEST 1077 help 1078 Say Y here if you have a touchscreen using the zforce 1079 infraread technology from Neonode. 1080 1081 If unsure, say N. 1082 1083 To compile this driver as a module, choose M here: the 1084 module will be called zforce_ts. 1085 1086config TOUCHSCREEN_COLIBRI_VF50 1087 tristate "Toradex Colibri on board touchscreen driver" 1088 depends on GPIOLIB && IIO && VF610_ADC 1089 help 1090 Say Y here if you have a Colibri VF50 and plan to use 1091 the on-board provided 4-wire touchscreen driver. 1092 1093 If unsure, say N. 1094 1095 To compile this driver as a module, choose M here: the 1096 module will be called colibri_vf50_ts. 1097 1098config TOUCHSCREEN_ROHM_BU21023 1099 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens" 1100 depends on I2C 1101 help 1102 Say Y here if you have a touchscreen using ROHM BU21023/24. 1103 1104 If unsure, say N. 1105 1106 To compile this driver as a module, choose M here: the 1107 module will be called bu21023_ts. 1108 1109endif 1110