Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2081045imj; Sun, 10 Feb 2019 18:11:55 -0800 (PST) X-Google-Smtp-Source: AHgI3IYYabzo4FmwCUmkcychsQFF++G/RE/pzEdzos/nYeePZxWG9QCvSaBk8bSRdwB12KMnbFQS X-Received: by 2002:aa7:800c:: with SMTP id j12mr16924926pfi.183.1549851115380; Sun, 10 Feb 2019 18:11:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549851115; cv=none; d=google.com; s=arc-20160816; b=ba4kpaiBO1vHbhLm9K7mXBqlj7hIJmfIOcObQsfjHq6hYWLDtVQKeRZpeZVP3BTFZR NzG/47j/QzXMloN6xisy+6/65NOOCQOyFxekGllv0015yeLrZ4/YzZoaCvxZ4yOfnq62 n8LdzvigMuc0gHJo1cRjTsmCGNkTTfAU3kqnw/dZucB3fN2nLVRXRuLP56zWjc+g5zbb Lc+T8H6occhCiUhqzXWRrRH0Aa87oboFmgG/OCXsnnMJBq6LfRgKlj0r0OS4kEDLTxo3 v/rzVEsiUrqXDXopp40Ck3X03Y0MoEhTcYXGhiQCkkYCsdbpxstGvIE1XeWByHb4cpLj XOYQ== 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=vq+nj6ebPB8Agr+UDzqKF1pCduATyxWNhqm6idkCqU4=; b=iB12iGCcswdYBztWzmaAwnSI07mhvTnM+AvGhzIBwtq9x+oHejBj5qNCqWbepXWKpn OZ+zy2E08sXkDGxZWwppS706I61b5i5ib9AMXOym7nDOTkAuMiW404AFFyg4cWD7mMez sZ1D14E7uVKK99SIZ1k1sLDWdh1VjsbZdSHqQJ/YL6RBhemoMOW75BNhrdgSz6cwWaMe jHhB1ElAQycQmiUAjKOmRN7sgQu4An/Lm6Hb15a5xNzzr9hJ1tN9Q2iVW2Mot8wqO+ef eWq73v9nl4lFEc/dOYFY2Qcv5b3/IuRntmsQ9hu5bryJmRqDfQ87N/kRwrx1JJ9hgS40 wijw== 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 a2si7725806pgw.264.2019.02.10.18.11.39; Sun, 10 Feb 2019 18:11:55 -0800 (PST) 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 S1726883AbfBKCL2 (ORCPT + 99 others); Sun, 10 Feb 2019 21:11:28 -0500 Received: from mga02.intel.com ([134.134.136.20]:41293 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726101AbfBKCL2 (ORCPT ); Sun, 10 Feb 2019 21:11:28 -0500 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; 10 Feb 2019 18:11:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,357,1544515200"; d="scan'208";a="137551012" Received: from helong-vb.png.intel.com ([10.226.243.17]) by orsmga001.jf.intel.com with ESMTP; 10 Feb 2019 18:11:24 -0800 From: "Hean-Loong, Ong" To: Rob Herring , Dinh Nguyen , Daniel Vetter , =?UTF-8?q?Noralf=20Tr=C3=B8nnes?= , Rienk de Jong 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: [PATCHv11 1/3] ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite Date: Mon, 11 Feb 2019 10:11:08 +0800 Message-Id: <20190211021110.2717-2-hean.loong.ong@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190211021110.2717-1-hean.loong.ong@intel.com> References: <20190211021110.2717-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 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