.. | .. |
---|
32 | 32 | secure- bindings only need to be used where both the Secure and Normal |
---|
33 | 33 | world views need to be described in a single device tree. |
---|
34 | 34 | |
---|
35 | | -Valid Secure world properties: |
---|
| 35 | +Valid Secure world properties |
---|
| 36 | +----------------------------- |
---|
36 | 37 | |
---|
37 | 38 | - secure-status : specifies whether the device is present and usable |
---|
38 | 39 | in the secure world. The combination of this with "status" allows |
---|
.. | .. |
---|
51 | 52 | status = "disabled"; secure-status = "okay"; /* S-only */ |
---|
52 | 53 | status = "disabled"; /* disabled in both */ |
---|
53 | 54 | status = "disabled"; secure-status = "disabled"; /* disabled in both */ |
---|
| 55 | + |
---|
| 56 | +The secure-chosen node |
---|
| 57 | +---------------------- |
---|
| 58 | + |
---|
| 59 | +Similar to the /chosen node which serves as a place for passing data |
---|
| 60 | +between firmware and the operating system, the /secure-chosen node may |
---|
| 61 | +be used to pass data to the Secure OS. Only the properties defined |
---|
| 62 | +below 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). |
---|