From: Igor Opaniuk <igor.opaniuk@foundries.io>
To: u-boot@lists.denx.de
Subject: [RFC PATCH v2 2/2] doc: device-tree-bindings: optee: support rpmb-dev property
Date: Sun, 24 Jan 2021 11:39:46 +0200 [thread overview]
Message-ID: <20210124093946.103018-2-igor.opaniuk@gmail.com> (raw)
In-Reply-To: <20210124093946.103018-1-igor.opaniuk@gmail.com>
From: Igor Opaniuk <igor.opaniuk@foundries.io>
Add support for "rpmb-dev" property which provides eMMC phandle
for RPMB-related operations.
This commit is created only to show DT node updates for RFC patch,
obviously that node should be updated in device-tree-bindings in
Linux first, that pulled here.
Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
---
Changes v2:
- Add ";" after phandle
doc/device-tree-bindings/firmware/linaro,optee-tz.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/device-tree-bindings/firmware/linaro,optee-tz.txt b/doc/device-tree-bindings/firmware/linaro,optee-tz.txt
index d38834c67d..1776dd9606 100644
--- a/doc/device-tree-bindings/firmware/linaro,optee-tz.txt
+++ b/doc/device-tree-bindings/firmware/linaro,optee-tz.txt
@@ -20,6 +20,8 @@ the reference implementation maintained by Linaro.
"hvc" : HVC #0, with the register assignments specified
in drivers/tee/optee/optee_smc.h
+- rpmb-dev : contains phandle to the eMMC device, whose RPMB partition
+ is used for secure storage.
Example:
@@ -27,5 +29,6 @@ Example:
optee {
compatible = "linaro,optee-tz";
method = "smc";
+ rpmb-dev = <&mmc0>;
};
};
--
2.25.1
next prev parent reply other threads:[~2021-01-24 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 9:39 [RFC PATCH v2 1/2] optee: obtain emmc rpmb info from dt Igor Opaniuk
2021-01-24 9:39 ` Igor Opaniuk [this message]
2021-01-25 8:50 ` Jens Wiklander
2021-01-25 11:49 ` Igor Opaniuk
2021-01-25 12:20 ` Jens Wiklander
2021-02-08 15:06 ` Patrick DELAUNAY
2021-02-08 23:33 ` Igor Opaniuk
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=20210124093946.103018-2-igor.opaniuk@gmail.com \
--to=igor.opaniuk@foundries.io \
--cc=u-boot@lists.denx.de \
/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.