mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	"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: [PATCH 0/5] Enable PSP security attributes on more SoCs
Date: Mon, 27 May 2024 10:26:44 -0500	[thread overview]
Message-ID: <20240527152649.3722-1-mario.limonciello@amd.com> (raw)

On some older SoCs the PSP doesn't export security attributes in the
capabilities register.  On these SoCs it is however possible to get
the information by a platform access command.

Restructure the driver to move all security attribute handling to
a central location and then add support for calling the platform
access command on those processors.

Mario Limonciello (5):
  crypto: ccp: Represent capabilities register as a union
  crypto: ccp: Move security attributes to their own file
  crypto: ccp: align psp_platform_access_msg
  crypto: ccp: Add support for getting security attributes on some older
    systems
  crypto: ccp: Move message about TSME being enabled later in init

 MAINTAINERS                         |   6 ++
 drivers/crypto/ccp/Makefile         |   3 +-
 drivers/crypto/ccp/dbc.c            |   2 +-
 drivers/crypto/ccp/hsti.c           | 138 ++++++++++++++++++++++++++++
 drivers/crypto/ccp/hsti.h           |  17 ++++
 drivers/crypto/ccp/psp-dev.c        |  23 ++---
 drivers/crypto/ccp/psp-dev.h        |  46 +++++-----
 drivers/crypto/ccp/sp-dev.h         |   2 +-
 drivers/crypto/ccp/sp-pci.c         |  65 ++-----------
 include/linux/psp-platform-access.h |   5 +-
 10 files changed, 208 insertions(+), 99 deletions(-)
 create mode 100644 drivers/crypto/ccp/hsti.c
 create mode 100644 drivers/crypto/ccp/hsti.h

-- 
2.43.0


             reply	other threads:[~2024-05-27 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 15:26 Mario Limonciello [this message]
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
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=20240527152649.3722-1-mario.limonciello@amd.com \
    --to=mario.limonciello@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=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®