Commit e655e2f
input: ti_am335x_tsc: Ignore previous pen down event when pen up event occurs
Frequently when a pen up event occurs the sampling for the previous pen down
event ends up being incomplete. From a userspace perspective you will see an
abnormal jump when comparing the pen down events to the one right before the
pen up event.
To avoid this issue delay sending a pen down event until the next touch
event has occurred. If the current touch event is not a pen up event then
send the previously detected pen down values. If the current touch event is
a pen up then simply ignore the previous pen down value.
Signed-off-by: Franklin S Cooper Jr. <fcooper@ti.com>
Acked-by: Vignesh R <vigneshr@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>1 parent 267f0e0 commit e655e2f
1 file changed
+16
-5
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
| 56 | + | |
| 57 | + | |
56 | 58 | | |
57 | 59 | | |
58 | 60 | | |
| |||
276 | 278 | | |
277 | 279 | | |
278 | 280 | | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
279 | 289 | | |
280 | 290 | | |
281 | 291 | | |
| |||
302 | 312 | | |
303 | 313 | | |
304 | 314 | | |
305 | | - | |
306 | | - | |
307 | | - | |
308 | | - | |
309 | | - | |
| 315 | + | |
| 316 | + | |
| 317 | + | |
| 318 | + | |
310 | 319 | | |
311 | 320 | | |
312 | 321 | | |
| |||
396 | 405 | | |
397 | 406 | | |
398 | 407 | | |
| 408 | + | |
399 | 409 | | |
400 | 410 | | |
401 | 411 | | |
| |||
472 | 482 | | |
473 | 483 | | |
474 | 484 | | |
| 485 | + | |
475 | 486 | | |
476 | 487 | | |
477 | 488 | | |
| |||
0 commit comments