From: Mario Limonciello <mario.limonciello@amd.com>
To: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>,
Tom Lendacky <Thomas.Lendacky@amd.com>,
John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Thomas Rijo-john <Rijo-john.Thomas@amd.com>,
Rajib Mahapatra <Rajib.Mahapatra@amd.com>,
Nimesh Easow <Nimesh.Easow@amd.com>
Subject: Re: [PATCH] crypto: ccp - Add support for PCI device 0x1134
Date: Fri, 7 Feb 2025 18:36:48 -0600 [thread overview]
Message-ID: <78f4d7ab-a4ff-47b3-ba27-00b583ffb6fc@amd.com> (raw)
In-Reply-To: <8e2b6da988e7cb922010847bb07b5e9cf84bb563.1738879803.git.Devaraj.Rangasamy@amd.com>
On 2/6/2025 16:11, Devaraj Rangasamy wrote:
> PCI device 0x1134 shares same register features as PCI device 0x17E0.
> Hence reuse same data for the new PCI device ID 0x1134.
>
> Signed-off-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/crypto/ccp/sp-pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/crypto/ccp/sp-pci.c b/drivers/crypto/ccp/sp-pci.c
> index 248d98fd8c48..5357c4308da0 100644
> --- a/drivers/crypto/ccp/sp-pci.c
> +++ b/drivers/crypto/ccp/sp-pci.c
> @@ -529,6 +529,7 @@ static const struct pci_device_id sp_pci_table[] = {
> { PCI_VDEVICE(AMD, 0x14CA), (kernel_ulong_t)&dev_vdata[5] },
> { PCI_VDEVICE(AMD, 0x15C7), (kernel_ulong_t)&dev_vdata[6] },
> { PCI_VDEVICE(AMD, 0x1649), (kernel_ulong_t)&dev_vdata[6] },
> + { PCI_VDEVICE(AMD, 0x1134), (kernel_ulong_t)&dev_vdata[7] },
> { PCI_VDEVICE(AMD, 0x17E0), (kernel_ulong_t)&dev_vdata[7] },
> { PCI_VDEVICE(AMD, 0x156E), (kernel_ulong_t)&dev_vdata[8] },
> /* Last entry must be zero */
> --
> 2.25.1
>
next prev parent reply other threads:[~2025-02-08 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 22:11 [PATCH] crypto: ccp - Add support for PCI device 0x1134 Devaraj Rangasamy
2025-02-07 21:09 ` Tom Lendacky
2025-02-08 0:36 ` Mario Limonciello [this message]
2025-02-16 5:26 ` Herbert Xu
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=78f4d7ab-a4ff-47b3-ba27-00b583ffb6fc@amd.com \
--to=mario.limonciello@amd.com \
--cc=Devaraj.Rangasamy@amd.com \
--cc=Nimesh.Easow@amd.com \
--cc=Rajib.Mahapatra@amd.com \
--cc=Rijo-john.Thomas@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox