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_DEV=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_DEV=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_CYTTSP5 288 tristate "Cypress TrueTouch Gen5 Touchscreen Driver" 289 depends on I2C 290 select REGMAP_I2C 291 select CRC_ITU_T 292 help 293 Driver for Parade TrueTouch Standard Product Generation 5 294 touchscreen controllers. I2C bus interface support only. 295 296 Say Y here if you have a Cypress Gen5 touchscreen. 297 298 If unsure, say N. 299 300 To compile this driver as a module, choose M here: the 301 module will be called cyttsp5. 302 303config TOUCHSCREEN_DA9034 304 tristate "Touchscreen support for Dialog Semiconductor DA9034" 305 depends on PMIC_DA903X 306 default y 307 help 308 Say Y here to enable the support for the touchscreen found 309 on Dialog Semiconductor DA9034 PMIC. 310 311 If unsure, say N. 312 313 To compile this driver as a module, choose M here: the 314 module will be called da9034-ts. 315 316config TOUCHSCREEN_DA9052 317 tristate "Dialog DA9052/DA9053 TSI" 318 depends on PMIC_DA9052 319 help 320 Say Y here to support the touchscreen found on Dialog Semiconductor 321 DA9052-BC and DA9053-AA/Bx PMICs. 322 323 If unsure, say N. 324 325 To compile this driver as a module, choose M here: the 326 module will be called da9052_tsi. 327 328config TOUCHSCREEN_DYNAPRO 329 tristate "Dynapro serial touchscreen" 330 select SERIO 331 help 332 Say Y here if you have a Dynapro serial touchscreen connected to 333 your system. 334 335 If unsure, say N. 336 337 To compile this driver as a module, choose M here: the 338 module will be called dynapro. 339 340config TOUCHSCREEN_HAMPSHIRE 341 tristate "Hampshire serial touchscreen" 342 select SERIO 343 help 344 Say Y here if you have a Hampshire serial touchscreen connected to 345 your system. 346 347 If unsure, say N. 348 349 To compile this driver as a module, choose M here: the 350 module will be called hampshire. 351 352config TOUCHSCREEN_EETI 353 tristate "EETI touchscreen panel support" 354 depends on I2C 355 help 356 Say Y here to enable support for I2C connected EETI touch panels. 357 358 To compile this driver as a module, choose M here: the 359 module will be called eeti_ts. 360 361config TOUCHSCREEN_EGALAX 362 tristate "EETI eGalax multi-touch panel support" 363 depends on I2C && OF 364 help 365 Say Y here to enable support for I2C connected EETI 366 eGalax multi-touch panels. 367 368 To compile this driver as a module, choose M here: the 369 module will be called egalax_ts. 370 371config TOUCHSCREEN_EGALAX_SERIAL 372 tristate "EETI eGalax serial touchscreen" 373 select SERIO 374 help 375 Say Y here to enable support for serial connected EETI 376 eGalax touch panels. 377 378 To compile this driver as a module, choose M here: the 379 module will be called egalax_ts_serial. 380 381config TOUCHSCREEN_EXC3000 382 tristate "EETI EXC3000 multi-touch panel support" 383 depends on I2C 384 help 385 Say Y here to enable support for I2C connected EETI 386 EXC3000 multi-touch panels. 387 388 To compile this driver as a module, choose M here: the 389 module will be called exc3000. 390 391config TOUCHSCREEN_FUJITSU 392 tristate "Fujitsu serial touchscreen" 393 select SERIO 394 help 395 Say Y here if you have the Fujitsu touchscreen (such as one 396 installed in Lifebook P series laptop) connected to your 397 system. 398 399 If unsure, say N. 400 401 To compile this driver as a module, choose M here: the 402 module will be called fujitsu-ts. 403 404config TOUCHSCREEN_GOODIX 405 tristate "Goodix I2C touchscreen" 406 depends on I2C 407 depends on GPIOLIB || COMPILE_TEST 408 help 409 Say Y here if you have the Goodix touchscreen (such as one 410 installed in Onda v975w tablets) connected to your 411 system. It also supports 5-finger chip models, which can be 412 found on ARM tablets, like Wexler TAB7200 and MSI Primo73. 413 414 If unsure, say N. 415 416 To compile this driver as a module, choose M here: the 417 module will be called goodix. 418 419config TOUCHSCREEN_HIDEEP 420 tristate "HiDeep Touch IC" 421 depends on I2C 422 help 423 Say Y here if you have a touchscreen using HiDeep. 424 425 If unsure, say N. 426 427 To compile this driver as a module, choose M here : the 428 module will be called hideep_ts. 429 430config TOUCHSCREEN_HYCON_HY46XX 431 tristate "Hycon hy46xx touchscreen support" 432 depends on I2C 433 help 434 Say Y here if you have a touchscreen using Hycon hy46xx 435 436 If unsure, say N. 437 438 To compile this driver as a module, choose M here: the 439 module will be called hycon-hy46xx. 440 441config TOUCHSCREEN_HYNITRON_CSTXXX 442 tristate "Hynitron touchscreen support" 443 depends on I2C 444 help 445 Say Y here if you have a touchscreen using a Hynitron 446 touchscreen controller. 447 448 If unsure, say N. 449 450 To compile this driver as a module, choose M here: the 451 module will be called hynitron-cstxxx. 452 453config TOUCHSCREEN_ILI210X 454 tristate "Ilitek ILI210X based touchscreen" 455 depends on I2C 456 select CRC_CCITT 457 help 458 Say Y here if you have a ILI210X based touchscreen 459 controller. This driver supports models ILI2102, 460 ILI2102s, ILI2103, ILI2103s and ILI2105. 461 Such kind of chipsets can be found in Amazon Kindle Fire 462 touchscreens. 463 464 If unsure, say N. 465 466 To compile this driver as a module, choose M here: the 467 module will be called ili210x. 468 469config TOUCHSCREEN_ILITEK 470 tristate "Ilitek I2C 213X/23XX/25XX/Lego Series Touch ICs" 471 depends on I2C 472 help 473 Say Y here if you have touchscreen with ILITEK touch IC, 474 it supports 213X/23XX/25XX and other Lego series. 475 476 If unsure, say N. 477 478 To compile this driver as a module, choose M here: the 479 module will be called ilitek_ts_i2c. 480 481config TOUCHSCREEN_IPROC 482 tristate "IPROC touch panel driver support" 483 depends on ARCH_BCM_IPROC || COMPILE_TEST 484 help 485 Say Y here if you want to add support for the IPROC touch 486 controller to your system. 487 488 If unsure, say N. 489 490 To compile this driver as a module, choose M here: the 491 module will be called bcm_iproc_tsc. 492 493config TOUCHSCREEN_S6SY761 494 tristate "Samsung S6SY761 Touchscreen driver" 495 depends on I2C 496 help 497 Say Y if you have the Samsung S6SY761 driver 498 499 If unsure, say N 500 501 To compile this driver as module, choose M here: the 502 module will be called s6sy761. 503 504config TOUCHSCREEN_GUNZE 505 tristate "Gunze AHL-51S touchscreen" 506 select SERIO 507 help 508 Say Y here if you have the Gunze AHL-51 touchscreen connected to 509 your system. 510 511 If unsure, say N. 512 513 To compile this driver as a module, choose M here: the 514 module will be called gunze. 515 516config TOUCHSCREEN_EKTF2127 517 tristate "Elan eKTF2127 I2C touchscreen" 518 depends on I2C 519 help 520 Say Y here if you have an Elan eKTF2127 touchscreen 521 connected to your system. 522 523 If unsure, say N. 524 525 To compile this driver as a module, choose M here: the 526 module will be called ektf2127. 527 528config TOUCHSCREEN_ELAN 529 tristate "Elan eKTH I2C touchscreen" 530 depends on I2C 531 help 532 Say Y here if you have an Elan eKTH I2C touchscreen 533 connected to your system. 534 535 If unsure, say N. 536 537 To compile this driver as a module, choose M here: the 538 module will be called elants_i2c. 539 540config TOUCHSCREEN_ELO 541 tristate "Elo serial touchscreens" 542 select SERIO 543 help 544 Say Y here if you have an Elo serial touchscreen connected to 545 your system. 546 547 If unsure, say N. 548 549 To compile this driver as a module, choose M here: the 550 module will be called elo. 551 552config TOUCHSCREEN_WACOM_W8001 553 tristate "Wacom W8001 penabled serial touchscreen" 554 select SERIO 555 help 556 Say Y here if you have an Wacom W8001 penabled serial touchscreen 557 connected to your system. 558 559 If unsure, say N. 560 561 To compile this driver as a module, choose M here: the 562 module will be called wacom_w8001. 563 564config TOUCHSCREEN_WACOM_I2C 565 tristate "Wacom Tablet support (I2C)" 566 depends on I2C 567 help 568 Say Y here if you want to use the I2C version of the Wacom 569 Pen Tablet. 570 571 If unsure, say N. 572 573 To compile this driver as a module, choose M here: the module 574 will be called wacom_i2c. 575 576config TOUCHSCREEN_LPC32XX 577 tristate "LPC32XX touchscreen controller" 578 depends on ARCH_LPC32XX 579 help 580 Say Y here if you have a LPC32XX device and want 581 to support the built-in touchscreen. 582 583 To compile this driver as a module, choose M here: the 584 module will be called lpc32xx_ts. 585 586config TOUCHSCREEN_MAX11801 587 tristate "MAX11801 based touchscreens" 588 depends on I2C 589 help 590 Say Y here if you have a MAX11801 based touchscreen 591 controller. 592 593 If unsure, say N. 594 595 To compile this driver as a module, choose M here: the 596 module will be called max11801_ts. 597 598config TOUCHSCREEN_MCS5000 599 tristate "MELFAS MCS-5000 touchscreen" 600 depends on I2C 601 help 602 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 603 chip in your system. 604 605 If unsure, say N. 606 607 To compile this driver as a module, choose M here: the 608 module will be called mcs5000_ts. 609 610config TOUCHSCREEN_MMS114 611 tristate "MELFAS MMS114 touchscreen" 612 depends on I2C 613 help 614 Say Y here if you have the MELFAS MMS114 touchscreen controller 615 chip in your system. 616 617 If unsure, say N. 618 619 To compile this driver as a module, choose M here: the 620 module will be called mms114. 621 622config TOUCHSCREEN_MELFAS_MIP4 623 tristate "MELFAS MIP4 Touchscreen" 624 depends on I2C 625 help 626 Say Y here if you have a MELFAS MIP4 Touchscreen device. 627 628 If unsure, say N. 629 630 To compile this driver as a module, choose M here: 631 the module will be called melfas_mip4. 632 633config TOUCHSCREEN_MSG2638 634 tristate "MStar msg2638 touchscreen support" 635 depends on I2C 636 depends on GPIOLIB || COMPILE_TEST 637 help 638 Say Y here if you have an I2C touchscreen using MStar msg2638. 639 640 If unsure, say N. 641 642 To compile this driver as a module, choose M here: the 643 module will be called msg2638. 644 645config TOUCHSCREEN_MTOUCH 646 tristate "MicroTouch serial touchscreens" 647 select SERIO 648 help 649 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 650 your system. 651 652 If unsure, say N. 653 654 To compile this driver as a module, choose M here: the 655 module will be called mtouch. 656 657config TOUCHSCREEN_NOVATEK_NVT_TS 658 tristate "Novatek NVT-ts touchscreen support" 659 depends on I2C 660 help 661 Say Y here if you have a Novatek NVT-ts touchscreen. 662 If unsure, say N. 663 664 To compile this driver as a module, choose M here: the 665 module will be called novatek-nvt-ts. 666 667config TOUCHSCREEN_IMAGIS 668 tristate "Imagis touchscreen support" 669 depends on I2C 670 help 671 Say Y here if you have an Imagis IST30xxC touchscreen. 672 If unsure, say N. 673 674 To compile this driver as a module, choose M here: the 675 module will be called imagis. 676 677config TOUCHSCREEN_IMX6UL_TSC 678 tristate "Freescale i.MX6UL touchscreen controller" 679 depends on ((OF && GPIOLIB) || COMPILE_TEST) && HAS_IOMEM 680 help 681 Say Y here if you have a Freescale i.MX6UL, and want to 682 use the internal touchscreen controller. 683 684 If unsure, say N. 685 686 To compile this driver as a module, choose M here: the 687 module will be called imx6ul_tsc. 688 689config TOUCHSCREEN_INEXIO 690 tristate "iNexio serial touchscreens" 691 select SERIO 692 help 693 Say Y here if you have an iNexio serial touchscreen connected to 694 your system. 695 696 If unsure, say N. 697 698 To compile this driver as a module, choose M here: the 699 module will be called inexio. 700 701config TOUCHSCREEN_MK712 702 tristate "ICS MicroClock MK712 touchscreen" 703 help 704 Say Y here if you have the ICS MicroClock MK712 touchscreen 705 controller chip in your system. 706 707 If unsure, say N. 708 709 To compile this driver as a module, choose M here: the 710 module will be called mk712. 711 712config TOUCHSCREEN_HP600 713 tristate "HP Jornada 6xx touchscreen" 714 depends on SH_HP6XX && SH_ADC 715 help 716 Say Y here if you have a HP Jornada 620/660/680/690 and want to 717 support the built-in touchscreen. 718 719 To compile this driver as a module, choose M here: the 720 module will be called hp680_ts_input. 721 722config TOUCHSCREEN_HP7XX 723 tristate "HP Jornada 7xx touchscreen" 724 depends on SA1100_JORNADA720_SSP 725 help 726 Say Y here if you have a HP Jornada 710/720/728 and want 727 to support the built-in touchscreen. 728 729 To compile this driver as a module, choose M here: the 730 module will be called jornada720_ts. 731 732config TOUCHSCREEN_IPAQ_MICRO 733 tristate "HP iPAQ Atmel Micro ASIC touchscreen" 734 depends on MFD_IPAQ_MICRO 735 help 736 Say Y here to enable support for the touchscreen attached to 737 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700 738 739 If unsure, say N. 740 741 To compile this driver as a module, choose M here: the 742 module will be called ipaq-micro-ts. 743 744config TOUCHSCREEN_HTCPEN 745 tristate "HTC Shift X9500 touchscreen" 746 depends on ISA 747 help 748 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 749 Clio / Shangrila and want to support the built-in touchscreen. 750 751 If unsure, say N. 752 753 To compile this driver as a module, choose M here: the 754 module will be called htcpen. 755 756config TOUCHSCREEN_PENMOUNT 757 tristate "Penmount serial touchscreen" 758 select SERIO 759 help 760 Say Y here if you have a Penmount 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 penmount. 767 768config TOUCHSCREEN_EDT_FT5X06 769 tristate "EDT FocalTech FT5x06 I2C Touchscreen support" 770 depends on I2C 771 select REGMAP_I2C 772 help 773 Say Y here if you have an EDT "Polytouch" touchscreen based 774 on the FocalTech FT5x06 family of controllers connected to 775 your system. 776 777 If unsure, say N. 778 779 To compile this driver as a module, choose M here: the 780 module will be called edt-ft5x06. 781 782config TOUCHSCREEN_RASPBERRYPI_FW 783 tristate "Raspberry Pi's firmware base touch screen support" 784 depends on RASPBERRYPI_FIRMWARE || (RASPBERRYPI_FIRMWARE=n && COMPILE_TEST) 785 help 786 Say Y here if you have the official Raspberry Pi 7 inch screen on 787 your system. 788 789 If unsure, say N. 790 791 To compile this driver as a module, choose M here: the 792 module will be called raspberrypi-ts. 793 794config TOUCHSCREEN_MIGOR 795 tristate "Renesas MIGO-R touchscreen" 796 depends on (SH_MIGOR || COMPILE_TEST) && I2C 797 help 798 Say Y here to enable MIGO-R touchscreen support. 799 800 If unsure, say N. 801 802 To compile this driver as a module, choose M here: the 803 module will be called migor_ts. 804 805config TOUCHSCREEN_TOUCHRIGHT 806 tristate "Touchright serial touchscreen" 807 select SERIO 808 help 809 Say Y here if you have a Touchright serial touchscreen connected to 810 your system. 811 812 If unsure, say N. 813 814 To compile this driver as a module, choose M here: the 815 module will be called touchright. 816 817config TOUCHSCREEN_TOUCHWIN 818 tristate "Touchwin serial touchscreen" 819 select SERIO 820 help 821 Say Y here if you have a Touchwin serial touchscreen connected to 822 your system. 823 824 If unsure, say N. 825 826 To compile this driver as a module, choose M here: the 827 module will be called touchwin. 828 829config TOUCHSCREEN_TI_AM335X_TSC 830 tristate "TI Touchscreen Interface" 831 depends on MFD_TI_AM335X_TSCADC 832 help 833 Say Y here if you have 4/5/8 wire touchscreen controller 834 to be connected to the ADC controller on your TI AM335x SoC. 835 836 If unsure, say N. 837 838 To compile this driver as a module, choose M here: the 839 module will be called ti_am335x_tsc. 840 841config TOUCHSCREEN_PIXCIR 842 tristate "PIXCIR I2C touchscreens" 843 depends on I2C 844 help 845 Say Y here if you have a pixcir i2c touchscreen 846 controller. 847 848 If unsure, say N. 849 850 To compile this driver as a module, choose M here: the 851 module will be called pixcir_i2c_ts. 852 853config TOUCHSCREEN_WDT87XX_I2C 854 tristate "Weida HiTech I2C touchscreen" 855 depends on I2C 856 help 857 Say Y here if you have a Weida WDT87XX I2C touchscreen 858 connected to your system. 859 860 If unsure, say N. 861 862 To compile this driver as a module, choose M here: the 863 module will be called wdt87xx_i2c. 864 865config TOUCHSCREEN_WM831X 866 tristate "Support for WM831x touchscreen controllers" 867 depends on MFD_WM831X 868 help 869 This enables support for the touchscreen controller on the WM831x 870 series of PMICs. 871 872 To compile this driver as a module, choose M here: the 873 module will be called wm831x-ts. 874 875config TOUCHSCREEN_WM97XX 876 tristate "Support for WM97xx AC97 touchscreen controllers" 877 depends on AC97_BUS || AC97_BUS_NEW 878 help 879 Say Y here if you have a Wolfson Microelectronics WM97xx 880 touchscreen connected to your system. Note that this option 881 only enables core driver, you will also need to select 882 support for appropriate chip below. 883 884 If unsure, say N. 885 886 To compile this driver as a module, choose M here: the 887 module will be called wm97xx-ts. 888 889config TOUCHSCREEN_WM9705 890 bool "WM9705 Touchscreen interface support" 891 depends on TOUCHSCREEN_WM97XX 892 default y 893 help 894 Say Y here to enable support for the Wolfson Microelectronics 895 WM9705 touchscreen controller. 896 897config TOUCHSCREEN_WM9712 898 bool "WM9712 Touchscreen interface support" 899 depends on TOUCHSCREEN_WM97XX 900 default y 901 help 902 Say Y here to enable support for the Wolfson Microelectronics 903 WM9712 touchscreen controller. 904 905config TOUCHSCREEN_WM9713 906 bool "WM9713 Touchscreen interface support" 907 depends on TOUCHSCREEN_WM97XX 908 default y 909 help 910 Say Y here to enable support for the Wolfson Microelectronics 911 WM9713 touchscreen controller. 912 913config TOUCHSCREEN_WM97XX_MAINSTONE 914 tristate "WM97xx Mainstone/Palm accelerated touch" 915 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 916 depends on SND_PXA2XX_LIB_AC97 917 help 918 Say Y here for support for streaming mode with WM97xx touchscreens 919 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 920 921 If unsure, say N. 922 923 To compile this driver as a module, choose M here: the 924 module will be called mainstone-wm97xx. 925 926config TOUCHSCREEN_USB_COMPOSITE 927 tristate "USB Touchscreen Driver" 928 depends on USB_ARCH_HAS_HCD 929 select USB 930 help 931 USB Touchscreen driver for: 932 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 933 - PanJit TouchSet USB 934 - 3M MicroTouch USB (EX II series) 935 - ITM 936 - some other eTurboTouch 937 - Gunze AHL61 938 - DMC TSC-10/25 939 - IRTOUCHSYSTEMS/UNITOP 940 - IdealTEK URTC1000 941 - GoTop Super_Q2/GogoPen/PenPower tablets 942 - JASTEC USB Touch Controller/DigiTech DTR-02U 943 - Zytronic controllers 944 - Elo TouchSystems 2700 IntelliTouch 945 - EasyTouch USB Touch Controller from Data Module 946 - e2i (Mimo monitors) 947 948 Have a look at <http://linux.chapter7.ch/touchkit/> for 949 a usage description and the required user-space stuff. 950 951 To compile this driver as a module, choose M here: the 952 module will be called usbtouchscreen. 953 954config TOUCHSCREEN_MXS_LRADC 955 tristate "Freescale i.MX23/i.MX28 LRADC touchscreen" 956 depends on MFD_MXS_LRADC 957 help 958 Say Y here if you have a touchscreen connected to the low-resolution 959 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor. 960 961 To compile this driver as a module, choose M here: the module will be 962 called mxs-lradc-ts. 963 964config TOUCHSCREEN_MX25 965 tristate "Freescale i.MX25 touchscreen input driver" 966 depends on MFD_MX25_TSADC 967 help 968 Enable support for touchscreen connected to your i.MX25. 969 970 To compile this driver as a module, choose M here: the 971 module will be called fsl-imx25-tcq. 972 973config TOUCHSCREEN_MC13783 974 tristate "Freescale MC13783 touchscreen input driver" 975 depends on MFD_MC13XXX 976 help 977 Say Y here if you have an Freescale MC13783 PMIC on your 978 board and want to use its touchscreen 979 980 If unsure, say N. 981 982 To compile this driver as a module, choose M here: the 983 module will be called mc13783_ts. 984 985config TOUCHSCREEN_USB_EGALAX 986 default y 987 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT 988 depends on TOUCHSCREEN_USB_COMPOSITE 989 990config TOUCHSCREEN_USB_PANJIT 991 default y 992 bool "PanJit device support" if EXPERT 993 depends on TOUCHSCREEN_USB_COMPOSITE 994 995config TOUCHSCREEN_USB_3M 996 default y 997 bool "3M/Microtouch EX II series device support" if EXPERT 998 depends on TOUCHSCREEN_USB_COMPOSITE 999 1000config TOUCHSCREEN_USB_ITM 1001 default y 1002 bool "ITM device support" if EXPERT 1003 depends on TOUCHSCREEN_USB_COMPOSITE 1004 1005config TOUCHSCREEN_USB_ETURBO 1006 default y 1007 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT 1008 depends on TOUCHSCREEN_USB_COMPOSITE 1009 1010config TOUCHSCREEN_USB_GUNZE 1011 default y 1012 bool "Gunze AHL61 device support" if EXPERT 1013 depends on TOUCHSCREEN_USB_COMPOSITE 1014 1015config TOUCHSCREEN_USB_DMC_TSC10 1016 default y 1017 bool "DMC TSC-10/25 device support" if EXPERT 1018 depends on TOUCHSCREEN_USB_COMPOSITE 1019 1020config TOUCHSCREEN_USB_IRTOUCH 1021 default y 1022 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT 1023 depends on TOUCHSCREEN_USB_COMPOSITE 1024 1025config TOUCHSCREEN_USB_IDEALTEK 1026 default y 1027 bool "IdealTEK URTC1000 device support" if EXPERT 1028 depends on TOUCHSCREEN_USB_COMPOSITE 1029 1030config TOUCHSCREEN_USB_GENERAL_TOUCH 1031 default y 1032 bool "GeneralTouch Touchscreen device support" if EXPERT 1033 depends on TOUCHSCREEN_USB_COMPOSITE 1034 1035config TOUCHSCREEN_USB_GOTOP 1036 default y 1037 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT 1038 depends on TOUCHSCREEN_USB_COMPOSITE 1039 1040config TOUCHSCREEN_USB_JASTEC 1041 default y 1042 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT 1043 depends on TOUCHSCREEN_USB_COMPOSITE 1044 1045config TOUCHSCREEN_USB_ELO 1046 default y 1047 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT 1048 depends on TOUCHSCREEN_USB_COMPOSITE 1049 1050config TOUCHSCREEN_USB_E2I 1051 default y 1052 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT 1053 depends on TOUCHSCREEN_USB_COMPOSITE 1054 1055config TOUCHSCREEN_USB_ZYTRONIC 1056 default y 1057 bool "Zytronic controller" if EXPERT 1058 depends on TOUCHSCREEN_USB_COMPOSITE 1059 1060config TOUCHSCREEN_USB_ETT_TC45USB 1061 default y 1062 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT 1063 depends on TOUCHSCREEN_USB_COMPOSITE 1064 1065config TOUCHSCREEN_USB_NEXIO 1066 default y 1067 bool "NEXIO/iNexio device support" if EXPERT 1068 depends on TOUCHSCREEN_USB_COMPOSITE 1069 1070config TOUCHSCREEN_USB_EASYTOUCH 1071 default y 1072 bool "EasyTouch USB Touch controller device support" if EXPERT 1073 depends on TOUCHSCREEN_USB_COMPOSITE 1074 help 1075 Say Y here if you have an EasyTouch USB Touch controller. 1076 If unsure, say N. 1077 1078config TOUCHSCREEN_TOUCHIT213 1079 tristate "Sahara TouchIT-213 touchscreen" 1080 select SERIO 1081 help 1082 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 1083 1084 If unsure, say N. 1085 1086 To compile this driver as a module, choose M here: the 1087 module will be called touchit213. 1088 1089config TOUCHSCREEN_TS4800 1090 tristate "TS-4800 touchscreen" 1091 depends on HAS_IOMEM && OF 1092 depends on SOC_IMX51 || COMPILE_TEST 1093 select MFD_SYSCON 1094 help 1095 Say Y here if you have a touchscreen on a TS-4800 board. 1096 1097 On TS-4800, the touchscreen is not handled directly by Linux but by 1098 a companion FPGA. 1099 1100 If unsure, say N. 1101 1102 To compile this driver as a module, choose M here: the 1103 module will be called ts4800_ts. 1104 1105config TOUCHSCREEN_TSC_SERIO 1106 tristate "TSC-10/25/40 serial touchscreen support" 1107 select SERIO 1108 help 1109 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected 1110 to your system. 1111 1112 If unsure, say N. 1113 1114 To compile this driver as a module, choose M here: the 1115 module will be called tsc40. 1116 1117config TOUCHSCREEN_TSC200X_CORE 1118 tristate 1119 1120config TOUCHSCREEN_TSC2004 1121 tristate "TSC2004 based touchscreens" 1122 depends on I2C 1123 select REGMAP_I2C 1124 select TOUCHSCREEN_TSC200X_CORE 1125 help 1126 Say Y here if you have a TSC2004 based touchscreen. 1127 1128 If unsure, say N. 1129 1130 To compile this driver as a module, choose M here: the 1131 module will be called tsc2004. 1132 1133config TOUCHSCREEN_TSC2005 1134 tristate "TSC2005 based touchscreens" 1135 depends on SPI_MASTER 1136 select REGMAP_SPI 1137 select TOUCHSCREEN_TSC200X_CORE 1138 help 1139 Say Y here if you have a TSC2005 based touchscreen. 1140 1141 If unsure, say N. 1142 1143 To compile this driver as a module, choose M here: the 1144 module will be called tsc2005. 1145 1146config TOUCHSCREEN_TSC2007 1147 tristate "TSC2007 based touchscreens" 1148 depends on I2C 1149 help 1150 Say Y here if you have a TSC2007 based touchscreen. 1151 1152 If unsure, say N. 1153 1154 To compile this driver as a module, choose M here: the 1155 module will be called tsc2007. 1156 1157config TOUCHSCREEN_TSC2007_IIO 1158 bool "IIO interface for external ADC input and temperature" 1159 depends on TOUCHSCREEN_TSC2007 1160 depends on IIO=y || IIO=TOUCHSCREEN_TSC2007 1161 help 1162 Saying Y here adds an iio interface to the tsc2007 which 1163 provides values for the AUX input (used for e.g. battery 1164 or ambient light monitoring), temperature and raw input 1165 values. 1166 1167config TOUCHSCREEN_PCAP 1168 tristate "Motorola PCAP touchscreen" 1169 depends on EZX_PCAP 1170 help 1171 Say Y here if you have a Motorola EZX telephone and 1172 want to enable support for the built-in touchscreen. 1173 1174 To compile this driver as a module, choose M here: the 1175 module will be called pcap_ts. 1176 1177config TOUCHSCREEN_RM_TS 1178 tristate "Raydium I2C Touchscreen" 1179 depends on I2C 1180 depends on GPIOLIB || COMPILE_TEST 1181 help 1182 Say Y here if you have Raydium series I2C touchscreen, 1183 such as RM32380, connected to your system. 1184 1185 If unsure, say N. 1186 1187 To compile this driver as a module, choose M here: the 1188 module will be called raydium_i2c_ts. 1189 1190config TOUCHSCREEN_SILEAD 1191 tristate "Silead I2C touchscreen" 1192 depends on I2C 1193 help 1194 Say Y here if you have the Silead touchscreen connected to 1195 your system. 1196 1197 If unsure, say N. 1198 1199 To compile this driver as a module, choose M here: the 1200 module will be called silead. 1201 1202config TOUCHSCREEN_SIS_I2C 1203 tristate "SiS 9200 family I2C touchscreen" 1204 depends on I2C 1205 select CRC_ITU_T 1206 depends on GPIOLIB || COMPILE_TEST 1207 help 1208 This enables support for SiS 9200 family over I2C based touchscreens. 1209 1210 If unsure, say N. 1211 1212 To compile this driver as a module, choose M here: the 1213 module will be called sis_i2c. 1214 1215config TOUCHSCREEN_ST1232 1216 tristate "Sitronix ST1232 or ST1633 touchscreen controllers" 1217 depends on I2C 1218 help 1219 Say Y here if you want to support the Sitronix ST1232 1220 or ST1633 touchscreen controller. 1221 1222 If unsure, say N. 1223 1224 To compile this driver as a module, choose M here: the 1225 module will be called st1232_ts. 1226 1227config TOUCHSCREEN_STMFTS 1228 tristate "STMicroelectronics STMFTS touchscreen" 1229 depends on I2C 1230 depends on LEDS_CLASS 1231 help 1232 Say Y here if you want support for STMicroelectronics 1233 STMFTS touchscreen. 1234 1235 To compile this driver as a module, choose M here: the 1236 module will be called stmfts. 1237 1238config TOUCHSCREEN_STMPE 1239 tristate "STMicroelectronics STMPE touchscreens" 1240 depends on MFD_STMPE 1241 depends on OF 1242 help 1243 Say Y here if you want support for STMicroelectronics 1244 STMPE touchscreen controllers. 1245 1246 To compile this driver as a module, choose M here: the 1247 module will be called stmpe-ts. 1248 1249config TOUCHSCREEN_SUN4I 1250 tristate "Allwinner sun4i resistive touchscreen controller support" 1251 depends on ARCH_SUNXI || COMPILE_TEST 1252 depends on HWMON 1253 depends on THERMAL || !THERMAL_OF 1254 help 1255 This selects support for the resistive touchscreen controller 1256 found on Allwinner sunxi SoCs. 1257 1258 To compile this driver as a module, choose M here: the 1259 module will be called sun4i-ts. 1260 1261config TOUCHSCREEN_SUR40 1262 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen" 1263 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA 1264 depends on VIDEO_DEV 1265 select VIDEOBUF2_DMA_SG 1266 help 1267 Say Y here if you want support for the Samsung SUR40 touchscreen 1268 (also known as Microsoft Surface 2.0 or Microsoft PixelSense). 1269 1270 To compile this driver as a module, choose M here: the 1271 module will be called sur40. 1272 1273config TOUCHSCREEN_SURFACE3_SPI 1274 tristate "Ntrig/Microsoft Surface 3 SPI touchscreen" 1275 depends on SPI 1276 depends on GPIOLIB || COMPILE_TEST 1277 help 1278 Say Y here if you have the Ntrig/Microsoft SPI touchscreen 1279 controller chip as found on the Surface 3 in your system. 1280 1281 If unsure, say N. 1282 1283 To compile this driver as a module, choose M here: the 1284 module will be called surface3_spi. 1285 1286config TOUCHSCREEN_SX8654 1287 tristate "Semtech SX8654 touchscreen" 1288 depends on I2C 1289 help 1290 Say Y here if you have a Semtech SX8654 touchscreen controller. 1291 1292 If unsure, say N 1293 1294 To compile this driver as a module, choose M here: the 1295 module will be called sx8654. 1296 1297config TOUCHSCREEN_TPS6507X 1298 tristate "TPS6507x based touchscreens" 1299 depends on I2C 1300 help 1301 Say Y here if you have a TPS6507x based touchscreen 1302 controller. 1303 1304 If unsure, say N. 1305 1306 To compile this driver as a module, choose M here: the 1307 module will be called tps6507x_ts. 1308 1309config TOUCHSCREEN_ZET6223 1310 tristate "Zeitec ZET6223 touchscreen driver" 1311 depends on I2C 1312 help 1313 Say Y here if you have a touchscreen using Zeitec ZET6223 1314 1315 If unsure, say N. 1316 1317 To compile this driver as a module, choose M here: the 1318 module will be called zet6223. 1319 1320config TOUCHSCREEN_ZFORCE 1321 tristate "Neonode zForce infrared touchscreens" 1322 depends on I2C 1323 depends on GPIOLIB || COMPILE_TEST 1324 help 1325 Say Y here if you have a touchscreen using the zforce 1326 infraread technology from Neonode. 1327 1328 If unsure, say N. 1329 1330 To compile this driver as a module, choose M here: the 1331 module will be called zforce_ts. 1332 1333config TOUCHSCREEN_COLIBRI_VF50 1334 tristate "Toradex Colibri on board touchscreen driver" 1335 depends on IIO 1336 depends on GPIOLIB || COMPILE_TEST 1337 help 1338 Say Y here if you have a Colibri VF50 and plan to use 1339 the on-board provided 4-wire touchscreen driver. 1340 1341 If unsure, say N. 1342 1343 To compile this driver as a module, choose M here: the 1344 module will be called colibri_vf50_ts. 1345 1346config TOUCHSCREEN_ROHM_BU21023 1347 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens" 1348 depends on I2C 1349 help 1350 Say Y here if you have a touchscreen using ROHM BU21023/24. 1351 1352 If unsure, say N. 1353 1354 To compile this driver as a module, choose M here: the 1355 module will be called bu21023_ts. 1356 1357config TOUCHSCREEN_IQS5XX 1358 tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller" 1359 depends on I2C 1360 help 1361 Say Y to enable support for the Azoteq IQS550/572/525 1362 family of trackpad/touchscreen controllers. 1363 1364 To compile this driver as a module, choose M here: the 1365 module will be called iqs5xx. 1366 1367config TOUCHSCREEN_ZINITIX 1368 tristate "Zinitix touchscreen support" 1369 depends on I2C 1370 help 1371 Say Y here if you have a touchscreen using Zinitix bt541, 1372 or something similar enough. 1373 1374 If unsure, say N. 1375 1376 To compile this driver as a module, choose M here: the 1377 module will be called zinitix. 1378 1379config TOUCHSCREEN_HIMAX_HX83112B 1380 tristate "Himax hx83112b touchscreen driver" 1381 depends on I2C 1382 select REGMAP_I2C 1383 help 1384 Say Y here to enable support for Himax hx83112b touchscreens. 1385 1386 If unsure, say N. 1387 1388 To compile this driver as a module, choose M here: the 1389 module will be called himax_hx83112b. 1390 1391endif 1392