summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorStephen Warren <swarren@wwwdotorg.org>2013-05-27 18:31:17 +0000
committerAnatolij Gustschin <agust@denx.de>2013-06-05 22:40:03 +0200
commit6a195d2d8a9c321817e1f034afcdc8c8642664bc (patch)
tree637cc6ddf38c66fc5d678c771fabb46f27750e3e /doc
parentdb0d47dd433bc7ba60b927fb0ff6835758a8893d (diff)
downloadtalos-obmc-uboot-6a195d2d8a9c321817e1f034afcdc8c8642664bc.tar.gz
talos-obmc-uboot-6a195d2d8a9c321817e1f034afcdc8c8642664bc.zip
lcd: add functions to set up simplefb device tree
simple-framebuffer is a new device tree binding that describes a pre- configured frame-buffer memory region and its format. The Linux kernel contains a driver that supports this binding. Implement functions to create a DT node (or fill in an existing node) with parameters that describe the framebuffer format that U-Boot is using. This will be immediately used by the Raspberry Pi board in U-Boot, and likely will be used by the Samsung ARM ChromeBook support soon too. It could well be used by many other boards (e.g. Tegra boards with built-in LCD panels, which aren't yet supported by the Linux kernel). Signed-off-by: Stephen Warren <swarren@wwwdotorg.org> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/device-tree-bindings/video/simple-framebuffer.txt25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/device-tree-bindings/video/simple-framebuffer.txt b/doc/device-tree-bindings/video/simple-framebuffer.txt
new file mode 100644
index 0000000000..3ea4605831
--- /dev/null
+++ b/doc/device-tree-bindings/video/simple-framebuffer.txt
@@ -0,0 +1,25 @@
+Simple Framebuffer
+
+A simple frame-buffer describes a raw memory region that may be rendered to,
+with the assumption that the display hardware has already been set up to scan
+out from that buffer.
+
+Required properties:
+- compatible: "simple-framebuffer"
+- reg: Should contain the location and size of the framebuffer memory.
+- width: The width of the framebuffer in pixels.
+- height: The height of the framebuffer in pixels.
+- stride: The number of bytes in each line of the framebuffer.
+- format: The format of the framebuffer surface. Valid values are:
+ - r5g6b5 (16-bit pixels, d[15:11]=r, d[10:5]=g, d[4:0]=b).
+
+Example:
+
+ framebuffer {
+ compatible = "simple-framebuffer";
+ reg = <0x1d385000 (1600 * 1200 * 2)>;
+ width = <1600>;
+ height = <1200>;
+ stride = <(1600 * 2)>;
+ format = "r5g6b5";
+ };
OpenPOWER on IntegriCloud