From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: linuxppc-dev@ozlabs.org
Subject: device tree interrupt-map/interrupt-map-mask properties for a 405EP board
Date: Wed, 17 Sep 2008 22:59:05 +0200 [thread overview]
Message-ID: <200809172259.05743.matthias.fuchs@esd-electronics.com> (raw)
Hi,
I am trying to setup a device tree for a 405EP based board.
I did not fully understand how to setup the interrupt-map-mask and
interrupt-map properties for the PCI node:
...
PCI0: pci@ec000000 {
...
interrupt-map-mask = <0x???? 0x0 0x0 0x0>;
interrupt-map = <
/* slot1: IDSEL AD12 - ext. Irq 4 */
0x???? 0x0 0x0 0x0 &UIC0 29 0x8
/* slot2: IDSEL AD13 - ext. Irq 5 */
0x???? 0x0 0x0 0x0 &UIC0 30 0x8
/* slot3: IDSEL AD14 - ext. Irq 6 */
0x???? 0x0 0x0 0x0 &UIC0 31 0x8
>;
};
I have three PCI slots on the board. How do I have to fill out the ???? fields
above? ADxx <-> IDSEL connection can be taken from the comments. Each slot
has its interrupt lines INTA..D connected to a single 405 external interrupt
input.
Where can I find any docs about this?
Matthias
reply other threads:[~2008-09-17 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200809172259.05743.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--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).