From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio add interrupt support on pca953x
Date: Wed, 23 Dec 2009 14:16:25 +0000 [thread overview]
Message-ID: <20091223141625.GC14455@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <771cded00912230548q12cf26a4j23e260017e3faf80@mail.gmail.com>
On Wed, Dec 23, 2009 at 09:48:07PM +0800, Haojian Zhuang wrote:
> On Wed, Dec 23, 2009 at 9:29 PM, Mark Brown
> >> While I fully understand your point, I'm more worried about the
> >> correctness of the approach. I'm under the impression that the use of
> >> IRQ_NESTED_THREAD is mandatory if we're using a threaded handler.
> >> @Mark Brown: what is your take on this? Is it possible to use
> >> generic_handle_irq() from within a threaded handler?
> > ICBW but I believe you'll find that you get into trouble with lockdep if
> > try to do that - the TWL4030 drivers in current mainline jump through
> > some hoops in the client drivers as a result of this if you want to look
> > at some examples. ?Once you're in a threaded IRQ you're in a slightly
> > different context and need to take account of that.
> So do you mean that we should disable IRQ in the threaded IRQ context?
I'm not sure exactly what makes you say that but if you're using the
genirq infrastructure then it should do the right thing for you here.
TWL4030 wasn't doing that (it predates genirq supporting I2C devices)
which was why it was running into trouble.
prev parent reply other threads:[~2009-12-23 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 12:29 [PATCH 1/2] gpio add interrupt support on pca953x Haojian Zhuang
2009-12-22 12:44 ` Trilok Soni
2009-12-22 12:51 ` Mark Brown
2009-12-22 13:41 ` Eric Miao
2009-12-22 13:54 ` Marc Zyngier
2009-12-22 19:59 ` Marc Zyngier
2009-12-23 1:34 ` Eric Miao
2009-12-23 8:35 ` Haojian Zhuang
2009-12-23 11:18 ` Marc Zyngier
2009-12-23 13:29 ` Mark Brown
2009-12-23 13:48 ` Haojian Zhuang
2009-12-23 14:16 ` Mark Brown [this message]
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=20091223141625.GC14455@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).