From: Herbert Xu <herbert@gondor.apana.org.au>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: davem@davemloft.net, thomas.lendacky@amd.com, john.allen@amd.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Rijo-john.Thomas@amd.com
Subject: Re: [PATCH 0/5] Add new platform support for DBC
Date: Fri, 15 Sep 2023 18:45:37 +0800 [thread overview]
Message-ID: <ZQQ10QeAA6hSMBuo@gondor.apana.org.au> (raw)
In-Reply-To: <20230907184846.47598-1-mario.limonciello@amd.com>
On Thu, Sep 07, 2023 at 01:48:41PM -0500, Mario Limonciello wrote:
> Some platforms that support dynamic boost control (DBC) support it via
> a different mailbox than the platform access mailbox.
>
> This series adds support for those platforms.
>
> It is tested on top of the fixes series. The prerequisite patches refer
> to that series.
> Link: https://lore.kernel.org/linux-crypto/20230829150759.156126-1-mario.limonciello@amd.com/T/#m47782729377f6fe5d62130cc701dae7f15306726
>
> Mario Limonciello (4):
> crypto: ccp: Add support for extended PSP mailbox commands
> crypto: ccp: Add a communication path abstraction for DBC
> crypto: ccp: Add a macro to check capabilities register
> crypto: ccp: Add support for DBC over PSP mailbox
>
> Tom Lendacky (1):
> crypto: ccp: Move direct access to some PSP registers out of TEE
>
> drivers/crypto/ccp/dbc.c | 72 ++++++++++++++-------
> drivers/crypto/ccp/dbc.h | 29 +++------
> drivers/crypto/ccp/psp-dev.c | 122 ++++++++++++++++++++++++++++-------
> drivers/crypto/ccp/psp-dev.h | 55 ++++++++++++++++
> drivers/crypto/ccp/sp-dev.h | 4 ++
> drivers/crypto/ccp/sp-pci.c | 22 ++++---
> drivers/crypto/ccp/tee-dev.c | 48 +++-----------
> drivers/crypto/ccp/tee-dev.h | 15 +----
> 8 files changed, 241 insertions(+), 126 deletions(-)
>
>
> base-commit: 7ba2090ca64ea1aa435744884124387db1fac70f
> prerequisite-patch-id: 4bcf7f3ea21472e4e28c2457cc9827f6023ec6ca
> prerequisite-patch-id: 903be53a20306f0188e52015dbfe5196738bb2eb
> prerequisite-patch-id: af396bafb6acaa9c203c1a2c5f4665171cb45e4f
> prerequisite-patch-id: abe450d4bf1de4a5664a41dbf84e72b1d4bfdae7
> prerequisite-patch-id: b0b9cf55fcb73a11de6f3da73412fb090562857a
> --
> 2.34.1
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2023-09-15 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 18:48 [PATCH 0/5] Add new platform support for DBC Mario Limonciello
2023-09-07 18:48 ` [PATCH 1/5] crypto: ccp: Move direct access to some PSP registers out of TEE Mario Limonciello
2023-09-14 7:18 ` Rijo Thomas
2023-09-07 18:48 ` [PATCH 2/5] crypto: ccp: Add support for extended PSP mailbox commands Mario Limonciello
2023-09-07 18:48 ` [PATCH 3/5] crypto: ccp: Add a communication path abstraction for DBC Mario Limonciello
2023-09-07 18:48 ` [PATCH 4/5] crypto: ccp: Add a macro to check capabilities register Mario Limonciello
2023-09-07 18:48 ` [PATCH 5/5] crypto: ccp: Add support for DBC over PSP mailbox Mario Limonciello
2023-09-07 21:28 ` [PATCH 0/5] Add new platform support for DBC Tom Lendacky
2023-09-14 8:38 ` Rijo Thomas
2023-09-15 10:45 ` Herbert Xu [this message]
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=ZQQ10QeAA6hSMBuo@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Rijo-john.Thomas@amd.com \
--cc=davem@davemloft.net \
--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