From: Jacob Moroni <jmoroni@google.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Logan Gunthorpe <logang@deltatee.com>,
David Hu <xuehaohu@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Jacob Moroni <jmoroni@google.com>
Subject: [PATCH 2/2] PCI/P2PDMA: Add Google SoCs to the P2P DMA host bridge list
Date: Thu, 9 Apr 2026 15:01:23 +0000 [thread overview]
Message-ID: <20260409150123.3538444-2-jmoroni@google.com> (raw)
In-Reply-To: <20260409150123.3538444-1-jmoroni@google.com>
All Google SoCs support p2p between root ports, so add a wildcard
rule to the host bridge list.
Tested-by: David Hu <xuehaohu@google.com>
Signed-off-by: Jacob Moroni <jmoroni@google.com>
---
drivers/pci/p2pdma.c | 2 ++
include/linux/pci_ids.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
index 25e9358d0..7c898542a 100644
--- a/drivers/pci/p2pdma.c
+++ b/drivers/pci/p2pdma.c
@@ -548,6 +548,8 @@ static const struct pci_p2pdma_whitelist_entry {
{PCI_VENDOR_ID_INTEL, 0x2033, 0},
{PCI_VENDOR_ID_INTEL, 0x2020, 0},
{PCI_VENDOR_ID_INTEL, 0x09a2, 0},
+ /* Google SoCs. */
+ {PCI_VENDOR_ID_GOOGLE, PCI_ANY_ID, 0},
{}
};
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 406abf629..24cb42f66 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -2586,6 +2586,8 @@
#define PCI_VENDOR_ID_AZWAVE 0x1a3b
+#define PCI_VENDOR_ID_GOOGLE 0x1ae0
+
#define PCI_VENDOR_ID_REDHAT_QUMRANET 0x1af4
#define PCI_SUBVENDOR_ID_REDHAT_QUMRANET 0x1af4
#define PCI_SUBDEVICE_ID_QEMU 0x1100
--
2.53.0.1213.gd9a14994de-goog
next prev parent reply other threads:[~2026-04-09 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 15:01 [PATCH 1/2] PCI/P2PDMA: Allow wildcard device IDs in host bridge list Jacob Moroni
2026-04-09 15:01 ` Jacob Moroni [this message]
2026-04-09 22:47 ` [PATCH 2/2] PCI/P2PDMA: Add Google SoCs to the P2P DMA " Logan Gunthorpe
2026-04-09 22:47 ` [PATCH 1/2] PCI/P2PDMA: Allow wildcard device IDs in " Logan Gunthorpe
2026-04-10 22:28 ` 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=20260409150123.3538444-2-jmoroni@google.com \
--to=jmoroni@google.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=xuehaohu@google.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