From: "Jeff Domogala" <jdomogala@acmepacket.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Handling of cascaded interrupt controllers
Date: Wed, 25 Aug 2004 16:08:58 -0400 [thread overview]
Message-ID: <NFBBJCNFKLFMBACPKDKCOEIFEFAA.jdomogala@acmepacket.com> (raw)
In-Reply-To: <20040825143025.GJ23113@mind.be>
I have a Marvell GT-64260A based custom board. The interrupt line out of
the GT is cascaded into a CPLD, which also has 15 other interrupt sources.
The way I handled this situation in VxWorks was to define interrupt vectors
for the CPLD interrupts, minus the one cascaded interrupt from the GT (so 15
interrupt vectors), then use 64 more interrupt vectors for the GT
interrupts. The cascaded interrupt would then call the GT's normal
interrupt handler to determine the interrupt source.
Is there a way to define two interrupt controller devices in this fashion in
Linux, where a single interrupt from one controller (the CPLD) can somehow
manage multiple interrupts for the other controller (the GT), with all
interrupt sources having unique vectors? This appears to be identical to a
cascaded pair of 8259 controllers. Or, do I do something similar to my
VxWorks implementation and create one interrupt controller device with
unique interrupt vectors for all sources except the cascaded CPLD interrupt
for the GT?
Regards,
Jeff
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-25 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 6:27 How to port ppc-linux to new custom boards? (virtexII) Patrick Huesmann
2004-08-24 7:25 ` Marc Leeman
2004-08-25 7:34 ` Marius Groeger
2004-08-25 7:57 ` Marc Leeman
2004-08-25 13:52 ` David Ho
2004-08-25 14:30 ` Peter Vandenabeele
2004-08-25 20:08 ` Jeff Domogala [this message]
2004-08-26 7:02 ` Marc Leeman
2004-08-24 8:01 ` Oliver Fuchs
2004-08-24 8:31 ` Peter Ryser
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=NFBBJCNFKLFMBACPKDKCOEIFEFAA.jdomogala@acmepacket.com \
--to=jdomogala@acmepacket.com \
--cc=linuxppc-embedded@lists.linuxppc.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).