From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Frank Li <Frank.li@nxp.com>,
Kelvin Cao <kelvin.cao@microchip.com>,
Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH v1 3/3] PCI: Add PCI1008 to switchtec NTB DMA alias quirk
Date: Tue, 14 Jul 2026 15:20:10 -0600 [thread overview]
Message-ID: <20260714212010.230606-4-logang@deltatee.com> (raw)
In-Reply-To: <20260714212010.230606-1-logang@deltatee.com>
Add the PCI1008 device ID to the quirk_switchtec_ntb_dma_alias
PCI fixup table. Without it, DMA transactions from a PCI1008 switch's
NTB function are not given the correct requester ID alias, which can
misdirect them under an IOMMU.
Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
---
drivers/pci/quirks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index b09f27f7846f..44ccee48349c 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -6090,6 +6090,7 @@ SWITCHTEC_PCI100X_QUIRK(0x1003); /* PCI1003XG4 */
SWITCHTEC_PCI100X_QUIRK(0x1004); /* PCI1004XG4 */
SWITCHTEC_PCI100X_QUIRK(0x1005); /* PCI1005XG4 */
SWITCHTEC_PCI100X_QUIRK(0x1006); /* PCI1006XG4 */
+SWITCHTEC_PCI100X_QUIRK(0x1008); /* PCI1008XG4 */
/*
--
2.47.3
next prev parent reply other threads:[~2026-07-14 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 21:20 [PATCH v1 0/3] switchtec: add new device IDs Logan Gunthorpe
2026-07-14 21:20 ` [PATCH v1 1/3] dmaengine: switchtec-dma: Add PCI1008 device ID Logan Gunthorpe
2026-07-14 21:28 ` sashiko-bot
2026-07-14 21:42 ` Logan Gunthorpe
2026-07-14 21:20 ` [PATCH v1 2/3] PCI/switch: switchtec: " Logan Gunthorpe
2026-07-14 21:23 ` sashiko-bot
2026-07-14 21:20 ` Logan Gunthorpe [this message]
2026-07-14 21:38 ` [PATCH v1 3/3] PCI: Add PCI1008 to switchtec NTB DMA alias quirk sashiko-bot
2026-07-14 21:44 ` Logan Gunthorpe
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=20260714212010.230606-4-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=dmaengine@vger.kernel.org \
--cc=kelvin.cao@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vkoul@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.