Kconfig 35.4 KB
Newer Older
L
Linus Torvalds 已提交
1
#
2
# Touchscreen driver configuration
L
Linus Torvalds 已提交
3 4 5 6 7 8 9 10 11 12 13
#
menuconfig INPUT_TOUCHSCREEN
	bool "Touchscreens"
	help
	  Say Y here, and a list of supported touchscreens will be displayed.
	  This option doesn't affect the kernel.

	  If unsure, say Y.

if INPUT_TOUCHSCREEN

14
config TOUCHSCREEN_PROPERTIES
15
	def_tristate INPUT
16
	depends on INPUT
17

H
Haojian Zhuang 已提交
18 19 20 21 22 23 24 25 26 27 28 29
config TOUCHSCREEN_88PM860X
	tristate "Marvell 88PM860x touchscreen"
	depends on MFD_88PM860X
	help
	  Say Y here if you have a 88PM860x PMIC and want to enable
	  support for the built-in touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called 88pm860x-ts.

D
David Brownell 已提交
30
config TOUCHSCREEN_ADS7846
31
	tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
D
David Brownell 已提交
32
	depends on SPI_MASTER
33
	depends on HWMON = n || HWMON
D
David Brownell 已提交
34 35
	help
	  Say Y here if you have a touchscreen interface using the
36 37 38
	  ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
	  and your board-specific setup code includes that in its
	  table of SPI devices.
D
David Brownell 已提交
39

40 41
	  If HWMON is selected, and the driver is told the reference voltage
	  on your board, you will also get hwmon interfaces for the voltage
