From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-input@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/3 2.6.39] Input: wm831x-ts - Fix races with IRQ management
Date: Tue, 3 May 2011 08:43:03 -0700 [thread overview]
Message-ID: <20110503154303.GA6509@core.coreip.homeip.net> (raw)
In-Reply-To: <20110503144618.GD2893@sirena.org.uk>
On Tue, May 03, 2011 at 03:46:18PM +0100, Mark Brown wrote:
> On Tue, Apr 19, 2011 at 07:17:52PM +0100, Mark Brown wrote:
> > If the WM831x pen down and data IRQs run in parallel it is possible for the
> > data and pen down IRQs to deadlock themselves as one is part way through
> > disabling its operation while the other is part way through enabling. Fix
> > this by always disabling the pen down interrupt while data is active and
> > vice versa. When a changeover is required we disable the IRQ that is to
> > be stopped then schedule work that will enable the new IRQ.
>
> Any updates on this?
I sent a pull request to Linus last night, hopefully he'll pull.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-05-03 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 18:17 [PATCH 1/3 2.6.39] Input: wm831x-ts - Fix races with IRQ management Mark Brown
2011-04-19 18:17 ` [PATCH 2/3] Input: wm831x-ts - Allow IRQ flags to be specified Mark Brown
2011-04-19 18:17 ` [PATCH 3/3] Input: wm831x-ts - Move BTN_TOUCH reporting to data transfer Mark Brown
2011-05-03 14:46 ` [PATCH 1/3 2.6.39] Input: wm831x-ts - Fix races with IRQ management Mark Brown
2011-05-03 15:43 ` Dmitry Torokhov [this message]
2011-05-03 15:44 ` Mark Brown
2011-05-03 15:49 ` Dmitry Torokhov
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=20110503154303.GA6509@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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).