From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: Simulating level triggered interrupts with edges
Date: Thu, 23 Jun 2011 02:23:53 +0100 [thread overview]
Message-ID: <20110623012352.GD20949@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1106222233580.11814@ionos>
On Wed, Jun 22, 2011 at 11:32:03PM +0200, Thomas Gleixner wrote:
> Though it's non-trivial. Think threaded interrupts, where we cannot
> deal with that in handle_irq_edge(). I have no immediate idea how to
> solve that at the core code, but feel free to have a stab.
Yes, that's why I asked - all the devices I care about have threaded
handlers and I care about a system where the interrupt controller is
threaded too. I was thinking error handling on set_type() and flags
but thought I must be missing something. I'll probably have a poke
sometime anyway.
prev parent reply other threads:[~2011-06-23 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 19:50 Simulating level triggered interrupts with edges Mark Brown
2011-06-22 21:32 ` Thomas Gleixner
2011-06-23 1:23 ` 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=20110623012352.GD20949@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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