Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp8914121ybi; Thu, 6 Jun 2019 23:38:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqwpGu5fA4W/NRBtF/SAAf9ZzFZdVE6zOeSJ13s+5Q6J+uIQ9FtbeDC0gZlqJfN+8keZo+yR X-Received: by 2002:a65:62cc:: with SMTP id m12mr1391798pgv.237.1559889528018; Thu, 06 Jun 2019 23:38:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559889528; cv=none; d=google.com; s=arc-20160816; b=JIDbe5/tnm1WYCpCkDYj5z7sdW0KSLtatSsgyH6BO7isR9SxdcQREcALFRVBKl6REj 8IrcMlKMZZh7kp7HEeL2W2w4qd74kanUGcK9Sw2/n3GUAeo/L1WEvSf9SYkNKV6Wnpo8 bgzRW76qmK+v34IOhr+ZEi2touBn7s2W0DWiuuEotLaErWul6O882jEKktj8C1Hx3pss rLPf3quiDa+v8T7LIzqmZ3yKjZ2qTpO47XeqQ2uyaqXWjSql9cy4WZo88NYjdq55TAex 9TeZlc9VHzF6suC26ppsp0xkKW8P5U/UmHRk6Lq8lcxeM1e2SOl66ipB9a0Q/uKm0Zf4 7ASA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=/4ZAyrF2P9L+ktmbOmH78FDJsrRkTVOfqtDkqrNwTxI=; b=UApXl07x5PuRYvD+VP5L9eiFIJ5cnWnwaEqIqUwwoc+kApe5tcT7/ZVRXtH1RhVde8 cw2BkpzobZ3epg2m5+GTrXrhNDg3e5eNuxo4fiNwXUqjLaqo/W1sTRxzgzITUW/EucO0 k7o+8SN/kvLGI+jMkMUE6itPLZN92YdvJr+0kAK6QUxSNevUm8iAhn/Ae0acmawNo1Q9 Qk5/jZr99e4OIIGrNtD36l/vlGtNug1/G54Mot8z0+GfXTyzCPPPhb6LzFvy9qWEIofV GPRZV3HlpH76sNe8I7dwQJDCYCJtw01kczo7GaNfSiKDx+8sI2EtBoCmRotARkAn2MJq CVrA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m13si994616pgq.546.2019.06.06.23.38.31; Thu, 06 Jun 2019 23:38:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727363AbfFGGef (ORCPT + 99 others); Fri, 7 Jun 2019 02:34:35 -0400 Received: from mga02.intel.com ([134.134.136.20]:49508 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726825AbfFGGed (ORCPT ); Fri, 7 Jun 2019 02:34:33 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jun 2019 23:34:32 -0700 X-ExtLoop1: 1 Received: from pg-eswbuild-angstrom-alpha.altera.com ([10.142.34.148]) by orsmga001.jf.intel.com with ESMTP; 06 Jun 2019 23:34:29 -0700 From: "Hean-Loong, Ong" To: Rob Herring , Dinh Nguyen , Daniel Vetter , Randy Dunlap 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, chin.liang.see@intel.com, Ong@vger.kernel.org Subject: [PATCHv15 1/3] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite Date: Fri, 7 Jun 2019 22:28:25 +0800 Message-Id: <20190607142827.329-2-hean.loong.ong@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190607142827.329-1-hean.loong.ong@intel.com> References: <20190607142827.329-1-hean.loong.ong@intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Ong, Hean Loong" Device tree binding for Intel FPGA Video and Image Processing Suite. The bindings would set the max width, max height, bits per pixel and memory port width. The device tree binding only supports the Intel Arria10 devkit and its variants. Vendor name retained as altr. Reviewed-by: Rob Herring V15: Reviewed V14: No Change V13: No change V12: Wrap comments and fix commit message V11: No change V10: No change V9: Remove Display port node V8: *Add port to Display port decoder 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 Signed-off-by: Ong, Hean Loong --- .../bindings/display/altr,vip-fb2.txt | 63 +++++++++++++++++++ 1 file changed, 63 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 000000000000..89a3b9e166a8 --- /dev/null +++ b/Documentation/devicetree/bindings/display/altr,vip-fb2.txt @@ -0,0 +1,63 @@ +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 + +Optional sub-nodes: +- ports: The connection to the encoder + +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) + +Required Properties Example: +---------------------------- + +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.17.1