From: carlo@caione.org (Carlo Caione)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 4/4] documentation: Add secure monitor binding documentation
Date: Mon, 23 May 2016 18:30:24 +0200 [thread overview]
Message-ID: <1464021024-29380-5-git-send-email-carlo@caione.org> (raw)
In-Reply-To: <1464021024-29380-1-git-send-email-carlo@caione.org>
From: Carlo Caione <carlo@endlessm.com>
Add the binding documentation for the Amlogic secure monitor driver.
Signed-off-by: Carlo Caione <carlo@endlessm.com>
---
.../bindings/firmware/meson/meson_sm.txt | 51 ++++++++++++++++++++++
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/firmware/meson/meson_sm.txt
diff --git a/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt b/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt
new file mode 100644
index 0000000..2b71716
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt
@@ -0,0 +1,51 @@
+* Amlogic Secure Monitor
+
+In the Amlogic SoCs the Secure Monitor code is used to provide access to the
+NVMEM, enable JTAG, set USB boot, etc...
+
+Required properties for the secure monitor node:
+- compatible: Should be "amlogic,meson-sm"
+- amlogic,sm-cmd-input-base: SMC32 function identifier to read the physical
+ address of the input buffer
+- amlogic,sm-cmd-output-base: SMC32 function identifier to read the physical
+ address of the output buffer
+
+Example:
+
+ #include <dt-bindings/firmware/meson-gxbb-sm.h>
+
+ ...
+
+ firmware {
+ compatible = "simple-bus";
+
+ sm: secure-monitor {
+ compatible = "amlogic,meson-sm";
+ amlogic,sm-cmd-input-base = <SM_GET_SHARE_MEM_INPUT_BASE>;
+ amlogic,sm-cmd-output-base = <SM_GET_SHARE_MEM_OUTPUT_BASE>;
+ };
+ };
+
+Node of a device using the secure monitor must have a custom property to
+specify the SMC32 function the driver is going to use. The values of all the
+SMC function identifiers are listed in a SoC-specific header file:
+
+"include/dt-bindings/firmware/meson-gxbb-sm.h" - for the Meson GXBB secure monitor.
+
+Example of the node using the secure monitor:
+
+ #include <dt-bindings/firmware/meson-gxbb-sm.h>
+
+ ...
+
+ efuse: efuse {
+ compatible = "amlogic,meson-gxbb-efuse";
+ secure-monitor = <&sm>;
+ amlogic,sm-cmd-read-efuse = <SM_EFUSE_READ>;
+ amlogic,sm-cmd-max-efuse = <SM_EFUSE_USER_MAX>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ ...
+ };
+
--
2.7.4
next prev parent reply other threads:[~2016-05-23 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 16:30 [PATCH v3 0/4] Add Amlogic secure monitor driver Carlo Caione
2016-05-23 16:30 ` [PATCH v3 1/4] firmware: Amlogic: Add " Carlo Caione
2016-05-23 20:58 ` Kevin Hilman
2016-05-24 8:08 ` Carlo Caione
2016-05-23 16:30 ` [PATCH v3 2/4] firmware: dt-bindings: Add secure monitor header file for GXBB Carlo Caione
2016-05-23 16:30 ` [PATCH v3 3/4] ARM64: dts: amlogic: gxbb: Enable secure monitor Carlo Caione
2016-05-23 16:30 ` Carlo Caione [this message]
2016-05-23 16:38 ` [PATCH v3 4/4] documentation: Add secure monitor binding documentation Mark Rutland
2016-05-23 16:59 ` Carlo Caione
2016-05-23 17:11 ` Mark Rutland
2016-05-24 8:03 ` Carlo Caione
2016-05-23 17:04 ` [PATCH v3 0/4] Add Amlogic secure monitor driver Matthias Brugger
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=1464021024-29380-5-git-send-email-carlo@caione.org \
--to=carlo@caione.org \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®