From: Brian Norris <briannorris@chromium.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Minghuan Lian <minghuan.Lian@nxp.com>,
Mingkai Hu <mingkai.hu@nxp.com>, Roy Zang <roy.zang@nxp.com>,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
imx@lists.linux.dev, linux-pci@vger.kernel.org
Subject: Re: Does dwc/pci-layerscape.c support AER?
Date: Wed, 2 Jul 2025 16:44:48 -0700 [thread overview]
Message-ID: <aGXEcHTfT2k2ayAj@google.com> (raw)
In-Reply-To: <aGW8NnHUlfv1NO3g@lizhi-Precision-Tower-5810>
Hi Frank,
On Wed, Jul 02, 2025 at 07:09:42PM -0400, Frank Li wrote:
> > Does the AER driver actually work on these platforms?
...
> There are several attempts to upstream customer Aer irq support in past years.
>
> For example:
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1161848.html
>
> some change port drivers.
>
> If you think it is valuable to support customer AER IRQ support, I can restart
> this work.
Interesting thread. I read through it, but I'm still not convinced about
one detail:
Are you sure that AER can't possibly work over MSI? Even today, the
Synopsys manuals say that their integrated MSI receiver "terminate[s]
inbound MSI requests (received on the RX wire)" and after terminating,
"an interrupt is signaled locally through the msi_ctrl_int output."
That means that their msi_ctrl_int signal only handles MSI requests from
downstream functions, and it implies that the default
drivers/pci/controller/dwc/pcie-designware-host.c
dw_pcie_msi_domain_info implementation will not actually see MSIs from
the root port (such as PME and AER). So yes, it *appears* that AER does
not work over MSI.
But crucially, it does *not* mean that the port will not generate valid
MSI requests, if you have some kind of logic that will receive it. So
for instance, I pointed out in another reply that some SoCs choose to
hook up GIC ITS:
commit 9c4cd0aef259 ("arm64: dts: qcom: x1e80100: enable GICv3 ITS for
PCIe")
"""
Note that using the GIC ITS on x1e80100 will cause Advanced Error
Reporting (AER) interrupts to be received on errors unlike when using
the internal MSI controller. Consequently, notifications about
(correctable) errors may now be logged for errors that previously went
unnoticed.
"""
And in fact, your arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi seems
to be doing the same. I'd be surprised if these port MSIs still don't
work after that.
OTOH, I do also believe there are SoCs where DWC PCIe is available, but
there is no external MSI controller, and so that same problem still may
exist. I may even have such SoCs available...
Brian
next prev parent reply other threads:[~2025-07-02 23:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 22:38 Does dwc/pci-layerscape.c support AER? Bjorn Helgaas
2025-07-02 23:04 ` Brian Norris
2025-07-02 23:09 ` Frank Li
2025-07-02 23:44 ` Brian Norris [this message]
2025-07-04 2:22 ` Frank Li
2025-07-15 22:17 ` Brian Norris
2025-07-16 7:17 ` Manivannan Sadhasivam
2025-07-16 15:20 ` Brian Norris
2025-07-16 16:05 ` Manivannan Sadhasivam
2025-07-16 17:25 ` Brian Norris
2025-07-16 20:42 ` Bjorn Helgaas
2025-07-16 21:22 ` Frank Li
2025-07-16 21:30 ` Bjorn Helgaas
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=aGXEcHTfT2k2ayAj@google.com \
--to=briannorris@chromium.org \
--cc=Frank.li@nxp.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=helgaas@kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-pci@vger.kernel.org \
--cc=minghuan.Lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=robh+dt@kernel.org \
--cc=roy.zang@nxp.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).