From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Gyorgy Szing <Gyorgy.Szing@arm.com>
Cc: "meta-arm@lists.yoctoproject.org" <meta-arm@lists.yoctoproject.org>
Subject: Re: [meta-arm] [PATCH v3 2/2] trusted-service: remove optee udev and group settings
Date: Thu, 17 Oct 2024 11:34:32 +0300 [thread overview]
Message-ID: <ZxDMGLYsOSe9rPFO@nuoska> (raw)
In-Reply-To: <AS8PR08MB589563A608DE289457643CA991472@AS8PR08MB5895.eurprd08.prod.outlook.com>
Hi,
On Thu, Oct 17, 2024 at 08:17:32AM +0000, Gyorgy Szing wrote:
> How is the system going to work if op-tee client is not deployed, but libts is? E.g. if the SPMC is Hafnium and no S-EL1 OP-TEE SP is needed, but the FWU SP is used?
If optee-client is not installed, then optee is not functional
in Linux userspace and rootfs so optee-test fails. The plain
kernel driver for optee will work and /dev/tee* and /dev/teepriv* interfaces
will pop up with root access rights, but not with the setup expected by
tee-supplicant systemd service file from optee-client. This may be enough for TS
use cases.
In the firmware side, optee services are not affected.
If this impacts libts users, then IMO they need to install optee-client or
setup the udev rules etc in some other way.
Is there some problem I missed or a setup which is not covered in meta-arm testing?
Cheers,
-Mikko
next prev parent reply other threads:[~2024-10-17 8:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 6:59 [PATCH v3 1/2] optee-client: use udev rule and systemd service from upstream Mikko Rapeli
2024-10-17 6:59 ` [PATCH v3 2/2] trusted-service: remove optee udev and group settings Mikko Rapeli
2024-10-17 8:17 ` [meta-arm] " Gyorgy Szing
2024-10-17 8:34 ` Mikko Rapeli [this message]
2024-10-17 9:44 ` Gyorgy Szing
2024-10-17 9:52 ` Mikko Rapeli
2024-10-17 10:54 ` Gyorgy Szing
2024-10-17 11:09 ` Mikko Rapeli
2024-10-17 13:38 ` Gyorgy Szing
2024-10-17 13:38 ` Adam Johnston
2024-10-17 14:48 ` Anton Antonov
2024-10-18 5:51 ` [meta-arm] " Mikko Rapeli
2024-10-23 14:22 ` [PATCH v3 1/2] optee-client: use udev rule and systemd service from upstream Tom Hochstein (OSS)
2024-10-23 14:30 ` Mikko Rapeli
[not found] ` <PAXPR04MB9448DC39953E357F3E73D07EE24D2@PAXPR04MB9448.eurprd04.prod.outlook.com>
2024-10-23 14:54 ` Mikko Rapeli
2024-10-29 17:02 ` Tom Hochstein
2024-10-30 8:02 ` [meta-arm] " Gyorgy Szing
2024-11-26 14:55 ` Mikko Rapeli
2024-11-26 21:05 ` Gyorgy Szing
2024-11-27 14:27 ` Mikko Rapeli
2024-12-11 14:42 ` Ross Burton
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=ZxDMGLYsOSe9rPFO@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Gyorgy.Szing@arm.com \
--cc=meta-arm@lists.yoctoproject.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.