On 18/11/14 13:10, Hans de Goede wrote: > If pre-filled framebuffer nodes are used, the firmware may need extra > properties to find the right node. This documents the properties to use > for this on sunxi platforms. > > Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> > Acked-by: Grant Likely <grant.likely@xxxxxxxxxx> > --- > .../bindings/video/simple-framebuffer-sunxi.txt | 33 ++++++++++++++++++++++ > 1 file changed, 33 insertions(+) > create mode 100644 Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt > > diff --git a/Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt b/Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt > new file mode 100644 > index 0000000..c46ba64 > --- /dev/null > +++ b/Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt > @@ -0,0 +1,33 @@ > +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: Sorry my ignorance, but what's sunxi and what's allwinner? Both names are mixed here. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
