| Message ID | 20190107095307.15233-2-mjourdan@baylibre.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | arm64: dts: meson: add simple-framebuffer nodes | expand |
On Mon, Jan 07, 2019 at 10:53:06AM +0100, Maxime Jourdan wrote: > 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. > > Signed-off-by: Maxime Jourdan <mjourdan@baylibre.com> > --- > .../display/simple-framebuffer-meson.txt | 33 +++++++++++++++++++ Use the compatible string for the file name: amlogic,simple-framebuffer.txt With that, Reviewed-by: Rob Herring <robh@kernel.org>
On Fri, Jan 11, 2019 at 11:25 PM Rob Herring <robh@kernel.org> wrote: > > On Mon, Jan 07, 2019 at 10:53:06AM +0100, Maxime Jourdan wrote: > > 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. > > > > Signed-off-by: Maxime Jourdan <mjourdan@baylibre.com> > > --- > > .../display/simple-framebuffer-meson.txt | 33 +++++++++++++++++++ > > Use the compatible string for the file name: > amlogic,simple-framebuffer.txt > > With that, > > Reviewed-by: Rob Herring <robh@kernel.org> Thanks for the review, will send a v3.
diff --git a/Documentation/devicetree/bindings/display/simple-framebuffer-meson.txt b/Documentation/devicetree/bindings/display/simple-framebuffer-meson.txt new file mode 100644 index 000000000000..aaa6c24c8e70 --- /dev/null +++ b/Documentation/devicetree/bindings/display/simple-framebuffer-meson.txt @@ -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>; + }; +};
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. Signed-off-by: Maxime Jourdan <mjourdan@baylibre.com> --- .../display/simple-framebuffer-meson.txt | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/simple-framebuffer-meson.txt