Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Alvaro Karsz <alvaro.karsz@solid-run.com>
To: virtualization@lists.linux-foundation.org
Cc: linux-pci@vger.kernel.org,
	Alvaro Karsz <alvaro.karsz@solid-run.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 2/3] New PCI quirk for SolidRun SNET DPU.
Date: Mon, 12 Dec 2022 16:24:53 +0200	[thread overview]
Message-ID: <20221212142454.3225177-3-alvaro.karsz@solid-run.com> (raw)
In-Reply-To: <20221212142454.3225177-1-alvaro.karsz@solid-run.com>

The DPU advertises FLR, but it may cause the device to hang.
This only happens with revision 0x1.

Signed-off-by: Alvaro Karsz <alvaro.karsz@solid-run.com>
---
 drivers/pci/quirks.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 285acc4aacc..809d03272c2 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -5343,6 +5343,14 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x149c, quirk_no_flr);
 DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);
 DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_no_flr);
 
+/* FLR may cause the SolidRun SNET DPU (rev 0x1) to hang */
+static void quirk_no_flr_snet(struct pci_dev *dev)
+{
+	if (dev->revision == 0x1)
+		quirk_no_flr(dev);
+}
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SOLIDRUN, 0x1000, quirk_no_flr_snet);
+
 static void quirk_no_ext_tags(struct pci_dev *pdev)
 {
 	struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus);
-- 
2.32.0


  parent reply	other threads:[~2022-12-12 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 14:24 [PATCH 0/3] virtio: vdpa: new SolidNET DPU driver Alvaro Karsz
2022-12-12 14:24 ` [PATCH 1/3] Add SolidRun vendor id Alvaro Karsz
2022-12-12 14:24 ` Alvaro Karsz [this message]
2022-12-12 14:24 ` [PATCH 3/3 v4] virtio: vdpa: new SolidNET DPU driver Alvaro Karsz
2022-12-12 15:01   ` Guenter Roeck
2022-12-12 16:29     ` Alvaro Karsz
2022-12-12 16:38       ` Alvaro Karsz
2022-12-12 17:01       ` Guenter Roeck
2022-12-12 17:46         ` Alvaro Karsz
2022-12-12 17:56           ` Alvaro Karsz
2022-12-12 19:05             ` Guenter Roeck
2022-12-12 20:17               ` Alvaro Karsz

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=20221212142454.3225177-3-alvaro.karsz@solid-run.com \
    --to=alvaro.karsz@solid-run.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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