From: Tom Lendacky <thomas.lendacky@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: "open list:AMD CRYPTOGRAPHIC COPROCESSOR (CCP) DRIVER - DB..."
<linux-crypto@vger.kernel.org>,
Richard Hughes <hughsient@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] crypto: ccp: Add support for getting security attributes on some older systems
Date: Tue, 28 May 2024 10:28:11 -0500 [thread overview]
Message-ID: <946a0fed-a3a0-8d67-8620-b58ce413cd12@amd.com> (raw)
In-Reply-To: <20240527152649.3722-5-mario.limonciello@amd.com>
On 5/27/24 10:26, Mario Limonciello wrote:
> Older systems will not populate the security attributes in the
> capabilities register. The PSP on these systems, however, does have a
> command to get the security attributes. Use this command during ccp
> startup to populate the attributes if they're missing.
>
> Closes: https://github.com/fwupd/fwupd/issues/5284
> Closes: https://github.com/fwupd/fwupd/issues/5675
> Closes: https://github.com/fwupd/fwupd/issues/6253
> Closes: https://github.com/fwupd/fwupd/issues/7280
> Closes: https://github.com/fwupd/fwupd/issues/6323
> Closes: https://github.com/fwupd/fwupd/discussions/5433
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/crypto/ccp/hsti.c | 63 +++++++++++++++++++++++++++++
> drivers/crypto/ccp/hsti.h | 2 +
> drivers/crypto/ccp/psp-dev.c | 5 +++
> drivers/crypto/ccp/psp-dev.h | 2 -
> drivers/crypto/ccp/sp-dev.h | 1 +
> drivers/crypto/ccp/sp-pci.c | 5 ++-
> include/linux/psp-platform-access.h | 1 +
> 7 files changed, 76 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/crypto/ccp/hsti.c b/drivers/crypto/ccp/hsti.c
> index 076c1d175b2b..8f583902d786 100644
> --- a/drivers/crypto/ccp/hsti.c
> +++ b/drivers/crypto/ccp/hsti.c
> +int psp_init_hsti(struct psp_device *psp)
> +{
> + int ret;
> +
> + if (PSP_FEATURE(psp, HSTI)) {
> + ret = psp_poulate_hsti(psp);
> + if (ret)
> + return ret;
> + }
> +
> + /*
> + * At this stage, if security information hasn't been populated by
> + * either the PSP or by the driver through the platform command,
> + * then there is nothing more to do.
> + */
> + if (!psp->capability.security_reporting)
> + return 0;
This should really be part of patch #5, since it doesn't make a lot of
sense at this stage.
Thanks,
Tom
> +
> + return 0;
> +}
next prev parent reply other threads:[~2024-05-28 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 15:26 [PATCH 0/5] Enable PSP security attributes on more SoCs Mario Limonciello
2024-05-27 15:26 ` [PATCH 1/5] crypto: ccp: Represent capabilities register as a union Mario Limonciello
2024-05-28 15:30 ` Tom Lendacky
2024-05-27 15:26 ` [PATCH 2/5] crypto: ccp: Move security attributes to their own file Mario Limonciello
2024-05-28 15:30 ` Tom Lendacky
2024-05-28 20:13 ` kernel test robot
2024-05-27 15:26 ` [PATCH 3/5] crypto: ccp: align psp_platform_access_msg Mario Limonciello
2024-05-28 15:30 ` Tom Lendacky
2024-05-27 15:26 ` [PATCH 4/5] crypto: ccp: Add support for getting security attributes on some older systems Mario Limonciello
2024-05-28 15:28 ` Tom Lendacky [this message]
2024-05-27 15:26 ` [PATCH 5/5] crypto: ccp: Move message about TSME being enabled later in init Mario Limonciello
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=946a0fed-a3a0-8d67-8620-b58ce413cd12@amd.com \
--to=thomas.lendacky@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=hughsient@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@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®