From: Scott Wood <scottwood@freescale.com>
To: robert lazarski <robertlazarski@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: external IRQ's
Date: Thu, 16 Aug 2007 11:23:57 -0500 [thread overview]
Message-ID: <46C47A1D.5030303@freescale.com> (raw)
In-Reply-To: <f87675ee0708160751u14f96dbcs3ad35a147b70a3f3@mail.gmail.com>
robert lazarski wrote:
> 1) Do I need to define those external IRQ's in both a device tree file
> under arch/powerpc/boot/dts and also in C code under
> arch/powerpc/platforms/85xx ?
Just in the dts.
> 2) I've been told on another list that "External interrupts start at
> zero (internal interrupt numbers have 0x10 added to them), so the
> first cell should correspond to the external IRQ
> number." I'm having a hard time applying that advice to a MDIO node
> and ethernet node in the device tree. For example, the CDS board for
> 8548 has the following:
>
> mdio@24520 {
> #address-cells = <1>;
> #size-cells = <0>;
> device_type = "mdio";
> compatible = "gianfar";
> reg = <24520 20>;
> phy0: ethernet-phy@0 {
> interrupt-parent = <&mpic>;
> interrupts = <35 0>;
> reg = <0>;
> device_type = "ethernet-phy";
> };
> ...
> };
I don't know what version of the dts you're looking at, but the one in
the current Linux tree has <5 1>, not <35 0>.
> I'm also not getting the ethernet interrupts in the above cds example:
>
> interrupts = <d 2 e 2 12 2>;
>
> Why start with 'd' and 'e' ? I noticed many if not all boards do that.
In the current dts, it's <1d 2 1e 2 22 2>.
It appears that the interrupt numbering was changed not too long ago,
and that external interrupts used to be numbered above the internal ones.
-Scott
next prev parent reply other threads:[~2007-08-16 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 14:51 external IRQ's robert lazarski
2007-08-16 16:23 ` Scott Wood [this message]
2007-08-16 21:34 ` robert lazarski
2007-08-16 21:43 ` Scott Wood
2007-08-17 14:03 ` robert lazarski
2007-08-17 16:28 ` Scott Wood
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=46C47A1D.5030303@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=robertlazarski@gmail.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).