From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Roland Dreier" <rdreier@cisco.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: demuxing irqs
Date: Sat, 13 Sep 2008 18:54:58 -0400 [thread overview]
Message-ID: <9e4733910809131554mb0c6660r3bcc993bb2ca082d@mail.gmail.com> (raw)
In-Reply-To: <adaprn7is80.fsf@cisco.com>
On Sat, Sep 13, 2008 at 6:41 PM, Roland Dreier <rdreier@cisco.com> wrote:
> > Can someone point me at a simple example of how to demux irqs using
> > the powerpc irq functions? I have eight devices on a single irq and I
> > want to turn them into virtual irqs.
>
> Sorry about the previous reply.
>
> Anyway, what are you going to demux based on? Do you have some other
> signal you can read in the interrupt dispatch code that tells you which
> device raised the interrupt? What happens if two devices raise an
> interrupt at the same time?
>
> If you just have 8 interrupt lines wire-ORed together then you probably
> just need to register your interrupt handlers with IRQF_SHARED and run 8
> interrupt handlers on an interrupt.
The muxed interrupts are inside a SOC CPU. For example eight GPIOs
can each individually be enabled to trigger hardware interrupt 7. When
I get hw interrupt 7 i want to demux it into 8 virtual interrupts.
There are eight bit registers for individually acking, enabling, etc
each of the eight multiplexed interrupts. With eight virutal
interrupts each user can register a different handler and isn't aware
the muxing is going on.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-09-13 22:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 19:06 demuxing irqs Jon Smirl
2008-09-13 22:41 ` Roland Dreier
2008-09-13 22:54 ` Jon Smirl [this message]
2008-09-13 23:04 ` Roland Dreier
2008-09-13 23:23 ` Jon Smirl
2008-09-14 14:06 ` Jon Smirl
2008-09-14 23:25 ` Jon Smirl
2008-09-15 3:06 ` Jon Smirl
2008-09-16 12:17 ` Anton Vorontsov
2008-09-16 12:37 ` Jon Smirl
2008-09-16 13:12 ` Anton Vorontsov
2008-09-16 13:36 ` Jon Smirl
2008-09-16 14:14 ` Anton Vorontsov
2008-09-16 14:24 ` Jon Smirl
2008-09-16 17:49 ` Scott Wood
2008-09-16 18:32 ` Jon Smirl
2008-09-16 21:42 ` Anton Vorontsov
2008-09-16 22:08 ` Jon Smirl
2008-09-16 23:24 ` Scott Wood
2008-09-16 23:47 ` Jon Smirl
2008-09-17 12:56 ` Anton Vorontsov
2008-09-17 14:09 ` Jon Smirl
2008-09-17 17:54 ` Stephen Neuendorffer
2008-09-16 14:29 ` Jon Smirl
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=9e4733910809131554mb0c6660r3bcc993bb2ca082d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=rdreier@cisco.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).