From: Mario Limonciello <mario.limonciello@amd.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Tom Lendacky <thomas.lendacky@amd.com>,
John Allen <john.allen@amd.com>
Cc: David S Miller <davem@davemloft.net>,
Mario Limonciello <mario.limonciello@amd.com>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 03/10] crypto: ccp: Add bootloader and TEE version offsets
Date: Fri, 28 Apr 2023 13:55:33 -0500 [thread overview]
Message-ID: <20230428185543.8381-4-mario.limonciello@amd.com> (raw)
In-Reply-To: <20230428185543.8381-1-mario.limonciello@amd.com>
The bootloader and TEE versions are stored in registers that can be
accessed from sysfs. This exports the information for recent client
and datacenter parts.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/crypto/ccp/sp-pci.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/crypto/ccp/sp-pci.c b/drivers/crypto/ccp/sp-pci.c
index 7ef7c09b4a2f..46dd7a2ade18 100644
--- a/drivers/crypto/ccp/sp-pci.c
+++ b/drivers/crypto/ccp/sp-pci.c
@@ -423,6 +423,7 @@ static const struct tee_vdata teev1 = {
.cmdbuff_addr_hi_reg = 0x1054c, /* C2PMSG_19 */
.ring_wptr_reg = 0x10550, /* C2PMSG_20 */
.ring_rptr_reg = 0x10554, /* C2PMSG_21 */
+ .info_reg = 0x109e8, /* C2PMSG_58 */
};
static const struct platform_access_vdata pa_v1 = {
@@ -435,6 +436,7 @@ static const struct platform_access_vdata pa_v1 = {
static const struct psp_vdata pspv1 = {
.sev = &sevv1,
+ .bootloader_info_reg = 0x105ec, /* C2PMSG_59 */
.feature_reg = 0x105fc, /* C2PMSG_63 */
.inten_reg = 0x10610, /* P2CMSG_INTEN */
.intsts_reg = 0x10614, /* P2CMSG_INTSTS */
@@ -442,6 +444,7 @@ static const struct psp_vdata pspv1 = {
static const struct psp_vdata pspv2 = {
.sev = &sevv2,
+ .bootloader_info_reg = 0x109ec, /* C2PMSG_59 */
.feature_reg = 0x109fc, /* C2PMSG_63 */
.inten_reg = 0x10690, /* P2CMSG_INTEN */
.intsts_reg = 0x10694, /* P2CMSG_INTSTS */
@@ -450,6 +453,7 @@ static const struct psp_vdata pspv2 = {
static const struct psp_vdata pspv3 = {
.tee = &teev1,
.platform_access = &pa_v1,
+ .bootloader_info_reg = 0x109ec, /* C2PMSG_59 */
.feature_reg = 0x109fc, /* C2PMSG_63 */
.inten_reg = 0x10690, /* P2CMSG_INTEN */
.intsts_reg = 0x10694, /* P2CMSG_INTSTS */
@@ -458,6 +462,7 @@ static const struct psp_vdata pspv3 = {
static const struct psp_vdata pspv4 = {
.sev = &sevv2,
.tee = &teev1,
+ .bootloader_info_reg = 0x109ec, /* C2PMSG_59 */
.feature_reg = 0x109fc, /* C2PMSG_63 */
.inten_reg = 0x10690, /* P2CMSG_INTEN */
.intsts_reg = 0x10694, /* P2CMSG_INTSTS */
--
2.34.1
next prev parent reply other threads:[~2023-04-28 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 18:55 [PATCH v2 00/10] Add dynamic boost control support Mario Limonciello
2023-04-28 18:55 ` [PATCH v2 01/10] crypto: ccp: Rename macro for security attributes Mario Limonciello
2023-05-01 18:36 ` Tom Lendacky
2023-04-28 18:55 ` [PATCH v2 02/10] crypto: ccp: Add support for displaying PSP firmware versions Mario Limonciello
2023-05-01 18:38 ` Tom Lendacky
2023-04-28 18:55 ` Mario Limonciello [this message]
2023-05-01 18:39 ` [PATCH v2 03/10] crypto: ccp: Add bootloader and TEE version offsets Tom Lendacky
2023-04-28 18:55 ` [PATCH v2 04/10] crypto: ccp: move setting PSP master to earlier in the init Mario Limonciello
2023-05-01 18:47 ` Tom Lendacky
2023-05-01 19:57 ` Limonciello, Mario
2023-04-28 18:55 ` [PATCH v2 05/10] crypto: ccp: Add support for fetching a nonce for dynamic boost control Mario Limonciello
2023-04-28 18:55 ` [PATCH v2 06/10] crypto: ccp: Add support for setting user ID " Mario Limonciello
2023-04-28 18:55 ` [PATCH v2 07/10] crypto: ccp: Add support for getting and setting DBC parameters Mario Limonciello
2023-04-28 18:55 ` [PATCH v2 08/10] crypto: ccp: Add a sample script for Dynamic Boost Control Mario Limonciello
2023-04-28 18:55 ` [PATCH v2 09/10] crypto: ccp: Add unit tests for dynamic boost control Mario Limonciello
2023-04-28 18:55 ` [PATCH v2 10/10] crypto: ccp: Add Mario to MAINTAINERS 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=20230428185543.8381-4-mario.limonciello@amd.com \
--to=mario.limonciello@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=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®