From: Simon Desfarges <simon.desfarges-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
To: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Interruption on PCI Bus
Date: Thu, 16 Apr 2009 09:58:58 +0200 [thread overview]
Message-ID: <49E6E542.5090504@fr.thalesgroup.com> (raw)
Hi everybody,
I am working on a custom board and I started to map the Interruptions of
the PCI on the dts file as follow:
pci@70000000 {
compatible = "abac-pci";
device_type = "pci";
#size-cells = <2>;
#address-cells = <3>;
#interrupt-cells = <1>;
reg = <0x20021000 0x1000>;
bus-range = <0 1>;
ranges = < /*Memory-space 1:1 mapping*/
0x2000000 0x0 0x90000000 0x90000000 0x0 0x10000000
/*No IO-space*/
0x1000000 0x0 0x00000000 0x00000000 0x0 0x00000000
>;
clock-frequency = <66666666>;
interrupt-parent = <&IT_controller>;
interrupts = <0xd>;
interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
interrupt-map = <
/* IDSEL 15 - only 1 slot with 1 IT*/
0x7800 0x0 0x0 0x1 &IT_controller 0xd
>;
};
I have some questions about interrupt mapping:
- If I understood well, when Linux wants to map its internal
interruptions, it generates a PCI address, masks it with the
<interrupt-map-mask> field and compares the result with the
<interrupt-map> field. But where do this address come from ? When in the
startup the interrupt mapping is done (in which part of code) ? Is it
automatic or have I to do that manually during PCI initialization ?
- I have read that in the config. space of PCI device, there is a
"PCI_INTERRUPT_LINE" which gives to the driver the interrupt number. So
I wonder who (Linux or U-Boot ?) and when this field is filled ?
Thank you for your attention.
Simon Desfarges
next reply other threads:[~2009-04-16 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 7:58 Simon Desfarges [this message]
[not found] ` <49E6E542.5090504-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-04-16 8:50 ` Interruption on PCI Bus Mitch Bradley
[not found] ` <49E6F14A.9010800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-04-16 14:20 ` Grant Likely
[not found] ` <fa686aa40904160720s77efa749u56392d7027467a4a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 15:12 ` Simon Desfarges
[not found] ` <49E74AC0.4000508-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-04-16 15:15 ` Grant Likely
[not found] ` <fa686aa40904160815y5eca6f5fn865762b645903c7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-17 8:24 ` Simon Desfarges
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=49E6E542.5090504@fr.thalesgroup.com \
--to=simon.desfarges-s/s/64waxt+h1tvi1vffb9bpr1lh4cv8@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.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