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