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_BITSY 33 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" 34 depends on SA1100_BITSY 35 select SERIO 36 help 37 Say Y here if you have the h3600 (Bitsy) touchscreen. 38 39 If unsure, say N. 40 41 To compile this driver as a module, choose M here: the 42 module will be called h3600_ts_input. 43 44config TOUCHSCREEN_CORGI 45 tristate "SharpSL (Corgi and Spitz series) touchscreen driver" 46 depends on PXA_SHARPSL 47 default y 48 help 49 Say Y here to enable the driver for the touchscreen on the 50 Sharp SL-C7xx and SL-Cxx00 series of PDAs. 51 52 If unsure, say N. 53 54 To compile this driver as a module, choose M here: the 55 module will be called corgi_ts. 56 57config TOUCHSCREEN_FUJITSU 58 tristate "Fujitsu serial touchscreen" 59 select SERIO 60 help 61 Say Y here if you have the Fujitsu touchscreen (such as one 62 installed in Lifebook P series laptop) connected to your 63 system. 64 65 If unsure, say N. 66 67 To compile this driver as a module, choose M here: the 68 module will be called fujitsu-ts. 69 70config TOUCHSCREEN_GUNZE 71 tristate "Gunze AHL-51S touchscreen" 72 select SERIO 73 help 74 Say Y here if you have the Gunze AHL-51 touchscreen connected to 75 your system. 76 77 If unsure, say N. 78 79 To compile this driver as a module, choose M here: the 80 module will be called gunze. 81 82config TOUCHSCREEN_ELO 83 tristate "Elo serial touchscreens" 84 select SERIO 85 help 86 Say Y here if you have an Elo serial touchscreen connected to 87 your system. 88 89 If unsure, say N. 90 91 To compile this driver as a module, choose M here: the 92 module will be called elo. 93 94config TOUCHSCREEN_MTOUCH 95 tristate "MicroTouch serial touchscreens" 96 select SERIO 97 help 98 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 99 your system. 100 101 If unsure, say N. 102 103 To compile this driver as a module, choose M here: the 104 module will be called mtouch. 105 106config TOUCHSCREEN_MK712 107 tristate "ICS MicroClock MK712 touchscreen" 108 help 109 Say Y here if you have the ICS MicroClock MK712 touchscreen 110 controller chip in your system. 111 112 If unsure, say N. 113 114 To compile this driver as a module, choose M here: the 115 module will be called mk712. 116 117config TOUCHSCREEN_HP600 118 tristate "HP Jornada 6xx touchscreen" 119 depends on SH_HP6XX && SH_ADC 120 help 121 Say Y here if you have a HP Jornada 620/660/680/690 and want to 122 support the built-in touchscreen. 123 124 To compile this driver as a module, choose M here: the 125 module will be called hp680_ts_input. 126 127config TOUCHSCREEN_HP7XX 128 tristate "HP Jornada 7xx touchscreen" 129 depends on SA1100_JORNADA720_SSP 130 help 131 Say Y here if you have a HP Jornada 710/720/728 and want 132 to support the built-in touchscreen. 133 134 To compile this driver as a module, choose M here: the 135 module will be called jornada720_ts. 136 137config TOUCHSCREEN_HTCPEN 138 tristate "HTC Shift X9500 touchscreen" 139 depends on ISA 140 help 141 Say Y here if you have an HTC Shift UMPC also known as HTC X9500 142 Clio / Shangrila and want to support the built-in touchscreen. 143 144 If unsure, say N. 145 146 To compile this driver as a module, choose M here: the 147 module will be called htcpen. 148 149config TOUCHSCREEN_PENMOUNT 150 tristate "Penmount serial touchscreen" 151 select SERIO 152 help 153 Say Y here if you have a Penmount serial touchscreen connected to 154 your system. 155 156 If unsure, say N. 157 158 To compile this driver as a module, choose M here: the 159 module will be called penmount. 160 161config TOUCHSCREEN_MIGOR 162 tristate "Renesas MIGO-R touchscreen" 163 depends on SH_MIGOR && I2C 164 help 165 Say Y here to enable MIGO-R touchscreen support. 166 167 If unsure, say N. 168 169 To compile this driver as a module, choose M here: the 170 module will be called migor_ts. 171 172config TOUCHSCREEN_TOUCHRIGHT 173 tristate "Touchright serial touchscreen" 174 select SERIO 175 help 176 Say Y here if you have a Touchright 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 touchright. 183 184config TOUCHSCREEN_TOUCHWIN 185 tristate "Touchwin serial touchscreen" 186 select SERIO 187 help 188 Say Y here if you have a Touchwin serial touchscreen connected to 189 your system. 190 191 If unsure, say N. 192 193 To compile this driver as a module, choose M here: the 194 module will be called touchwin. 195 196config TOUCHSCREEN_UCB1400 197 tristate "Philips UCB1400 touchscreen" 198 select AC97_BUS 199 help 200 This enables support for the Philips UCB1400 touchscreen interface. 201 The UCB1400 is an AC97 audio codec. The touchscreen interface 202 will be initialized only after the ALSA subsystem has been 203 brought up and the UCB1400 detected. You therefore have to 204 configure ALSA support as well (either built-in or modular, 205 independently of whether this driver is itself built-in or 206 modular) for this driver to work. 207 208 To compile this driver as a module, choose M here: the 209 module will be called ucb1400_ts. 210 211config TOUCHSCREEN_WM97XX 212 tristate "Support for WM97xx AC97 touchscreen controllers" 213 depends on AC97_BUS 214 help 215 Say Y here if you have a Wolfson Microelectronics WM97xx 216 touchscreen connected to your system. Note that this option 217 only enables core driver, you will also need to select 218 support for appropriate chip below. 219 220 If unsure, say N. 221 222 To compile this driver as a module, choose M here: the 223 module will be called wm97xx-ts. 224 225config TOUCHSCREEN_WM9705 226 bool "WM9705 Touchscreen interface support" 227 depends on TOUCHSCREEN_WM97XX 228 help 229 Say Y here if you have a Wolfson Microelectronics WM9705 230 touchscreen controller connected to your system. 231 232 If unsure, say N. 233 234config TOUCHSCREEN_WM9712 235 bool "WM9712 Touchscreen interface support" 236 depends on TOUCHSCREEN_WM97XX 237 help 238 Say Y here if you have a Wolfson Microelectronics WM9712 239 touchscreen controller connected to your system. 240 241 If unsure, say N. 242 243config TOUCHSCREEN_WM9713 244 bool "WM9713 Touchscreen interface support" 245 depends on TOUCHSCREEN_WM97XX 246 help 247 Say Y here if you have a Wolfson Microelectronics WM9713 touchscreen 248 controller connected to your system. 249 250 If unsure, say N. 251 252config TOUCHSCREEN_WM97XX_MAINSTONE 253 tristate "WM97xx Mainstone accelerated touch" 254 depends on TOUCHSCREEN_WM97XX && ARCH_PXA 255 help 256 Say Y here for support for streaming mode with WM97xx touchscreens 257 on Mainstone systems. 258 259 If unsure, say N. 260 261 To compile this driver as a module, choose M here: the 262 module will be called mainstone-wm97xx. 263 264config TOUCHSCREEN_USB_COMPOSITE 265 tristate "USB Touchscreen Driver" 266 depends on USB_ARCH_HAS_HCD 267 select USB 268 help 269 USB Touchscreen driver for: 270 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) 271 - PanJit TouchSet USB 272 - 3M MicroTouch USB (EX II series) 273 - ITM 274 - some other eTurboTouch 275 - Gunze AHL61 276 - DMC TSC-10/25 277 - IRTOUCHSYSTEMS/UNITOP 278 - IdealTEK URTC1000 279 - GoTop Super_Q2/GogoPen/PenPower tablets 280 281 Have a look at <http://linux.chapter7.ch/touchkit/> for 282 a usage description and the required user-space stuff. 283 284 To compile this driver as a module, choose M here: the 285 module will be called usbtouchscreen. 286 287config TOUCHSCREEN_USB_EGALAX 288 default y 289 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED 290 depends on TOUCHSCREEN_USB_COMPOSITE 291 292config TOUCHSCREEN_USB_PANJIT 293 default y 294 bool "PanJit device support" if EMBEDDED 295 depends on TOUCHSCREEN_USB_COMPOSITE 296 297config TOUCHSCREEN_USB_3M 298 default y 299 bool "3M/Microtouch EX II series device support" if EMBEDDED 300 depends on TOUCHSCREEN_USB_COMPOSITE 301 302config TOUCHSCREEN_USB_ITM 303 default y 304 bool "ITM device support" if EMBEDDED 305 depends on TOUCHSCREEN_USB_COMPOSITE 306 307config TOUCHSCREEN_USB_ETURBO 308 default y 309 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED 310 depends on TOUCHSCREEN_USB_COMPOSITE 311 312config TOUCHSCREEN_USB_GUNZE 313 default y 314 bool "Gunze AHL61 device support" if EMBEDDED 315 depends on TOUCHSCREEN_USB_COMPOSITE 316 317config TOUCHSCREEN_USB_DMC_TSC10 318 default y 319 bool "DMC TSC-10/25 device support" if EMBEDDED 320 depends on TOUCHSCREEN_USB_COMPOSITE 321 322config TOUCHSCREEN_USB_IRTOUCH 323 default y 324 bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED 325 depends on TOUCHSCREEN_USB_COMPOSITE 326 327config TOUCHSCREEN_USB_IDEALTEK 328 default y 329 bool "IdealTEK URTC1000 device support" if EMBEDDED 330 depends on TOUCHSCREEN_USB_COMPOSITE 331 332config TOUCHSCREEN_USB_GENERAL_TOUCH 333 default y 334 bool "GeneralTouch Touchscreen device support" if EMBEDDED 335 depends on TOUCHSCREEN_USB_COMPOSITE 336 337config TOUCHSCREEN_USB_GOTOP 338 default y 339 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED 340 depends on TOUCHSCREEN_USB_COMPOSITE 341 342endif 343