From: Rob Herring <robh@kernel.org> To: Nava kishore Manne <nava.manne@xilinx.com> Cc: atull@kernel.org, mdf@kernel.org, mark.rutland@arm.com, michal.simek@xilinx.com, rajanv@xilinx.com, jollys@xilinx.com, linux-fpga@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, chinnikishore369@gmail.com Subject: Re: [PATCH v4 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Date: Mon, 25 Mar 2019 14:18:49 -0500 [thread overview] Message-ID: <20190315235422.GA29658@bogus> (raw) In-Reply-To: <20190314140122.23372-7-nava.manne@xilinx.com> On Thu, Mar 14, 2019 at 07:31:22PM +0530, Nava kishore Manne wrote: > Add documentation to describe Xilinx ZynqMP fpga driver > bindings. > > Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com> > --- > Changes for v4: > -Modified binding description as suggested by Moritz Fischer. > 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. Huh? It was the fpga-regions that I suggested should perhaps be at the top-level. As long as pcap is a function exposed by the firmware it should be a child of it. > > .../bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 11 +++++++++++ > 1 file changed, 11 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..6d7f10775d9b > --- /dev/null > +++ b/Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt > @@ -0,0 +1,11 @@ > +Devicetree bindings for Zynq Ultrascale MPSoC FPGA Manager. > +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.18.0 >
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org> To: Nava kishore Manne <nava.manne@xilinx.com> Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, atull@kernel.org, linux-fpga@vger.kernel.org, michal.simek@xilinx.com, linux-kernel@vger.kernel.org, jollys@xilinx.com, rajanv@xilinx.com, mdf@kernel.org, linux-arm-kernel@lists.infradead.org, chinnikishore369@gmail.com Subject: Re: [PATCH v4 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Date: Mon, 25 Mar 2019 14:18:49 -0500 [thread overview] Message-ID: <20190315235422.GA29658@bogus> (raw) In-Reply-To: <20190314140122.23372-7-nava.manne@xilinx.com> On Thu, Mar 14, 2019 at 07:31:22PM +0530, Nava kishore Manne wrote: > Add documentation to describe Xilinx ZynqMP fpga driver > bindings. > > Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com> > --- > Changes for v4: > -Modified binding description as suggested by Moritz Fischer. > 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. Huh? It was the fpga-regions that I suggested should perhaps be at the top-level. As long as pcap is a function exposed by the firmware it should be a child of it. > > .../bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 11 +++++++++++ > 1 file changed, 11 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..6d7f10775d9b > --- /dev/null > +++ b/Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt > @@ -0,0 +1,11 @@ > +Devicetree bindings for Zynq Ultrascale MPSoC FPGA Manager. > +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.18.0 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-25 19:18 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-14 14:01 [PATCH v4 0/6]dt-bindings: Firmware node binding for ZynqMP core Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` [PATCH v4 1/6] dt-bindings: power: Add ZynqMP power domain bindings Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` [PATCH v4 2/6] dt-bindings: soc: Add ZynqMP PM bindings Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` [PATCH v4 3/6] dt-bindings: reset: Add bindings for ZynqMP reset driver Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` [PATCH v4 4/6] dt-bindings: pinctrl: Add ZynqMP pin controller bindings Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` [PATCH v4 5/6] dt-bindings: nvmem: Add bindings for ZynqMP nvmem driver Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` [PATCH v4 6/6] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-14 14:01 ` Nava kishore Manne 2019-03-22 7:16 ` Nava kishore Manne 2019-03-22 7:16 ` Nava kishore Manne 2019-03-22 7:16 ` Nava kishore Manne 2019-03-25 19:18 ` Rob Herring [this message] 2019-03-25 19:18 ` Rob Herring 2019-03-26 14:06 ` Nava kishore Manne 2019-03-26 14:06 ` Nava kishore Manne 2019-03-26 14:06 ` Nava kishore Manne
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190315235422.GA29658@bogus \ --to=robh@kernel.org \ --cc=atull@kernel.org \ --cc=chinnikishore369@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=jollys@xilinx.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-fpga@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=mdf@kernel.org \ --cc=michal.simek@xilinx.com \ --cc=nava.manne@xilinx.com \ --cc=rajanv@xilinx.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.