diff options
| author | Leif Lindholm <leif.lindholm@linaro.org> | 2014-11-27 12:56:05 -0500 |
|---|---|---|
| committer | Grant Likely <grant.likely@linaro.org> | 2014-12-03 18:12:35 -0500 |
| commit | 2a9d832cc9aae21ea827520fef635b6c49a06c6d (patch) | |
| tree | 6d2e3b625fc1910b1e09c3ce276859ab39177f23 | |
| parent | 63ebecc03d2f18411da51a0981bd63818bbd0b54 (diff) | |
of: Add bindings for chosen node, stdout-path
Add a global binding for the chosen node. Include a description of the
stdout-path, and an explicit statement on its extra options in the
context of a UART console.
Opening description stolen from www.devicetree.org, and part of the
remaining text provided by Mark Rutland.
Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
[grant.likely: remove reference to uart_parse_options]
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Grant Likely <grant.likely@linaro.org>
| -rw-r--r-- | Documentation/devicetree/bindings/chosen.txt | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/chosen.txt b/Documentation/devicetree/bindings/chosen.txt new file mode 100644 index 000000000000..ed838f453f7a --- /dev/null +++ b/Documentation/devicetree/bindings/chosen.txt | |||
| @@ -0,0 +1,46 @@ | |||
| 1 | The chosen node | ||
| 2 | --------------- | ||
| 3 | |||
| 4 | The chosen node does not represent a real device, but serves as a place | ||
| 5 | for passing data between firmware and the operating system, like boot | ||
| 6 | arguments. Data in the chosen node does not represent the hardware. | ||
| 7 | |||
| 8 | |||
| 9 | stdout-path property | ||
| 10 | -------------------- | ||
| 11 | |||
| 12 | Device trees may specify the device to be used for boot console output | ||
| 13 | with a stdout-path property under /chosen, as described in ePAPR, e.g. | ||
| 14 | |||
| 15 | / { | ||
| 16 | chosen { | ||
| 17 | stdout-path = "/serial@f00:115200"; | ||
| 18 | }; | ||
| 19 | |||
| 20 | serial@f00 { | ||
| 21 | compatible = "vendor,some-uart"; | ||
| 22 | reg = <0xf00 0x10>; | ||
| 23 | }; | ||
| 24 | }; | ||
| 25 | |||
| 26 | If the character ":" is present in the value, this terminates the path. | ||
| 27 | The meaning of any characters following the ":" is device-specific, and | ||
| 28 | must be specified in the relevant binding documentation. | ||
| 29 | |||
| 30 | For UART devices, the preferred binding is a string in the form: | ||
| 31 | |||
| 32 | <baud>{<parity>{<bits>{<flow>}}} | ||
| 33 | |||
| 34 | where | ||
| 35 | |||
| 36 | baud - baud rate in decimal | ||
| 37 | parity - 'n' (none), 'o', (odd) or 'e' (even) | ||
| 38 | bits - number of data bits | ||
| 39 | flow - 'r' (rts) | ||
| 40 | |||
| 41 | For example: 115200n8r | ||
| 42 | |||
| 43 | Implementation note: Linux will look for the property "linux,stdout-path" or | ||
| 44 | on PowerPC "stdout" if "stdout-path" is not found. However, the | ||
| 45 | "linux,stdout-path" and "stdout" properties are deprecated. New platforms | ||
| 46 | should only use the "stdout-path" property. | ||
