dt-bindings: meson: add specific simplefb bindings
authorMaxime Jourdan <mjourdan@baylibre.com>
Wed, 16 Jan 2019 12:40:29 +0000 (13:40 +0100)
committerKevin Hilman <khilman@baylibre.com>
Thu, 17 Jan 2019 19:59:57 +0000 (11:59 -0800)
Similar to simple-framebuffer-sunxi, we support different display pipelines
that the firmware is free to choose from.

This documents the "amlogic,simple-framebuffer" compatible and the
"amlogic,pipeline" extension.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Maxime Jourdan <mjourdan@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Documentation/devicetree/bindings/display/amlogic,simple-framebuffer.txt [new file with mode: 0644]

diff --git a/Documentation/devicetree/bindings/display/amlogic,simple-framebuffer.txt b/Documentation/devicetree/bindings/display/amlogic,simple-framebuffer.txt
new file mode 100644 (file)
index 0000000..aaa6c24
--- /dev/null
@@ -0,0 +1,33 @@
+Meson specific Simple Framebuffer bindings
+
+This binding documents meson specific extensions to the simple-framebuffer
+bindings. The meson simplefb u-boot code relies on the devicetree containing
+pre-populated simplefb nodes.
+
+These extensions are intended so that u-boot can select the right node based
+on which pipeline is being used. As such they are solely intended for
+firmware / bootloader use, and the OS should ignore them.
+
+Required properties:
+- compatible: "amlogic,simple-framebuffer", "simple-framebuffer"
+- amlogic,pipeline, one of:
+  "vpu-cvbs"
+  "vpu-hdmi"
+
+Example:
+
+chosen {
+       #address-cells = <2>;
+       #size-cells = <2>;
+       ranges;
+
+       simplefb_hdmi: framebuffer-hdmi {
+               compatible = "amlogic,simple-framebuffer",
+                            "simple-framebuffer";
+               amlogic,pipeline = "vpu-hdmi";
+               clocks = <&clkc CLKID_HDMI_PCLK>,
+                        <&clkc CLKID_CLK81>,
+                        <&clkc CLKID_GCLK_VENCI_INT0>;
+               power-domains = <&pwrc_vpu>;
+       };
+};