linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: linux-pci@vger.kernel.org,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	"Pali Rohár" <pali@kernel.org>,
	"Bharat Kumar Gogada" <bharat.kumar.gogada@xilinx.com>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Yao Hongbo" <yaohongbo@linux.alibaba.com>,
	"Naveen Naidu" <naveennaidu479@gmail.com>
Subject: Re: [PATCH v4 0/3] Fully enable AER
Date: Mon, 11 Jul 2022 14:53:53 -0500	[thread overview]
Message-ID: <20220711195353.GA683105@bhelgaas> (raw)
In-Reply-To: <20220125071820.2247260-1-sr@denx.de>

On Tue, Jan 25, 2022 at 08:18:17AM +0100, Stefan Roese wrote:
> While working on AER support on a ZynqMP based system, which has some
> PCIe Device connected via a PCIe switch, problems with AER enabling in
> the Device Control registers of all PCIe devices but the Root Port. In
> fact, only the Root Port has AER enabled right now. This patch set now
> fixes this problem by first fixing the AER enabing in the
> interconnected PCIe switches between the Root Port and the PCIe
> devices and in a 2nd patch, also enabling AER in the PCIe Endpoints.
> 
> Please note that these changes are quite invasive, as with these
> patches applied, AER now will be enabled in the Device Control
> registers of all available PCIe Endpoints, which currently is not the
> case.
> 
> Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> Cc: Bjorn Helgaas <helgaas@kernel.org>
> Cc: Pali Rohár <pali@kernel.org>
> Cc: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: Yao Hongbo <yaohongbo@linux.alibaba.com>
> Cc: Naveen Naidu <naveennaidu479@gmail.com>
> 
> Stefan Roese (3):
>   PCI/AER: Call pcie_set_ecrc_checking() for each PCIe device
>   PCI/portdrv: Don't disable AER reporting in
>     get_port_device_capability()
>   PCI/AER: Enable AER on all PCIe devices supporting it
> 
>  drivers/pci/pcie/aer.c          | 10 +++++++---
>  drivers/pci/pcie/portdrv_core.c |  9 +--------
>  2 files changed, 8 insertions(+), 11 deletions(-)

Applied to pci/err for v5.20, thanks and sorry for the delay.

      parent reply	other threads:[~2022-07-11 19:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25  7:18 [PATCH v4 0/3] Fully enable AER Stefan Roese
2022-01-25  7:18 ` [PATCH v4 1/3] PCI/AER: Call pcie_set_ecrc_checking() for each PCIe device Stefan Roese
2022-01-25 14:52   ` Pali Rohár
2022-01-25  7:18 ` [PATCH v4 2/3] PCI/portdrv: Don't disable AER reporting in get_port_device_capability() Stefan Roese
2022-01-25  7:18 ` [PATCH v4 3/3] PCI/AER: Enable AER on all PCIe devices supporting it Stefan Roese
2022-01-25 14:53   ` Pali Rohár
2022-04-04 20:22   ` Jonathan Derrick
2022-04-06  5:16     ` Stefan Roese
2022-04-06 14:49       ` Jonathan Derrick
2022-03-24 16:55 ` [PATCH v4 0/3] Fully enable AER Stefan Roese
2022-04-04 10:36   ` Stefan Roese
2022-07-11 19:53 ` Bjorn Helgaas [this message]

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=20220711195353.GA683105@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bharat.kumar.gogada@xilinx.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=naveennaidu479@gmail.com \
    --cc=pali@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sr@denx.de \
    --cc=yaohongbo@linux.alibaba.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).