summaryrefslogtreecommitdiff
path: root/mm/huge_memory.c
diff options
context:
space:
mode:
authorMarek Vasut <marex@denx.de>2015-05-08 08:25:49 +0300
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2015-05-22 03:06:13 +0300
commit77b071e7931dd762563ac74e3e448b2aef23ad2f (patch)
tree24853e0f28a3ceb3706a41aba4686c68141aee76 /mm/huge_memory.c
parente686e9e156109cd2475196689a3144d91cf354b3 (diff)
downloadlinux-77b071e7931dd762563ac74e3e448b2aef23ad2f.tar.xz
Input: smtpe-ts - wait 50mS until polling for pen-up
Wait a little bit longer, 50mS instead of 20mS, until the driver starts polling for pen-up. The problematic behavior before this patch is applied is as follows. The behavior was observed on the STMPE610QTR controller. Upon a physical pen-down event, the touchscreen reports one set of x-y-p coordinates and a pen-down event. After that, the pen-up polling is triggered and since the controller is not ready yet, the polling mistakenly detects a pen-up event while the physical state is still such that the pen is down on the touch surface. The pen-up handling flushes the controller FIFO, so after that, all the samples in the controller are discarded. The controller becomes ready shortly after this bogus pen-up handling and does generate again a pen-down interrupt. This time, the controller contains x-y-p samples which all read as zero. Since pressure value is zero, this set of samples is effectively ignored by userland. In the end, the driver just bounces between pen-down and bogus pen-up handling, generating no useful results. Fix this by giving the controller a bit more time before polling it for pen-up. Signed-off-by: Marek Vasut <marex@denx.de> Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'mm/huge_memory.c')
0 files changed, 0 insertions, 0 deletions