From: Daniel Walker <danielwa@cisco.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Suneel Garapati <sgarapati@marvell.com>,
Chandrakala Chavva <cchavva@marvell.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH-RFC] drivers: pci: pcieport: Allow AER service only on root ports
Date: Thu, 7 Oct 2021 12:44:09 -0700 [thread overview]
Message-ID: <20211007194409.3641467-1-danielwa@cisco.com> (raw)
From: Suneel Garapati <sgarapati@marvell.com>
Some AER interrupt capability registers may not be present on
non Root ports. Since there is no way to check presence of
ROOT_ERR_COMMAND and ROOT_ERR_STATUS registers. Allow AER
service only on root ports.
Otherwise AER interrupt message number is read incorrectly
causing MSIX vector registration to fail and fallback to legacy
unnecessarily.
Signed-off-by: Suneel Garapati <sgarapati@marvell.com>
Reviewed-by: Chandrakala Chavva <cchavva@marvell.com>
Reviewed-by: Sunil Kovvuri Goutham <sgoutham@marvell.com>
---
drivers/pci/pcie/portdrv_core.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
index 3ee63968deaa..edc355971a32 100644
--- a/drivers/pci/pcie/portdrv_core.c
+++ b/drivers/pci/pcie/portdrv_core.c
@@ -221,7 +221,16 @@ static int get_port_device_capability(struct pci_dev *dev)
}
#ifdef CONFIG_PCIEAER
+ /*
+ * Some AER interrupt capability registers may not be present on
+ * non Root ports. Since there is no way to check presence of
+ * ROOT_ERR_COMMAND and ROOT_ERR_STATUS registers. Allow AER
+ * service only on root ports. Refer PCIe rev5.0 spec v1.0 7.8.4.
+ * Otherwise AER interrupt message number is read incorrectly
+ * causing MSIX vector registration to fail and fallback to legacy.
+ */
if (dev->aer_cap && pci_aer_available() &&
+ pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT &&
(pcie_ports_native || host->native_aer)) {
services |= PCIE_PORT_SERVICE_AER;
--
2.25.1
next reply other threads:[~2021-10-07 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 19:44 Daniel Walker [this message]
2021-10-07 20:27 ` 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=20211007194409.3641467-1-danielwa@cisco.com \
--to=danielwa@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=cchavva@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sgarapati@marvell.com \
--cc=sgoutham@marvell.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
all inboxes | Powered by JetHome®