imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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: Tue, 15 Jul 2025 15:17:00 -0700	[thread overview]
Message-ID: <aHbTXCYXbxLSQhgK@google.com> (raw)
In-Reply-To: <aGc666o3EgtXQMGN@lizhi-Precision-Tower-5810>

Hi Frank,

Thanks for the response.

On Thu, Jul 03, 2025 at 10:22:35PM -0400, Frank Li wrote:
> I saw AER and PME irq registed. But I have not seen irq increased. I am not
> sure how to inject an error to test it.

I've tested AER-like conditions via one of two ways:

1. force asserting PERST#, and then try to read a config register. This
   should generate Complection Timeouts at least, and possibly other
   errors. This method may not necessarily yield AER logs, as it may
   also reset the error reporting registers that the Linux AER driver
   would expect to read. But it probably should still trigger an
   interrupt.
   This depends on having access to PERST#; many SoCs provide this as a
   GPIO which you could potentially control, although I don't see this
   in the layerscape driver at the moment.
2. asserting HOT RESET in the DWC controller. This is especially
   implementation specific, as it depends on how (if at all) the hot
   reset signal is connected into your SoC.

Not sure if any of that helps you for testing. And maybe you want to
wire up your platform IRQs anyway.

Brian

  reply	other threads:[~2025-07-15 22:17 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 [this message]
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=aHbTXCYXbxLSQhgK@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).