1 # SPDX-License-Identifier: GPL-2.0
4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Simple Framebuffer Device Tree Bindings
10 - Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
11 - Hans de Goede <hdegoede@redhat.com>
14 A simple frame-buffer describes a frame-buffer setup by firmware or
15 the bootloader, with the assumption that the display hardware has
16 already been set up to scan out from the memory pointed to by the
19 Since simplefb nodes represent runtime information they must be
20 sub-nodes of the chosen node (*). Simplefb nodes must be named
21 framebuffer@<address>.
23 If the devicetree contains nodes for the display hardware used by a
24 simplefb, then the simplefb node must contain a property called
25 display, which contains a phandle pointing to the primary display
26 hw node, so that the OS knows which simplefb to disable when handing
27 over control to a driver for the real hardware. The bindings for the
28 hw nodes must specify which node is considered the primary node.
30 It is advised to add display# aliases to help the OS determine how
31 to number things. If display# aliases are used, then if the simplefb
32 node contains a display property then the /aliases/display# path
33 must point to the display hw node the display property points to,
34 otherwise it must point directly to the simplefb node.
36 If a simplefb node represents the preferred console for user
37 interaction, then the chosen node stdout-path property should point
38 to it, or to the primary display hw node, as with display#
39 aliases. If display aliases are used then it should be set to the
42 It is advised that devicetree files contain pre-filled, disabled
43 framebuffer nodes, so that the firmware only needs to update the
44 mode information and enable them. This way if e.g. later on support
45 for more display clocks get added, the simplefb nodes will already
46 contain this info and the firmware does not need to be updated.
48 If pre-filled framebuffer nodes are used, the firmware may need
49 extra information to find the right node. In that case an extra
50 platform specific compatible and platform specific properties should
51 be used and documented.
57 - allwinner,simple-framebuffer
58 - amlogic,simple-framebuffer
59 - const: simple-framebuffer
62 description: Location and size of the framebuffer memory
65 description: List of clocks used by the framebuffer.
68 description: List of power domains used by the framebuffer.
71 $ref: /schemas/types.yaml#/definitions/uint32
72 description: Width of the framebuffer in pixels
75 $ref: /schemas/types.yaml#/definitions/uint32
76 description: Height of the framebuffer in pixels
79 $ref: /schemas/types.yaml#/definitions/uint32
80 description: Number of bytes of a line in the framebuffer
84 Format of the framebuffer:
85 * `a8b8g8r8` - 32-bit pixels, d[31:24]=a, d[23:16]=b, d[15:8]=g, d[7:0]=r
86 * `r5g6b5` - 16-bit pixels, d[15:11]=r, d[10:5]=g, d[4:0]=b
92 $ref: /schemas/types.yaml#/definitions/phandle
93 description: Primary display hardware node
96 description: Pipeline used by the framebuffer on Allwinner SoCs
104 - de_fe0-de_be0-lcd0-hdmi
105 - de_fe0-de_be0-lcd0-tve0
112 description: Pipeline used by the framebuffer on Amlogic SoCs
118 "^[a-zA-Z0-9-]+-supply$":
119 $ref: /schemas/types.yaml#/definitions/phandle
121 Regulators used by the framebuffer. These should be named
122 according to the names in the device design.
125 # The binding requires also reg, width, height, stride and format,
126 # but usually they will be filled by the bootloader.
134 const: allwinner,simple-framebuffer
144 const: amlogic,simple-framebuffer
151 additionalProperties: false
158 #address-cells = <1>;
162 #address-cells = <1>;
164 framebuffer0: framebuffer@1d385000 {
165 compatible = "allwinner,simple-framebuffer", "simple-framebuffer";
166 allwinner,pipeline = "de_be0-lcd0";
167 reg = <0x1d385000 3840000>;
172 clocks = <&ahb_gates 36>, <&ahb_gates 43>, <&ahb_gates 44>;
173 lcd-supply = <®_dc1sw>;