Received: by 2002:a4a:311b:0:0:0:0:0 with SMTP id k27-v6csp4164550ooa; Tue, 14 Aug 2018 01:58:35 -0700 (PDT) X-Google-Smtp-Source: AA+uWPyKW7slf8Z1N5KWY+Cr+tXT87T4xf7qVdWEYSaCkvSCVfh5ygQzpKp90KVTy1fDjxOCHAnc X-Received: by 2002:aa7:8713:: with SMTP id b19-v6mr22214798pfo.151.1534237114959; Tue, 14 Aug 2018 01:58:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534237114; cv=none; d=google.com; s=arc-20160816; b=Z9stCxVt6iAlX466XEZWMEfclNtE8hTrbvivRzJGtxrHRvUsloWTjJabTzrmMAiwY6 lcdAjjXR9fR1kwr6/9eQoVtEVsoyS29FQB9j6nbYWq/hGGJzsGIC2V0esJxugxZQHyCe Z7a8ex3Yv7d78PfA9Zft1NZpJzjJY6s0+kg7eGzBWfY4dGAphI6/Pp03ZJKyo9E21KtT oJFQ2NEPMrH96HejOpiYvWXlom6zyP10glSCkDixvTF9CHUSXPYDgYTdU1jTXFYFO4OT md6ZSzqBQeGvTE2cVgUhpxUbyGQ3R67cA60FuK0iPM3bRupJ3NIPunPLq9tSyQHQH/jF DFFA== 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:arc-authentication-results; bh=vq+nj6ebPB8Agr+UDzqKF1pCduATyxWNhqm6idkCqU4=; b=hGiDLMG39qwGFir+IpW+65NdCS85JomMhgE++UF2B3LpBYsQsOmAAsfYN9J1/wWd3u xRBM1CWV//x8ZsjJ6WVo9v33JvNFUpIAKqkLkExi+BTR82fkTXuiJCamNK/LIMo/qyCr ngTOGyUmS65fV0Uqhm+udavhk4Li+D3+scdVHVr8fdvcrh2btKMDFIu/ZKFNjp4cVPkB kcAvxrqEMLAd3TzUTYMTkRtwxuAmZ3aC3YxpGXCbZrhDJUzvnUgFtWlMhPWkkmwmdjcZ pxiuj3/Y4mjKBg9m9SwyUe+YPg66UF2X2FZmEWhQAoyZlYNy1zTEapVFH0B2yRsETUCi 4f1Q== 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 t6-v6si18857576pgk.215.2018.08.14.01.58.20; Tue, 14 Aug 2018 01:58:34 -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 S1731841AbeHNLni (ORCPT + 99 others); Tue, 14 Aug 2018 07:43:38 -0400 Received: from mga18.intel.com ([134.134.136.126]:33134 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731730AbeHNLnh (ORCPT ); Tue, 14 Aug 2018 07:43:37 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Aug 2018 01:57:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,237,1531810800"; d="scan'208";a="64771401" Received: from helong-vb.png.intel.com ([10.226.243.17]) by orsmga007.jf.intel.com with ESMTP; 14 Aug 2018 01:57:21 -0700 From: "Hean-Loong, Ong" To: Rob Herring , Dinh Nguyen , David Airlie 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, yves.vandervennet@intel.com, chin.liang.see@intel.com, Ong@vger.kernel.org Subject: [PATCH10 1/3] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite Date: Tue, 14 Aug 2018 16:57:07 +0800 Message-Id: <1534237029-2648-2-git-send-email-hean.loong.ong@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1534237029-2648-1-git-send-email-hean.loong.ong@intel.com> References: <1534237029-2648-1-git-send-email-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 binding involved would be generated from the Altera (Intel) Qsys system. The bindings would set the max width, max height, buts per pixel and memory port width. The device tree binding only supports the Intel Arria10 devkit and its variants. Vendor name retained as altr. 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 --- .../devicetree/bindings/display/altr,vip-fb2.txt | 63 ++++++++++++++++++++ 1 files changed, 63 insertions(+), 0 deletions(-) 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..89a3b9e --- /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>; + }; + }; + }; +}; -- 1.7.1