1# 2# Touchscreen driver configuration 3# 4menuconfig INPUT_TOUCHSCREEN 5 bool "Touchscreens" 6 help 7 Say Y here, and a list of supported touchscreens will be displayed. 8 This option doesn't affect the kernel. 9 10 If unsure, say Y. 11 12if INPUT_TOUCHSCREEN 13 14config TOUCHSCREEN_88PM860X 15 tristate "Marvell 88PM860x touchscreen" 16 depends on MFD_88PM860X 17 help 18 Say Y here if you have a 88PM860x PMIC and want to enable 19 support for the built-in touchscreen. 20 21 If unsure, say N. 22 23 To compile this driver as a module, choose M here: the 24 module will be called 88pm860x-ts. 25 26config TOUCHSCREEN_ADS7846 27 tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens" 28 depends on SPI_MASTER 29 depends on HWMON = n || HWMON 30 help 31 Say Y here if you have a touchscreen interface using the 32 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller, 33 and your board-specific setup code includes that in its 34 table of SPI devices. 35 36 If HWMON is selected, and the driver is told the reference voltage 37 on your board, you will also get hwmon interfaces for the voltage 38 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip. 39 40 If unsure, say N (but it's safe to say "Y"). 41 42 To compile this driver as a module, choose M here: the 43 module will be called ads7846. 44 45config TOUCHSCREEN_AD7877 46 tristate "AD7877 based touchscreens" 47 depends on SPI_MASTER 48 help 49 Say Y here if you have a touchscreen interface using the 50 AD7877 controller, and your board-specific initialization 51 code includes that in its table of SPI devices. 52 53 If unsure, say N (but it's safe to say "Y"). 54 55 To compile this driver as a module, choose M here: the 56 module will be called ad7877. 57 58config TOUCHSCREEN_AD7879 59 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface" 60 help 61 Say Y here if you want to support a touchscreen interface using 62 the AD7879-1/AD7889-1 controller. 63 64 You should select a bus connection too. 65 66 To compile this driver as a module, choose M here: the 67 module will be called ad7879. 68 69config TOUCHSCREEN_AD7879_I2C 70 tristate "support I2C bus connection" 71 depends on TOUCHSCREEN_AD7879 && I2C 72 help 73 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus. 74 75 To compile this driver as a module, choose M here: the 76 module will be called ad7879-i2c. 77 78config TOUCHSCREEN_AD7879_SPI 79 tristate "support SPI bus connection" 80 depends on TOUCHSCREEN_AD7879 && SPI_MASTER 81 help 82 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus. 83 84 If unsure, say N (but it's safe to say "Y"). 85 86 To compile this driver as a module, choose M here: the 87 module will be called ad7879-spi. 88 89config TOUCHSCREEN_ATMEL_MXT 90 tristate "Atmel mXT I2C Touchscreen" 91 depends on I2C 92 help 93 Say Y here if you have Atmel mXT series I2C touchscreen, 94 such as AT42QT602240/ATMXT224, connected to your system. 95 96 If unsure, say N. 97 98 To compile this driver as a module, choose M here: the 99 module will be called atmel_mxt_ts. 100 101config TOUCHSCREEN_AUO_PIXCIR 102 tristate "AUO in-cell touchscreen using Pixcir ICs" 103 depends on I2C 104 depends on GPIOLIB 105 help 106 Say Y here if you have a AUO display with in-cell touchscreen 107 using Pixcir ICs. 108 109 If unsure, say N. 110 111 To compile this driver as a module, choose M here: the 112 module will be called auo-pixcir-ts. 113 114config TOUCHSCREEN_BITSY 115 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" 116 depends on SA1100_BITSY 117 select SERIO 118 help 119 Say Y here if you have the h3600 (Bitsy) touchscreen. 120 121 If unsure, say N. 122 123 To compile this driver as a module, choose M here: the 124 module will be called h3600_ts_input. 125 126config TOUCHSCREEN_BU21013 127 tristate "BU21013 based touch panel controllers" 128 depends on I2C 129 help 130 Say Y here if you have a bu21013 touchscreen connected to 131 your system. 132 133 If unsure, say N. 134 135 To compile this driver as a module, choose M here: the 136 module will be called bu21013_ts. 137 138config TOUCHSCREEN_CY8CTMG110 139 tristate "cy8ctmg110 touchscreen" 140 depends on I2C 141 depends on GPIOLIB 142 143 help 144 Say Y here if you have a cy8ctmg110 capacitive touchscreen on 145 an AAVA device. 146 147 If unsure, say N. 148 149 To compile this driver as a module, choose M here: the 150 module will be called cy8ctmg110_ts. 151 152config TOUCHSCREEN_DA9034 153 tristate "Touchscreen support for Dialog Semiconductor DA9034" 154 depends on PMIC_DA903X 155 default y 156 help 157 Say Y here to enable the support for the touchscreen found 158 on Dialog Semiconductor DA9034 PMIC. 159 160config TOUCHSCREEN_DYNAPRO 161 tristate "Dynapro serial touchscreen" 162 select SERIO 163 help 164 Say Y here if you have a Dynapro serial touchscreen connected to 165 your system. 166 167 If unsure, say N. 168 169 To compile this driver as a module, choose M here: the 170 module will be called dynapro. 171 172config TOUCHSCREEN_HAMPSHIRE 173 tristate "Hampshire serial touchscreen" 174 select SERIO 175 help 176 Say Y here if you have a Hampshire serial touchscreen connected to 177 your system. 178 179 If unsure, say N. 180 181 To compile this driver as a module, choose M here: the 182 module will be called hampshire. 183 184config TOUCHSCREEN_EETI 185 tristate "EETI touchscreen panel support" 186 depends on I2C 187 help 188 Say Y here to enable support for I2C connected EETI touch panels. 189 190 To compile this driver as a module, choose M here: the 191 module will be called eeti_ts. 192 193config TOUCHSCREEN_EGALAX 194 tristate "EETI eGalax multi-touch panel support" 195 depends on I2C 196 help 197 Say Y here to enable support for I2C connected EETI 198 eGalax multi-touch panels. 199 200 To compile this driver as a module, choose M here: the 201 module will be called egalax_ts. 202 203config TOUCHSCREEN_FUJITSU 204 tristate "Fujitsu serial touchscreen" 205 select SERIO 206 help 207 Say Y here if you have the Fujitsu touchscreen (such as one 208 installed in Lifebook P series laptop) connected to your 209 system. 210 211 If unsure, say N. 212 213 To compile this driver as a module, choose M here: the 214 module will be called fujitsu-ts. 215 216config TOUCHSCREEN_S3C2410 217 tristate "Samsung S3C2410/generic touchscreen input driver" 218 depends on ARCH_S3C2410 || SAMSUNG_DEV_TS 219 select S3C_ADC 220 help 221 Say Y here if you have the s3c2410 touchscreen. 222 223 If unsure, say N. 224 225 To compile this driver as a module, choose M here: the 226 module will be called s3c2410_ts. 227 228config TOUCHSCREEN_GUNZE 229 tristate "Gunze AHL-51S touchscreen" 230 select SERIO 231 help 232 Say Y here if you have the Gunze AHL-51 touchscreen connected to 233 your system. 234 235 If unsure, say N. 236 237 To compile this driver as a module, choose M here: the 238 module will be called gunze. 239 240config TOUCHSCREEN_ELO 241 tristate "Elo serial touchscreens" 242 select SERIO 243 help 244 Say Y here if you have an Elo serial touchscreen connected to 245 your system. 246 247 If unsure, say N. 248 249 To compile this driver as a module, choose M here: the 250 module will be called elo. 251 252config TOUCHSCREEN_WACOM_W8001 253 tristate "Wacom W8001 penabled serial touchscreen" 254 select SERIO 255 help 256 Say Y here if you have an Wacom W8001 penabled serial touchscreen 257 connected to your system. 258 259 If unsure, say N. 260 261 To compile this driver as a module, choose M here: the 262 module will be called wacom_w8001. 263 264config TOUCHSCREEN_LPC32XX 265 tristate "LPC32XX touchscreen controller" 266 depends on ARCH_LPC32XX 267 help 268 Say Y here if you have a LPC32XX device and want 269 to support the built-in touchscreen. 270 271 To compile this driver as a module, choose M here: the 272 module will be called lpc32xx_ts. 273 274config TOUCHSCREEN_MAX11801 275 tristate "MAX11801 based touchscreens" 276 depends on I2C 277 help 278 Say Y here if you have a MAX11801 based touchscreen 279 controller. 280 281 If unsure, say N. 282 283 To compile this driver as a module, choose M here: the 284 module will be called max11801_ts. 285 286config TOUCHSCREEN_MCS5000 287 tristate "MELFAS MCS-5000 touchscreen" 288 depends on I2C 289 help 290 Say Y here if you have the MELFAS MCS-5000 touchscreen controller 291 chip in your system. 292 293 If unsure, say N. 294 295 To compile this driver as a module, choose M here: the 296 module will be called mcs5000_ts. 297 298config TOUCHSCREEN_MTOUCH 299 tristate "MicroTouch serial touchscreens" 300 select SERIO 301 help 302 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 303 your system. 304 305 If unsure, say N. 306 307 To compile this driver as a module, choose M here: the 308 module will be called mtouch. 309 310config TOUCHSCREEN_INEXIO 311 tristate "iNexio serial touchscreens" 312 select SERIO 313 help 314 Say Y here if you have an iNexio serial touchscreen connected to 315 your system. 316 317 If unsure, say N. 318 319 To compile this driver as a module, choose M here: the 320 module will be called inexio. 321 322config TOUCHSCREEN_INTEL_MID 323 tristate "Intel MID platform resistive touchscreen" 324 depends on INTEL_SCU_IPC 325 help 326 Say Y here if you have a Intel MID based touchscreen in 327 your system. 328 329 If unsure, say N. 330 331 To compile this driver as a module, choose M here: the 332 module will be called intel_mid_touch. 333 334config TOUCHSCREEN_MK712 335 tristate "ICS MicroClock MK712 touchscreen" 336 help 337 Say Y here if you have the ICS MicroClock MK712 touchscreen 338 controller chip in your system. 339 340 If unsure, say N. 341 342 To compile this driver as a module, choose M here: the 343 module will be called mk712. 344 345config TOUCHSCREEN_HP600 346 tristate "HP Jornada 6xx touchscreen" 347 depends on SH_HP6XX && SH_ADC 348 help 349 Say Y here if you have a HP Jornada 620/660/680/690 and want to 350 support the built-in touchscreen. 351 352 To compile this driver as a module, choose M here: the 353 module will be called hp680_ts_input. 354 355config TOUCHSCREEN_HP7XX 356 tristate "HP Jornada 7xx touchscreen" 357 depends on SA1100_JORNADA720_SSP 358 help 359 Say Y here if you have a HP Jornada 710/720/728 and want 360 to support the built-in touchscreen. 361 362 To compile this driver as a module, choose M here: the 363 module will be called jornada720_ts. 364 365config TOUCHSCREEN_HTCPEN 366 tristate "HTC Shift X9500 touchscreen" 367 depends on ISA 368 help 369 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 370 Clio / Shangrila and want to support the built-in touchscreen. 371 372 If unsure, say N. 373 374 To compile this driver as a module, choose M here: the 375 module will be called htcpen. 376 377config TOUCHSCREEN_PENMOUNT 378 tristate "Penmount serial touchscreen" 379 select SERIO 380 help 381 Say Y here if you have a Penmount serial touchscreen connected to 382 your system. 383 384 If unsure, say N. 385 386 To compile this driver as a module, choose M here: the 387 module will be called penmount. 388 389config TOUCHSCREEN_MIGOR 390 tristate "Renesas MIGO-R touchscreen" 391 depends on SH_MIGOR && I2C 392 help 393 Say Y here to enable MIGO-R touchscreen support. 394 395 If unsure, say N. 396 397 To compile this driver as a module, choose M here: the 398 module will be called migor_ts. 399 400config TOUCHSCREEN_TNETV107X 401 tristate "TI TNETV107X touchscreen support" 402 depends on ARCH_DAVINCI_TNETV107X 403 help 404 Say Y here if you want to use the TNETV107X touchscreen. 405 406 To compile this driver as a module, choose M here: the 407 module will be called tnetv107x-ts. 408 409config TOUCHSCREEN_TOUCHRIGHT 410 tristate "Touchright serial touchscreen" 411 select SERIO 412 help 413 Say Y here if you have a Touchright serial touchscreen connected to 414 your system. 415 416 If unsure, say N. 417 418 To compile this driver as a module, choose M here: the 419 module will be called touchright. 420 421config TOUCHSCREEN_TOUCHWIN 422 tristate "Touchwin serial touchscreen" 423 select SERIO 424 help 425 Say Y here if you have a Touchwin serial touchscreen connected to 426 your system. 427 428 If unsure, say N. 429 430 To compile this driver as a module, choose M here: the 431 module will be called touchwin. 432 433config TOUCHSCREEN_ATMEL_TSADCC 434 tristate "Atmel Touchscreen Interface" 435 depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 436 help 437 Say Y here if you have a 4-wire touchscreen connected to the 438 ADC Controller on your Atmel SoC (such as the AT91SAM9RL). 439 440 If unsure, say N. 441 442 To compile this driver as a module, choose M here: the 443 module will be called atmel_tsadcc. 444 445config TOUCHSCREEN_UCB1400 446 tristate "Philips UCB1400 touchscreen" 447 depends on AC97_BUS 448 depends on UCB1400_CORE 449 help 450 This enables support for the Philips UCB1400 touchscreen interface. 451 The UCB1400 is an AC97 audio codec. The touchscreen interface 452 will be initialized only after the ALSA subsystem has been 453 brought up and the UCB1400 detected. You therefore have to 454 configure ALSA support as well (either built-in or modular, 455 independently of whether this driver is itself built-in or 456 modular) for this driver to work. 457 458 To compile this driver as a module, choose M here: the 459 module will be called ucb1400_ts. 460 461config TOUCHSCREEN_PIXCIR 462 tristate "PIXCIR I2C touchscreens" 463 depends on I2C 464 help 465 Say Y here if you have a pixcir i2c touchscreen 466 controller. 467 468 If unsure, say N. 469 470 To compile this driver as a module, choose M here: the 471 module will be called pixcir_i2c_ts. 472 473config TOUCHSCREEN_WM831X 474 tristate "Support for WM831x touchscreen controllers" 475 depends on MFD_WM831X 476 help 477 This enables support for the touchscreen controller on the WM831x 478 series of PMICs. 479 480 To compile this driver as a module, choose M here: the 481 module will be called wm831x-ts. 482 483config TOUCHSCREEN_WM97XX 484 tristate "Support for WM97xx AC97 touchscreen controllers" 485 depends on AC97_BUS 486 help 487 Say Y here if you have a Wolfson Microelectronics WM97xx 488 touchscreen connected to your system. Note that this option 489 only enables core driver, you will also need to select 490 support for appropriate chip below. 491 492 If unsure, say N. 493 494 To compile this driver as a module, choose M here: the 495 module will be called wm97xx-ts. 496 497config TOUCHSCREEN_WM9705 498 bool "WM9705 Touchscreen interface support" 499 depends on TOUCHSCREEN_WM97XX 500 default y 501 help 502 Say Y here to enable support for the Wolfson Microelectronics 503 WM9705 touchscreen controller. 504 505config TOUCHSCREEN_WM9712 506 bool "WM9712 Touchscreen interface support" 507 depends on TOUCHSCREEN_WM97XX 508 default y 509 help 510 Say Y here to enable support for the Wolfson Microelectronics 511 WM9712 touchscreen controller. 512 513config TOUCHSCREEN_WM9713 514 bool "WM9713 Touchscreen interface support" 515 depends on TOUCHSCREEN_WM97XX 516 default y 517 help 518 Say Y here to enable support for the Wolfson Microelectronics 519 WM9713 touchscreen controller. 520 521config TOUCHSCREEN_WM97XX_ATMEL 522 tristate "WM97xx Atmel accelerated touch" 523 depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91) 524 help 525 Say Y here for support for streaming mode with WM97xx touchscreens 526 on Atmel AT91 or AVR32 systems with an AC97C module. 527 528 Be aware that this will use channel B in the controller for 529 streaming data, this must not conflict with other AC97C drivers. 530 531 If unsure, say N. 532 533 To compile this driver as a module, choose M here: the module will 534 be called atmel-wm97xx. 535 536config TOUCHSCREEN_WM97XX_MAINSTONE 537 tristate "WM97xx Mainstone/Palm accelerated touch" 538 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 539 help 540 Say Y here for support for streaming mode with WM97xx touchscreens 541 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. 542 543 If unsure, say N. 544 545 To compile this driver as a module, choose M here: the 546 module will be called mainstone-wm97xx. 547 548config TOUCHSCREEN_WM97XX_ZYLONITE 549 tristate "Zylonite accelerated touch" 550 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 551 select TOUCHSCREEN_WM9713 552 help 553 Say Y here for support for streaming mode with the touchscreen 554 on Zylonite systems. 555 556 If unsure, say N. 557 558 To compile this driver as a module, choose M here: the 559 module will be called zylonite-wm97xx. 560 561config TOUCHSCREEN_USB_COMPOSITE 562 tristate "USB Touchscreen Driver" 563 depends on USB_ARCH_HAS_HCD 564 select USB 565 help 566 USB Touchscreen driver for: 567 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 568 - PanJit TouchSet USB 569 - 3M MicroTouch USB (EX II series) 570 - ITM 571 - some other eTurboTouch 572 - Gunze AHL61 573 - DMC TSC-10/25 574 - IRTOUCHSYSTEMS/UNITOP 575 - IdealTEK URTC1000 576 - GoTop Super_Q2/GogoPen/PenPower tablets 577 - JASTEC USB Touch Controller/DigiTech DTR-02U 578 - Zytronic controllers 579 - Elo TouchSystems 2700 IntelliTouch 580 581 Have a look at <http://linux.chapter7.ch/touchkit/> for 582 a usage description and the required user-space stuff. 583 584 To compile this driver as a module, choose M here: the 585 module will be called usbtouchscreen. 586 587config TOUCHSCREEN_MC13783 588 tristate "Freescale MC13783 touchscreen input driver" 589 depends on MFD_MC13783 590 help 591 Say Y here if you have an Freescale MC13783 PMIC on your 592 board and want to use its touchscreen 593 594 If unsure, say N. 595 596 To compile this driver as a module, choose M here: the 597 module will be called mc13783_ts. 598 599config TOUCHSCREEN_USB_EGALAX 600 default y 601 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT 602 depends on TOUCHSCREEN_USB_COMPOSITE 603 604config TOUCHSCREEN_USB_PANJIT 605 default y 606 bool "PanJit device support" if EXPERT 607 depends on TOUCHSCREEN_USB_COMPOSITE 608 609config TOUCHSCREEN_USB_3M 610 default y 611 bool "3M/Microtouch EX II series device support" if EXPERT 612 depends on TOUCHSCREEN_USB_COMPOSITE 613 614config TOUCHSCREEN_USB_ITM 615 default y 616 bool "ITM device support" if EXPERT 617 depends on TOUCHSCREEN_USB_COMPOSITE 618 619config TOUCHSCREEN_USB_ETURBO 620 default y 621 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT 622 depends on TOUCHSCREEN_USB_COMPOSITE 623 624config TOUCHSCREEN_USB_GUNZE 625 default y 626 bool "Gunze AHL61 device support" if EXPERT 627 depends on TOUCHSCREEN_USB_COMPOSITE 628 629config TOUCHSCREEN_USB_DMC_TSC10 630 default y 631 bool "DMC TSC-10/25 device support" if EXPERT 632 depends on TOUCHSCREEN_USB_COMPOSITE 633 634config TOUCHSCREEN_USB_IRTOUCH 635 default y 636 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT 637 depends on TOUCHSCREEN_USB_COMPOSITE 638 639config TOUCHSCREEN_USB_IDEALTEK 640 default y 641 bool "IdealTEK URTC1000 device support" if EXPERT 642 depends on TOUCHSCREEN_USB_COMPOSITE 643 644config TOUCHSCREEN_USB_GENERAL_TOUCH 645 default y 646 bool "GeneralTouch Touchscreen device support" if EXPERT 647 depends on TOUCHSCREEN_USB_COMPOSITE 648 649config TOUCHSCREEN_USB_GOTOP 650 default y 651 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT 652 depends on TOUCHSCREEN_USB_COMPOSITE 653 654config TOUCHSCREEN_USB_JASTEC 655 default y 656 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT 657 depends on TOUCHSCREEN_USB_COMPOSITE 658 659config TOUCHSCREEN_USB_ELO 660 default y 661 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT 662 depends on TOUCHSCREEN_USB_COMPOSITE 663 664config TOUCHSCREEN_USB_E2I 665 default y 666 bool "e2i Touchscreen controller (e.g. from Mimo 740)" 667 depends on TOUCHSCREEN_USB_COMPOSITE 668 669config TOUCHSCREEN_USB_ZYTRONIC 670 default y 671 bool "Zytronic controller" if EXPERT 672 depends on TOUCHSCREEN_USB_COMPOSITE 673 674config TOUCHSCREEN_USB_ETT_TC45USB 675 default y 676 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT 677 depends on TOUCHSCREEN_USB_COMPOSITE 678 679config TOUCHSCREEN_USB_NEXIO 680 default y 681 bool "NEXIO/iNexio device support" if EXPERT 682 depends on TOUCHSCREEN_USB_COMPOSITE 683 684config TOUCHSCREEN_TOUCHIT213 685 tristate "Sahara TouchIT-213 touchscreen" 686 select SERIO 687 help 688 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 689 690 If unsure, say N. 691 692 To compile this driver as a module, choose M here: the 693 module will be called touchit213. 694 695config TOUCHSCREEN_TSC_SERIO 696 tristate "TSC-10/25/40 serial touchscreen support" 697 select SERIO 698 help 699 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected 700 to your system. 701 702 If unsure, say N. 703 704 To compile this driver as a module, choose M here: the 705 module will be called tsc40. 706 707config TOUCHSCREEN_TSC2005 708 tristate "TSC2005 based touchscreens" 709 depends on SPI_MASTER && GENERIC_HARDIRQS 710 help 711 Say Y here if you have a TSC2005 based touchscreen. 712 713 If unsure, say N. 714 715 To compile this driver as a module, choose M here: the 716 module will be called tsc2005. 717 718config TOUCHSCREEN_TSC2007 719 tristate "TSC2007 based touchscreens" 720 depends on I2C 721 help 722 Say Y here if you have a TSC2007 based touchscreen. 723 724 If unsure, say N. 725 726 To compile this driver as a module, choose M here: the 727 module will be called tsc2007. 728 729config TOUCHSCREEN_W90X900 730 tristate "W90P910 touchscreen driver" 731 depends on HAVE_CLK 732 help 733 Say Y here if you have a W90P910 based touchscreen. 734 735 To compile this driver as a module, choose M here: the 736 module will be called w90p910_ts. 737 738config TOUCHSCREEN_PCAP 739 tristate "Motorola PCAP touchscreen" 740 depends on EZX_PCAP 741 help 742 Say Y here if you have a Motorola EZX telephone and 743 want to enable support for the built-in touchscreen. 744 745 To compile this driver as a module, choose M here: the 746 module will be called pcap_ts. 747 748config TOUCHSCREEN_ST1232 749 tristate "Sitronix ST1232 touchscreen controllers" 750 depends on I2C 751 help 752 Say Y here if you want to support Sitronix ST1232 753 touchscreen controller. 754 755 If unsure, say N. 756 757 To compile this driver as a module, choose M here: the 758 module will be called st1232_ts. 759 760config TOUCHSCREEN_STMPE 761 tristate "STMicroelectronics STMPE touchscreens" 762 depends on MFD_STMPE 763 help 764 Say Y here if you want support for STMicroelectronics 765 STMPE touchscreen controllers. 766 767 To compile this driver as a module, choose M here: the 768 module will be called stmpe-ts. 769 770config TOUCHSCREEN_TPS6507X 771 tristate "TPS6507x based touchscreens" 772 depends on I2C 773 help 774 Say Y here if you have a TPS6507x based touchscreen 775 controller. 776 777 If unsure, say N. 778 779 To compile this driver as a module, choose M here: the 780 module will be called tps6507x_ts. 781 782endif 783