From: "robert lazarski" <robertlazarski@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: external IRQ's
Date: Thu, 16 Aug 2007 17:34:42 -0400 [thread overview]
Message-ID: <f87675ee0708161434i9f38b0dg123a767822cf7402@mail.gmail.com> (raw)
In-Reply-To: <46C47A1D.5030303@freescale.com>
On 8/16/07, Scott Wood <scottwood@freescale.com> wrote:
> 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.
Thanks, I notice in 2.6.23-rc3 there no longer are a series of
mpic_assign_isu() .
>
> 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>.
Thanks for pointing that out! 2.6.22.2 has 35 as the interrupt, while
2.6.23-rc3 has 5. 35 didn't make any sense to me since the old ppc
arch used 5.
>
> > 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
>
Why <1d 2 1e 2 22 2> ? I can't seem to parse these numbers - how do I
know what to use for my external interupts 1,2 for phy's 0,1 using a
88E1121R and for external interupts 3,4 for phy's 2,3 using a 88E1111
?
Thanks!
Robert
next prev parent reply other threads:[~2007-08-16 21:34 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
2007-08-16 21:34 ` robert lazarski [this message]
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=f87675ee0708161434i9f38b0dg123a767822cf7402@mail.gmail.com \
--to=robertlazarski@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).