Lines Matching refs:secure
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
21 validly have "secure-" versions; this list will be enlarged on a
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
38 - secure-status : specifies whether the device is present and usable
39 in the secure world. The combination of this with "status" allows
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
60 between firmware and the operating system, the /secure-chosen node may
62 below may appear in the /secure-chosen node.
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