dt-bindings: Add schemas for simple-framebuffer
Subsystems (5)
PATCH v2 1/1 dt-bindings: Add schemas for simple-framebuffer
The simple framebuffer is a binding that allows the bootloader to setup a framebuffer, describe it in the Device Tree for the OS to pick it up and use it as is.
Replace the current binding by a schema to allow the validation tools to check those nodes.
Cc Bartlomiej Zolnierkiewicz <[email protected]>
Cc Chen-Yu Tsai <[email protected]>
Cc Hans de Goede <[email protected]>
Cc Maxime Jourdan <[email protected]>
Signed-off-by Maxime Ripard <[email protected]>
---
Changes from v1:
- Switched to enum where it made sense
- Updated the SPDX license identifier
--- .../display/amlogic,simple-framebuffer.txt | 33 ---- .../display/simple-framebuffer-sunxi.txt | 36 ---- .../bindings/display/simple-framebuffer.txt | 91 ---------- .../bindings/display/simple-framebuffer.yaml | 160 ++++++++++++++++++ 4 files changed, 160 insertions(+), 160 deletions(-) delete mode 100644 Documentation/devicetree/bindings/display/amlogic,simple-framebuffer.txt delete mode 100644 Documentation/devicetree/bindings/display/simple-framebuffer-sunxi.txt delete mode 100644 Documentation/devicetree/bindings/display/simple-framebuffer.txt create mode 100644 Documentation/devicetree/bindings/display/simple-framebuffer.yaml
Documentation/devicetree/bindings/display/amlogic,simple-framebuffer.txt deleted +0 -33
@@ -1,33 +0,0 @@ -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>; - }; -};
Documentation/devicetree/bindings/display/simple-framebuffer-sunxi.txt deleted +0 -36
@@ -1,36 +0,0 @@ -Sunxi specific Simple Framebuffer bindings - -This binding documents sunxi specific extensions to the simple-framebuffer -bindings. The sunxi 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: "allwinner,simple-framebuffer" -- allwinner,pipeline, one of: - "de_be0-lcd0" - "de_be1-lcd1" - "de_be0-lcd0-hdmi" - "de_be1-lcd1-hdmi" - "mixer0-lcd0" - "mixer0-lcd0-hdmi" - "mixer1-lcd1-hdmi" - "mixer1-lcd1-tve" - -Example: - -chosen { - #address-cells = <1>; - #size-cells = <1>; - ranges; - - framebuffer@0 { - compatible = "allwinner,simple-framebuffer", "simple-framebuffer"; - allwinner,pipeline = "de_be0-lcd0-hdmi"; - clocks = <&pll5 1>, <&ahb_gates 36>, <&ahb_gates 43>, - <&ahb_gates 44>; - }; -};
Documentation/devicetree/bindings/display/simple-framebuffer.txt deleted +0 -91
91 lines not on this page · raw message
Documentation/devicetree/bindings/display/simple-framebuffer.yaml new file +160 -0
160 lines not on this page · raw message
Signature · 1 line
2.20.1