Lines Matching +full:normal +full:-
4 "Normal" and "Secure". Most devicetree consumers (including the Linux
5 kernel) are not TrustZone aware and run entirely in either the Normal
8 visible only in the Secure address space, only in the Normal address
15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
18 "vendor,secure-foo". If there is no "secure-" property then the Secure
19 world value is the same as specified for the Normal world by the
20 non-prefixed property. However, only the properties listed below may
21 validly have "secure-" versions; this list will be enlarged on a
22 case-by-case basis.
25 been annotated to indicate the presence of Secure-only devices can
26 still be processed unmodified by existing Non-secure software (and in
32 secure- bindings only need to be used where both the Secure and Normal
36 -----------------------------
38 - secure-status : specifies whether the device is present and usable
41 specified. If "secure-status" is not specified it defaults to the
47 secure-status = "okay"; /* visible in both */
49 status = "okay"; secure-status = "okay"; /* visible in both */
50 secure-status = "disabled"; /* NS-only */
51 status = "okay"; secure-status = "disabled"; /* NS-only */
52 status = "disabled"; secure-status = "okay"; /* S-only */
54 status = "disabled"; secure-status = "disabled"; /* disabled in both */
56 The secure-chosen node
57 ----------------------
60 between firmware and the operating system, the /secure-chosen node may
62 below may appear in the /secure-chosen node.
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
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).