From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: Interruption on PCI Bus
Date: Thu, 16 Apr 2009 08:20:04 -0600 [thread overview]
Message-ID: <fa686aa40904160720s77efa749u56392d7027467a4a@mail.gmail.com> (raw)
In-Reply-To: <49E6F14A.9010800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
On Thu, Apr 16, 2009 at 2:50 AM, Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org> wrote:
> Sorry for being so vague. As the person who originally devised this
> interrupt tree stuff, I'm pretty sure about the intention, but much less
> sure about what specific versions of Linux and U-Boot actually do.
> Hopefully someone else can give you a definitive answer about that.
U-Boot doesn't really do anything with interrupts. It usually just
polls everything.
Linux arch/powerpc does walk the device tree to get irq routing and
resolve to a Linux-internal virtual IRQ number. I'm pretty sure that
the IRQ registers are normally ignored unless something goes wrong
with parsing the tree. See arch/powerpc/kernel/pci-common.c and
search for of_irq_map_pci().
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-04-16 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 7:58 Interruption on PCI Bus Simon Desfarges
[not found] ` <49E6E542.5090504-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-04-16 8:50 ` Mitch Bradley
[not found] ` <49E6F14A.9010800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-04-16 14:20 ` Grant Likely [this message]
[not found] ` <fa686aa40904160720s77efa749u56392d7027467a4a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 15:12 ` Simon Desfarges
[not found] ` <49E74AC0.4000508-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-04-16 15:15 ` Grant Likely
[not found] ` <fa686aa40904160815y5eca6f5fn865762b645903c7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-17 8:24 ` Simon Desfarges
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=fa686aa40904160720s77efa749u56392d7027467a4a@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.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