Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5d85a847 authored by Hans de Goede's avatar Hans de Goede Committed by Tomi Valkeinen
Browse files

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: default avatarHans de Goede <hdegoede@redhat.com>
Acked-by: default avatarGrant Likely <grant.likely@linaro.org>
Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
parent 8284731e

Documentation/devicetree/bindings/video/simple-framebuffer.txt

+4 −6
Original line number Diff line number Diff line
@@ -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 .



Required properties:

- compatible: "simple-framebuffer"