From: Brian Norris <briannorris@chromium.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Frank Li <Frank.li@nxp.com>, 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, 16 Jul 2025 08:20:38 -0700 [thread overview]
Message-ID: <aHfDRm2S8N8Qus_m@google.com> (raw)
In-Reply-To: <tikcdb63ti6hbpypusxdiaoattpuez5rgpsglzllagnqfm5voa@5eornv77pl4i>
On Wed, Jul 16, 2025 at 12:47:10PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Jul 02, 2025 at 04:44:48PM GMT, Brian Norris wrote:
> > On Wed, Jul 02, 2025 at 07:09:42PM -0400, Frank Li wrote:
> > 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...
> >
>
> Yes, pretty much all Qcom SoCs without GIC-v3 ITS suffer from this limitation.
> And the same should be true for other vendors also.
>
> Interestingly, the Qcom SoCs route the AER/PME via 'global' SPI interrupt, which
> is only handled by the controller driver. This is similar to the 'aer' SPI
> interrupt in layerscape platforms.
Yeah, I have some SoCs like this as well. But I also believe that I have
INTx available, and that even when MSI doesn't work for AER/PME, INTx
might.
Do Qcom SoCs route INTx?
> So I think there is an incentive in allowing the AER driver to work with vendor
> specific IRQs.
Yeah, I suppose even if my SoC (and Qcom, depending on the above answer)
might work with INTx, it really does seem like an arbitrary decision
about what SoC makers connected which DWC signals, so I suspect this is
true.
Brian
next prev parent reply other threads:[~2025-07-16 15:20 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
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 [this message]
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=aHfDRm2S8N8Qus_m@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=mani@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.