From: Nava kishore Manne <navam@xilinx.com>
To: Rob Herring <robh@kernel.org>
Cc: Michal Simek <michals@xilinx.com>,
"mdf@kernel.org" <mdf@kernel.org>,
"trix@redhat.com" <trix@redhat.com>,
"arnd@arndb.de" <arnd@arndb.de>, Rajan Vaja <RAJANV@xilinx.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Amit Sunil Dhamne <amitsuni@xlnx.xilinx.com>,
Tejas Patel <tejasp@xlnx.xilinx.com>,
"zou_wei@huawei.com" <zou_wei@huawei.com>,
Sai Krishna Potthuri <lakshmis@xilinx.com>,
Ravi Patel <RAVIPATE@xilinx.com>,
"iwamatsu@nigauri.org" <iwamatsu@nigauri.org>,
Jiaying Liang <jliang@xilinx.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
git <git@xilinx.com>,
"chinnikishore369@gmail.com" <chinnikishore369@gmail.com>
Subject: RE: [PATCH v6 3/4] dt-bindings: firmware: Add bindings for xilinx firmware
Date: Fri, 4 Jun 2021 07:36:53 +0000 [thread overview]
Message-ID: <PH0PR02MB7336CA9287C41D64CBB4D5E2C23B9@PH0PR02MB7336.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20210602183131.GA3706177@robh.at.kernel.org>
Hi Rob,
Thanks for providing the review comments.
Please find my response inline.
> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: Thursday, June 3, 2021 12:02 AM
> To: Nava kishore Manne <navam@xilinx.com>
> Cc: Michal Simek <michals@xilinx.com>; mdf@kernel.org; trix@redhat.com;
> arnd@arndb.de; Rajan Vaja <RAJANV@xilinx.com>;
> gregkh@linuxfoundation.org; Amit Sunil Dhamne
> <amitsuni@xlnx.xilinx.com>; Tejas Patel <tejasp@xlnx.xilinx.com>;
> zou_wei@huawei.com; Sai Krishna Potthuri <lakshmis@xilinx.com>; Ravi
> Patel <RAVIPATE@xilinx.com>; iwamatsu@nigauri.org; Jiaying Liang
> <jliang@xilinx.com>; devicetree@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; linux-kernel@vger.kernel.org; linux-
> fpga@vger.kernel.org; git <git@xilinx.com>; chinnikishore369@gmail.com
> Subject: Re: [PATCH v6 3/4] dt-bindings: firmware: Add bindings for xilinx
> firmware
>
> On Thu, May 20, 2021 at 01:39:53PM +0530, Nava kishore Manne wrote:
> > Add documentation to describe Xilinx firmware driver bindings.
> > Firmware driver provides an interface to firmware APIs.
> > Interface APIs can be used by any driver to communicate to Platform
> > Management Unit.
> >
> > Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> > ---
> > Changes for v4:
> > -Added new yaml file for xilinx firmware
> > as suggested by Rob.
> > Changes for v5:
> > -Fixed some minor issues and updated the fpga node name to
> versal_fpga.
> >
> > Changes for v6:
> > -Added AES and Clk nodes as a sub nodes to the firmware node.
> >
> > .../firmware/xilinx/xlnx,zynqmp-firmware.yaml | 102
> > ++++++++++++++++++
> > 1 file changed, 102 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-
> firmware
> > .yaml
> >
> > diff --git
> > a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-
> firmwa
> > re.yaml
> > b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-
> firmwa
> > re.yaml
> > new file mode 100644
> > index 000000000000..58016191e150
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-fi
> > +++ rmware.yaml
> > @@ -0,0 +1,102 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
> > +---
> > +$id:
> > +http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.ya
> > +ml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Xilinx firmware driver
> > +
> > +maintainers:
> > + - Nava kishore Manne <nava.manne@xilinx.com>
> > +
> > +description:
> > + The zynqmp-firmware node describes the interface to platform
> firmware.
> > + ZynqMP has an interface to communicate with secure firmware.
> > +Firmware
> > + driver provides an interface to firmware APIs. Interface APIs can
> > +be
> > + used by any driver to communicate to PMUFW(Platform Management
> Unit).
> > + These requests include clock management, pin control, device
> > +control,
> > + power management service, FPGA service and other platform
> > +management
> > + services.
> > +
> > +properties:
> > + compatible:
> > + oneOf:
> > + - description:
> > + For implementations complying for Zynq Ultrascale+ MPSoC.
> > + const: xlnx,zynqmp-firmware
> > +
> > + - description:
> > + For implementations complying for Versal.
> > + const: xlnx,versal-firmware
> > +
> > + method:
> > + description: |
> > + The method of calling the PM-API firmware layer.
> > + Permitted values are.
> > + - "smc" : SMC #0, following the SMCCC
> > + - "hvc" : HVC #0, following the SMCCC
> > +
> > + $ref: /schemas/types.yaml#/definitions/string-array
> > + enum:
> > + - smc
> > + - hvc
> > +
> > +patternProperties:
> > + "versal_fpga":
>
> This says 'fooversal_fpgabar' is a valid node name.
>
> You don't need a pattern, move under 'properties'. Same for the other child
> nodes.
>
Will fix in v7.
> > + $ref: "../../fpga/xlnx,versal-fpga.yaml#"
>
> /schemas/fpga/...
>
> Don't need quotes.
>
Will fix in v7.
> > + description: Compatible of the FPGA device.
> > + type: object
> > + required:
> > + - compatible
>
> Drop. What's required should be in xlnx,versal-fpga.yaml.
>
Will fix in v7.
> > +
> > + "zynqmp-aes":
>
> Same comments as above on the rest of the child nodes.
>
Will fix in v7.
> > + $ref: "../../crypto/xlnx,zynqmp-aes.yaml#"
> > + description: |
> > + The ZynqMP AES-GCM hardened cryptographic accelerator is
> > + used to encrypt or decrypt the data with provided key and
> > + initialization vector.
> > + type: object
> > + required:
> > + - compatible
> > +
> > + "clock-controller":
> > + $ref: "../../clock/xlnx,versal-clk.yaml#"
> > + description: |
> > + The clock controller is a hardware block of Xilinx versal
> > + clock tree. It reads required input clock frequencies from
> > + the devicetree and acts as clock provider for all clock
> > + consumers of PS clocks.list of clock specifiers which are
> > + external input clocks to the given clock controller.
> > + type: object
> > + required:
> > + - compatible
> > + - "#clock-cells"
> > + - clocks
> > + - clock-names
> > +
> > +required:
> > + - compatible
> > +
> > +examples:
> > + - |
> > + versal-firmware {
> > + compatible = "xlnx,versal-firmware";
> > + method = "smc";
> > +
> > + versal_fpga: versal_fpga {
> > + compatible = "xlnx,versal-fpga";
> > + };
> > +
> > + xlnx_aes: zynqmp-aes {
> > + compatible = "xlnx,zynqmp-aes";
> > + };
> > +
> > + versal_clk: clock-controller {
> > + #clock-cells = <1>;
> > + compatible = "xlnx,versal-clk";
> > + clocks = <&ref>, <&alt_ref>, <&pl_alt_ref>;
> > + clock-names = "ref", "alt_ref", "pl_alt_ref";
> > + };
> > + };
> > +
> > +additionalProperties: false
>
> Move this before the example.
Will fix in v7.
Regards,
Navakishore.
next prev parent reply other threads:[~2021-06-04 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 8:09 [PATCH v6 0/4]Add Bitstream configuration support for Versal Nava kishore Manne
2021-05-20 8:09 ` [PATCH v6 1/4] drivers: firmware: Add PDI load API support Nava kishore Manne
2021-05-20 8:09 ` [PATCH v6 2/4] dt-bindings: fpga: Add binding doc for versal fpga manager Nava kishore Manne
2021-06-02 18:32 ` Rob Herring
2021-05-20 8:09 ` [PATCH v6 3/4] dt-bindings: firmware: Add bindings for xilinx firmware Nava kishore Manne
2021-06-02 18:31 ` Rob Herring
2021-06-04 7:36 ` Nava kishore Manne [this message]
2021-05-20 8:09 ` [PATCH v6 4/4] fpga: versal-fpga: Add versal fpga manager driver Nava kishore Manne
2021-05-20 8:48 ` Greg KH
2021-06-01 6:56 ` Nava kishore Manne
2021-06-01 15:43 ` Moritz Fischer
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=PH0PR02MB7336CA9287C41D64CBB4D5E2C23B9@PH0PR02MB7336.namprd02.prod.outlook.com \
--to=navam@xilinx.com \
--cc=RAJANV@xilinx.com \
--cc=RAVIPATE@xilinx.com \
--cc=amitsuni@xlnx.xilinx.com \
--cc=arnd@arndb.de \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=iwamatsu@nigauri.org \
--cc=jliang@xilinx.com \
--cc=lakshmis@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michals@xilinx.com \
--cc=robh@kernel.org \
--cc=tejasp@xlnx.xilinx.com \
--cc=trix@redhat.com \
--cc=zou_wei@huawei.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).