Hi Carlo,
On 05/25/2016 10:18 PM, Carlo Caione wrote:
> From: Carlo Caione <carlo@xxxxxxxxxxxx>
>
> Add the binding documentation for the Amlogic secure monitor driver.
>
> Signed-off-by: Carlo Caione <carlo@xxxxxxxxxxxx>
> ---
> .../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>;
> +
> + ...
> + };
> +
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
