From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eran Liberty <liberty@extricom.com>
Cc: linux-pci@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Freescale P2020 / 85xx PCIe and Advance Error Reporting (AER) service problem
Date: Mon, 11 Oct 2010 22:32:01 +1100 [thread overview]
Message-ID: <1286796721.5220.2.camel@pasglop> (raw)
In-Reply-To: <4CB2E517.8020401@extricom.com>
> BUT if we take into consideration that:
> 1. Freescale is a serious dude in the hood and on the whole does a good
> job with its products and their Linux support.
Sure but that's irrelevant to the technical problem at hand :-)
> 2. The P2020 does state it has an MSI mechanism support (although one is
> not present as a PCIe capability header for some reason)
Then it's broken :-(
> 3. Errors in general and AER are major features in PCIe.
> 4. PCIe has been here quite a while and it is not new to Freescale or
> anyone else.
Right but we don't do AER on ppc44x either, I know we should but for
some reason, AER hasn't been on anybody #1 priority list in embedded
world so far...
> I am much more inclined to believe that I have missed something by a
> mile then that Freescale did. I just don't know what I am missing.
No, I think you haven't and we just need to fix it :-)
Cheers,
Ben.
> My device tree is a clone of "arch/ powerpc/ boot/ dts/ p2020rdb.dts"
>
> It has a PCI node that looks like this:
> ----------------------------- snip -----------------------------
> pci0: pcie@ffe09000 {
> cell-index = <1>;
> compatible = "fsl,mpc8548-pcie";
> device_type = "pci";
> #interrupt-cells = <1>;
> #size-cells = <2>;
> #address-cells = <3>;
> reg = <0 0xffe09000 0 0x1000>;
> bus-range = <0 255>;
> ranges = <0x2000000 0x0 0xa0000000 0 0xa0000000 0x0 0x20000000
> 0x1000000 0x0 0x00000000 0 0xffc30000 0x0 0x10000>;
> clock-frequency = <33333333>;
> interrupt-parent = <&mpic>;
> interrupts = <25 2>;
> interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
> interrupt-map = <
> /* IDSEL 0x0 */
> 0000 0x0 0x0 0x1 &mpic 0x4 0x1
> 0000 0x0 0x0 0x2 &mpic 0x5 0x1
> 0000 0x0 0x0 0x3 &mpic 0x6 0x1
> 0000 0x0 0x0 0x4 &mpic 0x7 0x1
> >;
> pcie@0 {
> reg = <0x0 0x0 0x0 0x0 0x0>;
> #size-cells = <2>;
> #address-cells = <3>;
> device_type = "pci";
> ranges = <0x2000000 0x0 0xa0000000
> 0x2000000 0x0 0xa0000000
> 0x0 0x20000000
>
> 0x1000000 0x0 0x0
> 0x1000000 0x0 0x0
> 0x0 0x100000>;
> };
> };
> ----------------------------- snap -----------------------------
>
> and under "soc" it has an MSI node that looks like that:
> ----------------------------- snip -----------------------------
> msi@41600 {
> compatible = "fsl,p2020-msi", "fsl,mpic-msi";
> reg = <0x41600 0x80>;
> msi-available-ranges = <0 0x100>;
> interrupts = <
> 0xe0 0
> 0xe1 0
> 0xe2 0
> 0xe3 0
> 0xe4 0
> 0xe5 0
> 0xe6 0
> 0xe7 0>;
> interrupt-parent = <&mpic>;
> };
> ----------------------------- snap -----------------------------
>
> -- Liberty
>
next prev parent reply other threads:[~2010-10-11 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 12:30 Freescale P2020 / 85xx PCIe and Advance Error Reporting (AER) service problem Eran Liberty
2010-10-07 14:42 ` Kumar Gala
2010-10-10 10:02 ` Eran Liberty
2010-10-11 0:19 ` Benjamin Herrenschmidt
2010-10-11 10:21 ` Eran Liberty
2010-10-11 11:32 ` Benjamin Herrenschmidt [this message]
2010-10-17 19:24 ` Freescale P2020 CPU Freeze over PCIe abort signal Eran Liberty
2010-10-18 5:26 ` Bin Meng
2010-10-18 9:52 ` tiejun.chen
2010-10-18 11:44 ` Eran Liberty
2010-10-18 18:00 ` Eran Liberty
2010-10-19 16:53 ` Eran Liberty
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=1286796721.5220.2.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=liberty@extricom.com \
--cc=linux-pci@vger.kernel.org \
--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).