From: Sumit Garg via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: OP-TEE TrustedFirmware <op-tee@lists.trustedfirmware.org>,
linaro-open-discussions@op-lists.linaro.org
Subject: Re: Linaro OP-TEE Contribution, LOC, monthly meeting May 27
Date: Mon, 26 May 2025 15:54:37 +0530 [thread overview]
Message-ID: <aDRBZVy9tsws659J@sumit-X1> (raw)
In-Reply-To: <CAHUa44HpAVR+sDM-Jb6DWo_goFMRZt3VVpi7Kg=5+aYpJLssZw@mail.gmail.com>
Hi Jens,
On Mon, May 26, 2025 at 11:15:37AM +0200, Jens Wiklander wrote:
> Hi,
>
> Tomorrow, Tuesday, it's time for another LOC monthly meeting. For time
> and connection details, see the calendar at
> https://www.trustedfirmware.org/meetings/
>
> OP-TEE version 4.6.0 was released on April 25.
>
> Amir posted a v4 [1] of the QTEE driver. Sumit and I have spent quite
> a bit of time reviewing this, but it would be welcome with comments
> from others, too. For instance, for "tee: add
> TEE_IOCTL_PARAM_ATTR_TYPE_UBUF" which adds yet another type of memory
> reference.
>
> optee_ftpm Issue "Warning in _plat__GetUnique()" [2], digging in this
> reveals further issues.
>
> [1] https://lore.kernel.org/lkml/20250428-qcom-tee-using-tee-ss-without-mem-obj-v4-0-6a143640a6cb@oss.qualcomm.com/
> [2] https://github.com/OP-TEE/optee_ftpm/issues/15
>
> Are there any other topics?
Another topic:
- dTPM access via OP-TEE and exposing access to Linux via kernel driver
(tpm_ftpm_tee)
-Sumit
prev parent reply other threads:[~2025-05-26 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 9:15 Linaro OP-TEE Contribution, LOC, monthly meeting May 27 Jens Wiklander
2025-05-26 10:24 ` Sumit Garg via OP-TEE [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=aDRBZVy9tsws659J@sumit-X1 \
--to=op-tee@lists.trustedfirmware.org \
--cc=jens.wiklander@linaro.org \
--cc=linaro-open-discussions@op-lists.linaro.org \
--cc=sumit.garg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox