From: Nicholas Beck <nbeck@mpc-data.co.uk>
To: magnus.damm@gmail.com
Cc: linux-sh@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] Touch screen driver for the SuperH MigoR board
Date: Tue, 01 Jul 2008 11:33:11 +0100 [thread overview]
Message-ID: <486A07E7.1070906@mpc-data.co.uk> (raw)
Hi Magnus,
Firstly, thanks for the great work. I have one issue with the touch
screen driver for the MigoR board though.
I don't get any BTN_TOUCH release events using the touch screen driver
for the MigoR board. Do you experience the same problem?
I only see the first BTN_TOUCH down and then the absolute x-y pairs. The
input framework gobbles up the subsequent BTN_TOUCH down events until it
detects a BTN_TOUCH release event, as it should do. But the release
event does not occur at the moment (for me at least), so a tap cannot be
performed.
I have a patch that adds a timer to perform the BTN_TOUCH release event
(kind of like a WDT), that I can submit if this is of any interest?
Thanks in advance,
Nicholas Beck
WARNING: multiple messages have this Message-ID (diff)
From: Nicholas Beck <nbeck@mpc-data.co.uk>
To: magnus.damm@gmail.com
Cc: linux-sh@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] Touch screen driver for the SuperH MigoR board
Date: Tue, 01 Jul 2008 10:33:11 +0000 [thread overview]
Message-ID: <486A07E7.1070906@mpc-data.co.uk> (raw)
In-Reply-To: <20080321111630.13138.14500.sendpatchset@rx1.opensource.se>
Hi Magnus,
Firstly, thanks for the great work. I have one issue with the touch
screen driver for the MigoR board though.
I don't get any BTN_TOUCH release events using the touch screen driver
for the MigoR board. Do you experience the same problem?
I only see the first BTN_TOUCH down and then the absolute x-y pairs. The
input framework gobbles up the subsequent BTN_TOUCH down events until it
detects a BTN_TOUCH release event, as it should do. But the release
event does not occur at the moment (for me at least), so a tap cannot be
performed.
I have a patch that adds a timer to perform the BTN_TOUCH release event
(kind of like a WDT), that I can submit if this is of any interest?
Thanks in advance,
Nicholas Beck
next reply other threads:[~2008-07-01 10:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 10:33 Nicholas Beck [this message]
2008-07-01 10:33 ` [PATCH] Touch screen driver for the SuperH MigoR board Nicholas Beck
2008-07-01 11:22 ` Magnus Damm
2008-07-01 11:22 ` Magnus Damm
-- strict thread matches above, loose matches on Subject: below --
2008-03-28 9:51 [PATCH] Touch screen driver for the SuperH MigoR board V2 Magnus Damm
2008-03-28 9:51 ` Magnus Damm
2008-04-02 6:08 ` Dmitry Torokhov
2008-04-02 6:08 ` Dmitry Torokhov
2008-04-04 8:21 ` Magnus Damm
2008-04-04 8:21 ` Magnus Damm
2008-04-04 16:14 ` Dmitry Torokhov
2008-04-04 16:14 ` Dmitry Torokhov
2008-04-25 10:29 ` Magnus Damm
2008-04-25 10:29 ` Magnus Damm
2008-04-27 5:07 ` Dmitry Torokhov
2008-04-27 5:07 ` Dmitry Torokhov
2008-05-07 12:14 ` Magnus Damm
2008-05-07 12:14 ` Magnus Damm
2008-03-21 11:16 [PATCH] Touch screen driver for the SuperH MigoR board Magnus Damm
2008-03-21 11:16 ` Magnus Damm
2008-03-21 22:55 ` Andrew Morton
2008-03-21 22:55 ` Andrew Morton
2008-03-26 4:03 ` Magnus Damm
2008-03-26 4:03 ` Magnus Damm
2008-03-26 11:29 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486A07E7.1070906@mpc-data.co.uk \
--to=nbeck@mpc-data.co.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.