linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hean-Loong, Ong" <hean.loong.ong@intel.com>
To: Rob Herring <robh+dt@kernel.org>,
	Dinh Nguyen <dinguyen@kernel.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org, hean.loong.ong@intel.com,
	Ong@vger.kernel.org
Subject: [PATCHv7] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite
Date: Tue,  5 Sep 2017 15:12:30 +0800	[thread overview]
Message-ID: <1504595552-9209-2-git-send-email-hean.loong.ong@intel.com> (raw)
In-Reply-To: <1504595552-9209-1-git-send-email-hean.loong.ong@intel.com>

From: Ong Hean Loong <hean.loong.ong@intel.com>

Device tree binding for Intel FPGA Video and Image
Processing Suite. The binding involved would be generated
from the Altera (Intel) Qsys system. The bindings would
set the max width, max height and memory port width.
The device tree binding only supports the Intel Arria10
devkit and its variants. Vendor name retained as altr.

Signed-off-by: Ong, Hean Loong <hean.loong.ong@intel.com>
---

V7:
*Fix OF graph for better description
*Add description for encoder

V6:
*Description have not describe DT device in general

V5:
*remove bindings for bits per symbol as it has only one value which is 8

V4:
*fix properties that does not describe the values

V3:
*OF graph not in accordance to graph.txt

V2:
*Remove Linux driver description

V1:
*Missing vendor prefix

---
---
 .../devicetree/bindings/display/altr,vip-fb2.txt   | 74 ++++++++++++++++++++++
 1 file changed, 74 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/display/altr,vip-fb2.txt

diff --git a/Documentation/devicetree/bindings/display/altr,vip-fb2.txt b/Documentation/devicetree/bindings/display/altr,vip-fb2.txt
new file mode 100644
index 0000000..bf0055d
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/altr,vip-fb2.txt
@@ -0,0 +1,74 @@
+Intel Video and Image Processing(VIP) Frame Buffer II bindings
+
+Supported hardware: Intel FPGA SoC Arria10 and above with display port IP
+
+The Video Frame Buffer II in Video Image Processing (VIP) suite is an IP core
+that interfaces between system memory and Avalon-ST video ports. The IP core
+can be configured to support the memory reader (from memory to Avalon-ST)
+and/or memory writer (from Avalon-ST to memory) interfaces.
+
+More information the FPGA video IP component can be acquired from
+https://www.altera.com/content/dam/altera-www/global/en_US/pdfs\
+/literature/ug/ug_vip.pdf
+
+DT-Bindings:
+=============
+Required properties:
+----------------------------
+- compatible: "altr,vip-frame-buffer-2.0"
+- reg: Physical base address and length of the framebuffer controller's
+	registers.
+- altr,max-width: The maximum width of the framebuffer in pixels.
+- altr,max-height: The maximum height of the framebuffer in pixels.
+- altr,mem-port-width = the bus width of the avalon master port
+	on the frame reader
+
+Connections between the Frame Buffer II and other video IP cores in the system
+are modelled using the OF graph DT bindings. The Frame Buffer II node has up
+to two OF graph ports. When the memory writer interface is enabled, port 0
+maps to the Avalon-ST Input (din) port. When the memory reader interface is
+enabled, port 1 maps to the Avalon-ST Output (dout) port.
+
+The encoder is built into the FPGA HW design and therefore would not
+be accessible from the DDR.
+
+		Port 0				Port1
+---------------------------------------------------------
+ARRIA10 AVALON_ST (DIN)		AVALON_ST (DOUT)
+
+Example:
+----------------------------
+
+           +------------------------------+
+           |        FPGA                  |    +------------+
+           +---------+ +--------------+   |    |  DP        |
++-----+    |  VIP    | | DP           |   +---->  Connector |
+|     |    |  Frame  | | Controller   |   |    |            |
+| D   +---->  Buffer | +--------------+   |    +------------+
+| D   |    |         | +--------------+   |
+| R   |    |         | | DP           |   |
+|     |    +---------+ | Encoder      |   |
+|     |    |           +--------------+   |
++-----+    +------------------------------+
+
+
+framebuffer@100000280 {
+        compatible = "altr,vip-frame-buffer-2.0";
+        reg = <0x00000001 0x00000280 0x00000040>;
+        altr,max-width = <1280>;
+        altr,max-height = <720>;
+        altr,mem-port-width = <128>;
+
+        ports {
+                #address-cells = <1>;
+                #size-cells = <0>;
+
+                port@1 {
+                        reg = <1>;
+                        fb_output: endpoint {
+                                remote-endpoint = <&dp_encoder_input>;
+                        };
+                };
+        };
+};
+
-- 
2.7.4

  reply	other threads:[~2017-09-05  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  7:12 [PATCHv7 0/3] Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
2017-09-05  7:12 ` Hean-Loong, Ong [this message]
2017-09-12 21:48   ` [PATCHv7] ARM:dt-bindings:display " Rob Herring
2017-09-05  7:12 ` [PATCHv7 2/3] ARM:socfpga-defconfig " Hean-Loong, Ong
2017-09-05  7:12 ` [PATCHv7 3/3] ARM:drm ivip " Hean-Loong, Ong
2017-09-05 11:08   ` Daniel Vetter

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=1504595552-9209-2-git-send-email-hean.loong.ong@intel.com \
    --to=hean.loong.ong@intel.com \
    --cc=Ong@vger.kernel.org \
    --cc=daniel.vetter@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.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).