public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
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, rafael@kernel.org, lenb@kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] Documentation: tpm: add documentation for the CRB FF-A interface
Date: Fri, 14 Feb 2025 01:38:44 +0200	[thread overview]
Message-ID: <Z66ChI32MRi2q0xT@kernel.org> (raw)
In-Reply-To: <b9a7d98a-2723-45e0-bb3b-19cd31473251@arm.com>

On Thu, Feb 13, 2025 at 04:17:56PM -0600, Stuart Yoder wrote:
> 
> 
> On 2/13/25 4:11 PM, Jarkko Sakkinen wrote:
> > On Wed, Feb 12, 2025 at 04:05:48PM -0600, Stuart Yoder wrote:
> > > Add documentation providing details of how the CRB driver interacts
> > > with FF-A.
> > > 
> > > Signed-off-by: Stuart Yoder <stuart.yoder@arm.com>
> > > ---
> > >   Documentation/security/tpm/tpm_ffa_crb.rst | 65 ++++++++++++++++++++++
> > >   1 file changed, 65 insertions(+)
> > >   create mode 100644 Documentation/security/tpm/tpm_ffa_crb.rst
> > > 
> > > diff --git a/Documentation/security/tpm/tpm_ffa_crb.rst b/Documentation/security/tpm/tpm_ffa_crb.rst
> > > new file mode 100644
> > > index 000000000000..c70f8904a93d
> > > --- /dev/null
> > > +++ b/Documentation/security/tpm/tpm_ffa_crb.rst
> > > @@ -0,0 +1,65 @@
> > > +.. SPDX-License-Identifier: GPL-2.0
> > > +
> > > +========================
> > > +TPM CRB over FF-A Driver
> > > +========================
> > > +
> > > +The TPM Command Response Buffer (CRB) interface is a standard TPM interface
> > > +defined in the TCG PC Client Platform TPM Profile (PTP) Specification [1]_.
> > > +The CRB provides a structured set of control registers a client uses when
> > > +interacting with a TPM as well as a data buffer for storing TPM commands and
> > > +responses. A CRB interface can be implemented in:
> > > +
> > > +- hardware registers in a discrete TPM chip
> > > +
> > > +- in memory for a TPM running in isolated environment where shared memory
> > > +  allows a client to interact with the TPM
> > > +
> > > +The Firmware Framework for Arm A-profile (FF-A) [2]_ is a specification
> > > +that defines interfaces and protocols for the following purposes:
> > > +
> > > +- Compartmentalize firmware into software partitions that run in the Arm
> > > +  Secure world environment (also know as TrustZone)
> > 
> > Does that also cover ARM CCA? Just a question (not a review question).
> 
> No, CCA is for confidential VMs which is a separate trusted execution
> environment and FF-A is not used there.

OK, cool, just plain interested :-)

> 
> Thanks,
> Stuart

BR, Jarkko

      reply	other threads:[~2025-02-13 23:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 22:05 [PATCH v2 0/5] Add support for the TPM FF-A start method Stuart Yoder
2025-02-12 22:05 ` [PATCH v2 1/5] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-02-13 22:14   ` Jarkko Sakkinen
2025-02-13 22:22     ` Stuart Yoder
2025-02-13 23:37       ` Jarkko Sakkinen
2025-02-16  0:28   ` kernel test robot
2025-02-12 22:05 ` [PATCH v2 2/5] tpm_crb: refactor check for idle support into TPM into inline function Stuart Yoder
2025-02-13 22:13   ` Jarkko Sakkinen
2025-02-13 22:23     ` Stuart Yoder
2025-02-12 22:05 ` [PATCH v2 3/5] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-02-12 22:05 ` [PATCH v2 4/5] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-02-12 22:05 ` [PATCH v2 5/5] Documentation: tpm: add documentation for the CRB FF-A interface Stuart Yoder
2025-02-13 22:11   ` Jarkko Sakkinen
2025-02-13 22:17     ` Stuart Yoder
2025-02-13 23:38       ` Jarkko Sakkinen [this message]

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=Z66ChI32MRi2q0xT@kernel.org \
    --to=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=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