From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Gleixner <tglx@linutronix.de>,
mingo@elte.hu, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: genirq: Add a set_irq_handler_locked() function
Date: Mon, 12 Feb 2007 14:17:28 +1100 [thread overview]
Message-ID: <20070212031728.GA30401@localhost.localdomain> (raw)
In-Reply-To: <20070209073640.GA29988@flint.arm.linux.org.uk>
On Fri, Feb 09, 2007 at 07:36:40AM +0000, Russell King wrote:
> On Fri, Feb 09, 2007 at 02:48:42PM +1100, David Gibson wrote:
> > At present set_irq_handler() and all the existing variants take the
> > desc->lock for the irq in question before adjusting the irq's flow
> > handler. This can cause problems for irq chips for which a given
> > interrupt can be either level or edge depending on what's attached.
>
> Are you sure you need to change the flow handler depending on how
> you program the device?
>
> Since the outset of this design, I've had what are essentially edge
> based interrupt sources using the "level" handlers because they haven't
> had a "broken" edge implementation. By that, I mean that the masking
> is done in such a way that you miss edges when the source is masked.
>
> If you do not miss edges while the source is masked, there's no point
> in having the complexity of the "edge" based handler in the path - it
> buys you nothing. Just use the "level" handler instead.
I see... how terribly obvious.
As far as I know, the 4xx UIC does things correctly, though I don't
have handy any devices with edge interrupts to test it with.
It would still be nice to have this change, so we can use the
lazy-masking from handle_edge_irq(), but I guess I can do without it
for now.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-02-12 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070207023353.GC23870@localhost.localdomain>
[not found] ` <1170940949.3646.1.camel@chaos>
2007-02-09 3:48 ` David Gibson
2007-02-09 7:36 ` Russell King
2007-02-12 3:17 ` David Gibson [this message]
2007-02-12 9:35 ` Russell King
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=20070212031728.GA30401@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
Powered by JetHome