From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-input@vger.kernel.org, linux-sh@vger.kernel.org,
lethal@linux-sh.org, broonie@sirena.org.uk,
akpm@linux-foundation.org
Subject: Re: [PATCH] Touch screen driver for the SuperH MigoR board V2
Date: Fri, 4 Apr 2008 12:14:47 -0400 [thread overview]
Message-ID: <20080404120837.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <aec7e5c30804040121k584a0ae5o909b48fbd970245d@mail.gmail.com>
Hi Magnus,
On Fri, Apr 04, 2008 at 05:21:48PM +0900, Magnus Damm wrote:
> I just tested using latest sh-2.6 git with evtest. Everything seems to
> work well. The patch is much cleaner now. Please apply.
>
I was just looking the driver over one more time before applying it
and I think there is a race in migor_ts_remove():
+ /* cancel pending work and wait for migor_ts_poscheck() to finish */
+ cancel_delayed_work_sync(&priv->work);
+
What if interrupt comes here, before we got a chance to shut off the
device? IRQ is still enabled and it will schedule migor_ts_poscheck()
again. I think we need to call disable_irq() before canceling the work.
Since the driver does not support sharing IRQs that should be allright.
What do you think?
+ /* disable controller */
+ i2c_master_send(client, migor_ts_dis_seq, sizeof(migor_ts_dis_seq));
+
+ free_irq(priv->irq, priv);
Thank you.
--
Dmitry
next prev parent reply other threads:[~2008-04-04 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 9:51 [PATCH] Touch screen driver for the SuperH MigoR board V2 Magnus Damm
2008-04-02 6:08 ` Dmitry Torokhov
2008-04-04 8:21 ` Magnus Damm
2008-04-04 16:14 ` Dmitry Torokhov [this message]
2008-04-25 10:29 ` Magnus Damm
2008-04-27 5:07 ` Dmitry Torokhov
2008-05-07 12:14 ` Magnus Damm
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=20080404120837.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@sirena.org.uk \
--cc=lethal@linux-sh.org \
--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 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).