lkml.org 
[lkml]   [2015]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v6 3/6] dt/bindings: add bindings for optee
On Thu, Oct 29, 2015 at 09:21:25AM +0100, Jens Wiklander wrote:
> Introduces optee prefix and adds bindings for ARM TrustZone based OP-TEE
> implementation.
>
> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
> ---
> .../bindings/arm/firmware/optee,optee-tz.txt | 29 ++++++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> 2 files changed, 30 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/firmware/optee,optee-tz.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/firmware/optee,optee-tz.txt b/Documentation/devicetree/bindings/arm/firmware/optee,optee-tz.txt
> new file mode 100644
> index 0000000..0a8ed0d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/firmware/optee,optee-tz.txt
> @@ -0,0 +1,29 @@
> +OP-TEE Device Tree Bindings
> +
> +OP-TEE is a piece of software using hardware features to provide a Trusted
> +Execution Environment. The security can be provided with ARM TrustZone, but
> +also by virtualization or a separate chip. As there's no single OP-TEE
> +vendor we're using "optee" as the first part of compatible property,
> +indicating the OP-TEE protocol is used when communicating with the secure
> +world.
> +
> +* OP-TEE based on ARM TrustZone required properties:
> +
> +- compatible : should contain "optee,optee-tz"

I would leave off optee as a vendor. Different implementations by
vendors should then add their vendor prefix as they all have the chance
to screw-up something. I suppose we could do "linaro" as the reference
implementation.

> +
> +- method : The method of calling the OP-TEE Trusted OS. Permitted
> + values are:
> +
> + "smc" : SMC #0, with the register assignments specified
> + in drivers/tee/optee/optee_smc.h
> +
> + "hvc" : HVC #0, with the register assignments specified
> + in drivers/tee/optee/optee_smc.h

The use here would be a guest VM calling thru to hypervisor and then
hypervisor calling optee?

> +
> +
> +
> +Example:
> + optee {

This should go under a /firmware node similar to
Documentation/devicetree/bindings/arm/firmware/tlm,trusted-foundations.txt.

Rob


\
 
 \ /
  Last update: 2015-11-16 18:21    [W:0.092 / U:1.592 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site