42
	  (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
43

D
David Brownell 已提交
44 45 46 47 48
	  If unsure, say N (but it's safe to say "Y").

	  To compile this driver as a module, choose M here: the
	  module will be called ads7846.

49 50 51 52 53 54 55 56 57 58 59 60 61
config TOUCHSCREEN_AD7877
	tristate "AD7877 based touchscreens"
	depends on SPI_MASTER
	help
	  Say Y here if you have a touchscreen interface using the
	  AD7877 controller, and your board-specific initialization
	  code includes that in its table of SPI devices.

	  If unsure, say N (but it's safe to say "Y").

	  To compile this driver as a module, choose M here: the
	  module will be called ad7877.

62 63
config TOUCHSCREEN_AD7879
	tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
64
	help
65 66
	  Say Y here if you want to support a touchscreen interface using
	  the AD7879-1/AD7889-1 controller.
67

68
	  You should select a bus connection too.
69 70 71 72

	  To compile this driver as a module, choose M here: the
	  module will be called ad7879.

73 74 75
config TOUCHSCREEN_AD7879_I2C
	tristate "support I2C bus connection"
	depends on TOUCHSCREEN_AD7879 && I2C
76
	select REGMAP_I2C
77 78 79 80 81 82
	help
	  Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called ad7879-i2c.

83
config TOUCHSCREEN_AD7879_SPI
84 85
	tristate "support SPI bus connection"
	depends on TOUCHSCREEN_AD7879 && SPI_MASTER
86
	select REGMAP_SPI
87
	help
88
	  Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
89 90 91 92

	  If unsure, say N (but it's safe to say "Y").

	  To compile this driver as a module, choose M here: the
93
	  module will be called ad7879-spi.
94

95 96 97 98 99 100 101 102 103 104 105 106 107
config TOUCHSCREEN_ADC
	tristate "Generic ADC based resistive touchscreen"
	depends on IIO
	select IIO_BUFFER_CB
	help
	  Say Y here if you want to use the generic ADC
	  resistive touchscreen driver.

	  If unsure, say N (but it's safe to say "Y").

	  To compile this driver as a module, choose M here: the
	  module will be called resistive-adc-touch.ko.

108
config TOUCHSCREEN_AR1021_I2C
109
	tristate "Microchip AR1020/1021 i2c touchscreen"
110 111
	depends on I2C && OF
	help
112 113
	  Say Y here if you have the Microchip AR1020 or AR1021 touchscreen
	  controller chip in your system.
114 115 116 117 118 119

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called ar1021_i2c.

120 121 122
config TOUCHSCREEN_ATMEL_MXT
	tristate "Atmel mXT I2C Touchscreen"
	depends on I2C
123
	select FW_LOADER
124 125 126 127 128 129 130 131 132
	help
	  Say Y here if you have Atmel mXT series I2C touchscreen,
	  such as AT42QT602240/ATMXT224, connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called atmel_mxt_ts.

133 134
config TOUCHSCREEN_ATMEL_MXT_T37
	bool "Support T37 Diagnostic Data"
135 136
	depends on TOUCHSCREEN_ATMEL_MXT
	depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m)
137
	select VIDEOBUF2_VMALLOC
138
	help
139 140
	  Say Y here if you want support to output data from the T37
	  Diagnostic Data object using a V4L device.
141

142 143 144
config TOUCHSCREEN_AUO_PIXCIR
	tristate "AUO in-cell touchscreen using Pixcir ICs"
	depends on I2C
145
	depends on GPIOLIB || COMPILE_TEST
146 147 148 149 150 151 152 153 154
	help
	  Say Y here if you have a AUO display with in-cell touchscreen
	  using Pixcir ICs.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called auo-pixcir-ts.

155 156 157 158 159 160 161 162 163 164 165 166
config TOUCHSCREEN_BU21013
	tristate "BU21013 based touch panel controllers"
	depends on I2C
	help
	  Say Y here if you have a bu21013 touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called bu21013_ts.

Z
Zhu Yi 已提交
167 168 169 170 171 172 173 174 175 176 177 178
config TOUCHSCREEN_BU21029
	tristate "Rohm BU21029 based touch panel controllers"
	depends on I2C
	help
	  Say Y here if you have a Rohm BU21029 touchscreen controller
	  connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called bu21029_ts.

179 180
config TOUCHSCREEN_CHIPONE_ICN8318
	tristate "chipone icn8318 touchscreen controller"
181
	depends on GPIOLIB || COMPILE_TEST
182 183 184 185 186 187 188 189 190 191
	depends on I2C
	depends on OF
	help
	  Say Y here if you have a ChipOne icn8318 based I2C touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called chipone_icn8318.

192 193 194 195 196 197 198 199 200 201 202
config TOUCHSCREEN_CHIPONE_ICN8505
	tristate "chipone icn8505 touchscreen controller"
	depends on I2C && ACPI
	help
	  Say Y here if you have a ChipOne icn8505 based I2C touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called chipone_icn8505.

203 204 205
config TOUCHSCREEN_CY8CTMG110
	tristate "cy8ctmg110 touchscreen"
	depends on I2C
206
	depends on GPIOLIB || COMPILE_TEST
207 208 209 210 211 212 213 214 215
	help
	  Say Y here if you have a cy8ctmg110 capacitive touchscreen on
	  an AAVA device.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called cy8ctmg110_ts.

216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246
config TOUCHSCREEN_CYTTSP_CORE
	tristate "Cypress TTSP touchscreen"
	help
	  Say Y here if you have a touchscreen using controller from
	  the Cypress TrueTouch(tm) Standard Product family connected
	  to your system. You will also need to select appropriate
	  bus connection below.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called cyttsp_core.

config TOUCHSCREEN_CYTTSP_I2C
	tristate "support I2C bus connection"
	depends on TOUCHSCREEN_CYTTSP_CORE && I2C
	help
	  Say Y here if the touchscreen is connected via I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called cyttsp_i2c.

config TOUCHSCREEN_CYTTSP_SPI
	tristate "support SPI bus connection"
	depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
	help
	  Say Y here if the touchscreen is connected via SPI bus.

	  To compile this driver as a module, choose M here: the
	  module will be called cyttsp_spi.

247 248 249 250 251 252 253 254 255 256 257 258
config TOUCHSCREEN_CYTTSP4_CORE
	tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
	help
	  Core driver for Cypress TrueTouch(tm) Standard Product
	  Generation4 touchscreen controllers.

	  Say Y here if you have a Cypress Gen4 touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here.

259 260 261 262 263 264 265 266 267
config TOUCHSCREEN_CYTTSP4_I2C
	tristate "support I2C bus connection"
	depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
	help
	  Say Y here if the touchscreen is connected via I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called cyttsp4_i2c.

268 269 270 271 272 273 274 275 276
config TOUCHSCREEN_CYTTSP4_SPI
	tristate "support SPI bus connection"
	depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
	help
	  Say Y here if the touchscreen is connected via SPI bus.

	  To compile this driver as a module, choose M here: the
	  module will be called cyttsp4_spi.

E
Eric Miao 已提交
277 278 279 280 281 282 283 284
config TOUCHSCREEN_DA9034
	tristate "Touchscreen support for Dialog Semiconductor DA9034"
	depends on PMIC_DA903X
	default y
	help
	  Say Y here to enable the support for the touchscreen found
	  on Dialog Semiconductor DA9034 PMIC.

285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301
	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called da9034-ts.

config TOUCHSCREEN_DA9052
	tristate "Dialog DA9052/DA9053 TSI"
	depends on PMIC_DA9052
	help
	  Say Y here to support the touchscreen found on Dialog Semiconductor
	  DA9052-BC and DA9053-AA/Bx PMICs.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called da9052_tsi.

302 303 304 305 306 307 308 309 310 311 312 313
config TOUCHSCREEN_DYNAPRO
	tristate "Dynapro serial touchscreen"
	select SERIO
	help
	  Say Y here if you have a Dynapro serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called dynapro.

314 315 316 317 318 319 320 321 322 323 324 325
config TOUCHSCREEN_HAMPSHIRE
	tristate "Hampshire serial touchscreen"
	select SERIO
	help
	  Say Y here if you have a Hampshire serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called hampshire.

326 327 328 329 330 331 332 333 334
config TOUCHSCREEN_EETI
	tristate "EETI touchscreen panel support"
	depends on I2C
	help
	  Say Y here to enable support for I2C connected EETI touch panels.

	  To compile this driver as a module, choose M here: the
	  module will be called eeti_ts.

335 336
config TOUCHSCREEN_EGALAX
	tristate "EETI eGalax multi-touch panel support"
337
	depends on I2C && OF
338 339 340 341 342 343 344
	help
	  Say Y here to enable support for I2C connected EETI
	  eGalax multi-touch panels.

	  To compile this driver as a module, choose M here: the
	  module will be called egalax_ts.

345 346 347 348 349 350 351 352 353 354
config TOUCHSCREEN_EGALAX_SERIAL
	tristate "EETI eGalax serial touchscreen"
	select SERIO
	help
	  Say Y here to enable support for serial connected EETI
	  eGalax touch panels.

	  To compile this driver as a module, choose M here: the
	  module will be called egalax_ts_serial.

355 356 357 358 359 360 361 362 363 364
config TOUCHSCREEN_EXC3000
	tristate "EETI EXC3000 multi-touch panel support"
	depends on I2C
	help
	  Say Y here to enable support for I2C connected EETI
	  EXC3000 multi-touch panels.

	  To compile this driver as a module, choose M here: the
	  module will be called exc3000.

365 366 367 368 369 370 371 372 373 374 375 376 377
config TOUCHSCREEN_FUJITSU
	tristate "Fujitsu serial touchscreen"
	select SERIO
	help
	  Say Y here if you have the Fujitsu touchscreen (such as one
	  installed in Lifebook P series laptop) connected to your
	  system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called fujitsu-ts.

378 379
config TOUCHSCREEN_GOODIX
	tristate "Goodix I2C touchscreen"
380
	depends on I2C
381
	depends on GPIOLIB || COMPILE_TEST
382 383 384
	help
	  Say Y here if you have the Goodix touchscreen (such as one
	  installed in Onda v975w tablets) connected to your
385 386
	  system. It also supports 5-finger chip models, which can be
	  found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
387 388 389 390 391 392

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called goodix.

393 394 395 396 397 398 399 400
config TOUCHSCREEN_HIDEEP
	tristate "HiDeep Touch IC"
	depends on I2C
	help
	  Say Y here if you have a touchscreen using HiDeep.

	  If unsure, say N.

401
	  To compile this driver as a module, choose M here : the
402 403
	  module will be called hideep_ts.

404 405 406 407 408 409 410 411 412 413 414 415 416 417 418
config TOUCHSCREEN_ILI210X
	tristate "Ilitek ILI210X based touchscreen"
	depends on I2C
	help
	  Say Y here if you have a ILI210X based touchscreen
	  controller. This driver supports models ILI2102,
	  ILI2102s, ILI2103, ILI2103s and ILI2105.
	  Such kind of chipsets can be found in Amazon Kindle Fire
	  touchscreens.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called ili210x.

419 420 421 422 423 424 425 426 427 428 429 430
config TOUCHSCREEN_IPROC
	tristate "IPROC touch panel driver support"
	depends on ARCH_BCM_IPROC || COMPILE_TEST
	help
	  Say Y here if you want to add support for the IPROC touch
	  controller to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called bcm_iproc_tsc.

431
config TOUCHSCREEN_S3C2410
432
	tristate "Samsung S3C2410/generic touchscreen input driver"
433
	depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
434
	depends on S3C_ADC
435 436 437 438 439 440 441 442
	help
	  Say Y here if you have the s3c2410 touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called s3c2410_ts.

443 444 445 446 447 448 449 450 451 452 453
config TOUCHSCREEN_S6SY761
	tristate "Samsung S6SY761 Touchscreen driver"
	depends on I2C
	help
	  Say Y if you have the Samsung S6SY761 driver

	  If unsure, say N

	  To compile this driver as module, choose M here: the
	  module will be called s6sy761.

L
Linus Torvalds 已提交
454 455 456 457 458 459 460 461 462 463 464 465
config TOUCHSCREEN_GUNZE
	tristate "Gunze AHL-51S touchscreen"
	select SERIO
	help
	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called gunze.

466 467 468 469 470 471 472 473 474 475 476 477
config TOUCHSCREEN_EKTF2127
	tristate "Elan eKTF2127 I2C touchscreen"
	depends on I2C
	help
	  Say Y here if you have an Elan eKTF2127 touchscreen
	  connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called ektf2127.

478 479 480 481 482 483 484 485 486 487 488 489
config TOUCHSCREEN_ELAN
	tristate "Elan eKTH I2C touchscreen"
	depends on I2C
	help
	  Say Y here if you have an Elan eKTH I2C touchscreen
	  connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called elants_i2c.

L
Linus Torvalds 已提交
490 491 492 493 494 495 496 497 498 499
config TOUCHSCREEN_ELO
	tristate "Elo serial touchscreens"
	select SERIO
	help
	  Say Y here if you have an Elo serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
500
	  module will be called elo.
L
Linus Torvalds 已提交
501

502 503 504 505 506 507 508 509 510 511 512 513
config TOUCHSCREEN_WACOM_W8001
	tristate "Wacom W8001 penabled serial touchscreen"
	select SERIO
	help
	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
	  connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called wacom_w8001.

514 515 516 517 518 519 520 521 522 523 524 525
config TOUCHSCREEN_WACOM_I2C
	tristate "Wacom Tablet support (I2C)"
	depends on I2C
	help
	  Say Y here if you want to use the I2C version of the Wacom
	  Pen Tablet.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the module
	  will be called wacom_i2c.

526 527 528 529 530 531 532 533 534 535
config TOUCHSCREEN_LPC32XX
	tristate "LPC32XX touchscreen controller"
	depends on ARCH_LPC32XX
	help
	  Say Y here if you have a LPC32XX device and want
	  to support the built-in touchscreen.

	  To compile this driver as a module, choose M here: the
	  module will be called lpc32xx_ts.

536 537 538 539 540 541 542 543 544 545 546 547
config TOUCHSCREEN_MAX11801
	tristate "MAX11801 based touchscreens"
	depends on I2C
	help
	  Say Y here if you have a MAX11801 based touchscreen
	  controller.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called max11801_ts.

548 549 550 551 552 553 554 555 556 557 558
config TOUCHSCREEN_MCS5000
	tristate "MELFAS MCS-5000 touchscreen"
	depends on I2C
	help
	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
	  chip in your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called mcs5000_ts.
559

560 561
config TOUCHSCREEN_MMS114
	tristate "MELFAS MMS114 touchscreen"
562
	depends on I2C
563 564 565 566 567 568 569 570 571
	help
	  Say Y here if you have the MELFAS MMS114 touchscreen controller
	  chip in your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called mms114.

572 573 574 575 576 577 578 579 580 581 582
config TOUCHSCREEN_MELFAS_MIP4
	tristate "MELFAS MIP4 Touchscreen"
	depends on I2C
	help
	  Say Y here if you have a MELFAS MIP4 Touchscreen device.

	  If unsure, say N.

	  To compile this driver as a module, choose M here:
	  the module will be called melfas_mip4.

L
Linus Torvalds 已提交
583 584 585 586 587 588 589 590 591 592 593 594
config TOUCHSCREEN_MTOUCH
	tristate "MicroTouch serial touchscreens"
	select SERIO
	help
	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called mtouch.

595 596 597 598 599 600 601 602 603 604 605 606
config TOUCHSCREEN_IMX6UL_TSC
	tristate "Freescale i.MX6UL touchscreen controller"
	depends on (OF && GPIOLIB) || COMPILE_TEST
	help
	  Say Y here if you have a Freescale i.MX6UL, and want to
	  use the internal touchscreen controller.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called imx6ul_tsc.

607 608 609 610 611 612 613 614 615 616 617 618
config TOUCHSCREEN_INEXIO
	tristate "iNexio serial touchscreens"
	select SERIO
	help
	  Say Y here if you have an iNexio serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called inexio.

L
Linus Torvalds 已提交
619 620 621 622 623 624 625 626 627 628 629 630
config TOUCHSCREEN_MK712
	tristate "ICS MicroClock MK712 touchscreen"
	help
	  Say Y here if you have the ICS MicroClock MK712 touchscreen
	  controller chip in your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called mk712.

config TOUCHSCREEN_HP600
631
	tristate "HP Jornada 6xx touchscreen"
632
	depends on SH_HP6XX && SH_ADC
L
Linus Torvalds 已提交
633
	help
634
	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
L
Linus Torvalds 已提交
635 636 637 638 639
          support the built-in touchscreen.

	  To compile this driver as a module, choose M here: the
	  module will be called hp680_ts_input.

640
config TOUCHSCREEN_HP7XX
641
	tristate "HP Jornada 7xx touchscreen"
642 643 644 645 646 647 648 649
	depends on SA1100_JORNADA720_SSP
	help
	  Say Y here if you have a HP Jornada 710/720/728 and want
	  to support the built-in touchscreen.

	  To compile this driver as a module, choose M here: the
	  module will be called jornada720_ts.

650 651 652 653 654 655 656 657 658 659 660 661
config TOUCHSCREEN_IPAQ_MICRO
	tristate "HP iPAQ Atmel Micro ASIC touchscreen"
	depends on MFD_IPAQ_MICRO
	help
	  Say Y here to enable support for the touchscreen attached to
	  the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called ipaq-micro-ts.

662 663 664 665 666 667 668 669 670 671 672 673
config TOUCHSCREEN_HTCPEN
	tristate "HTC Shift X9500 touchscreen"
	depends on ISA
	help
	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
	  Clio / Shangrila and want to support the built-in touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called htcpen.

674 675 676 677 678 679 680 681 682 683 684 685
config TOUCHSCREEN_PENMOUNT
	tristate "Penmount serial touchscreen"
	select SERIO
	help
	  Say Y here if you have a Penmount serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called penmount.

686 687 688 689 690 691 692 693 694 695 696 697 698
config TOUCHSCREEN_EDT_FT5X06
	tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
	depends on I2C
	help
	  Say Y here if you have an EDT "Polytouch" touchscreen based
	  on the FocalTech FT5x06 family of controllers connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called edt-ft5x06.

699 700 701 702 703 704 705 706 707 708 709 710
config TOUCHSCREEN_RASPBERRYPI_FW
	tristate "Raspberry Pi's firmware base touch screen support"
	depends on RASPBERRYPI_FIRMWARE || COMPILE_TEST
	help
	  Say Y here if you have the official Raspberry Pi 7 inch screen on
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called raspberrypi-ts.

711 712
config TOUCHSCREEN_MIGOR
	tristate "Renesas MIGO-R touchscreen"
713
	depends on (SH_MIGOR || COMPILE_TEST) && I2C
714 715 716 717 718 719 720 721
	help
	  Say Y here to enable MIGO-R touchscreen support.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called migor_ts.

722 723 724 725 726 727 728 729 730 731 732 733
config TOUCHSCREEN_TOUCHRIGHT
	tristate "Touchright serial touchscreen"
	select SERIO
	help
	  Say Y here if you have a Touchright serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called touchright.

734 735 736 737 738 739 740 741 742 743 744 745
config TOUCHSCREEN_TOUCHWIN
	tristate "Touchwin serial touchscreen"
	select SERIO
	help
	  Say Y here if you have a Touchwin serial touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called touchwin.

746
config TOUCHSCREEN_TI_AM335X_TSC
747
	tristate "TI Touchscreen Interface"
748
	depends on MFD_TI_AM335X_TSCADC
749 750 751 752 753 754 755
	help
	  Say Y here if you have 4/5/8 wire touchscreen controller
	  to be connected to the ADC controller on your TI AM335x SoC.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
756
	  module will be called ti_am335x_tsc.
757

758 759
config TOUCHSCREEN_UCB1400
	tristate "Philips UCB1400 touchscreen"
760
	depends on AC97_BUS
761
	depends on UCB1400_CORE
762 763 764 765 766 767 768 769 770 771 772 773
	help
	  This enables support for the Philips UCB1400 touchscreen interface.
	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
	  will be initialized only after the ALSA subsystem has been
	  brought up and the UCB1400 detected.  You therefore have to
	  configure ALSA support as well (either built-in or modular,
	  independently of whether this driver is itself built-in or
	  modular) for this driver to work.

	  To compile this driver as a module, choose M here: the
	  module will be called ucb1400_ts.

774 775 776 777 778 779 780 781 782 783 784 785
config TOUCHSCREEN_PIXCIR
	tristate "PIXCIR I2C touchscreens"
	depends on I2C
	help
	  Say Y here if you have a pixcir i2c touchscreen
	  controller.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called pixcir_i2c_ts.

786 787 788 789 790 791 792 793 794 795 796 797
config TOUCHSCREEN_WDT87XX_I2C
	tristate "Weida HiTech I2C touchscreen"
	depends on I2C
	help
	  Say Y here if you have a Weida WDT87XX I2C touchscreen
	  connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called wdt87xx_i2c.

798 799 800 801 802 803 804 805 806 807
config TOUCHSCREEN_WM831X
	tristate "Support for WM831x touchscreen controllers"
	depends on MFD_WM831X
	help
	  This enables support for the touchscreen controller on the WM831x
	  series of PMICs.

	  To compile this driver as a module, choose M here: the
	  module will be called wm831x-ts.

808 809
config TOUCHSCREEN_WM97XX
	tristate "Support for WM97xx AC97 touchscreen controllers"
810
	depends on AC97_BUS || AC97_BUS_NEW
811 812 813 814 815 816 817 818 819 820 821
	help
	  Say Y here if you have a Wolfson Microelectronics WM97xx
	  touchscreen connected to your system. Note that this option
	  only enables core driver, you will also need to select
	  support for appropriate chip below.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called wm97xx-ts.

822 823 824
config TOUCHSCREEN_WM9705
	bool "WM9705 Touchscreen interface support"
	depends on TOUCHSCREEN_WM97XX
825
	default y
826
	help
827 828
	  Say Y here to enable support for the Wolfson Microelectronics
	  WM9705 touchscreen controller.
829

830 831 832
config TOUCHSCREEN_WM9712
	bool "WM9712 Touchscreen interface support"
	depends on TOUCHSCREEN_WM97XX
833
	default y
834
	help
835 836
	  Say Y here to enable support for the Wolfson Microelectronics
	  WM9712 touchscreen controller.
837

838 839 840
config TOUCHSCREEN_WM9713
	bool "WM9713 Touchscreen interface support"
	depends on TOUCHSCREEN_WM97XX
841
	default y
842
	help
843 844
	  Say Y here to enable support for the Wolfson Microelectronics
	  WM9713 touchscreen controller.
845

846
config TOUCHSCREEN_WM97XX_MAINSTONE
847
	tristate "WM97xx Mainstone/Palm accelerated touch"
848 849 850
	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
	help
	  Say Y here for support for streaming mode with WM97xx touchscreens
851
	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
852 853 854 855 856 857

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called mainstone-wm97xx.

858 859 860 861 862 863 864 865 866 867 868 869 870
config TOUCHSCREEN_WM97XX_ZYLONITE
	tristate "Zylonite accelerated touch"
	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
	select TOUCHSCREEN_WM9713
	help
	  Say Y here for support for streaming mode with the touchscreen
	  on Zylonite systems.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called zylonite-wm97xx.

871 872
config TOUCHSCREEN_USB_COMPOSITE
	tristate "USB Touchscreen Driver"
873
	depends on USB_ARCH_HAS_HCD
874 875 876 877 878 879 880 881 882 883
	select USB
	help
	  USB Touchscreen driver for:
	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
	  - PanJit TouchSet USB
	  - 3M MicroTouch USB (EX II series)
	  - ITM
	  - some other eTurboTouch
	  - Gunze AHL61
	  - DMC TSC-10/25
884
	  - IRTOUCHSYSTEMS/UNITOP
885
	  - IdealTEK URTC1000
886
	  - GoTop Super_Q2/GogoPen/PenPower tablets
887
	  - JASTEC USB Touch Controller/DigiTech DTR-02U
888
	  - Zytronic controllers
889
	  - Elo TouchSystems 2700 IntelliTouch
890
	  - EasyTouch USB Touch Controller from Data Modul
891
	  - e2i (Mimo monitors)
892 893 894 895 896 897 898

	  Have a look at <http://linux.chapter7.ch/touchkit/> for
	  a usage description and the required user-space stuff.

	  To compile this driver as a module, choose M here: the
	  module will be called usbtouchscreen.

899 900 901 902 903 904 905 906 907 908
config TOUCHSCREEN_MXS_LRADC
	tristate "Freescale i.MX23/i.MX28 LRADC touchscreen"
	depends on MFD_MXS_LRADC
	help
	  Say Y here if you have a touchscreen connected to the low-resolution
	  analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.

	  To compile this driver as a module, choose M here: the module will be
	  called mxs-lradc-ts.

909 910 911 912 913 914 915 916 917
config TOUCHSCREEN_MX25
	tristate "Freescale i.MX25 touchscreen input driver"
	depends on MFD_MX25_TSADC
	help
	  Enable support for touchscreen connected to your i.MX25.

	  To compile this driver as a module, choose M here: the
	  module will be called fsl-imx25-tcq.

918 919
config TOUCHSCREEN_MC13783
	tristate "Freescale MC13783 touchscreen input driver"
920
	depends on MFD_MC13XXX
921 922 923 924 925 926 927 928 929
	help
	  Say Y here if you have an Freescale MC13783 PMIC on your
	  board and want to use its touchscreen

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called mc13783_ts.

930 931
config TOUCHSCREEN_USB_EGALAX
	default y
932
	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
933 934 935 936
	depends on TOUCHSCREEN_USB_COMPOSITE

config TOUCHSCREEN_USB_PANJIT
	default y
937
	bool "PanJit device support" if EXPERT
938 939 940 941
	depends on TOUCHSCREEN_USB_COMPOSITE

config TOUCHSCREEN_USB_3M
	default y
942
	bool "3M/Microtouch EX II series device support" if EXPERT
943 944 945 946
	depends on TOUCHSCREEN_USB_COMPOSITE

config TOUCHSCREEN_USB_ITM
	default y
947
	bool "ITM device support" if EXPERT
948 949 950 951
	depends on TOUCHSCREEN_USB_COMPOSITE

config TOUCHSCREEN_USB_ETURBO
	default y
952
	bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
953 954 955 956
	depends on TOUCHSCREEN_USB_COMPOSITE

config TOUCHSCREEN_USB_GUNZE
	default y
957
	bool "Gunze AHL61 device support" if EXPERT
958 959 960 961
	depends on TOUCHSCREEN_USB_COMPOSITE

config TOUCHSCREEN_USB_DMC_TSC10
	default y
962
	bool "DMC TSC-10/25 device support" if EXPERT
963 964
	depends on TOUCHSCREEN_USB_COMPOSITE

965 966
config TOUCHSCREEN_USB_IRTOUCH
	default y
967
	bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
968 969
	depends on TOUCHSCREEN_USB_COMPOSITE

970 971
config TOUCHSCREEN_USB_IDEALTEK
	default y
972
	bool "IdealTEK URTC1000 device support" if EXPERT
973 974
	depends on TOUCHSCREEN_USB_COMPOSITE

975 976
config TOUCHSCREEN_USB_GENERAL_TOUCH
	default y
977
	bool "GeneralTouch Touchscreen device support" if EXPERT
978 979
	depends on TOUCHSCREEN_USB_COMPOSITE

980 981
config TOUCHSCREEN_USB_GOTOP
	default y
982
	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
983 984
	depends on TOUCHSCREEN_USB_COMPOSITE

985 986
config TOUCHSCREEN_USB_JASTEC
	default y
987
	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
988 989
	depends on TOUCHSCREEN_USB_COMPOSITE

990 991 992 993 994
config TOUCHSCREEN_USB_ELO
	default y
	bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
	depends on TOUCHSCREEN_USB_COMPOSITE

995 996
config TOUCHSCREEN_USB_E2I
	default y
997
	bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
998 999
	depends on TOUCHSCREEN_USB_COMPOSITE

1000 1001
config TOUCHSCREEN_USB_ZYTRONIC
	default y
1002
	bool "Zytronic controller" if EXPERT
1003 1004
	depends on TOUCHSCREEN_USB_COMPOSITE

1005
config TOUCHSCREEN_USB_ETT_TC45USB
1006
	default y
1007
	bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
1008 1009
	depends on TOUCHSCREEN_USB_COMPOSITE

1010 1011
config TOUCHSCREEN_USB_NEXIO
	default y
1012
	bool "NEXIO/iNexio device support" if EXPERT
1013 1014
	depends on TOUCHSCREEN_USB_COMPOSITE

1015 1016
config TOUCHSCREEN_USB_EASYTOUCH
	default y
1017
	bool "EasyTouch USB Touch controller device support" if EXPERT
1018 1019
	depends on TOUCHSCREEN_USB_COMPOSITE
	help
S
Shawn Landden 已提交
1020
	  Say Y here if you have an EasyTouch USB Touch controller.
1021 1022
	  If unsure, say N.

1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033
config TOUCHSCREEN_TOUCHIT213
	tristate "Sahara TouchIT-213 touchscreen"
	select SERIO
	help
	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called touchit213.

1034 1035 1036
config TOUCHSCREEN_TS4800
	tristate "TS-4800 touchscreen"
	depends on HAS_IOMEM && OF
1037
	depends on SOC_IMX51 || COMPILE_TEST
1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050
	select MFD_SYSCON
	select INPUT_POLLDEV
	help
	  Say Y here if you have a touchscreen on a TS-4800 board.

	  On TS-4800, the touchscreen is not handled directly by Linux but by
	  a companion FPGA.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called ts4800_ts.

1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062
config TOUCHSCREEN_TSC_SERIO
	tristate "TSC-10/25/40 serial touchscreen support"
	select SERIO
	help
	  Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
	  to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called tsc40.

1063 1064 1065
config TOUCHSCREEN_TSC200X_CORE
	tristate

1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078
config TOUCHSCREEN_TSC2004
	tristate "TSC2004 based touchscreens"
	depends on I2C
	select REGMAP_I2C
	select TOUCHSCREEN_TSC200X_CORE
	help
	  Say Y here if you have a TSC2004 based touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called tsc2004.

1079
config TOUCHSCREEN_TSC2005
1080 1081
	tristate "TSC2005 based touchscreens"
	depends on SPI_MASTER
1082
	select REGMAP_SPI
1083
	select TOUCHSCREEN_TSC200X_CORE
1084 1085
	help
	  Say Y here if you have a TSC2005 based touchscreen.
1086 1087 1088 1089 1090 1091

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called tsc2005.

1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102
config TOUCHSCREEN_TSC2007
	tristate "TSC2007 based touchscreens"
	depends on I2C
	help
	  Say Y here if you have a TSC2007 based touchscreen.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called tsc2007.

1103 1104 1105 1106 1107 1108 1109 1110 1111 1112
config TOUCHSCREEN_TSC2007_IIO
	bool "IIO interface for external ADC input and temperature"
	depends on TOUCHSCREEN_TSC2007
	depends on IIO=y || IIO=TOUCHSCREEN_TSC2007
	help
	  Saying Y here adds an iio interface to the tsc2007 which
	  provides values for the AUX input (used for e.g. battery
	  or ambient light monitoring), temperature and raw input
	  values.

1113 1114
config TOUCHSCREEN_W90X900
	tristate "W90P910 touchscreen driver"
1115
	depends on ARCH_W90X900
1116 1117 1118 1119 1120 1121
	help
	  Say Y here if you have a W90P910 based touchscreen.

	  To compile this driver as a module, choose M here: the
	  module will be called w90p910_ts.

1122 1123 1124 1125 1126 1127 1128 1129 1130
config TOUCHSCREEN_PCAP
	tristate "Motorola PCAP touchscreen"
	depends on EZX_PCAP
	help
	  Say Y here if you have a Motorola EZX telephone and
	  want to enable support for the built-in touchscreen.

	  To compile this driver as a module, choose M here: the
	  module will be called pcap_ts.
1131

1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144
config TOUCHSCREEN_RM_TS
	tristate "Raydium I2C Touchscreen"
	depends on I2C
	depends on GPIOLIB || COMPILE_TEST
	help
	  Say Y here if you have Raydium series I2C touchscreen,
	  such as RM32380, connected to your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called raydium_i2c_ts.

1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156
config TOUCHSCREEN_SILEAD
	tristate "Silead I2C touchscreen"
	depends on I2C
	help
	  Say Y here if you have the Silead touchscreen connected to
	  your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called silead.

1157 1158 1159
config TOUCHSCREEN_SIS_I2C
	tristate "SiS 9200 family I2C touchscreen"
	depends on I2C
1160
	select CRC_ITU_T
1161 1162 1163 1164 1165 1166 1167 1168 1169
	depends on GPIOLIB || COMPILE_TEST
	help
	  This enables support for SiS 9200 family over I2C based touchscreens.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called sis_i2c.

1170 1171
config TOUCHSCREEN_ST1232
	tristate "Sitronix ST1232 touchscreen controllers"
1172 1173
	depends on I2C
	help
1174 1175
	  Say Y here if you want to support Sitronix ST1232
	  touchscreen controller.
1176 1177 1178 1179

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
1180
	  module will be called st1232_ts.
1181

1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192
config TOUCHSCREEN_STMFTS
	tristate "STMicroelectronics STMFTS touchscreen"
	depends on I2C
	depends on LEDS_CLASS
	help
	  Say Y here if you want support for STMicroelectronics
	  STMFTS touchscreen.

	  To compile this driver as a module, choose M here: the
	  module will be called stmfts.

1193 1194 1195
config TOUCHSCREEN_STMPE
	tristate "STMicroelectronics STMPE touchscreens"
	depends on MFD_STMPE
1196
	depends on (OF || COMPILE_TEST)
1197 1198 1199 1200 1201 1202 1203
	help
	  Say Y here if you want support for STMicroelectronics
	  STMPE touchscreen controllers.

	  To compile this driver as a module, choose M here: the
	  module will be called stmpe-ts.

1204 1205 1206
config TOUCHSCREEN_SUN4I
	tristate "Allwinner sun4i resistive touchscreen controller support"
	depends on ARCH_SUNXI || COMPILE_TEST
1207
	depends on HWMON
1208
	depends on THERMAL || !THERMAL_OF
1209 1210 1211 1212 1213 1214 1215
	help
	  This selects support for the resistive touchscreen controller
	  found on Allwinner sunxi SoCs.

	  To compile this driver as a module, choose M here: the
	  module will be called sun4i-ts.

1216 1217
config TOUCHSCREEN_SUR40
	tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1218
	depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1219
	depends on VIDEO_V4L2
1220
	select INPUT_POLLDEV
1221
	select VIDEOBUF2_DMA_SG
1222 1223 1224 1225 1226 1227 1228
	help
	  Say Y here if you want support for the Samsung SUR40 touchscreen
	  (also known as Microsoft Surface 2.0 or Microsoft PixelSense).

	  To compile this driver as a module, choose M here: the
	  module will be called sur40.

1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241
config TOUCHSCREEN_SURFACE3_SPI
	tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
	depends on SPI
	depends on GPIOLIB || COMPILE_TEST
	help
	  Say Y here if you have the Ntrig/Microsoft SPI touchscreen
	  controller chip as found on the Surface 3 in your system.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called surface3_spi.

1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252
config TOUCHSCREEN_SX8654
	tristate "Semtech SX8654 touchscreen"
	depends on I2C
	help
	  Say Y here if you have a Semtech SX8654 touchscreen controller.

	  If unsure, say N

	  To compile this driver as a module, choose M here: the
	  module will be called sx8654.

1253 1254 1255
config TOUCHSCREEN_TPS6507X
	tristate "TPS6507x based touchscreens"
	depends on I2C
1256
	select INPUT_POLLDEV
1257 1258 1259 1260 1261 1262 1263 1264 1265
	help
	  Say Y here if you have a TPS6507x based touchscreen
	  controller.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called tps6507x_ts.

1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276
config TOUCHSCREEN_ZET6223
	tristate "Zeitec ZET6223 touchscreen driver"
	depends on I2C
	help
	  Say Y here if you have a touchscreen using Zeitec ZET6223

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called zet6223.

1277 1278 1279
config TOUCHSCREEN_ZFORCE
	tristate "Neonode zForce infrared touchscreens"
	depends on I2C
1280
	depends on GPIOLIB || COMPILE_TEST
1281 1282 1283 1284 1285 1286 1287 1288 1289
	help
	  Say Y here if you have a touchscreen using the zforce
	  infraread technology from Neonode.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called zforce_ts.

1290 1291
config TOUCHSCREEN_COLIBRI_VF50
	tristate "Toradex Colibri on board touchscreen driver"
1292 1293
	depends on IIO && VF610_ADC
	depends on GPIOLIB || COMPILE_TEST
1294 1295 1296 1297 1298 1299 1300 1301 1302
	help
	  Say Y here if you have a Colibri VF50 and plan to use
	  the on-board provided 4-wire touchscreen driver.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called colibri_vf50_ts.

1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313
config TOUCHSCREEN_ROHM_BU21023
	tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
	depends on I2C
	help
	  Say Y here if you have a touchscreen using ROHM BU21023/24.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
	  module will be called bu21023_ts.

L
Linus Torvalds 已提交
1314
endif