From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH 2/2] optee-ftpm: enumerate also without tee-supplicant
Date: Mon, 22 Apr 2024 11:13:05 +0300 [thread overview]
Message-ID: <ZiYcEcLpKX9DDjpd@nuoska> (raw)
In-Reply-To: <CAFA6WYMk9vA429qR4jQ=TW5Odj9T3mnFQF_yzVCTdYhPKCX04g@mail.gmail.com>
Hi,
On Mon, Apr 22, 2024 at 01:02:49AM -0700, Sumit Garg wrote:
> Hi Mikko,
>
> On Wed, 17 Apr 2024 at 04:08, Mikko Rapeli via lists.yoctoproject.org
> <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote:
> >
> > Userspace like systemd boot manager would need to know
> > how to find TPM and fTPM devices for rootfs encryption.
> > Thus expose an fTPM TA enumeration also without tee-supplicant
>
> fTPM TA due to secure storage requirements needs a tee-supplicant to
> be up and running for a successful kernel driver probe. So CI failure
> is expected as you see in the other thread.
>
> So it's a chicken and egg situation for your rootfs encryption
> use-case. I suppose once the RPMB subsystem [1] makes its way into the
> mainline kernel then the dependency on tee-supplicant can be dropped.
>
> [1] https://lists.trustedfirmware.org/archives/list/op-tee@lists.trustedfirmware.org/thread/6A62HMDQST2O3T2UGGN6UPXZKLKLUNM4/
Yes, optee and kernel RPMB support without tee-supplicant in userspace are
the reason why I'm testing changes like this. I actually have both the
optee and kernel changes applied in the setup I'm testing and am trying to
upstream some of the changes. It can be that this fTPM enumeration change
doesn't work without the optee and kernel RPMB changes. For testing
purposes the tf-a change is very nice to have so that qemu boot with
and without swtpm can be tested. I'll look into details of this fTPM enumeration
related error.
Cheers,
-Mikko
next prev parent reply other threads:[~2024-04-22 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:07 [PATCH 1/2] trusted-firmware-a: continue if TPM device is missing Mikko Rapeli
2024-04-17 11:07 ` [PATCH 2/2] optee-ftpm: enumerate also without tee-supplicant Mikko Rapeli
2024-04-22 8:02 ` [meta-arm] " Sumit Garg
2024-04-22 8:13 ` Mikko Rapeli [this message]
2024-04-30 12:44 ` Mikko Rapeli
2024-04-20 22:40 ` [PATCH 1/2] trusted-firmware-a: continue if TPM device is missing Jon Mason
2024-04-22 7:29 ` Mikko Rapeli
2024-04-23 18:21 ` Jon Mason
2024-04-24 6:37 ` Mikko Rapeli
-- strict thread matches above, loose matches on Subject: below --
2024-04-30 12:37 [PATCH v2 0/6] TPM and fTPM test Mikko Rapeli
2024-04-30 12:37 ` [PATCH 1/6] trusted-firmware-a: continue if TPM device is missing Mikko Rapeli
2024-04-30 12:37 ` [PATCH 2/6] optee-os: inrease heap size with fTPM Mikko Rapeli
2024-04-30 12:37 ` [PATCH 3/6] oeqa runtime: add optee.py test Mikko Rapeli
2024-04-30 12:37 ` [PATCH 4/6] oeqa runtime: add ftpm.py test Mikko Rapeli
2024-04-30 12:37 ` [PATCH 5/6] ci/qemuarm64-secureboot.yml: install optee and test both optee and ftpm Mikko Rapeli
2024-04-30 12:37 ` [PATCH 6/6] ci/qemuarm-secureboot.yml: " Mikko Rapeli
2024-05-01 2:06 ` [PATCH v2 0/6] TPM and fTPM test Jon Mason
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=ZiYcEcLpKX9DDjpd@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=sumit.garg@linaro.org \
/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.