1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Touchscreen driver configuration 4# 5menuconfig INPUT_TOUCHSCREEN 6 bool "Touchscreens" 7 help 8 Say Y here, and a list of supported touchscreens will be displayed. 9 This option doesn't affect the kernel. 10 11 If unsure, say Y. 12 13if INPUT_TOUCHSCREEN 14 15config TOUCHSCREEN_88PM860X 16 tristate "Marvell 88PM860x touchscreen" 17 depends on MFD_88PM860X 18 help 19 Say Y here if you have a 88PM860x PMIC and want to enable 20 support for the built-in touchscreen. 21 22 If unsure, say N. 23 24 To compile this driver as a module, choose M here: the 25 module will be called 88pm860x-ts. 26 27config TOUCHSCREEN_ADS7846 28 tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens" 29 depends on SPI_MASTER 30 depends on HWMON = n || HWMON 31 help 32 Say Y here if you have a touchscreen interface using the 33 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller, 34 and your board-specific setup code includes that in its 35 table of SPI devices. 36 37 If HWMON is selected, and the driver is told the reference voltage 38 on your board, you will also get hwmon interfaces for the voltage 39 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip. 40 41 If unsure, say N (but it's safe to say "Y"). 42 43 To compile this driver as a module, choose M here: the 44 module will be called ads7846. 45 46config TOUCHSCREEN_AD7877 47 tristate "AD7877 based touchscreens" 48 depends on SPI_MASTER 49 help 50 Say Y here if you have a touchscreen interface using the 51 AD7877 controller, and your board-specific initialization 52 code includes that in its table of SPI devices. 53 54 If unsure, say N (but it's safe to say "Y"). 55 56 To compile this driver as a module, choose M here: the 57 module will be called ad7877. 58 59config TOUCHSCREEN_AD7879 60 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface" 61 help 62 Say Y here if you want to support a touchscreen interface using 63 the AD7879-1/AD7889-1 controller. 64 65 You should select a bus connection too. 66 67 To compile this driver as a module, choose M here: the 68 module will be called ad7879. 69 70config TOUCHSCREEN_AD7879_I2C 71 tristate "support I2C bus connection" 72 depends on TOUCHSCREEN_AD7879 && I2C 73 select REGMAP_I2C 74 help 75 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus. 76 77 To compile this driver as a module, choose M here: the 78 module will be called ad7879-i2c. 79 80config TOUCHSCREEN_AD7879_SPI 81 tristate "support SPI bus connection" 82 depends on TOUCHSCREEN_AD7879 && SPI_MASTER 83 select REGMAP_SPI 84 help 85 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus. 86 87 If unsure, say N (but it's safe to say "Y"). 88 89 To compile this driver as a module, choose M here: the 90 module will be called ad7879-spi. 91 92config TOUCHSCREEN_ADC 93 tristate "Generic ADC based resistive touchscreen" 94 depends on IIO 95 select IIO_BUFFER 96 select IIO_BUFFER_CB 97 help 98 Say Y here if you want to use the generic ADC 99 resistive touchscreen driver. 100 101 If unsure, say N (but it's safe to say "Y"). 102 103 To compile this driver as a module, choose M here: the 104 module will be called resistive-adc-touch.ko. 105 106config TOUCHSCREEN_AR1021_I2C 107 tristate "Microchip AR1020/1021 i2c touchscreen" 108 depends on I2C && OF 109 help 110 Say Y here if you have the Microchip AR1020 or AR1021 touchscreen 111 controller chip in 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 ar1021_i2c. 117 118config TOUCHSCREEN_ATMEL_MXT 119 tristate "Atmel mXT I2C Touchscreen" 120 depends on I2C 121 select FW_LOADER 122 help 123 Say Y here if you have Atmel mXT series I2C touchscreen, 124 such as AT42QT602240/ATMXT224, connected to your system. 125 126 If unsure, say N. 127 128 To compile this driver as a module, choose M here: the 129 module will be called atmel_mxt_ts. 130 131config TOUCHSCREEN_ATMEL_MXT_T37 132 bool "Support T37 Diagnostic Data" 133 depends on TOUCHSCREEN_ATMEL_MXT 134 depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m) 135 select VIDEOBUF2_VMALLOC 136 help 137 Say Y here if you want support to output data from the T37 138 Diagnostic Data object using a V4L device. 139 140config TOUCHSCREEN_AUO_PIXCIR 141 tristate "AUO in-cell touchscreen using Pixcir ICs" 142 depends on I2C 143 depends on GPIOLIB || COMPILE_TEST 144 help 145 Say Y here if you have a AUO display with in-cell touchscreen 146 using Pixcir ICs. 147 148 If unsure, say N. 149 150 To compile this driver as a module, choose M here: the 151 module will be called auo-pixcir-ts. 152 153config TOUCHSCREEN_BU21013 154 tristate "BU21013 based touch panel controllers" 155 depends on I2C 156 help 157 Say Y here if you have a bu21013 touchscreen connected to 158 your system. 159 160 If unsure, say N. 161 162 To compile this driver as a module, choose M here: the 163 module will be called bu21013_ts. 164 165config TOUCHSCREEN_BU21029 166 tristate "Rohm BU21029 based touch panel controllers" 167 depends on I2C 168 help 169 Say Y here if you have a Rohm BU21029 touchscreen controller 170 connected to your system. 171 172 If unsure, say N. 173 174 To compile this driver as a module, choose M here: the 175 module will be called bu21029_ts. 176 177config TOUCHSCREEN_CHIPONE_ICN8318 178 tristate "chipone icn8318 touchscreen controller" 179 depends on GPIOLIB || COMPILE_TEST 180 depends on I2C 181 depends on OF 182 help 183 Say Y here if you have a ChipOne icn8318 based I2C touchscreen. 184 185 If unsure, say N. 186 187 To compile this driver as a module, choose M here: the 188 module will be called chipone_icn8318. 189 190config TOUCHSCREEN_CHIPONE_ICN8505 191 tristate "chipone icn8505 touchscreen controller" 192 depends on I2C && ACPI 193 help 194 Say Y here if you have a ChipOne icn8505 based I2C touchscreen. 195 196 If unsure, say N. 197 198 To compile this driver as a module, choose M here: the 199 module will be called chipone_icn8505. 200 201config TOUCHSCREEN_CY8CTMA140 202 tristate "cy8ctma140 touchscreen" 203 depends on I2C 204 help 205 Say Y here if you have a Cypress CY8CTMA140 capacitive 206 touchscreen also just known as "TMA140" 207 208 If unsure, say N. 209 210 To compile this driver as a module, choose M here: the 211 module will be called cy8ctma140. 212 213config TOUCHSCREEN_CY8CTMG110 214 tristate "cy8ctmg110 touchscreen" 215 depends on I2C 216 depends on GPIOLIB || COMPILE_TEST 217 help 218 Say Y here if you have a cy8ctmg110 capacitive touchscreen on 219 an AAVA device. 220 221 If unsure, say N. 222 223 To compile this driver as a module, choose M here: the 224 module will be called cy8ctmg110_ts. 225 226config TOUCHSCREEN_CYTTSP_CORE 227 tristate "Cypress TTSP touchscreen" 228 help 229 Say Y here if you have a touchscreen using controller from 230 the Cypress TrueTouch(tm) Standard Product family connected 231 to your system. You will also need to select appropriate 232 bus connection below. 233 234 If unsure, say N. 235 236 To compile this driver as a module, choose M here: the 237 module will be called cyttsp_core. 238 239config TOUCHSCREEN_CYTTSP_I2C 240 tristate "support I2C bus connection" 241 depends on TOUCHSCREEN_CYTTSP_CORE && I2C 242 help 243 Say Y here if the touchscreen is connected via I2C bus. 244 245 To compile this driver as a module, choose M here: the 246 module will be called cyttsp_i2c. 247 248config TOUCHSCREEN_CYTTSP_SPI 249 tristate "support SPI bus connection" 250 depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER 251 help 252 Say Y here if the touchscreen is connected via SPI bus. 253 254 To compile this driver as a module, choose M here: the 255 module will be called cyttsp_spi. 256 257config TOUCHSCREEN_CYTTSP4_CORE 258 tristate "Cypress TrueTouch Gen4 Touchscreen Driver" 259 help 260 Core driver for Cypress TrueTouch(tm) Standard Product 261 Generation4 touchscreen controllers. 262 263 Say Y here if you have a Cypress Gen4 touchscreen. 264 265 If unsure, say N. 266 267 To compile this driver as a module, choose M here. 268 269config TOUCHSCREEN_CYTTSP4_I2C 270 tristate "support I2C bus connection" 271 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C 272 help 273 Say Y here if the touchscreen is connected via I2C bus. 274 275 To compile this driver as a module, choose M here: the 276 module will be called cyttsp4_i2c. 277 278config TOUCHSCREEN_CYTTSP4_SPI 279 tristate "support SPI bus connection" 280 depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER 281 help 282 Say Y here if the touchscreen is connected via SPI bus. 283 284 To compile this driver as a module, choose M here: the 285 module will be called cyttsp4_spi. 286 287config TOUCHSCREEN_DA9034 288 tristate "Touchscreen support for Dialog Semiconductor DA9034" 289 depends on PMIC_DA903X 290 default y 291 help 292 Say Y here to enable the support for the touchscreen found 293 on Dialog Semiconductor DA9034 PMIC. 294 295 If unsure, say N. 296 297 To compile this driver as a module, choose M here: the 298 module will be called da9034-ts. 299 300config TOUCHSCREEN_DA9052 301 tristate "Dialog DA9052/DA9053 TSI" 302 depends on PMIC_DA9052 303 help 304 Say Y here to support the touchscreen found on Dialog Semiconductor 305 DA9052-BC and DA9053-AA/Bx PMICs. 306 307 If unsure, say N. 308 309 To compile this driver as a module, choose M here: the 310 module will be called da9052_tsi. 311 312config TOUCHSCREEN_DYNAPRO 313 tristate "Dynapro serial touchscreen" 314 select SERIO 315 help 316 Say Y here if you have a Dynapro serial touchscreen connected to 317 your 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 dynapro. 323 324config TOUCHSCREEN_HAMPSHIRE 325 tristate "Hampshire serial touchscreen" 326 select SERIO 327 help 328 Say Y here if you have a Hampshire serial touchscreen connected to 329 your system. 330 331 If unsure, say N. 332 333 To compile this driver as a module, choose M here: the 334 module will be called hampshire. 335 336config TOUCHSCREEN_EETI 337 tristate "EETI touchscreen panel support" 338 depends on I2C 339 help 340 Say Y here to enable support for I2C connected EETI touch panels. 341 342 To compile this driver as a module, choose M here: the 343 module will be called eeti_ts. 344 345config TOUCHSCREEN_EGALAX 346 tristate "EETI eGalax multi-touch panel support" 347 depends on I2C && OF 348 help 349 Say Y here to enable support for I2C connected EETI 350 eGalax multi-touch panels. 351 352 To compile this driver as a module, choose M here: the 353 module will be called egalax_ts. 354 355config TOUCHSCREEN_EGALAX_SERIAL 356 tristate "EETI eGalax serial touchscreen" 357 select SERIO 358 help 359 Say Y here to enable support for serial connected EETI 360 eGalax touch panels. 361 362 To compile this driver as a module, choose M here: the 363 module will be called egalax_ts_serial. 364 365config TOUCHSCREEN_EXC3000 366 tristate "EETI EXC3000 multi-touch panel support" 367 depends on I2C 368 help 369 Say Y here to enable support for I2C connected EETI 370 EXC3000 multi-touch panels. 371 372 To compile this driver as a module, choose M here: the 373 module will be called exc3000. 374 375config TOUCHSCREEN_FUJITSU 376 tristate "Fujitsu serial touchscreen" 377 select SERIO 378 help 379 Say Y here if you have the Fujitsu touchscreen (such as one 380 installed in Lifebook P series laptop) connected to your 381 system. 382 383 If unsure, say N. 384 385 To compile this driver as a module, choose M here: the 386 module will be called fujitsu-ts. 387 388config TOUCHSCREEN_GOODIX 389 tristate "Goodix I2C touchscreen" 390 depends on I2C 391 depends on GPIOLIB || COMPILE_TEST 392 help 393 Say Y here if you have the Goodix touchscreen (such as one 394 installed in Onda v975w tablets) connected to your 395 system. It also supports 5-finger chip models, which can be 396 found on ARM tablets, like Wexler TAB7200 and MSI Primo73. 397 398 If unsure, say N. 399 400 To compile this driver as a module, choose M here: the 401 module will be called goodix. 402 403config TOUCHSCREEN_HIDEEP 404 tristate "HiDeep Touch IC" 405 depends on I2C 406 help 407 Say Y here if you have a touchscreen using HiDeep. 408 409 If unsure, say N. 410 411 To compile this driver as a module, choose M here : the 412 module will be called hideep_ts. 413 414config TOUCHSCREEN_ILI210X 415 tristate "Ilitek ILI210X based touchscreen" 416 depends on I2C 417 help 418 Say Y here if you have a ILI210X based touchscreen 419 controller. This driver supports models ILI2102, 420 ILI2102s, ILI2103, ILI2103s and ILI2105. 421 Such kind of chipsets can be found in Amazon Kindle Fire 422 touchscreens. 423 424 If unsure, say N. 425 426 To compile this driver as a module, choose M here: the 427 module will be called ili210x. 428 429config TOUCHSCREEN_ILITEK 430 tristate "Ilitek I2C 213X/23XX/25XX/Lego Series Touch ICs" 431 depends on I2C 432 help 433 Say Y here if you have touchscreen with ILITEK touch IC, 434 it supports 213X/23XX/25XX and other Lego series. 435 436 If unsure, say N. 437 438 To compile this driver as a module, choose M here: the 439 module will be called ilitek_ts_i2c. 440 441config TOUCHSCREEN_IPROC 442 tristate "IPROC touch panel driver support" 443 depends on ARCH_BCM_IPROC || COMPILE_TEST 444 help 445 Say Y here if you want to add support for the IPROC touch 446 controller to your system. 447 448 If unsure, say N. 449 450 To compile this driver as a module, choose M here: the 451 module will be called bcm_iproc_tsc. 452 453config TOUCHSCREEN_S3C2410 454 tristate "Samsung S3C2410/generic touchscreen input driver" 455 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS 456 depends on S3C_ADC 457 help 458 Say Y here if you have the s3c2410 touchscreen. 459 460 If unsure, say N. 461 462 To compile this driver as a module, choose M here: the 463 module will be called s3c2410_ts. 464 465config TOUCHSCREEN_S6SY761 466 tristate "Samsung S6SY761 Touchscreen driver" 467 depends on I2C 468 help 469 Say Y if you have the Samsung S6SY761 driver 470 471 If unsure, say N 472 473 To compile this driver as module, choose M here: the 474 module will be called s6sy761. 475 476config TOUCHSCREEN_GUNZE 477 tristate "Gunze AHL-51S touchscreen" 478 select SERIO 479 help 480 Say Y here if you have the Gunze AHL-51 touchscreen connected to 481 your system. 482 483 If unsure, say N. 484 485 To compile this driver as a module, choose M here: the 486 module will be called gunze. 487 488config TOUCHSCREEN_EKTF2127 489 tristate "Elan eKTF2127 I2C touchscreen" 490 depends on I2C 491 help 492 Say Y here if you have an Elan eKTF2127 touchscreen 493 connected to your system. 494 495 If unsure, say N. 496 497 To compile this driver as a module, choose M here: the 498 module will be called ektf2127. 499 500config TOUCHSCREEN_ELAN 501 tristate "Elan eKTH I2C touchscreen" 502 depends on I2C 503 help 504 Say Y here if you have an Elan eKTH I2C touchscreen 505 connected to your system. 506 507 If unsure, say N. 508 509 To compile this driver as a module, choose M here: the 510 module will be called elants_i2c. 511 512config TOUCHSCREEN_ELO 513 tristate "Elo serial touchscreens" 514 select SERIO 515 help 516 Say Y here if you have an Elo serial touchscreen connected to 517 your system. 518 519 If unsure, say N. 520 521 To compile this driver as a module, choose M here: the 522 module will be called elo. 523 524config TOUCHSCREEN_WACOM_W8001 525 tristate "Wacom W8001 penabled serial touchscreen" 526 select SERIO 527 help 528 Say Y here if you have an Wacom W8001 penabled serial touchscreen 529 connected to your system. 530 531 If unsure, say N. 532 533 To compile this driver as a module, choose M here: the 534 module will be called wacom_w8001. 535 536config TOUCHSCREEN_WACOM_I2C 537 tristate "Wacom Tablet support (I2C)" 538 depends on I2C 539 help 540 Say Y here if you want to use the I2C version of the Wacom 541 Pen Tablet. 542 543 If unsure, say N. 544 545 To compile this driver as a module, choose M here: the module 546 will be called wacom_i2c. 547 548config TOUCHSCREEN_LPC32XX 549 tristate "LPC32XX touchscreen controller" 550 depends on ARCH_LPC32XX 551 help 552 Say Y here if you have a LPC32XX device and want 553 to support the built-in touchscreen. 554 555 To compile this driver as a module, choose M here: the 556 module will be called lpc32xx_ts. 557 558config TOUCHSCREEN_MAX11801 559 tristate "MAX11801 based touchscreens" 560 depends on I2C 561 help 562 Say Y here if you have a MAX11801 based touchscreen 563 controller. 564 565 If unsure, say N. 566 567 To compile this driver as a module, choose M here: the 568 module will be called max11801_ts. 569 570config TOUCHSCREEN_MCS5000 571 tristate "MELFAS MCS-5000 touchscreen" 572 depends on I2C 573 help 574 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 575 chip in your system. 576 577 If unsure, say N. 578 579 To compile this driver as a module, choose M here: the 580 module will be called mcs5000_ts. 581 582config TOUCHSCREEN_MMS114 583 tristate "MELFAS MMS114 touchscreen" 584 depends on I2C 585 help 586 Say Y here if you have the MELFAS MMS114 touchscreen controller 587 chip in your system. 588 589 If unsure, say N. 590 591 To compile this driver as a module, choose M here: the 592 module will be called mms114. 593 594config TOUCHSCREEN_MELFAS_MIP4 595 tristate "MELFAS MIP4 Touchscreen" 596 depends on I2C 597 help 598 Say Y here if you have a MELFAS MIP4 Touchscreen device. 599 600 If unsure, say N. 601 602 To compile this driver as a module, choose M here: 603 the module will be called melfas_mip4. 604 605config TOUCHSCREEN_MSG2638 606 tristate "MStar msg2638 touchscreen support" 607 depends on I2C 608 depends on GPIOLIB || COMPILE_TEST 609 help 610 Say Y here if you have an I2C touchscreen using MStar msg2638. 611 612 If unsure, say N. 613 614 To compile this driver as a module, choose M here: the 615 module will be called msg2638. 616 617config TOUCHSCREEN_MTOUCH 618 tristate "MicroTouch serial touchscreens" 619 select SERIO 620 help 621 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 622 your system. 623 624 If unsure, say N. 625 626 To compile this driver as a module, choose M here: the 627 module will be called mtouch. 628 629config TOUCHSCREEN_IMX6UL_TSC 630 tristate "Freescale i.MX6UL touchscreen controller" 631 depends on ((OF && GPIOLIB) || COMPILE_TEST) && HAS_IOMEM 632 help 633 Say Y here if you have a Freescale i.MX6UL, and want to 634 use the internal touchscreen controller. 635 636 If unsure, say N. 637 638 To compile this driver as a module, choose M here: the 639 module will be called imx6ul_tsc. 640 641config TOUCHSCREEN_INEXIO 642 tristate "iNexio serial touchscreens" 643 select SERIO 644 help 645 Say Y here if you have an iNexio serial touchscreen connected to 646 your system. 647 648 If unsure, say N. 649 650 To compile this driver as a module, choose M here: the 651 module will be called inexio. 652 653config TOUCHSCREEN_MK712 654 tristate "ICS MicroClock MK712 touchscreen" 655 help 656 Say Y here if you have the ICS MicroClock MK712 touchscreen 657 controller chip in your system. 658 659 If unsure, say N. 660 661 To compile this driver as a module, choose M here: the 662 module will be called mk712. 663 664config TOUCHSCREEN_HP600 665 tristate "HP Jornada 6xx touchscreen" 666 depends on SH_HP6XX && SH_ADC 667 help 668 Say Y here if you have a HP Jornada 620/660/680/690 and want to 669 support the built-in touchscreen. 670 671 To compile this driver as a module, choose M here: the 672 module will be called hp680_ts_input. 673 674config TOUCHSCREEN_HP7XX 675 tristate "HP Jornada 7xx touchscreen" 676 depends on SA1100_JORNADA720_SSP 677 help 678 Say Y here if you have a HP Jornada 710/720/728 and want 679 to support the built-in touchscreen. 680 681 To compile this driver as a module, choose M here: the 682 module will be called jornada720_ts. 683 684config TOUCHSCREEN_IPAQ_MICRO 685 tristate "HP iPAQ Atmel Micro ASIC touchscreen" 686 depends on MFD_IPAQ_MICRO 687 help 688 Say Y here to enable support for the touchscreen attached to 689 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700 690 691 If unsure, say N. 692 693 To compile this driver as a module, choose M here: the 694 module will be called ipaq-micro-ts. 695 696config TOUCHSCREEN_HTCPEN 697 tristate "HTC Shift X9500 touchscreen" 698 depends on ISA 699 help 700 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 701 Clio / Shangrila and want to support the built-in touchscreen. 702 703 If unsure, say N. 704 705 To compile this driver as a module, choose M here: the 706 module will be called htcpen. 707 708config TOUCHSCREEN_PENMOUNT 709 tristate "Penmount serial touchscreen" 710 select SERIO 711 help 712 Say Y here if you have a Penmount serial touchscreen connected to 713 your system. 714 715 If unsure, say N. 716 717 To compile this driver as a module, choose M here: the 718 module will be called penmount. 719 720config TOUCHSCREEN_EDT_FT5X06 721 tristate "EDT FocalTech FT5x06 I2C Touchscreen support" 722 depends on I2C 723 help 724 Say Y here if you have an EDT "Polytouch" touchscreen based 725 on the FocalTech FT5x06 family of controllers connected to 726 your system. 727 728 If unsure, say N. 729 730 To compile this driver as a module, choose M here: the 731 module will be called edt-ft5x06. 732 733config TOUCHSCREEN_RASPBERRYPI_FW 734 tristate "Raspberry Pi's firmware base touch screen support" 735 depends on RASPBERRYPI_FIRMWARE || (RASPBERRYPI_FIRMWARE=n && COMPILE_TEST) 736 help 737 Say Y here if you have the official Raspberry Pi 7 inch screen on 738 your system. 739 740 If unsure, say N. 741 742 To compile this driver as a module, choose M here: the 743 module will be called raspberrypi-ts. 744 745config TOUCHSCREEN_MIGOR 746 tristate "Renesas MIGO-R touchscreen" 747 depends on (SH_MIGOR || COMPILE_TEST) && I2C 748 help 749 Say Y here to enable MIGO-R touchscreen support. 750 751 If unsure, say N. 752 753 To compile this driver as a module, choose M here: the 754 module will be called migor_ts. 755 756config TOUCHSCREEN_TOUCHRIGHT 757 tristate "Touchright serial touchscreen" 758 select SERIO 759 help 760 Say Y here if you have a Touchright serial touchscreen connected to 761 your system. 762 763 If unsure, say N. 764 765 To compile this driver as a module, choose M here: the 766 module will be called touchright. 767 768config TOUCHSCREEN_TOUCHWIN 769 tristate "Touchwin serial touchscreen" 770 select SERIO 771 help 772 Say Y here if you have a Touchwin serial touchscreen connected to 773 your system. 774 775 If unsure, say N. 776 777 To compile this driver as a module, choose M here: the 778 module will be called touchwin. 779 780config TOUCHSCREEN_TI_AM335X_TSC 781 tristate "TI Touchscreen Interface" 782 depends on MFD_TI_AM335X_TSCADC 783 help 784 Say Y here if you have 4/5/8 wire touchscreen controller 785 to be connected to the ADC controller on your TI AM335x SoC. 786 787 If unsure, say N. 788 789 To compile this driver as a module, choose M here: the 790 module will be called ti_am335x_tsc. 791 792config TOUCHSCREEN_UCB1400 793 tristate "Philips UCB1400 touchscreen" 794 depends on AC97_BUS 795 depends on UCB1400_CORE 796 help 797 This enables support for the Philips UCB1400 touchscreen interface. 798 The UCB1400 is an AC97 audio codec. The touchscreen interface 799 will be initialized only after the ALSA subsystem has been 800 brought up and the UCB1400 detected. You therefore have to 801 configure ALSA support as well (either built-in or modular, 802 independently of whether this driver is itself built-in or 803 modular) for this driver to work. 804 805 To compile this driver as a module, choose M here: the 806 module will be called ucb1400_ts. 807 808config TOUCHSCREEN_PIXCIR 809 tristate "PIXCIR I2C touchscreens" 810 depends on I2C 811 help 812 Say Y here if you have a pixcir i2c touchscreen 813 controller. 814 815 If unsure, say N. 816 817 To compile this driver as a module, choose M here: the 818 module will be called pixcir_i2c_ts. 819 820config TOUCHSCREEN_WDT87XX_I2C 821 tristate "Weida HiTech I2C touchscreen" 822 depends on I2C 823 help 824 Say Y here if you have a Weida WDT87XX I2C touchscreen 825 connected to your system. 826 827 If unsure, say N. 828 829 To compile this driver as a module, choose M here: the 830 module will be called wdt87xx_i2c. 831 832config TOUCHSCREEN_WM831X 833 tristate "Support for WM831x touchscreen controllers" 834 depends on MFD_WM831X 835 help 836 This enables support for the touchscreen controller on the WM831x 837 series of PMICs. 838 839 To compile this driver as a module, choose M here: the 840 module will be called wm831x-ts. 841 842config TOUCHSCREEN_WM97XX 843 tristate "Support for WM97xx AC97 touchscreen controllers" 844 depends on AC97_BUS || AC97_BUS_NEW 845 help 846 Say Y here if you have a Wolfson Microelectronics WM97xx 847 touchscreen connected to your system. Note that this option 848 only enables core driver, you will also need to select 849 support for appropriate chip below. 850 851 If unsure, say N. 852 853 To compile this driver as a module, choose M here: the 854 module will be called wm97xx-ts. 855 856config TOUCHSCREEN_WM9705 857 bool "WM9705 Touchscreen interface support" 858 depends on TOUCHSCREEN_WM97XX 859 default y 860 help 861 Say Y here to enable support for the Wolfson Microelectronics 862 WM9705 touchscreen controller. 863 864config TOUCHSCREEN_WM9712 865 bool "WM9712 Touchscreen interface support" 866 depends on TOUCHSCREEN_WM97XX 867 default y 868 help 869 Say Y here to enable support for the Wolfson Microelectronics 870 WM9712 touchscreen controller. 871 872config TOUCHSCREEN_WM9713 873 bool "WM9713 Touchscreen interface support" 874 depends on TOUCHSCREEN_WM97XX 875 default y 876 help 877 Say Y here to enable support for the Wolfson Microelectronics 878 WM9713 touchscreen controller. 879 880config TOUCHSCREEN_WM97XX_MAINSTONE 881 tristate "WM97xx Mainstone/Palm accelerated touch" 882 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 883 help 884 Say Y here for support for streaming mode with WM97xx touchscreens 885 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 886 887 If unsure, say N. 888 889 To compile this driver as a module, choose M here: the 890 module will be called mainstone-wm97xx. 891 892config TOUCHSCREEN_WM97XX_ZYLONITE 893 tristate "Zylonite accelerated touch" 894 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 895 select TOUCHSCREEN_WM9713 896 help 897 Say Y here for support for streaming mode with the touchscreen 898 on Zylonite systems. 899 900 If unsure, say N. 901 902 To compile this driver as a module, choose M here: the 903 module will be called zylonite-wm97xx. 904 905config TOUCHSCREEN_USB_COMPOSITE 906 tristate "USB Touchscreen Driver" 907 depends on USB_ARCH_HAS_HCD 908 select USB 909 help 910 USB Touchscreen driver for: 911 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 912 - PanJit TouchSet USB 913 - 3M MicroTouch USB (EX II series) 914 - ITM 915 - some other eTurboTouch 916 - Gunze AHL61 917 - DMC TSC-10/25 918 - IRTOUCHSYSTEMS/UNITOP 919 - IdealTEK URTC1000 920 - GoTop Super_Q2/GogoPen/PenPower tablets 921 - JASTEC USB Touch Controller/DigiTech DTR-02U 922 - Zytronic controllers 923 - Elo TouchSystems 2700 IntelliTouch 924 - EasyTouch USB Touch Controller from Data Modul 925 - e2i (Mimo monitors) 926 927 Have a look at <http://linux.chapter7.ch/touchkit/> for 928 a usage description and the required user-space stuff. 929 930 To compile this driver as a module, choose M here: the 931 module will be called usbtouchscreen. 932 933config TOUCHSCREEN_MXS_LRADC 934 tristate "Freescale i.MX23/i.MX28 LRADC touchscreen" 935 depends on MFD_MXS_LRADC 936 help 937 Say Y here if you have a touchscreen connected to the low-resolution 938 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor. 939 940 To compile this driver as a module, choose M here: the module will be 941 called mxs-lradc-ts. 942 943config TOUCHSCREEN_MX25 944 tristate "Freescale i.MX25 touchscreen input driver" 945 depends on MFD_MX25_TSADC 946 help 947 Enable support for touchscreen connected to your i.MX25. 948 949 To compile this driver as a module, choose M here: the 950 module will be called fsl-imx25-tcq. 951 952config TOUCHSCREEN_MC13783 953 tristate "Freescale MC13783 touchscreen input driver" 954 depends on MFD_MC13XXX 955 help 956 Say Y here if you have an Freescale MC13783 PMIC on your 957 board and want to use its touchscreen 958 959 If unsure, say N. 960 961 To compile this driver as a module, choose M here: the 962 module will be called mc13783_ts. 963 964config TOUCHSCREEN_USB_EGALAX 965 default y 966 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT 967 depends on TOUCHSCREEN_USB_COMPOSITE 968 969config TOUCHSCREEN_USB_PANJIT 970 default y 971 bool "PanJit device support" if EXPERT 972 depends on TOUCHSCREEN_USB_COMPOSITE 973 974config TOUCHSCREEN_USB_3M 975 default y 976 bool "3M/Microtouch EX II series device support" if EXPERT 977 depends on TOUCHSCREEN_USB_COMPOSITE 978 979config TOUCHSCREEN_USB_ITM 980 default y 981 bool "ITM device support" if EXPERT 982 depends on TOUCHSCREEN_USB_COMPOSITE 983 984config TOUCHSCREEN_USB_ETURBO 985 default y 986 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT 987 depends on TOUCHSCREEN_USB_COMPOSITE 988 989config TOUCHSCREEN_USB_GUNZE 990 default y 991 bool "Gunze AHL61 device support" if EXPERT 992 depends on TOUCHSCREEN_USB_COMPOSITE 993 994config TOUCHSCREEN_USB_DMC_TSC10 995 default y 996 bool "DMC TSC-10/25 device support" if EXPERT 997 depends on TOUCHSCREEN_USB_COMPOSITE 998 999config TOUCHSCREEN_USB_IRTOUCH 1000 default y 1001 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT 1002 depends on TOUCHSCREEN_USB_COMPOSITE 1003 1004config TOUCHSCREEN_USB_IDEALTEK 1005 default y 1006 bool "IdealTEK URTC1000 device support" if EXPERT 1007 depends on TOUCHSCREEN_USB_COMPOSITE 1008 1009config TOUCHSCREEN_USB_GENERAL_TOUCH 1010 default y 1011 bool "GeneralTouch Touchscreen device support" if EXPERT 1012 depends on TOUCHSCREEN_USB_COMPOSITE 1013 1014config TOUCHSCREEN_USB_GOTOP 1015 default y 1016 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT 1017 depends on TOUCHSCREEN_USB_COMPOSITE 1018 1019config TOUCHSCREEN_USB_JASTEC 1020 default y 1021 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT 1022 depends on TOUCHSCREEN_USB_COMPOSITE 1023 1024config TOUCHSCREEN_USB_ELO 1025 default y 1026 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT 1027 depends on TOUCHSCREEN_USB_COMPOSITE 1028 1029config TOUCHSCREEN_USB_E2I 1030 default y 1031 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT 1032 depends on TOUCHSCREEN_USB_COMPOSITE 1033 1034config TOUCHSCREEN_USB_ZYTRONIC 1035 default y 1036 bool "Zytronic controller" if EXPERT 1037 depends on TOUCHSCREEN_USB_COMPOSITE 1038 1039config TOUCHSCREEN_USB_ETT_TC45USB 1040 default y 1041 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT 1042 depends on TOUCHSCREEN_USB_COMPOSITE 1043 1044config TOUCHSCREEN_USB_NEXIO 1045 default y 1046 bool "NEXIO/iNexio device support" if EXPERT 1047 depends on TOUCHSCREEN_USB_COMPOSITE 1048 1049config TOUCHSCREEN_USB_EASYTOUCH 1050 default y 1051 bool "EasyTouch USB Touch controller device support" if EXPERT 1052 depends on TOUCHSCREEN_USB_COMPOSITE 1053 help 1054 Say Y here if you have an EasyTouch USB Touch controller. 1055 If unsure, say N. 1056 1057config TOUCHSCREEN_TOUCHIT213 1058 tristate "Sahara TouchIT-213 touchscreen" 1059 select SERIO 1060 help 1061 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 1062 1063 If unsure, say N. 1064 1065 To compile this driver as a module, choose M here: the 1066 module will be called touchit213. 1067 1068config TOUCHSCREEN_TS4800 1069 tristate "TS-4800 touchscreen" 1070 depends on HAS_IOMEM && OF 1071 depends on SOC_IMX51 || COMPILE_TEST 1072 select MFD_SYSCON 1073 help 1074 Say Y here if you have a touchscreen on a TS-4800 board. 1075 1076 On TS-4800, the touchscreen is not handled directly by Linux but by 1077 a companion FPGA. 1078 1079 If unsure, say N. 1080 1081 To compile this driver as a module, choose M here: the 1082 module will be called ts4800_ts. 1083 1084config TOUCHSCREEN_TSC_SERIO 1085 tristate "TSC-10/25/40 serial touchscreen support" 1086 select SERIO 1087 help 1088 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected 1089 to your system. 1090 1091 If unsure, say N. 1092 1093 To compile this driver as a module, choose M here: the 1094 module will be called tsc40. 1095 1096config TOUCHSCREEN_TSC200X_CORE 1097 tristate 1098 1099config TOUCHSCREEN_TSC2004 1100 tristate "TSC2004 based touchscreens" 1101 depends on I2C 1102 select REGMAP_I2C 1103 select TOUCHSCREEN_TSC200X_CORE 1104 help 1105 Say Y here if you have a TSC2004 based touchscreen. 1106 1107 If unsure, say N. 1108 1109 To compile this driver as a module, choose M here: the 1110 module will be called tsc2004. 1111 1112config TOUCHSCREEN_TSC2005 1113 tristate "TSC2005 based touchscreens" 1114 depends on SPI_MASTER 1115 select REGMAP_SPI 1116 select TOUCHSCREEN_TSC200X_CORE 1117 help 1118 Say Y here if you have a TSC2005 based touchscreen. 1119 1120 If unsure, say N. 1121 1122 To compile this driver as a module, choose M here: the 1123 module will be called tsc2005. 1124 1125config TOUCHSCREEN_TSC2007 1126 tristate "TSC2007 based touchscreens" 1127 depends on I2C 1128 help 1129 Say Y here if you have a TSC2007 based touchscreen. 1130 1131 If unsure, say N. 1132 1133 To compile this driver as a module, choose M here: the 1134 module will be called tsc2007. 1135 1136config TOUCHSCREEN_TSC2007_IIO 1137 bool "IIO interface for external ADC input and temperature" 1138 depends on TOUCHSCREEN_TSC2007 1139 depends on IIO=y || IIO=TOUCHSCREEN_TSC2007 1140 help 1141 Saying Y here adds an iio interface to the tsc2007 which 1142 provides values for the AUX input (used for e.g. battery 1143 or ambient light monitoring), temperature and raw input 1144 values. 1145 1146config TOUCHSCREEN_PCAP 1147 tristate "Motorola PCAP touchscreen" 1148 depends on EZX_PCAP 1149 help 1150 Say Y here if you have a Motorola EZX telephone and 1151 want to enable support for the built-in touchscreen. 1152 1153 To compile this driver as a module, choose M here: the 1154 module will be called pcap_ts. 1155 1156config TOUCHSCREEN_RM_TS 1157 tristate "Raydium I2C Touchscreen" 1158 depends on I2C 1159 depends on GPIOLIB || COMPILE_TEST 1160 help 1161 Say Y here if you have Raydium series I2C touchscreen, 1162 such as RM32380, connected to your system. 1163 1164 If unsure, say N. 1165 1166 To compile this driver as a module, choose M here: the 1167 module will be called raydium_i2c_ts. 1168 1169config TOUCHSCREEN_SILEAD 1170 tristate "Silead I2C touchscreen" 1171 depends on I2C 1172 help 1173 Say Y here if you have the Silead touchscreen connected to 1174 your system. 1175 1176 If unsure, say N. 1177 1178 To compile this driver as a module, choose M here: the 1179 module will be called silead. 1180 1181config TOUCHSCREEN_SIS_I2C 1182 tristate "SiS 9200 family I2C touchscreen" 1183 depends on I2C 1184 select CRC_ITU_T 1185 depends on GPIOLIB || COMPILE_TEST 1186 help 1187 This enables support for SiS 9200 family over I2C based touchscreens. 1188 1189 If unsure, say N. 1190 1191 To compile this driver as a module, choose M here: the 1192 module will be called sis_i2c. 1193 1194config TOUCHSCREEN_ST1232 1195 tristate "Sitronix ST1232 or ST1633 touchscreen controllers" 1196 depends on I2C 1197 help 1198 Say Y here if you want to support the Sitronix ST1232 1199 or ST1633 touchscreen controller. 1200 1201 If unsure, say N. 1202 1203 To compile this driver as a module, choose M here: the 1204 module will be called st1232_ts. 1205 1206config TOUCHSCREEN_STMFTS 1207 tristate "STMicroelectronics STMFTS touchscreen" 1208 depends on I2C 1209 depends on LEDS_CLASS 1210 help 1211 Say Y here if you want support for STMicroelectronics 1212 STMFTS touchscreen. 1213 1214 To compile this driver as a module, choose M here: the 1215 module will be called stmfts. 1216 1217config TOUCHSCREEN_STMPE 1218 tristate "STMicroelectronics STMPE touchscreens" 1219 depends on MFD_STMPE 1220 depends on (OF || COMPILE_TEST) 1221 help 1222 Say Y here if you want support for STMicroelectronics 1223 STMPE touchscreen controllers. 1224 1225 To compile this driver as a module, choose M here: the 1226 module will be called stmpe-ts. 1227 1228config TOUCHSCREEN_SUN4I 1229 tristate "Allwinner sun4i resistive touchscreen controller support" 1230 depends on ARCH_SUNXI || COMPILE_TEST 1231 depends on HWMON 1232 depends on THERMAL || !THERMAL_OF 1233 help 1234 This selects support for the resistive touchscreen controller 1235 found on Allwinner sunxi SoCs. 1236 1237 To compile this driver as a module, choose M here: the 1238 module will be called sun4i-ts. 1239 1240config TOUCHSCREEN_SUR40 1241 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen" 1242 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA 1243 depends on VIDEO_V4L2 1244 select VIDEOBUF2_DMA_SG 1245 help 1246 Say Y here if you want support for the Samsung SUR40 touchscreen 1247 (also known as Microsoft Surface 2.0 or Microsoft PixelSense). 1248 1249 To compile this driver as a module, choose M here: the 1250 module will be called sur40. 1251 1252config TOUCHSCREEN_SURFACE3_SPI 1253 tristate "Ntrig/Microsoft Surface 3 SPI touchscreen" 1254 depends on SPI 1255 depends on GPIOLIB || COMPILE_TEST 1256 help 1257 Say Y here if you have the Ntrig/Microsoft SPI touchscreen 1258 controller chip as found on the Surface 3 in your system. 1259 1260 If unsure, say N. 1261 1262 To compile this driver as a module, choose M here: the 1263 module will be called surface3_spi. 1264 1265config TOUCHSCREEN_SX8654 1266 tristate "Semtech SX8654 touchscreen" 1267 depends on I2C 1268 help 1269 Say Y here if you have a Semtech SX8654 touchscreen controller. 1270 1271 If unsure, say N 1272 1273 To compile this driver as a module, choose M here: the 1274 module will be called sx8654. 1275 1276config TOUCHSCREEN_TPS6507X 1277 tristate "TPS6507x based touchscreens" 1278 depends on I2C 1279 help 1280 Say Y here if you have a TPS6507x based touchscreen 1281 controller. 1282 1283 If unsure, say N. 1284 1285 To compile this driver as a module, choose M here: the 1286 module will be called tps6507x_ts. 1287 1288config TOUCHSCREEN_ZET6223 1289 tristate "Zeitec ZET6223 touchscreen driver" 1290 depends on I2C 1291 help 1292 Say Y here if you have a touchscreen using Zeitec ZET6223 1293 1294 If unsure, say N. 1295 1296 To compile this driver as a module, choose M here: the 1297 module will be called zet6223. 1298 1299config TOUCHSCREEN_ZFORCE 1300 tristate "Neonode zForce infrared touchscreens" 1301 depends on I2C 1302 depends on GPIOLIB || COMPILE_TEST 1303 help 1304 Say Y here if you have a touchscreen using the zforce 1305 infraread technology from Neonode. 1306 1307 If unsure, say N. 1308 1309 To compile this driver as a module, choose M here: the 1310 module will be called zforce_ts. 1311 1312config TOUCHSCREEN_COLIBRI_VF50 1313 tristate "Toradex Colibri on board touchscreen driver" 1314 depends on IIO && VF610_ADC 1315 depends on GPIOLIB || COMPILE_TEST 1316 help 1317 Say Y here if you have a Colibri VF50 and plan to use 1318 the on-board provided 4-wire touchscreen driver. 1319 1320 If unsure, say N. 1321 1322 To compile this driver as a module, choose M here: the 1323 module will be called colibri_vf50_ts. 1324 1325config TOUCHSCREEN_ROHM_BU21023 1326 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens" 1327 depends on I2C 1328 help 1329 Say Y here if you have a touchscreen using ROHM BU21023/24. 1330 1331 If unsure, say N. 1332 1333 To compile this driver as a module, choose M here: the 1334 module will be called bu21023_ts. 1335 1336config TOUCHSCREEN_IQS5XX 1337 tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller" 1338 depends on I2C 1339 help 1340 Say Y to enable support for the Azoteq IQS550/572/525 1341 family of trackpad/touchscreen controllers. 1342 1343 To compile this driver as a module, choose M here: the 1344 module will be called iqs5xx. 1345 1346config TOUCHSCREEN_ZINITIX 1347 tristate "Zinitix touchscreen support" 1348 depends on I2C 1349 help 1350 Say Y here if you have a touchscreen using Zinitix bt541, 1351 or something similar enough. 1352 1353 If unsure, say N. 1354 1355 To compile this driver as a module, choose M here: the 1356 module will be called zinitix. 1357 1358endif 1359