From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stuart Yoder <stuart.yoder@arm.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
sudeep.holla@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tpm_crb: ffa_tpm: fix/update comments describing the CRB over FFA ABI
Date: Wed, 30 Apr 2025 19:06:53 +0300 [thread overview]
Message-ID: <aBJKnYJgke_clJOn@kernel.org> (raw)
In-Reply-To: <20250430154723.1025101-1-stuart.yoder@arm.com>
On Wed, Apr 30, 2025 at 10:47:23AM -0500, Stuart Yoder wrote:
> -Fix the comment describing the 'start' function, which was a cut/paste
> mistake for a different function.
>
> -The comment for DIRECT_REQ and DIRECT_RESP only mentioned AArch32
> and listed 32-bit function IDs. Update to include 64-bit.
>
> Signed-off-by: Stuart Yoder <stuart.yoder@arm.com>
> ---
> v2:
> -squashed the two comment updates into a single patch
>
> drivers/char/tpm/tpm_crb_ffa.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/char/tpm/tpm_crb_ffa.c b/drivers/char/tpm/tpm_crb_ffa.c
> index 3169a87a56b60..134747911ba38 100644
> --- a/drivers/char/tpm/tpm_crb_ffa.c
> +++ b/drivers/char/tpm/tpm_crb_ffa.c
> @@ -38,9 +38,11 @@
> * messages.
> *
> * All requests with FFA_MSG_SEND_DIRECT_REQ and FFA_MSG_SEND_DIRECT_RESP
> - * are using the AArch32 SMC calling convention with register usage as
> - * defined in FF-A specification:
> - * w0: Function ID (0x8400006F or 0x84000070)
> + * are using the AArch32 or AArch64 SMC calling convention with register usage
> + * as defined in FF-A specification:
> + * w0: Function ID
> + * -for 32-bit: 0x8400006F or 0x84000070
> + * -for 64-bit: 0xC400006F or 0xC4000070
> * w1: Source/Destination IDs
> * w2: Reserved (MBZ)
> * w3-w7: Implementation defined, free to be used below
> @@ -68,7 +70,8 @@
> #define CRB_FFA_GET_INTERFACE_VERSION 0x0f000001
>
> /*
> - * Return information on a given feature of the TPM service
> + * Notifies the TPM service that a TPM command or TPM locality request is
> + * ready to be processed, and allows the TPM service to process it.
> * Call register usage:
> * w3: Not used (MBZ)
> * w4: TPM service function ID, CRB_FFA_START
> --
> 2.34.1
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
next prev parent reply other threads:[~2025-04-30 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 15:47 [PATCH v2] tpm_crb: ffa_tpm: fix/update comments describing the CRB over FFA ABI Stuart Yoder
2025-04-30 16:06 ` Jarkko Sakkinen [this message]
2025-04-30 16:17 ` Sudeep Holla
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=aBJKnYJgke_clJOn@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stuart.yoder@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox