diff options
| -rw-r--r-- | Documentation/devicetree/bindings/video/simple-framebuffer.txt | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/Documentation/devicetree/bindings/video/simple-framebuffer.txt b/Documentation/devicetree/bindings/video/simple-framebuffer.txt index f8fb7e6e5609..4474ef6e0b95 100644 --- a/Documentation/devicetree/bindings/video/simple-framebuffer.txt +++ b/Documentation/devicetree/bindings/video/simple-framebuffer.txt | |||
| @@ -31,12 +31,10 @@ enable them. This way if e.g. later on support for more display clocks get | |||
| 31 | added, the simplefb nodes will already contain this info and the firmware | 31 | added, the simplefb nodes will already contain this info and the firmware |
| 32 | does not need to be updated. | 32 | does not need to be updated. |
| 33 | 33 | ||
| 34 | If pre-filled framebuffer nodes are used, they should be named | 34 | If pre-filled framebuffer nodes are used, the firmware may need extra |
| 35 | "framebuffer#-<output>", e.g. "framebuffer0-hdmi". The output should be | 35 | information to find the right node. In that case an extra platform specific |
| 36 | included in the name since different outputs typically require different | 36 | compatible and platform specific properties should be used and documented, |
| 37 | clocks and the clocks are part of the pre-populated nodes. The firmware must | 37 | see e.g. simple-framebuffer-sunxi.txt . |
| 38 | rename the nodes to the standard "framebuffer@<address>" name using the | ||
| 39 | runtime chosen address when enabling the nodes. | ||
| 40 | 38 | ||
| 41 | Required properties: | 39 | Required properties: |
| 42 | - compatible: "simple-framebuffer" | 40 | - compatible: "simple-framebuffer" |