From: Scott Wood <scottwood@freescale.com>
To: robert lazarski <robertlazarski@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: external IRQ's
Date: Fri, 17 Aug 2007 11:28:04 -0500 [thread overview]
Message-ID: <46C5CC94.9090902@freescale.com> (raw)
In-Reply-To: <f87675ee0708170703t632db650o95fd7ec16f587c37@mail.gmail.com>
robert lazarski wrote:
> On 8/16/07, Scott Wood <scottwood@freescale.com> wrote:
>
>>robert lazarski wrote:
>>
>>>Why <1d 2 1e 2 22 2> ? I can't seem to parse these numbers
>>
>>They alternate between IRQ numbers and level/sense information, and the
>>IRQ numbers are the internal IRQ number plus 16.
>
>
> Thanks, The "internal IRQ number plus 16" part is the info I was
> lacking. However by 'internal IRQ' do you mean DMA? I just asked the
> hardware engineer and that's what he thought you may have meant.
No, I mean interrupts that come from on-chip devices, rather than
external interrupt pins.
> So in '1d' the first cell is the irq and the second cell is the sense
> level, how is the '1' calculated from 'internal IRQ number plus 16' .
> Thanks for you patience, I'm just not getting that part yet.
What do you mean, the '1'?
From table 10-3 of the 8548 manual, the eTSEC1 transmit interrupt is
internal interrupt 13, or 0xd. Adding 16 gives 0x1d.
It's (apparently) level-triggered active-high, so the sense is 2,
according to the table in booting-without-of.txt.
>>If, like the CDS board, you have level-triggered active-low phy
>>interrupts, then <0 1>, <1 1>, <2 1>, and <3 1>. If not, then choose an
>>appropriate value for the second cell based on booting-without-of.txt.
>>
>
>
> Kool, think I got this part. Do the 0-3 irq's in the mdio node
> influence in any way the ethernet nodes irq's - the <1d 2 1e 2 22 2>
> in this example ?
No.
-Scott
prev parent reply other threads:[~2007-08-17 16:28 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
2007-08-16 21:43 ` Scott Wood
2007-08-17 14:03 ` robert lazarski
2007-08-17 16:28 ` Scott Wood [this message]
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=46C5CC94.9090902@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).