From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] documentation: Add secure monitor binding documentation
Date: Wed, 18 May 2016 18:35:18 -0500 [thread overview]
Message-ID: <20160518233518.GA11027@rob-hp-laptop> (raw)
In-Reply-To: <1463583382-15614-5-git-send-email-carlo@caione.org>
On Wed, May 18, 2016 at 04:56:22PM +0200, 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>
> ---
> .../devicetree/bindings/soc/meson/meson_sm.txt | 45 ++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/meson/meson_sm.txt
>
> diff --git a/Documentation/devicetree/bindings/soc/meson/meson_sm.txt b/Documentation/devicetree/bindings/soc/meson/meson_sm.txt
> new file mode 100644
> index 0000000..f59c732
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/meson/meson_sm.txt
bindings/firmware/
> @@ -0,0 +1,45 @@
> +* 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
Use '-' rather than '_'.
> +
> +Example:
> +
> + #include <dt-bindings/soc/meson-gxbb-sm.h>
> +
> + ...
> +
> + sm {
Put this under a /firmware node.
> + 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/soc/meson-gxbb-sm.h" - for the Meson GXBB secure monitor.
> +
> +Example of the node using the secure monitor:
> +
> + #include <dt-bindings/soc/meson-gxbb-sm.h>
> +
> + ...
> +
> + efuse: efuse {
> + compatible = "amlogic,meson-gxbb-efuse";
> + amlogic,sm_cmd_read_efuse = <SM_EFUSE_READ>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + ...
> + };
> +
> --
> 2.7.4
>
prev parent reply other threads:[~2016-05-18 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 14:56 [PATCH v2 0/4] Add Amlogic secure monitor driver Carlo Caione
2016-05-18 14:56 ` [PATCH v2 1/4] soc: Amlogic: Add " Carlo Caione
2016-05-23 11:38 ` Matthias Brugger
2016-05-23 11:43 ` Carlo Caione
2016-05-18 14:56 ` [PATCH v2 2/4] soc: dt-bindings: Add secure monitor header file for GXBB Carlo Caione
2016-05-18 14:56 ` [PATCH v2 3/4] ARM64: dts: amlogic: gxbb: Enable secure monitor Carlo Caione
2016-05-18 14:56 ` [PATCH v2 4/4] documentation: Add secure monitor binding documentation Carlo Caione
2016-05-18 23:35 ` Rob Herring [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=20160518233518.GA11027@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@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