linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Magnus Damm" <magnus.damm@gmail.com>
To: Nicholas Beck <nbeck@mpc-data.co.uk>
Cc: linux-sh@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] Touch screen driver for the SuperH MigoR board
Date: Tue, 1 Jul 2008 20:22:56 +0900	[thread overview]
Message-ID: <aec7e5c30807010422m4ea7dcdqae2efe5caf93efb2@mail.gmail.com> (raw)
In-Reply-To: <486A07E7.1070906@mpc-data.co.uk>

Hi Nicholas,

Thanks for your email!

On Tue, Jul 1, 2008 at 7:33 PM, Nicholas Beck <nbeck@mpc-data.co.uk> wrote:
> 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?

This problem has been fixed by Dmitry Torokhov. The linux-input
archives seem gone though.

The updated patch below did not make it into 2.6.26, but it should be
included in 2.6.27.

http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=885c316d776b64728b4ed30e3af60d23c9e46825

> 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?

Does Dmitrys patch above solve your problem? If not, please post your
patch and I'll have a look.

Thank you!

/ magnus

  reply	other threads:[~2008-07-01 11:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 10:33 [PATCH] Touch screen driver for the SuperH MigoR board Nicholas Beck
2008-07-01 11:22 ` Magnus Damm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-21 11:16 Magnus Damm
2008-03-21 22:55 ` Andrew Morton
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=aec7e5c30807010422m4ea7dcdqae2efe5caf93efb2@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=nbeck@mpc-data.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).