Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3710628imj; Tue, 12 Feb 2019 03:25:30 -0800 (PST) X-Google-Smtp-Source: AHgI3IYkZZGZSPX2VbLgbMHER5XPAz92CXVY0HWgSVEHI5nVGNAgZZBWTOMwcYezVD7VH7mkKJaR X-Received: by 2002:a62:62c5:: with SMTP id w188mr3526807pfb.160.1549970730631; Tue, 12 Feb 2019 03:25:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549970730; cv=none; d=google.com; s=arc-20160816; b=nuni5KmxqEIIz9PkSTjG0eSy2FUYshKutw+Gla6SAu/vYgj3lqfFGVnrPZHBPu/t8c LA1VSmlMNwV6qegtptcEM6BI3kn42WOyVhnl0gNfuyjGw2UcHdbd45Kp0Ps8ylel7zDC aylEaJb9r9MV0gkH8c/JnmCxCdmK/L6Rw0KbWAwipeSark532mcKKoVaVoMyQU2UTfrf 3RuyQmcIjuH/HlEeNI36fIwagcE1eXF/YAW/DlRYktzb2DtkNY2cW9BRHRHPpq6i/psi xKf52uEzImxy2zSUf39LnnaVI53WLRVYXfVH46drMIRu3dESYEu0Z6E4weKe7yQCo/hh BJKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=1TQumLme3VslgLidIYqA5/lXkSqNK175qjGod6Gj/HI=; b=b6ZN6X6OSQ/Dyql3ulZ/906sl/VAPb9wo96Y529u1zoovDaaA08axXBy+aM2f5sJ2l gWriCS0tA96fxFDWTF1tuISD0hR2NRN+0Bfxy5Vg3iqZFvAyQQK8gSnSieHNe1uVrD6W wFwV43LzdivLaracFSRTbn/y1wjiM48FLSKD2N1+nMoNnkyxZglrjRrQNw6ULJnjgPML axp2XVDLc4KOdpARd1w3fgULlyZPo/ZYnr5vvrqtvVTb0ptd2THMOfJGk3GTZ54cKtM9 mM2u4gTLQuec40t4XTAskYu4Knsf9cpT7ueDAOpxGWo3cdwYPIWoGE8ayVsYOyGjunbI pHoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ettus-com.20150623.gappssmtp.com header.s=20150623 header.b=SEG2klxA; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ci9si4735457plb.252.2019.02.12.03.25.15; Tue, 12 Feb 2019 03:25:30 -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; dkim=pass header.i=@ettus-com.20150623.gappssmtp.com header.s=20150623 header.b=SEG2klxA; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728689AbfBLLCo (ORCPT + 99 others); Tue, 12 Feb 2019 06:02:44 -0500 Received: from mail-yb1-f193.google.com ([209.85.219.193]:36853 "EHLO mail-yb1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727553AbfBLLCo (ORCPT ); Tue, 12 Feb 2019 06:02:44 -0500 Received: by mail-yb1-f193.google.com with SMTP id h40so863831ybj.3 for ; Tue, 12 Feb 2019 03:02:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ettus-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1TQumLme3VslgLidIYqA5/lXkSqNK175qjGod6Gj/HI=; b=SEG2klxAVYy3ShSSvEnQjvAi5binY5sJpnF1brUGgZaRCWfmXlmt7tuHBEPUR/5GuP HTltwY1qZU+5O5IOCOpgkF1ssKDIH8RoggYP249RiUDzD0gqasf7MLm831mK9rtkIb9E cCz7sx1QKqWMrUgUtFyIrcFapMhGqjMAd7h8AsKIPXXJ8cj5wb6QrcJeCtmGVajnBEdW qgi+uk+zUIIzZdYfKUL/6XRLz8DVPovVDLhJvMlBFwRxrNjyMuAxZRh5tGz8AMXmrA8+ N8HqOgiZ/dcx1gS7SLGw8eX18LKhMYIfIrqeJvWmMjUIRx8Yavfs9fExdYrZt3Dx00vv 6flw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1TQumLme3VslgLidIYqA5/lXkSqNK175qjGod6Gj/HI=; b=gTiYwNOLA7FZxV10ah8uET4L2Tl3COlnRSCzfk3BpAmz7J8mCEGNITQU7vJWGARf/7 QzsgqHXnvYTw0kYG03gitdY3VmR+LwrxzdGhd0HuoX3f7LisYqsyP03wLwx820GdPa1K e3M0u3TD2hcap2gVgriVu+CbxjF0FoF9egDOgiM67d6Kr3kFXOWbZ2SNbpO70pLNITzQ DPv04hFx+89MDcVAT12rrimtEhjCj+KNpvJH1Ew+1hZ9oRsDHHV6zgBzVcSM+sj8Jpz/ DVGWvkh67x56xmDES9qo0uqgZBeNeybn5uLitGjfrESzsP6fZ7jrKoExMExsb2Wl1qbO wGVQ== X-Gm-Message-State: AHQUAuYo+srL00loLZFNRzm1M6AwlRQBgdIDfeNyk7oNN8MHKFYEWGSH j3xhnzy+kPiIGhpHy+Eb3M/nrqSwc9rt0dqnkcDdZw== X-Received: by 2002:a25:7d05:: with SMTP id y5mr2250739ybc.439.1549969363078; Tue, 12 Feb 2019 03:02:43 -0800 (PST) MIME-Version: 1.0 References: <20190211161736.23844-1-nava.manne@xilinx.com> In-Reply-To: <20190211161736.23844-1-nava.manne@xilinx.com> From: Moritz Fischer Date: Tue, 12 Feb 2019 03:02:32 -0800 Message-ID: Subject: Re: [PATCH v3 2/3] dt-bindings: fpga: Add bindings for ZynqMP fpga driver To: Nava kishore Manne Cc: Alan Tull , Rob Herring , Mark Rutland , Michal Simek , Rajan Vaja , Jolly Shah , linux-fpga@vger.kernel.org, Devicetree List , linux-arm-kernel , Linux Kernel Mailing List , kishore m Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nava, a couple of nits inline. otherwise looks fine to me. On Sun, Feb 10, 2019 at 8:17 AM Nava kishore Manne wrote: > > Add documentation to describe Xilinx ZynqMP fpga driver > bindings. > > Signed-off-by: Nava kishore Manne > --- > Changes for v3: > -Created patches on top of 5.0-rc5. > No functional changes. > Changes for v2: > -Removed "----" separators. > Changes for v1: > -Created a Seperate(New) DT binding file as > suggested by Rob. > > Changes for RFC-V2: > -Moved pcap node as a child to firwmare > node as suggested by Rob. > > .../devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt > > diff --git a/Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt b/Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt > new file mode 100644 > index 0000000..1f6f588 > --- /dev/null > +++ b/Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt > @@ -0,0 +1,13 @@ > +Device Tree zynqmp-fpga bindings for the Zynq Ultrascale+ MPSoC controlled > +using ZynqMP SoC firmware interface How about: Devicetree bindings for Zynq Ultrascale MPSoC FPGA Manager. > +For Bitstream configuration on ZynqMp Soc uses processor configuration > +port(PCAP) to configure the programmable logic(PL) through PS by using > +FW interface. ZynqMP or ZynqMp, let's stay consistent here. How about: The ZynqMP SoC uses the PCAP (Processor configuration Port) to configure the Programmable Logic (PL). The configuration uses the firmware interface. > + > +Required properties: > +- compatible: should contain "xlnx,zynqmp-pcap-fpga" > + > +Example: > + zynqmp_pcap: pcap { > + compatible = "xlnx,zynqmp-pcap-fpga"; > + }; > -- > 2.7.4 > Thanks, Moritz