From: Jon Loeliger <jdl@freescale.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Randy Brown <rbrown@istor.com>,
Chris Carlson <ccarlson@istor.com>,
Kevin Smith <ksmith@istor.com>,
"linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: How do external irq's get mapped?
Date: Fri, 27 Apr 2007 12:35:34 -0500 [thread overview]
Message-ID: <1177695334.8797.30.camel@ld0161-tx32> (raw)
In-Reply-To: <46322CE4.1060004@ru.mvista.com>
On Fri, 2007-04-27 at 12:03, Sergei Shtylyov wrote:
> Hello.
>
> Charles Krinke wrote:
>
> > Let me try a more simplified IRQ question a different way by only
> > referring to the 8541.
>
> > There are 12 external interrupt sources, irq[0..11] and as I understand
> > it, they all go through one vector, ExternalInput set in
> > head_fsl_booke.S and this vector resolves to "do_IRQ()", which I believe
> > is in arch/powerpc/kernel/irq.c (not arch/ppc/kernel/...).
>
> > I am striving to understand how mapping of these external pins
> > irq[0..11] gets to IRQ numbers as shown with "cat /proc/interrupts".
>
> IIUC, the external IRQ #'s should follow those occupied by 32 internal IRQs.
> But those shown in that file are "virtual" numbers, i.e. they got re-mapped by the kernel as it sees fit (basically, it tries to assign the same # to IRQs above 15 and remaps those below)
And remember, Ben distorted the IRQ World right about
somewhere in that time frame too.
Kumar, can you remind us?
> > Could someone point me at some references I can read to understand this
> > nuance of the 8541 in a linux-2.6.17.11 kernel, please.
>
> I'm not sure arch/powerpc/ in 2.6.17 had the complete MPC8541 support...
Which might be a different way of saying "You should try the
current top of git or 2.6.21." :-)
jdl
next prev parent reply other threads:[~2007-04-27 17:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 16:10 gcj & PPC405 Patrick Olinet
2007-04-26 18:36 ` IRQ questions & puzzles Charles Krinke
2007-04-27 15:17 ` Charles Krinke
2007-04-27 15:41 ` Jon Loeliger
2007-04-27 16:55 ` How do external irq's get mapped? Charles Krinke
2007-04-27 17:03 ` Sergei Shtylyov
2007-04-27 17:35 ` Jon Loeliger [this message]
2007-04-27 17:38 ` Charles Krinke
2007-04-27 17:46 ` Sergei Shtylyov
2007-04-27 18:05 ` Charles Krinke
2007-04-27 18:42 ` Sergei Shtylyov
2007-04-27 19:34 ` Charles Krinke
2007-04-27 20:58 ` Charles Krinke
2007-04-27 21:23 ` Andy Fleming
2007-04-27 22:51 ` Charles Krinke
2007-04-28 2:30 ` Zhang Wei-r63237
2007-04-30 16:25 ` I2C support for 8541 Charles Krinke
2007-05-02 10:43 ` Clemens Koller
2007-10-13 13:52 ` Vitaly Bordug
2007-04-30 14:32 ` How do external irq's get mapped? Charles Krinke
2007-05-01 0:22 ` Andy Fleming
2007-05-01 23:11 ` Charles Krinke
2007-05-02 18:42 ` Andy Fleming
2007-05-02 22:11 ` Charles Krinke
2007-05-02 22:43 ` Andy Fleming
2007-05-03 20:19 ` Charles Krinke
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=1177695334.8797.30.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=ccarlson@istor.com \
--cc=ksmith@istor.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rbrown@istor.com \
--cc=sshtylyov@ru.mvista.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).