From: Scott Wood <scottwood@freescale•com>
To: Gary Thomas <gary@mlbassoc•com>
Cc: Linuxppc-dev@ozlabs•org
Subject: Re: More DTS questions
Date: Wed, 3 Sep 2008 12:12:25 -0500 [thread overview]
Message-ID: <20080903171225.GB10979@loki.buserror.net> (raw)
In-Reply-To: <48BE92C0.2020205@mlbassoc.com>
On Wed, Sep 03, 2008 at 07:36:00AM -0600, Gary Thomas wrote:
> pci@f0000d00 {
> #interrupt-cells = <1>;
> #size-cells = <2>;
> #address-cells = <3>;
> device_type = "pci";
> compatible = "fsl,mpc5200-pci";
> reg = <0xf0000d00 0x100>;
> interrupt-map-mask = <0xf800 0 0 7>;
> interrupt-map = <0xc000 0 0 1 &mpc5200_pic 0 0 3
> 0xc000 0 0 2 &mpc5200_pic 0 0 3
> 0xc000 0 0 3 &mpc5200_pic 0 0 3
> 0xc000 0 0 4 &mpc5200_pic 0 0 3>;
> clock-frequency = <0>; // From boot loader
> interrupts = <2 8 0 2 9 0 2 10 0>;
> interrupt-parent = <&mpc5200_pic>;
> bus-range = <0 0>;
> ranges = <0x42000000 0 0x80000000 0x80000000 0 0x10000000
> 0x02000000 0 0x90000000 0x90000000 0 0x10000000
> 0x01000000 0 0x00000000 0xa0000000 0 0x01000000>;
> };
>
> The things that truly aren't clear are the various lists.
> For example, how does "interrupt-map" and "interrupts" describe
> how the interrupts are handled?
It is described in this document:
http://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.0.pdf
> I don't see any reference in the code to these names (how does a driver
> get access to such properties?)
Look in arch/powerpc/kernel/prom_parse.c.
You'll want to change &mpc5200_pic in your interrupt-map to point to your
FPGA interrupt controller, and change the interrupt specifiers accordingly.
-Scott
next prev parent reply other threads:[~2008-09-03 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 13:36 More DTS questions Gary Thomas
2008-09-03 17:12 ` Scott Wood [this message]
2008-09-04 3:18 ` Benjamin Herrenschmidt
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=20080903171225.GB10979@loki.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=gary@mlbassoc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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