aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJerome Forissier <jerome.forissier@linaro.org>2018-10-08 06:16:42 -0400
committerRob Herring <robh@kernel.org>2018-10-12 16:44:12 -0400
commit22a7488c54a03773ef7cf0dc952047c75cc1446a (patch)
tree610beb4818dbf01b48a0889d59a34cf9bb695f49
parentd81cc4a8e47219fbe60d49446f04ed3e9c1657d9 (diff)
Documentation: dt: Add binding for /secure-chosen/stdout-path
Some platforms may use a single device tree to describe two address spaces, as described in d9f43babb998 ("Documentation: dt: Add bindings for Secure-only devices"). For these platforms it makes sense to define a secure counterpart of /chosen, namely: /secure-chosen. This new node is meant to be used by the secure firmware to pass data to the secure OS. Only the stdout-path property is supported for now. Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org> Signed-off-by: Rob Herring <robh@kernel.org>
-rw-r--r--Documentation/devicetree/bindings/arm/secure.txt19
1 files changed, 18 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/arm/secure.txt b/Documentation/devicetree/bindings/arm/secure.txt
index e31303fb233a..f27bbff2c780 100644
--- a/Documentation/devicetree/bindings/arm/secure.txt
+++ b/Documentation/devicetree/bindings/arm/secure.txt
@@ -32,7 +32,8 @@ describe the view of Secure world using the standard bindings. These
32secure- bindings only need to be used where both the Secure and Normal 32secure- bindings only need to be used where both the Secure and Normal
33world views need to be described in a single device tree. 33world views need to be described in a single device tree.
34 34
35Valid Secure world properties: 35Valid Secure world properties
36-----------------------------
36 37
37- secure-status : specifies whether the device is present and usable 38- secure-status : specifies whether the device is present and usable
38 in the secure world. The combination of this with "status" allows 39 in the secure world. The combination of this with "status" allows
@@ -51,3 +52,19 @@ Valid Secure world properties:
51 status = "disabled"; secure-status = "okay"; /* S-only */ 52 status = "disabled"; secure-status = "okay"; /* S-only */
52 status = "disabled"; /* disabled in both */ 53 status = "disabled"; /* disabled in both */
53 status = "disabled"; secure-status = "disabled"; /* disabled in both */ 54 status = "disabled"; secure-status = "disabled"; /* disabled in both */
55
56The secure-chosen node
57----------------------
58
59Similar to the /chosen node which serves as a place for passing data
60between firmware and the operating system, the /secure-chosen node may
61be used to pass data to the Secure OS. Only the properties defined
62below may appear in the /secure-chosen node.
63
64- stdout-path : specifies the device to be used by the Secure OS for
65 its console output. The syntax is the same as for /chosen/stdout-path.
66 If the /secure-chosen node exists but the stdout-path property is not
67 present, the Secure OS should not perform any console output. If
68 /secure-chosen does not exist, the Secure OS should use the value of
69 /chosen/stdout-path instead (that is, use the same device as the
70 Normal world OS).