From: Bjorn Helgaas <helgaas@kernel.org>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"Natu, Mahesh" <mahesh.natu@intel.com>
Subject: Re: [PATCH v2] PCI/EDR: Clear PCIe Device Status errors after EDR error recovery
Date: Fri, 7 Apr 2023 16:52:59 -0500 [thread overview]
Message-ID: <20230407215259.GA3825733@bhelgaas> (raw)
In-Reply-To: <20230407215142.GA3825302@bhelgaas>
On Fri, Apr 07, 2023 at 04:51:44PM -0500, Bjorn Helgaas wrote:
> I'll post a follow-up patch to add a couple comments there,
> too.
Comments I propose:
PCI/EDR: Add edr_handle_event() comments
EDR documentation is a bit sketchy. Add a couple comments to
edr_handle_event() about the devices involved.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
diff --git a/drivers/pci/pcie/edr.c b/drivers/pci/pcie/edr.c
index 87734e4c3c20..135ddb53661c 100644
--- a/drivers/pci/pcie/edr.c
+++ b/drivers/pci/pcie/edr.c
@@ -151,9 +151,17 @@ static void edr_handle_event(acpi_handle handle, u32 event, void *data)
if (event != ACPI_NOTIFY_DISCONNECT_RECOVER)
return;
+ /*
+ * pdev itself is still present, but one or more of its child
+ * devices have been disconnected (ACPI v6.3, sec 5.6.6).
+ */
pci_info(pdev, "EDR event received\n");
- /* Locate the port which issued EDR event */
+ /*
+ * Locate the port that experienced the containment event. pdev
+ * may be that port or a parent of it (PCI Firmware r3.3, sec
+ * 4.6.13).
+ */
edev = acpi_dpc_port_get(pdev);
if (!edev) {
pci_err(pdev, "Firmware failed to locate DPC port\n");
next prev parent reply other threads:[~2023-04-07 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 23:54 [PATCH v2] PCI/EDR: Clear PCIe Device Status errors after EDR error recovery Kuppuswamy Sathyanarayanan
2023-03-24 17:53 ` Sathyanarayanan Kuppuswamy
2023-03-29 22:09 ` Bjorn Helgaas
2023-03-29 22:38 ` Sathyanarayanan Kuppuswamy
2023-03-30 15:45 ` Bjorn Helgaas
2023-03-31 6:46 ` Sathyanarayanan Kuppuswamy
2023-03-31 15:10 ` Bjorn Helgaas
2023-04-06 21:07 ` Bjorn Helgaas
2023-04-06 21:52 ` Sathyanarayanan Kuppuswamy
2023-04-06 22:21 ` Bjorn Helgaas
2023-04-06 22:46 ` Natu, Mahesh
2023-04-07 5:31 ` Sathyanarayanan Kuppuswamy
2023-04-07 16:46 ` Bjorn Helgaas
2023-04-07 22:19 ` Sathyanarayanan Kuppuswamy
2023-04-07 22:41 ` Bjorn Helgaas
2023-04-07 21:51 ` Bjorn Helgaas
2023-04-07 21:52 ` Bjorn Helgaas [this message]
2023-04-07 22:25 ` Sathyanarayanan Kuppuswamy
2023-04-07 22:21 ` Sathyanarayanan Kuppuswamy
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=20230407215259.GA3825733@bhelgaas \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mahesh.natu@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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