From: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>
Cc: peterhuewe@gmx.de, jarkko@kernel.org, jgg@ziepe.ca,
sumit.garg@oss.qualcomm.com, linux-kernel@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3 0/2] tpm: OP-TEE transport core for discrete and firmware TPMs
Date: Wed, 11 Nov 2026 23:02:57 +0100 [thread overview]
Message-ID: <avTmEXZzyyjxA2dy@trex> (raw)
In-Reply-To: <20261111215940.3503287-1-jorge.ramirez@oss.qualcomm.com>
On 11/11/26 22:59:33, Jorge Ramirez-Ortiz wrote:
> This adds a driver for a discrete TPM that OP-TEE owns and the normal
> world cannot reach directly, and factors the shared OP-TEE TEE transport
> into a small core so the existing fTPM driver uses it too:
>
> - a transport core shared by the OP-TEE TPM front-ends;
> - a new discrete TPM front-end;
> - the fTPM driver converted onto the core, keeping its name, its
> platform/OF binding and its shutdown path.
>
> Patch 1 is the feature; patch 2 is the fTPM conversion that justifies the
> core. Both front-ends were exercised on the Qualcomm Lemans EVK over the
> shared core: the discrete ST33 TPM (patch 1) and the MS-TPM-20 firmware
> TPM TA (patch 2), each presenting a working /dev/tpm0 (tpm2_getrandom,
> PCR read). The fTPM TA is the same MS-TPM-20 reference the existing
> tpm_ftpm_tee platforms use.
>
> This is the normal-world half. The secure-world OP-TEE support it binds
> to -- the in-core TPM2 SPI (TIS) driver and the mediator pseudo TA that
> relays commands to it -- is under review separately:
>
> OP-TEE support: https://github.com/OP-TEE/optee_os/pull/8155
> locality 4: https://github.com/OP-TEE/optee_os/issues/8160
> (design follow-up: the secure world policing
> normal-world locality access to the shared chip)
>
> Build and test it on the Qualcomm Lemans EVK (a discrete ST33 TPM on
> SPI, owned by OP-TEE):
>
> https://qualcomm-linux.github.io/qcom-buildroot/lemans/quick-start.html
The above was the wrong link, please use this one:
https://qualcomm-linux.github.io/qcom-buildroot/lemans/devel_lemans_security_dtpm.html
prev parent reply other threads:[~2026-11-11 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 21:59 Jorge Ramirez-Ortiz
2026-11-11 21:59 ` [PATCH v3 1/2] tpm: add OP-TEE transport core and a discrete TPM driver Jorge Ramirez-Ortiz
2026-11-11 21:59 ` [PATCH v3 2/2] tpm_ftpm_tee: use the tpm_optee transport core Jorge Ramirez-Ortiz
2026-11-11 22:02 ` Jorge Ramirez [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=avTmEXZzyyjxA2dy@trex \
--to=jorge.ramirez@oss.qualcomm.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=sumit.garg@oss.qualcomm.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®