From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: "Logan Gunthorpe" <logang@deltatee.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Christian König" <christian.koenig@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Alex Deucher" <alexdeucher@gmail.com>
Subject: [PATCH] PCI/P2PDMA: Add AMD Zen 2 root complex to the list of allowed bridges
Date: Thu, 23 Jul 2020 11:43:17 -0600 [thread overview]
Message-ID: <20200723174317.2783-1-logang@deltatee.com> (raw)
The AMD Zen 2 root complex (Starship/Matisse) was tested for P2PDMA
transactions between root ports and found to work. Therefore add it
to the list.
Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>
Cc: Christian König <christian.koenig@amd.com>
Cc: Huang Rui <ray.huang@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>
---
drivers/pci/p2pdma.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
index e8e444eeb1cd..3d67a1ee083e 100644
--- a/drivers/pci/p2pdma.c
+++ b/drivers/pci/p2pdma.c
@@ -284,6 +284,8 @@ static const struct pci_p2pdma_whitelist_entry {
{PCI_VENDOR_ID_AMD, 0x1450, 0},
{PCI_VENDOR_ID_AMD, 0x15d0, 0},
{PCI_VENDOR_ID_AMD, 0x1630, 0},
+ /* AMD ZEN 2 */
+ {PCI_VENDOR_ID_AMD, 0x1480, 0},
/* Intel Xeon E5/Core i7 */
{PCI_VENDOR_ID_INTEL, 0x3c00, REQ_SAME_HOST_BRIDGE},
base-commit: ba47d845d715a010f7b51f6f89bae32845e6acb7
--
2.20.1
next reply other threads:[~2020-07-23 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 17:43 Logan Gunthorpe [this message]
2020-07-23 18:01 ` [PATCH] PCI/P2PDMA: Add AMD Zen 2 root complex to the list of allowed bridges Alex Deucher
2020-07-23 19:57 ` Bjorn Helgaas
2020-07-23 20:10 ` Logan Gunthorpe
2020-07-23 20:18 ` Alex Deucher
2020-07-23 20:45 ` Logan Gunthorpe
2020-07-24 16:07 ` Alex Deucher
2020-07-24 19:20 ` Logan Gunthorpe
2020-07-24 15:06 ` Bjorn Helgaas
2020-07-24 15:56 ` Logan Gunthorpe
2020-07-27 9:20 ` Jonathan Cameron
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=20200723174317.2783-1-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=alexdeucher@gmail.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ray.huang@amd.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