Received: by 2002:ac0:b08d:0:0:0:0:0 with SMTP id l13csp1856942imc; Fri, 22 Feb 2019 12:31:33 -0800 (PST) X-Google-Smtp-Source: AHgI3IZTVix4Ocvodm7NmffFKCL47Ce8D4h2/hE7QJ9S0wdpJEuKCLB0kBMpMjCXCHPI8gEu3KCK X-Received: by 2002:a17:902:4a0c:: with SMTP id w12mr5882452pld.174.1550867493177; Fri, 22 Feb 2019 12:31:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550867493; cv=none; d=google.com; s=arc-20160816; b=AG5cQn0iEsYwnwNLEaafz2y6s+6qlCv5Cbo2ixb2mt5WdTxHghjAVXPKPlKtlsHuHe /J7k1Zs8kpWKMugqUsceOX5O+aiosITwOb8G+4JUMEdc+N56nvE3zGRW0ZZSgqElxkqM Wrs3kmqqbjKVPkBcHxKa9or33FI0JiN3psH0gA8pG/6Sk2w4de3CAvuLHwz0zx4b/JVL jUyQbXfrq3hBDAZfJ5p38+86Qr83lEXk91o38U++AS7nemlgwuRG9VGkaasPN7L6wqqv rBCs/X3htAA9NSF9tEx4yvWhMVOIgHrGmJ0xWX/r8JwR2MxImIKnarVk9y+3fygsJpjE 591w== 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=GI6pecMD2qygT6qhzSdxbyFi86fYBuQvK9Y100txbhw=; b=rKHBoJquwRv+2nT+VAWq1Ks+XLD1BMxWq0D3CS/Kp/OCMhqChtz4oiswGdEdR+/O5B 68owusUaFcVy3X5/D0wunTg47dYbza16KjGvBrWG4CYFfGSv2thj9ff8q7/3AE+f9RJC LdI/txsgJjPLiXEednUbMqGQcYnIbkDiM/T4fa/2Dpqfdp+bnFOtCieFa+PevG7+1cjq rIuDMj6HYk+aC8QgPOXm42kaJlPvW8Go7Xg63irC32bOGjXwyOMlE9uvmn2FGZIaHYCY CRGH9cgviWbiMoyVCQfz6UG3O5KHmkZTj2V+IySIp7RZCOvn6H3uk5L11wrajkh2GNVl 91xQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="0a/odKRC"; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 187si2406635pfb.41.2019.02.22.12.31.18; Fri, 22 Feb 2019 12:31:33 -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=@kernel.org header.s=default header.b="0a/odKRC"; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726870AbfBVUaw (ORCPT + 99 others); Fri, 22 Feb 2019 15:30:52 -0500 Received: from mail.kernel.org ([198.145.29.99]:46736 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725900AbfBVUav (ORCPT ); Fri, 22 Feb 2019 15:30:51 -0500 Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 430D72075C; Fri, 22 Feb 2019 20:30:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550867450; bh=7bLM5+3IQujF98X0zL8N6k213Vu2WBiNhmN2ZhN2wn4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=0a/odKRCAEfajT0phPV6BkT7Egdgtv/TrdEu5463Gz4xuckzFiw2IO108Fs38K2ae 8VSrPlcIfzLZXhF0jOYljDCrGUelFHRzqgIdFE7+q8ZuisL6tyQRz59zR2YbKlalfd nqheEZi/lECELl0vWMNzVFdv9NkcTfD+Zp6iJVso= Received: by mail-qt1-f180.google.com with SMTP id p25so4050269qtb.3; Fri, 22 Feb 2019 12:30:50 -0800 (PST) X-Gm-Message-State: AHQUAuZ6yyT05Ofpa/Ua4gN68zCF5L+XbdQSadNHUDue0y0NouovSpLx VrW7bvmILHATtnv35HJzNvxnQVdVYlTec+Zocg== X-Received: by 2002:aed:2a2f:: with SMTP id c44mr4692215qtd.144.1550867449490; Fri, 22 Feb 2019 12:30:49 -0800 (PST) MIME-Version: 1.0 References: <20190121173835.21173-1-nava.manne@xilinx.com> <20190121173835.21173-7-nava.manne@xilinx.com> <20190121154928.GA32129@bogus> In-Reply-To: From: Rob Herring Date: Fri, 22 Feb 2019 14:30:38 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver To: Nava kishore Manne Cc: "mark.rutland@arm.com" , Michal Simek , Rajan Vaja , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , Jolly Shah , "chinnikishore369@gmail.com" 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 On Wed, Jan 23, 2019 at 2:46 PM Nava kishore Manne wrote: > > Hi Rob, > > > > Thanks for providing the comments... Please fix your mailer to send plain text emails to mail lists. > > -----Original Message----- > > > From: Rob Herring [mailto:robh@kernel.org] > > > Sent: Monday, January 21, 2019 9:19 PM > > > To: Nava kishore Manne > > > Cc: mark.rutland@arm.com; Michal Simek ; Rajan Vaja > > > ; linux-arm-kernel@lists.infradead.org; linux- > > > kernel@vger.kernel.org; devicetree@vger.kernel.org; Jolly Shah > > > ; chinnikishore369@gmail.com > > > Subject: Re: [PATCH v3 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga > > > driver > > > > > > On Mon, Jan 21, 2019 at 11:08:35PM +0530, Nava kishore Manne wrote: > > > > Add documentation to describe Xilinx ZynqMP fpga driver bindings. > > > > > > > > Signed-off-by: Nava kishore Manne > > > > --- > > > > Changes for v3: > > > > -Removed PCAP as a child node to the FW and Created > > > > an independent node since PCAP driver is a consumer > > > > not a provider. > > > > > > > > .../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 000000000000..1f6f58872311 > > > > --- /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 For Bitstream > > > > +configuration on ZynqMp Soc uses processor configuration > > > > +port(PCAP) to configure the programmable logic(PL) through PS by > > > > +using FW interface. > > > > + > > > > +Required properties: > > > > +- compatible: should contain "xlnx,zynqmp-pcap-fpga" > > > > + > > > > +Example: > > > > + zynqmp_pcap: pcap { > > > > + compatible = "xlnx,zynqmp-pcap-fpga"; > > > > + }; > > > > > > There's no need for a DT node. Just make the firware driver create a platform > > > device for pcap. > > > > > > > This driver being used by the FPGA manager framework(fpga-region) to apply overlay's so this node is needed AFAIK. The binding says nothing about child nodes and what they are. Please define that. Rob