mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rijo Thomas <Rijo-john.Thomas@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	John Allen <john.allen@amd.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: ccp - Add support for new CCP/PSP device ID
Date: Mon, 25 Jul 2022 13:10:30 +0530	[thread overview]
Message-ID: <edd96cb6-aa74-bc21-9275-ca9e1f80c100@amd.com> (raw)
In-Reply-To: <188ecbc9-8624-2b74-7963-5f1b909ddf2f@amd.com>



On 7/20/2022 6:28 PM, Tom Lendacky wrote:
> On 7/19/22 11:13, Mario Limonciello wrote:
>> Add a new CCP/PSP PCI device ID.  This uses same register offsets
>> as the previously supported structure.
>>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> 
> Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
> 

Acked-by: Rijo Thomas <Rijo-john.Thomas@amd.com>

>> ---
>>   drivers/crypto/ccp/sp-pci.c | 7 +++++++
>>   1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/crypto/ccp/sp-pci.c b/drivers/crypto/ccp/sp-pci.c
>> index b5970ae54d0e..792d6da7f0c0 100644
>> --- a/drivers/crypto/ccp/sp-pci.c
>> +++ b/drivers/crypto/ccp/sp-pci.c
>> @@ -427,6 +427,12 @@ static const struct sp_dev_vdata dev_vdata[] = {
>>           .bar = 2,
>>   #ifdef CONFIG_CRYPTO_DEV_SP_PSP
>>           .psp_vdata = &pspv2,
>> +#endif
>> +    },
>> +    {    /* 6 */
>> +        .bar = 2,
>> +#ifdef CONFIG_CRYPTO_DEV_SP_PSP
>> +        .psp_vdata = &pspv3,
>>   #endif
>>       },
>>   };
>> @@ -438,6 +444,7 @@ static const struct pci_device_id sp_pci_table[] = {
>>       { PCI_VDEVICE(AMD, 0x15DF), (kernel_ulong_t)&dev_vdata[4] },
>>       { PCI_VDEVICE(AMD, 0x1649), (kernel_ulong_t)&dev_vdata[4] },
>>       { PCI_VDEVICE(AMD, 0x14CA), (kernel_ulong_t)&dev_vdata[5] },
>> +    { PCI_VDEVICE(AMD, 0x15C7), (kernel_ulong_t)&dev_vdata[6] },
>>       /* Last entry must be zero */
>>       { 0, }
>>   };

  reply	other threads:[~2022-07-25  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 16:13 Mario Limonciello
2022-07-20 12:58 ` Tom Lendacky
2022-07-25  7:40   ` Rijo Thomas [this message]
2022-07-29 10:34 ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2021-08-20 14:56 John Allen
2021-08-27  8:35 ` 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=edd96cb6-aa74-bc21-9275-ca9e1f80c100@amd.com \
    --to=rijo-john.thomas@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 \
    --cc=mario.limonciello@amd.com \
    --cc=thomas.lendacky@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

all inboxes | Powered by JetHome®