Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2951253imc; Wed, 13 Mar 2019 05:26:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqy4nbQE1DkYsy2izKXBERVpher9Azr4Hcr12BbXYHGfUoUJ8nJYEnf8LeAE4pkkbZMF0pyW X-Received: by 2002:a65:6210:: with SMTP id d16mr26395207pgv.189.1552480013965; Wed, 13 Mar 2019 05:26:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552480013; cv=none; d=google.com; s=arc-20160816; b=NE/WB9RScZQ1akRvjGG8GzmwpC4V2Mh8QZ/9SC84WIslgrTQB56v79JWKzPMsQWjAE s/qBLDeEd/NwPvdyaDuCO4pPEw/2wuA5VZ0XWU8F7CqdTFicUdGb9RXZFWgUzADdoFCo 4yg6aZUWEbevf8qt8P8t5cR8Fv+rxomsygs8A9CvsHhoCVO1L3ITfp0PJwzFiSVobVdJ 1BXe7jzQHbulF2Pjsj5NsVplMIqfH2OzKF1D4/2Q52aJYalIoB2yshaGrQ/5BNxTt/SQ DjtmG7wPSNRmzTsSQLStyBZ0vtqPkqzIhfRizKPm1+y9EfDOsqbA2tO+H0i6jYGRup4k 8ZEg== 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=sdQ2G5N/SFe5QjR+tgf0Qy7ZU2v3u1XJFNRfghUf5jQ=; b=zmnl8t5fwUE+zsEDEiBwFxkZOG5LoITJMUBO0M6nTIY7ZIds1sWgiFzqTTeRAR/vmU BW705GcB8997wZC0Ad3RidQqT6ftztBLNUqg8AWD1nQ59JtovRYLalxFcSBztRSDFS79 Bvit7dgyMTC5srerG2/+i4ddVcM+ytkk/Mi6guG2aWJIe1YcVPUErTGezUFNv/rI87uY kyEKtu3fE+DTKHN3niP+A3fokQhTzsHxbHEhQgFd0Xp0VHFwkcU22spFSCQoNbNouN2h tZ+37+ib9KDiPadfRAlu9/kAU+gWdfS9EYu4H4h9vN/T6h2zJSwM+0virpg9++nJBrrC +IOg== 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 o62si10465337pfi.198.2019.03.13.05.26.37; Wed, 13 Mar 2019 05:26:53 -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 S1726670AbfCMMZ7 (ORCPT + 99 others); Wed, 13 Mar 2019 08:25:59 -0400 Received: from mga09.intel.com ([134.134.136.24]:62129 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725883AbfCMMZ5 (ORCPT ); Wed, 13 Mar 2019 08:25:57 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Mar 2019 05:25:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,474,1544515200"; d="scan'208";a="133958985" Received: from pg-eswbuild-angstrom-alpha.png.intel.com ([10.226.214.8]) by fmsmga007.fm.intel.com with ESMTP; 13 Mar 2019 05:25:54 -0700 From: "Hean-Loong, Ong" To: Rob Herring , Dinh Nguyen , Daniel Vetter 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: [PATCHv14 1/3] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite Date: Thu, 14 Mar 2019 04:22:04 +0800 Message-Id: <20190313202206.921-2-hean.loong.ong@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190313202206.921-1-hean.loong.ong@intel.com> References: <20190313202206.921-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. 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 --- .../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