From: Yi Chou <yich-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Julius Werner <jwerner-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
jkardatzke-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
jens.wiklander-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
"yich-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org"
<yich-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
chenyian-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org
Subject: Device tree usage in TF-A & OP-Tee consultation
Date: Tue, 13 Jun 2023 12:25:19 +0800 [thread overview]
Message-ID: <CABOkjxJnzTm=jJUy4Zgi9kGxLTBHvmrkM80UhgSdzyYcL4xfzA@mail.gmail.com> (raw)
Hi, Linux device tree maintainers,
I am writing to you today to request a review of some custom device
tree bindings that we have developed. These bindings are not used by
the Linux kernel, but they are used by OP-TEE[1], a secure execution
environment for embedded systems.
We have placed these bindings under the "chosen" node in the device
tree, as suggested by Jeffrey Kardatzke.[2]
The full bindings path would be "chosen/widevine/{tpm-auth-pk, huk,
widevine-dice, widevine-ta-key}".
We would like to have our bindings reviewed by a device tree
maintainer to ensure that they are correct. We would also like to get
your feedback on the best way to document these bindings.
Thank you for your time and consultation.
Sincerely,
Yi
[1]: https://github.com/OP-TEE/optee_os
[2]: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/20442
next reply other threads:[~2023-06-13 4:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 4:25 Yi Chou [this message]
[not found] ` <CABOkjxJnzTm=jJUy4Zgi9kGxLTBHvmrkM80UhgSdzyYcL4xfzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-13 14:38 ` Device tree usage in TF-A & OP-Tee consultation Rob Herring
2023-06-13 14:58 ` Simon Glass
[not found] ` <CAPnjgZ1inUgJ94kugnGSDbQ0dhfxouObyr=VjdUYG81+bv5DjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-14 7:52 ` Yi Chou
2023-06-20 16:50 ` Simon Glass
[not found] ` <CAODwPW9-ueC6e-A766fRbiWJpiuN07WrRWVKJEoR-zRg7WYK6A@mail.gmail.com>
[not found] ` <CAODwPW9-ueC6e-A766fRbiWJpiuN07WrRWVKJEoR-zRg7WYK6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-07 20:35 ` Rob Herring
[not found] ` <CAL_Jsq+SeqSVTP89idwo8fNUvzk_H+WcbNW7R+yasMk26EW+hA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-24 10:02 ` Yi Chou
[not found] ` <CABOkjxLSKT3NvCUfxdWnMBVyaY9qCYdFupr+CRn=HXetRaWD2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-25 14:51 ` Simon Glass
[not found] ` <CAPnjgZ3d7-hKVZ_isAFXp_MxnNq4phWsAdJ19qKSHS7CAwp1qA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-25 16:37 ` Rob Herring
[not found] ` <CAL_Jsq+k=7eHmta-0OqmSP8wZVErkS6zyuJ5D5V1YVKciv0Zwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-08 8:08 ` Yi Chou
[not found] ` <CABOkjxKG=qfgSwDpY5+=jsS4K68maPYKZA4DkKHxaJ_XHRdfNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-09 14:58 ` Rob Herring
[not found] ` <CAL_JsqKOEELQR6G4egrC=d94o9ZHsfuaSz0cVP8gzakZORjh7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-10 7:39 ` Yi Chou
[not found] ` <CABOkjxKwnS5K082dZgcxqZ+x5+AMeuDsW_u7mVko81_td9u_uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-15 14:44 ` Simon Glass
[not found] ` <CAPnjgZ2QUEDqOkWyDm=tvBAxJRxH+TrQWDfmC8rQsSNdxR=iCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-15 23:58 ` Yi Chou
[not found] ` <CABOkjx+DT99NgWCWmKyexDvDR8-RLOdjnXpoOr5MOBeFwdwd9w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-16 1:57 ` Simon Glass
[not found] ` <CAPnjgZ3b7vXTUVdTYVNP=k8dGqNu9-pnLUV-jLJ-taa01MThOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-08-16 5:34 ` Yi Chou
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='CABOkjxJnzTm=jJUy4Zgi9kGxLTBHvmrkM80UhgSdzyYcL4xfzA@mail.gmail.com' \
--to=yich-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=chenyian-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jens.wiklander-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=jkardatzke-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=jwerner-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=yich-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).