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_ADS7846 15 tristate "ADS7846/TSC2046 and ADS7843 based touchscreens" 16 depends on SPI_MASTER 17 depends on HWMON = n || HWMON 18 help 19 Say Y here if you have a touchscreen interface using the 20 ADS7846/TSC2046 or ADS7843 controller, and your board-specific 21 setup code includes that in its table of SPI devices. 22 23 If HWMON is selected, and the driver is told the reference voltage 24 on your board, you will also get hwmon interfaces for the voltage 25 (and on ads7846/tsc2046, temperature) sensors of this chip. 26 27 If unsure, say N (but it's safe to say "Y"). 28 29 To compile this driver as a module, choose M here: the 30 module will be called ads7846. 31 32config TOUCHSCREEN_AD7877 33 tristate "AD7877 based touchscreens" 34 depends on SPI_MASTER 35 help 36 Say Y here if you have a touchscreen interface using the 37 AD7877 controller, and your board-specific initialization 38 code includes that in its table of SPI devices. 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 ad7877. 44 45config TOUCHSCREEN_AD7879_I2C 46 tristate "AD7879 based touchscreens: AD7879-1 I2C Interface" 47 depends on I2C 48 select TOUCHSCREEN_AD7879 49 help 50 Say Y here if you have a touchscreen interface using the 51 AD7879-1 controller, and your board-specific initialization 52 code includes that in its table of I2C 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 ad7879. 58 59config TOUCHSCREEN_AD7879_SPI 60 tristate "AD7879 based touchscreens: AD7879 SPI Interface" 61 depends on SPI_MASTER && TOUCHSCREEN_AD7879_I2C = n 62 select TOUCHSCREEN_AD7879 63 help 64 Say Y here if you have a touchscreen interface using the 65 AD7879 controller, and your board-specific initialization 66 code includes that in its table of SPI devices. 67 68 If unsure, say N (but it's safe to say "Y"). 69 70 To compile this driver as a module, choose M here: the 71 module will be called ad7879. 72 73config TOUCHSCREEN_AD7879 74 tristate 75 default n 76 77config TOUCHSCREEN_BITSY 78 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" 79 depends on SA1100_BITSY 80 select SERIO 81 help 82 Say Y here if you have the h3600 (Bitsy) touchscreen. 83 84 If unsure, say N. 85 86 To compile this driver as a module, choose M here: the 87 module will be called h3600_ts_input. 88 89config TOUCHSCREEN_CORGI 90 tristate "SharpSL (Corgi and Spitz series) touchscreen driver (DEPRECATED)" 91 depends on PXA_SHARPSL 92 select CORGI_SSP_DEPRECATED 93 default y 94 help 95 Say Y here to enable the driver for the touchscreen on the 96 Sharp SL-C7xx and SL-Cxx00 series of PDAs. 97 98 If unsure, say N. 99 100 To compile this driver as a module, choose M here: the 101 module will be called corgi_ts. 102 103 NOTE: this driver is deprecated, try enable SPI and generic 104 ADS7846-based touchscreen driver. 105 106config TOUCHSCREEN_DA9034 107 tristate "Touchscreen support for Dialog Semiconductor DA9034" 108 depends on PMIC_DA903X 109 default y 110 help 111 Say Y here to enable the support for the touchscreen found 112 on Dialog Semiconductor DA9034 PMIC. 113 114config TOUCHSCREEN_FUJITSU 115 tristate "Fujitsu serial touchscreen" 116 select SERIO 117 help 118 Say Y here if you have the Fujitsu touchscreen (such as one 119 installed in Lifebook P series laptop) connected to your 120 system. 121 122 If unsure, say N. 123 124 To compile this driver as a module, choose M here: the 125 module will be called fujitsu-ts. 126 127config TOUCHSCREEN_GUNZE 128 tristate "Gunze AHL-51S touchscreen" 129 select SERIO 130 help 131 Say Y here if you have the Gunze AHL-51 touchscreen connected to 132 your system. 133 134 If unsure, say N. 135 136 To compile this driver as a module, choose M here: the 137 module will be called gunze. 138 139config TOUCHSCREEN_ELO 140 tristate "Elo serial touchscreens" 141 select SERIO 142 help 143 Say Y here if you have an Elo serial touchscreen connected to 144 your system. 145 146 If unsure, say N. 147 148 To compile this driver as a module, choose M here: the 149 module will be called elo. 150 151config TOUCHSCREEN_WACOM_W8001 152 tristate "Wacom W8001 penabled serial touchscreen" 153 select SERIO 154 help 155 Say Y here if you have an Wacom W8001 penabled serial touchscreen 156 connected to your system. 157 158 If unsure, say N. 159 160 To compile this driver as a module, choose M here: the 161 module will be called wacom_w8001. 162 163 164config TOUCHSCREEN_MTOUCH 165 tristate "MicroTouch serial touchscreens" 166 select SERIO 167 help 168 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 169 your system. 170 171 If unsure, say N. 172 173 To compile this driver as a module, choose M here: the 174 module will be called mtouch. 175 176config TOUCHSCREEN_INEXIO 177 tristate "iNexio serial touchscreens" 178 select SERIO 179 help 180 Say Y here if you have an iNexio serial touchscreen connected to 181 your system. 182 183 If unsure, say N. 184 185 To compile this driver as a module, choose M here: the 186 module will be called inexio. 187 188config TOUCHSCREEN_MK712 189 tristate "ICS MicroClock MK712 touchscreen" 190 help 191 Say Y here if you have the ICS MicroClock MK712 touchscreen 192 controller chip in your system. 193 194 If unsure, say N. 195 196 To compile this driver as a module, choose M here: the 197 module will be called mk712. 198 199config TOUCHSCREEN_HP600 200 tristate "HP Jornada 6xx touchscreen" 201 depends on SH_HP6XX && SH_ADC 202 help 203 Say Y here if you have a HP Jornada 620/660/680/690 and want to 204 support the built-in touchscreen. 205 206 To compile this driver as a module, choose M here: the 207 module will be called hp680_ts_input. 208 209config TOUCHSCREEN_HP7XX 210 tristate "HP Jornada 7xx touchscreen" 211 depends on SA1100_JORNADA720_SSP 212 help 213 Say Y here if you have a HP Jornada 710/720/728 and want 214 to support the built-in touchscreen. 215 216 To compile this driver as a module, choose M here: the 217 module will be called jornada720_ts. 218 219config TOUCHSCREEN_HTCPEN 220 tristate "HTC Shift X9500 touchscreen" 221 depends on ISA 222 help 223 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 224 Clio / Shangrila and want to support the built-in touchscreen. 225 226 If unsure, say N. 227 228 To compile this driver as a module, choose M here: the 229 module will be called htcpen. 230 231config TOUCHSCREEN_PENMOUNT 232 tristate "Penmount serial touchscreen" 233 select SERIO 234 help 235 Say Y here if you have a Penmount serial touchscreen connected to 236 your system. 237 238 If unsure, say N. 239 240 To compile this driver as a module, choose M here: the 241 module will be called penmount. 242 243config TOUCHSCREEN_MIGOR 244 tristate "Renesas MIGO-R touchscreen" 245 depends on SH_MIGOR && I2C 246 help 247 Say Y here to enable MIGO-R touchscreen support. 248 249 If unsure, say N. 250 251 To compile this driver as a module, choose M here: the 252 module will be called migor_ts. 253 254config TOUCHSCREEN_TOUCHRIGHT 255 tristate "Touchright serial touchscreen" 256 select SERIO 257 help 258 Say Y here if you have a Touchright serial touchscreen connected to 259 your system. 260 261 If unsure, say N. 262 263 To compile this driver as a module, choose M here: the 264 module will be called touchright. 265 266config TOUCHSCREEN_TOUCHWIN 267 tristate "Touchwin serial touchscreen" 268 select SERIO 269 help 270 Say Y here if you have a Touchwin serial touchscreen connected to 271 your system. 272 273 If unsure, say N. 274 275 To compile this driver as a module, choose M here: the 276 module will be called touchwin. 277 278config TOUCHSCREEN_ATMEL_TSADCC 279 tristate "Atmel Touchscreen Interface" 280 depends on ARCH_AT91SAM9RL 281 help 282 Say Y here if you have a 4-wire touchscreen connected to the 283 ADC Controller on your Atmel SoC (such as the AT91SAM9RL). 284 285 If unsure, say N. 286 287 To compile this driver as a module, choose M here: the 288 module will be called atmel_tsadcc. 289 290config TOUCHSCREEN_UCB1400 291 tristate "Philips UCB1400 touchscreen" 292 depends on AC97_BUS 293 depends on UCB1400_CORE 294 help 295 This enables support for the Philips UCB1400 touchscreen interface. 296 The UCB1400 is an AC97 audio codec. The touchscreen interface 297 will be initialized only after the ALSA subsystem has been 298 brought up and the UCB1400 detected. You therefore have to 299 configure ALSA support as well (either built-in or modular, 300 independently of whether this driver is itself built-in or 301 modular) for this driver to work. 302 303 To compile this driver as a module, choose M here: the 304 module will be called ucb1400_ts. 305 306config TOUCHSCREEN_WM97XX 307 tristate "Support for WM97xx AC97 touchscreen controllers" 308 depends on AC97_BUS 309 help 310 Say Y here if you have a Wolfson Microelectronics WM97xx 311 touchscreen connected to your system. Note that this option 312 only enables core driver, you will also need to select 313 support for appropriate chip below. 314 315 If unsure, say N. 316 317 To compile this driver as a module, choose M here: the 318 module will be called wm97xx-ts. 319 320config TOUCHSCREEN_WM9705 321 bool "WM9705 Touchscreen interface support" 322 depends on TOUCHSCREEN_WM97XX 323 default y 324 help 325 Say Y here to enable support for the Wolfson Microelectronics 326 WM9705 touchscreen controller. 327 328config TOUCHSCREEN_WM9712 329 bool "WM9712 Touchscreen interface support" 330 depends on TOUCHSCREEN_WM97XX 331 default y 332 help 333 Say Y here to enable support for the Wolfson Microelectronics 334 WM9712 touchscreen controller. 335 336config TOUCHSCREEN_WM9713 337 bool "WM9713 Touchscreen interface support" 338 depends on TOUCHSCREEN_WM97XX 339 default y 340 help 341 Say Y here to enable support for the Wolfson Microelectronics 342 WM9713 touchscreen controller. 343 344config TOUCHSCREEN_WM97XX_MAINSTONE 345 tristate "WM97xx Mainstone accelerated touch" 346 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 347 help 348 Say Y here for support for streaming mode with WM97xx touchscreens 349 on Mainstone systems. 350 351 If unsure, say N. 352 353 To compile this driver as a module, choose M here: the 354 module will be called mainstone-wm97xx. 355 356config TOUCHSCREEN_WM97XX_ZYLONITE 357 tristate "Zylonite accelerated touch" 358 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE 359 select TOUCHSCREEN_WM9713 360 help 361 Say Y here for support for streaming mode with the touchscreen 362 on Zylonite systems. 363 364 If unsure, say N. 365 366 To compile this driver as a module, choose M here: the 367 module will be called zylonite-wm97xx. 368 369config TOUCHSCREEN_USB_COMPOSITE 370 tristate "USB Touchscreen Driver" 371 depends on USB_ARCH_HAS_HCD 372 select USB 373 help 374 USB Touchscreen driver for: 375 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 376 - PanJit TouchSet USB 377 - 3M MicroTouch USB (EX II series) 378 - ITM 379 - some other eTurboTouch 380 - Gunze AHL61 381 - DMC TSC-10/25 382 - IRTOUCHSYSTEMS/UNITOP 383 - IdealTEK URTC1000 384 - GoTop Super_Q2/GogoPen/PenPower tablets 385 386 Have a look at <http://linux.chapter7.ch/touchkit/> for 387 a usage description and the required user-space stuff. 388 389 To compile this driver as a module, choose M here: the 390 module will be called usbtouchscreen. 391 392config TOUCHSCREEN_USB_EGALAX 393 default y 394 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED 395 depends on TOUCHSCREEN_USB_COMPOSITE 396 397config TOUCHSCREEN_USB_PANJIT 398 default y 399 bool "PanJit device support" if EMBEDDED 400 depends on TOUCHSCREEN_USB_COMPOSITE 401 402config TOUCHSCREEN_USB_3M 403 default y 404 bool "3M/Microtouch EX II series device support" if EMBEDDED 405 depends on TOUCHSCREEN_USB_COMPOSITE 406 407config TOUCHSCREEN_USB_ITM 408 default y 409 bool "ITM device support" if EMBEDDED 410 depends on TOUCHSCREEN_USB_COMPOSITE 411 412config TOUCHSCREEN_USB_ETURBO 413 default y 414 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED 415 depends on TOUCHSCREEN_USB_COMPOSITE 416 417config TOUCHSCREEN_USB_GUNZE 418 default y 419 bool "Gunze AHL61 device support" if EMBEDDED 420 depends on TOUCHSCREEN_USB_COMPOSITE 421 422config TOUCHSCREEN_USB_DMC_TSC10 423 default y 424 bool "DMC TSC-10/25 device support" if EMBEDDED 425 depends on TOUCHSCREEN_USB_COMPOSITE 426 427config TOUCHSCREEN_USB_IRTOUCH 428 default y 429 bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED 430 depends on TOUCHSCREEN_USB_COMPOSITE 431 432config TOUCHSCREEN_USB_IDEALTEK 433 default y 434 bool "IdealTEK URTC1000 device support" if EMBEDDED 435 depends on TOUCHSCREEN_USB_COMPOSITE 436 437config TOUCHSCREEN_USB_GENERAL_TOUCH 438 default y 439 bool "GeneralTouch Touchscreen device support" if EMBEDDED 440 depends on TOUCHSCREEN_USB_COMPOSITE 441 442config TOUCHSCREEN_USB_GOTOP 443 default y 444 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED 445 depends on TOUCHSCREEN_USB_COMPOSITE 446 447config TOUCHSCREEN_TOUCHIT213 448 tristate "Sahara TouchIT-213 touchscreen" 449 select SERIO 450 help 451 Say Y here if you have a Sahara TouchIT-213 Tablet PC. 452 453 If unsure, say N. 454 455 To compile this driver as a module, choose M here: the 456 module will be called touchit213. 457 458config TOUCHSCREEN_TSC2007 459 tristate "TSC2007 based touchscreens" 460 depends on I2C 461 help 462 Say Y here if you have a TSC2007 based touchscreen. 463 464 If unsure, say N. 465 466 To compile this driver as a module, choose M here: the 467 module will be called tsc2007. 468 469endif 470