From: narmstrong@baylibre•com (Neil Armstrong)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/3] documentation: Add secure monitor binding documentation
Date: Thu, 26 May 2016 09:20:27 +0200 [thread overview]
Message-ID: <5746A3BB.3030505@baylibre.com> (raw)
In-Reply-To: <1464207511-11786-3-git-send-email-carlo@caione.org>
Hi Carlo,
On 05/25/2016 10:18 PM, Carlo Caione wrote:
> 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 | 42 ++++++++++++++++++++++
> 1 file changed, 42 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..896758d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/firmware/meson/meson_sm.txt
> @@ -0,0 +1,42 @@
> +* 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-gxbb-sm"
> +
> +Example:
> +
> + #include <dt-bindings/firmware/meson-sm.h>
> +
> + ...
> +
> + firmware {
> + compatible = "simple-bus";
> +
> + sm: secure-monitor {
> + compatible = "amlogic,meson-gxbb-sm";
> + };
> + };
> +
> +Node of a device using the secure monitor must have a custom property to
> +specify the SMC32 function ID the driver is going to use.
> +
> +Example of the node using the secure monitor:
> +
> + #include <dt-bindings/firmware/meson-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>;
Same here, since the compatible is "gxbb" specific, there is no need for these properties, and so no need for the dt-bindings header.
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + ...
> + };
> +
>
next prev parent reply other threads:[~2016-05-26 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 20:18 [PATCH v4 0/3] Add Amlogic secure monitor driver Carlo Caione
2016-05-25 20:18 ` [PATCH v4 1/3] firmware: Amlogic: Add " Carlo Caione
2016-05-26 7:17 ` Neil Armstrong
2016-05-26 7:45 ` Carlo Caione
2016-05-25 20:18 ` [PATCH v4 2/3] documentation: Add secure monitor binding documentation Carlo Caione
2016-05-26 7:20 ` Neil Armstrong [this message]
2016-05-25 20:18 ` [PATCH v4 3/3] ARM64: dts: amlogic: gxbb: Enable secure monitor Carlo Caione
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=5746A3BB.3030505@baylibre.com \
--to=narmstrong@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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