|author||Hans de Goede <email@example.com>||2014-11-18 12:10:50 +0100|
|committer||Tomi Valkeinen <firstname.lastname@example.org>||2014-11-26 10:17:42 +0200|
dt-bindings: simplefb: Drop the advice about using a specific path for nodes
This goes contrary to how devicetree usually works, so drop it. Instead if the firmware needs to be able to find a specific node it should use a platform specific compatible + properties for this. Signed-off-by: Hans de Goede <email@example.com> Acked-by: Grant Likely <firstname.lastname@example.org> Signed-off-by: Tomi Valkeinen <email@example.com>
Diffstat (limited to 'Documentation/devicetree/bindings/video')
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
@@ -31,12 +31,10 @@ enable them. This way if e.g. later on support for more display clocks get
added, the simplefb nodes will already contain this info and the firmware
does not need to be updated.
-If pre-filled framebuffer nodes are used, they should be named
-"framebuffer#-<output>", e.g. "framebuffer0-hdmi". The output should be
-included in the name since different outputs typically require different
-clocks and the clocks are part of the pre-populated nodes. The firmware must
-rename the nodes to the standard "framebuffer@<address>" name using the
-runtime chosen address when enabling the nodes.
+If pre-filled framebuffer nodes are used, the firmware may need extra
+information to find the right node. In that case an extra platform specific
+compatible and platform specific properties should be used and documented,
+see e.g. simple-framebuffer-sunxi.txt .
- compatible: "simple-framebuffer"