[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2a71d30-97da-0b1e-7942-f7dd63b0ddab@redhat.com>
Date: Tue, 6 Jul 2021 14:09:02 -0700
From: Tom Rix <trix@...hat.com>
To: Nava kishore Manne <nava.manne@...inx.com>, robh+dt@...nel.org,
michal.simek@...inx.com, mdf@...nel.org, arnd@...db.de,
rajan.vaja@...inx.com, gregkh@...uxfoundation.org,
amit.sunil.dhamne@...inx.com, tejas.patel@...inx.com,
zou_wei@...wei.com, lakshmi.sai.krishna.potthuri@...inx.com,
ravi.patel@...inx.com, iwamatsu@...auri.org,
wendy.liang@...inx.com, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-fpga@...r.kernel.org, git@...inx.com,
chinnikishore369@...il.com
Subject: Re: [PATCH v8 4/5] dt-bindings: firmware: Remove
xlnx,zynqmp-firmware.txt file
On 6/26/21 8:52 AM, Nava kishore Manne wrote:
> The funtionality of xlnx,zynqmp-firmware.txt is replaced with
functionality
Tom
> xlnx,zynqmp-firmware.yaml bindings so this patch removes the
> zynqmp-firmware.txt file
>
> Signed-off-by: Nava kishore Manne <nava.manne@...inx.com>
> ---
> Changes for v8:
> -Removed xlnx,zynqmp-firmware.txt as suggested by rob.
>
> .../firmware/xilinx/xlnx,zynqmp-firmware.txt | 44 -------------------
> 1 file changed, 44 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt
>
> diff --git a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt
> deleted file mode 100644
> index 18c3aea90df2..000000000000
> --- a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt
> +++ /dev/null
> @@ -1,44 +0,0 @@
> ------------------------------------------------------------------
> -Device Tree Bindings for the Xilinx Zynq MPSoC Firmware Interface
> ------------------------------------------------------------------
> -
> -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.
> -
> -Required properties:
> - - compatible: Must contain any of below:
> - "xlnx,zynqmp-firmware" for Zynq Ultrascale+ MPSoC
> - "xlnx,versal-firmware" for Versal
> - - method: The method of calling the PM-API firmware layer.
> - Permitted values are:
> - - "smc" : SMC #0, following the SMCCC
> - - "hvc" : HVC #0, following the SMCCC
> -
> --------
> -Example
> --------
> -
> -Zynq Ultrascale+ MPSoC
> -----------------------
> -firmware {
> - zynqmp_firmware: zynqmp-firmware {
> - compatible = "xlnx,zynqmp-firmware";
> - method = "smc";
> - ...
> - };
> -};
> -
> -Versal
> -------
> -firmware {
> - versal_firmware: versal-firmware {
> - compatible = "xlnx,versal-firmware";
> - method = "smc";
> - ...
> - };
> -};
Powered by blists - more mailing lists