renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-19 18:53:52 +08:00
Code

dt-bindings: simplefb: Drop the advice about using a specific path for nodes

Browse Source 
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 <hdegoede@redhat.com>
Acked-by: Grant Likely <grant.likely@linaro.org>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
This commit is contained in:
Hans de Goede 2014-11-18 12:10:50 +01:00 committed by Tomi Valkeinen
parent 8284731eb5
commit 5d85a8478e
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/devicetree/bindings/video/simple-framebuffer.txt
View File

@ -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"