tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
fork
Configure Feed
Select the types of activity you want to include in your feed.
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 680/690 touchscreen"
119 depends on SH_HP6XX && SH_ADC
120 help
121 Say Y here if you have a HP Jornada 680 or 690 and want to
122 support the built-in touchscreen.
123
124 If unsure, say N.
125
126 To compile this driver as a module, choose M here: the
127 module will be called hp680_ts_input.
128
129config TOUCHSCREEN_HP7XX
130 tristate "HP Jornada 710/720/728 touchscreen"
131 depends on SA1100_JORNADA720_SSP
132 help
133 Say Y here if you have a HP Jornada 710/720/728 and want
134 to support the built-in touchscreen.
135
136 To compile this driver as a module, choose M here: the
137 module will be called jornada720_ts.
138
139config TOUCHSCREEN_PENMOUNT
140 tristate "Penmount serial touchscreen"
141 select SERIO
142 help
143 Say Y here if you have a Penmount 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 penmount.
150
151config TOUCHSCREEN_TOUCHRIGHT
152 tristate "Touchright serial touchscreen"
153 select SERIO
154 help
155 Say Y here if you have a Touchright serial touchscreen connected to
156 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 touchright.
162
163config TOUCHSCREEN_TOUCHWIN
164 tristate "Touchwin serial touchscreen"
165 select SERIO
166 help
167 Say Y here if you have a Touchwin serial touchscreen connected to
168 your system.
169
170 If unsure, say N.
171
172 To compile this driver as a module, choose M here: the
173 module will be called touchwin.
174
175config TOUCHSCREEN_UCB1400
176 tristate "Philips UCB1400 touchscreen"
177 select AC97_BUS
178 help
179 This enables support for the Philips UCB1400 touchscreen interface.
180 The UCB1400 is an AC97 audio codec. The touchscreen interface
181 will be initialized only after the ALSA subsystem has been
182 brought up and the UCB1400 detected. You therefore have to
183 configure ALSA support as well (either built-in or modular,
184 independently of whether this driver is itself built-in or
185 modular) for this driver to work.
186
187 To compile this driver as a module, choose M here: the
188 module will be called ucb1400_ts.
189
190config TOUCHSCREEN_USB_COMPOSITE
191 tristate "USB Touchscreen Driver"
192 depends on USB_ARCH_HAS_HCD
193 select USB
194 help
195 USB Touchscreen driver for:
196 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
197 - PanJit TouchSet USB
198 - 3M MicroTouch USB (EX II series)
199 - ITM
200 - some other eTurboTouch
201 - Gunze AHL61
202 - DMC TSC-10/25
203 - IRTOUCHSYSTEMS/UNITOP
204 - IdealTEK URTC1000
205 - GoTop Super_Q2/GogoPen/PenPower tablets
206
207 Have a look at <http://linux.chapter7.ch/touchkit/> for
208 a usage description and the required user-space stuff.
209
210 To compile this driver as a module, choose M here: the
211 module will be called usbtouchscreen.
212
213config TOUCHSCREEN_USB_EGALAX
214 default y
215 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
216 depends on TOUCHSCREEN_USB_COMPOSITE
217
218config TOUCHSCREEN_USB_PANJIT
219 default y
220 bool "PanJit device support" if EMBEDDED
221 depends on TOUCHSCREEN_USB_COMPOSITE
222
223config TOUCHSCREEN_USB_3M
224 default y
225 bool "3M/Microtouch EX II series device support" if EMBEDDED
226 depends on TOUCHSCREEN_USB_COMPOSITE
227
228config TOUCHSCREEN_USB_ITM
229 default y
230 bool "ITM device support" if EMBEDDED
231 depends on TOUCHSCREEN_USB_COMPOSITE
232
233config TOUCHSCREEN_USB_ETURBO
234 default y
235 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
236 depends on TOUCHSCREEN_USB_COMPOSITE
237
238config TOUCHSCREEN_USB_GUNZE
239 default y
240 bool "Gunze AHL61 device support" if EMBEDDED
241 depends on TOUCHSCREEN_USB_COMPOSITE
242
243config TOUCHSCREEN_USB_DMC_TSC10
244 default y
245 bool "DMC TSC-10/25 device support" if EMBEDDED
246 depends on TOUCHSCREEN_USB_COMPOSITE
247
248config TOUCHSCREEN_USB_IRTOUCH
249 default y
250 bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
251 depends on TOUCHSCREEN_USB_COMPOSITE
252
253config TOUCHSCREEN_USB_IDEALTEK
254 default y
255 bool "IdealTEK URTC1000 device support" if EMBEDDED
256 depends on TOUCHSCREEN_USB_COMPOSITE
257
258config TOUCHSCREEN_USB_GENERAL_TOUCH
259 default y
260 bool "GeneralTouch Touchscreen device support" if EMBEDDED
261 depends on TOUCHSCREEN_USB_COMPOSITE
262
263config TOUCHSCREEN_USB_GOTOP
264 default y
265 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
266 depends on TOUCHSCREEN_USB_COMPOSITE
267
268endif