Thread (14 messages) flat view 14 messages, 4 authors, 2011-12-14

Re: [PATCH] edt_ts: EDT Touchscreen driver

From: Anatolij Gustschin <agust@denx.de>
Date: 2011-11-17 12:20:44

Hi Ilya,

On Thu, 17 Nov 2011 00:44:17 +0400
Ilya Yanok [off-list ref] wrote:
Hi Dmitry, Anatolij,

On 15.11.2011 21:41, Dmitry Torokhov wrote:
quoted
quoted
quoted
Do you really need to read gpio state in IRQ? Can't you simply rely on
'event' do decide whether to emit input events?
We can't rely on the 'event' only. The peculiar behaviour of the
touch controller enforces this. The touch controller toggles the
interrupt line when you keep the finger down. The rate is not exactly
specified by the the manufacturer (~80/sec). Measured rate deviates
from this specified rate. Valid touch packet data can be read when
interrupt line is pulled down.
So what ensures that the gpio line stays low between the check and the
time you get access to i2c bus and get around reading the data.
Anatolij, could you please comment on this? What can we do about this?
Check the pin state after i2c read maybe?
I received a suggestion to look at the time elapsed since falling
edge of the GPIO IRQ before reading the touch packet data and
skip reading if it is too late. I'll also check what the touch
packet data looks like when reading it while finger is down but
the line stays high. 

Anatolij
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help