linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Andre Schwarz" <andre.schwarz@matrix-vision.de>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: simple MPC5200B system
Date: Tue, 18 Mar 2008 10:21:50 -0600	[thread overview]
Message-ID: <fa686aa40803180921l654d6336udd285cf13e4138b5@mail.gmail.com> (raw)
In-Reply-To: <47DFDC5B.90304@matrix-vision.de>

On Tue, Mar 18, 2008 at 9:14 AM, Andre Schwarz
<andre.schwarz@matrix-vision.de> wrote:
>  I've read some discussions about the "interrupt-map" attribute of the pci
> node. I tried to follow Ben and David in their explanations - obviously I
> didn't really get it.
>  Looks like there are a lot of people outside who need some enlightenment
> ... including me, of course.
>
>  Maybe you can clarify this ?
>
>  Taken from motionpro.dts ...
>

First, you also need to look at interrupt-map-mask to interpret these
values; from motionpro.dts:

interrupt-map-mask = <f800 0 0 7>;

which is applied to the unit interrupt specifier to figure out how to
map onto the interrupt controller.  The /size/ of this field is
obtained by adding #address-cells with #interrupt-cells. (3+1=4).

'f8' refers to the upper 5 bits of the interrupt identifier which is a
number from 0-31 which relates to the IDSEL line as you guessed.  The
'7' covers the lower 3 bits of the interrupt specifier which can be 1,
2, 3 or 4.

The 120 bits in the middle are irrelevant, so interrupt-map-mask
leaves them as zeros.

>      interrupt-map = <c000 0 0 1 &mpc5200_pic 0 0 3 // 1st slot
>                                   c000 0 0 2 &mpc5200_pic 1 1 3
>                                   c000 0 0 3 &mpc5200_pic 1 2 3
>                                   c000 0 0 4 &mpc5200_pic 1 3 3
>
>                                   c800 0 0 1 &mpc5200_pic 1 1 3 // 2nd slot
>                                   c800 0 0 2 &mpc5200_pic 1 2 3
>                                   c800 0 0 3 &mpc5200_pic 1 3 3
>                                   c800 0 0 4 &mpc5200_pic 0 0 3>;
>
>
>  First parameter seems to be the slot number, i.e. IDSEL line of the PCI
> device.
>  How is this value coded ? Are these the bits 15..11 of the configuration
> address ?

I don't remember how this is encoded.  On the lite5200, idsel is wired
to d0 and d1 for slots 1 and 2 respectively, yet these values suggest
slots 24 and 25.  I'll need to look at this again later.

>
>  2nd + 3rd paramter : no clue ! can you explain ?

first 3 cells are the unit address and is #address-cells large.  Only
the first cell contains real data.

>
>  4th : seem to be INT_A ... _D of a PCI device. Usually a device uses only
> INT_A. Do we need 4 entries in any case ?

you only need entries for irq lines that are wired up.  If your board
does not wire up _B, _C and _D, then don't have an entry for them.
However, if they are wired up then you should describe them.

>
>  5th : ok - parent pic

Correct.

>
>  6th ... 8th  : IRQ representation of the parent pic, which gives :
>
>      6th : 0=CRIT for irq0 pin, 1=MAIN for irq1..3 pins
>      7th : irq number. 1 for the irq0 pin inside CRIT level. irq1..3 have
> number 1..3 inside MAIN level.
>      8th : should be 3 = "level low" which is default for PCI.

Correct.

There is also some good information here:
http://playground.sun.com/1275/practice/imap/imap0_9d.pdf

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-03-18 16:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 19:15 simple MPC5200B system André Schwarz
2008-03-16 20:01 ` Grant Likely
2008-03-17  9:35   ` André Schwarz
2008-03-18  8:49   ` Andre Schwarz
2008-03-18 10:34     ` Andre Schwarz
2008-03-18 14:31       ` Grant Likely
2008-03-18 15:14         ` Andre Schwarz
2008-03-18 16:21           ` Grant Likely [this message]
2008-03-18 16:44             ` Andre Schwarz
2008-03-20  0:14     ` Wolfgang Denk
2008-03-20  0:21       ` David Gibson
2008-03-20  7:48         ` André Schwarz
2008-03-20  8:20           ` David Gibson
2008-03-20  9:11             ` André Schwarz
2008-03-20  9:29             ` Stefan Roese

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=fa686aa40803180921l654d6336udd285cf13e4138b5@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=andre.schwarz@matrix-vision.de \
    --cc=linuxppc-dev@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).