From: Stuart Yoder <stuart.yoder@arm.com>
To: linux-integrity@vger.kernel.org, jarkko@kernel.org,
peterhuewe@gmx.de, jgg@ziepe.ca, sudeep.holla@arm.com,
rafael@kernel.org, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Add support for the TPM FF-A start method
Date: Mon, 10 Feb 2025 17:22:23 -0600 [thread overview]
Message-ID: <20250210232227.97761-1-stuart.yoder@arm.com> (raw)
These patches add support for the CRB FF-A start method defined
in the TCG ACPI specification v1.4 and the FF-A ABI defined
in the Arm TPM Service CRB over FF-A (DEN0138) specification.
(https://developer.arm.com/documentation/den0138/latest/)
FF-A is a messaging framework for Arm-based systems and in the
context of the TPM driver is used to signal 'start' to a CRB-based
TPM service which is hosted in an FF-A secure partition running in
TrustZone.
The first patch adds an FF-A driver to handle the FF-A messaging when
communicating with a CRB-based TPM secure partition built on FF-A.
The driver is probed when the TPM secure partition is discovered by
the Linux FF-A infrastructure.
The second patch consolidates the check for idle support in the CRB
driver to one place.
The third patch defines the new ACPI start method enumeration for
CRB over FF-A.
The fourth patch adds support for the FF-A ACPI start method to
the TPM crb driver.
Stuart Yoder (4):
tpm_crb: implement driver compliant to CRB over FF-A
tpm_crb: refactor check for idle support into TPM into inline function
ACPICA: add start method for Arm FF-A
tpm_crb: add support for the Arm FF-A start method
drivers/char/tpm/Kconfig | 9 ++
drivers/char/tpm/Makefile | 1 +
drivers/char/tpm/ffa_crb.c | 310 +++++++++++++++++++++++++++++++++++++
drivers/char/tpm/ffa_crb.h | 30 ++++
drivers/char/tpm/tpm_crb.c | 81 +++++++++-
include/acpi/actbl3.h | 1 +
6 files changed, 426 insertions(+), 6 deletions(-)
create mode 100644 drivers/char/tpm/ffa_crb.c
create mode 100644 drivers/char/tpm/ffa_crb.h
--
2.34.1
next reply other threads:[~2025-02-10 23:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 23:22 Stuart Yoder [this message]
2025-02-10 23:22 ` [PATCH 1/4] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-02-11 21:08 ` Jarkko Sakkinen
2025-02-11 23:21 ` Stuart Yoder
2025-02-10 23:22 ` [PATCH 2/4] tpm_crb: refactor check for idle support into TPM into inline function Stuart Yoder
2025-02-10 23:22 ` [PATCH 3/4] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-02-11 9:57 ` Sudeep Holla
2025-02-11 21:50 ` Stuart Yoder
2025-02-10 23:22 ` [PATCH 4/4] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-02-11 6:45 ` [PATCH 0/4] Add support for the TPM " Sumit Garg
2025-02-11 16:09 ` Stuart Yoder
2025-02-12 7:39 ` Sumit Garg
2025-02-12 21:55 ` Stuart Yoder
2025-02-13 5:31 ` Sumit Garg
2025-02-13 15:19 ` Stuart Yoder
2025-02-17 5:17 ` Sumit Garg
2025-02-17 16:56 ` Stuart Yoder
2025-02-21 13:46 ` Sumit Garg
2025-02-21 14:02 ` Sudeep Holla
2025-02-21 18:29 ` Stuart Yoder
2025-02-22 15:39 ` Sudeep Holla
2025-02-11 10:12 ` Sudeep Holla
2025-02-11 21:07 ` Jarkko Sakkinen
2025-02-11 23:21 ` Stuart Yoder
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=20250210232227.97761-1-stuart.yoder@arm.com \
--to=stuart.yoder@arm.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.