From: Xiubo Li <Li.Xiubo@freescale.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/4] video: fsl-dcfb: Add devicetree binding support
Date: Wed, 03 Dec 2014 09:16:00 +0000 [thread overview]
Message-ID: <1417598162-40433-3-git-send-email-Li.Xiubo@freescale.com> (raw)
In-Reply-To: <1417598162-40433-1-git-send-email-Li.Xiubo@freescale.com>
Add devicetree binding support for fsl-dcfb framebuffer driver. It
uses the generic display bindings and helper functions.
Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
---
.../devicetree/bindings/video/fsl,dcfb.txt | 52 ++++++++++++++++++++++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/video/fsl,dcfb.txt
diff --git a/Documentation/devicetree/bindings/video/fsl,dcfb.txt b/Documentation/devicetree/bindings/video/fsl,dcfb.txt
new file mode 100644
index 0000000..2f3d02b
--- /dev/null
+++ b/Documentation/devicetree/bindings/video/fsl,dcfb.txt
@@ -0,0 +1,52 @@
+* Freescale Simple Display Controller FB Driver
+
+== For dcfb node =+Required properties:
+- compatible: Should be one of "fsl,ls1021a-dcfb".
+- reg: Address and length of the register set for dcfb.
+- clocks: From common clock binding: handle to dcfb clock.
+- clock-names: From common clock binding: Shall be "dcfb".
+- display: The phandle to display node.
+
+Optional properties:
+- scfg-controller: The phandle of scfg node.
+
+== For display sub-node =+Required properties:
+- bits-per-pixel: <16> for RGB565,
+ <24> for RGB888,
+ <32> for RGB8888.
+
+Required timing node for dispplay sub-node:
+- display-timings: Refer to binding doc display-timing.txt for details.
+
+Examples:
+dcfb: dcfb@2ce0000 {
+ compatible = "fsl,ls1021a-dcfb";
+ reg = <0x0 0x2ce0000 0x0 0x10000>;
+ clocks = <&platform_clk 0>;
+ clock-names = "dcfb";
+ scfg-controller = <&scfg>;
+ display = <&display>;
+
+ display: display@0 {
+ bits-per-pixel = <24>;
+
+ display-timings {
+ native-mode = <&timing0>;
+ timing0: nl4827hc19 {
+ clock-frequency = <10870000>;
+ hactive = <480>;
+ vactive = <272>;
+ hback-porch = <2>;
+ hfront-porch = <2>;
+ vback-porch = <1>;
+ vfront-porch = <1>;
+ hsync-len = <41>;
+ vsync-len = <2>;
+ hsync-active = <1>;
+ vsync-active = <1>;
+ };
+ };
+ };
+};
--
2.1.0.27.g96db324
next prev parent reply other threads:[~2014-12-03 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 9:15 [PATCHv2 0/4] LS1021A: Add dcfb framebuffer driver support Xiubo Li
2014-12-03 9:15 ` [PATCHv2 1/4] video: fsl-dcfb: Add dcfb framebuffer driver for LS1021A platform Xiubo Li
2014-12-04 9:21 ` Alexander Stein
2014-12-03 9:16 ` Xiubo Li [this message]
2014-12-03 9:16 ` [PATCHv2 3/4] ARM: ls1021a: dtsi: Add dt node support for dcfb Xiubo Li
2014-12-03 9:16 ` [PATCHv2 4/4] ARM: ls1021a: dts: Add and enable dt node " Xiubo Li
2014-12-03 9:51 ` [PATCHv2 0/4] LS1021A: Add dcfb framebuffer driver support Arnd Bergmann
2014-12-04 1:56 ` Li.Xiubo
2014-12-04 8:10 ` Tomi Valkeinen
2014-12-04 8:30 ` Li.Xiubo
2014-12-04 9:09 ` Tomi Valkeinen
2014-12-04 9:54 ` Li.Xiubo
2014-12-04 9:59 ` Tomi Valkeinen
2014-12-04 10:03 ` Li.Xiubo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417598162-40433-3-git-send-email-Li.Xiubo@freescale.com \
--to=li.xiubo@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).