public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tanmay Shah <tanmay.shah@amd.com>
To: andersson@kernel.org, mathieu.poirier@linaro.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, michal.simek@amd.com, ben.levinsky@amd.com
Cc: linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Subject: Re: [PATCH v11 2/4] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings
Date: Wed, 28 Feb 2024 13:20:38 -0600	[thread overview]
Message-ID: <ebf6eb21-8dd8-4ca7-afe1-7149817c8f34@amd.com> (raw)
In-Reply-To: <20240219174437.3722620-3-tanmay.shah@amd.com>

Hi Krzysztof,

Ping for reviews. Also have question.

I am referring this patch from patchwork link: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240219174437.3722620-8-tanmay.shah@amd.com/

Patchwork shows that dtbs-check was failed, but I am sending dts changes in next patch. So dtbs-check failure only with bindings patch is expected.

How to resolve this? Should I send dtb changes same as bindings? Or we can ignore dtbs-check errors for now?

Thanks,

Tanmay

On 2/19/24 11:44 AM, Tanmay Shah wrote:
> From: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
>
> Introduce bindings for TCM memory address space on AMD-xilinx Zynq
> UltraScale+ platform. It will help in defining TCM in device-tree
> and make it's access platform agnostic and data-driven.
>
> Tightly-coupled memories(TCMs) are low-latency memory that provides
> predictable instruction execution and predictable data load/store
> timing. Each Cortex-R5F processor contains two 64-bit wide 64 KB memory
> banks on the ATCM and BTCM ports, for a total of 128 KB of memory.
>
> The TCM resources(reg, reg-names and power-domain) are documented for
> each TCM in the R5 node. The reg and reg-names are made as required
> properties as we don't want to hardcode TCM addresses for future
> platforms and for zu+ legacy implementation will ensure that the
> old dts w/o reg/reg-names works and stable ABI is maintained.
>
> It also extends the examples for TCM split and lockstep modes.
>
> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
> Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
> ---
>
> Changes in v11:
>   - Fix yamllint warning and reduce indentation as needed
>
>  .../remoteproc/xlnx,zynqmp-r5fss.yaml         | 192 ++++++++++++++++--
>  1 file changed, 170 insertions(+), 22 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/xlnx,zynqmp-r5fss.yaml b/Documentation/devicetree/bindings/remoteproc/xlnx,zynqmp-r5fss.yaml
> index 78aac69f1060..77030edf41fa 100644
> --- a/Documentation/devicetree/bindings/remoteproc/xlnx,zynqmp-r5fss.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/xlnx,zynqmp-r5fss.yaml
> @@ -20,9 +20,21 @@ properties:
>    compatible:
>      const: xlnx,zynqmp-r5fss
>  
> +  "#address-cells":
> +    const: 2
> +
> +  "#size-cells":
> +    const: 2
> +
> +  ranges:
> +    description: |
> +      Standard ranges definition providing address translations for
> +      local R5F TCM address spaces to bus addresses.
> +
>    xlnx,cluster-mode:
>      $ref: /schemas/types.yaml#/definitions/uint32
>      enum: [0, 1, 2]
> +    default: 1
>      description: |
>        The RPU MPCore can operate in split mode (Dual-processor performance), Safety
>        lock-step mode(Both RPU cores execute the same code in lock-step,
> @@ -37,7 +49,7 @@ properties:
>        2: single cpu mode
>  
>  patternProperties:
> -  "^r5f-[a-f0-9]+$":
> +  "^r5f@[0-9a-f]+$":
>      type: object
>      description: |
>        The RPU is located in the Low Power Domain of the Processor Subsystem.
> @@ -54,9 +66,6 @@ patternProperties:
>        compatible:
>          const: xlnx,zynqmp-r5f
>  
> -      power-domains:
> -        maxItems: 1
> -
>        mboxes:
>          minItems: 1
>          items:
> @@ -101,35 +110,174 @@ patternProperties:
>  
>      required:
>        - compatible
> -      - power-domains
>  
> -    unevaluatedProperties: false
> +allOf:
> +  - if:
> +      properties:
> +        xlnx,cluster-mode:
> +          enum:
> +            - 1
> +    then:
> +      patternProperties:
> +        "^r5f@[0-9a-f]+$":
> +          type: object
> +
> +          properties:
> +            reg:
> +              minItems: 1
> +              items:
> +                - description: ATCM internal memory
> +                - description: BTCM internal memory
> +                - description: extra ATCM memory in lockstep mode
> +                - description: extra BTCM memory in lockstep mode
> +
> +            reg-names:
> +              minItems: 1
> +              items:
> +                - const: atcm0
> +                - const: btcm0
> +                - const: atcm1
> +                - const: btcm1
> +
> +            power-domains:
> +              minItems: 2
> +              maxItems: 5
> +
> +          required:
> +            - reg
> +            - reg-names
> +            - power-domains
> +
> +    else:
> +      patternProperties:
> +        "^r5f@[0-9a-f]+$":
> +          type: object
> +
> +          properties:
> +            reg:
> +              minItems: 1
> +              items:
> +                - description: ATCM internal memory
> +                - description: BTCM internal memory
> +
> +            reg-names:
> +              minItems: 1
> +              items:
> +                - const: atcm0
> +                - const: btcm0
> +
> +            power-domains:
> +              minItems: 2
> +              maxItems: 3
> +
> +          required:
> +            - reg
> +            - reg-names
> +            - power-domains
>  
>  required:
>    - compatible
> +  - "#address-cells"
> +  - "#size-cells"
> +  - ranges
>  
>  additionalProperties: false
>  
>  examples:
>    - |
> -    remoteproc {
> -        compatible = "xlnx,zynqmp-r5fss";
> -        xlnx,cluster-mode = <1>;
> -
> -        r5f-0 {
> -            compatible = "xlnx,zynqmp-r5f";
> -            power-domains = <&zynqmp_firmware 0x7>;
> -            memory-region = <&rproc_0_fw_image>, <&rpu0vdev0buffer>, <&rpu0vdev0vring0>, <&rpu0vdev0vring1>;
> -            mboxes = <&ipi_mailbox_rpu0 0>, <&ipi_mailbox_rpu0 1>;
> -            mbox-names = "tx", "rx";
> +    #include <dt-bindings/power/xlnx-zynqmp-power.h>
> +
> +    // Split mode configuration
> +    soc {
> +        #address-cells = <2>;
> +        #size-cells = <2>;
> +
> +        remoteproc@ffe00000 {
> +            compatible = "xlnx,zynqmp-r5fss";
> +            xlnx,cluster-mode = <0>;
> +
> +            #address-cells = <2>;
> +            #size-cells = <2>;
> +            ranges = <0x0 0x0 0x0 0xffe00000 0x0 0x10000>,
> +                     <0x0 0x20000 0x0 0xffe20000 0x0 0x10000>,
> +                     <0x1 0x0 0x0 0xffe90000 0x0 0x10000>,
> +                     <0x1 0x20000 0x0 0xffeb0000 0x0 0x10000>;
> +
> +            r5f@0 {
> +                compatible = "xlnx,zynqmp-r5f";
> +                reg = <0x0 0x0 0x0 0x10000>, <0x0 0x20000 0x0 0x10000>;
> +                reg-names = "atcm0", "btcm0";
> +                power-domains = <&zynqmp_firmware PD_RPU_0>,
> +                                <&zynqmp_firmware PD_R5_0_ATCM>,
> +                                <&zynqmp_firmware PD_R5_0_BTCM>;
> +                memory-region = <&rproc_0_fw_image>, <&rpu0vdev0buffer>,
> +                                <&rpu0vdev0vring0>, <&rpu0vdev0vring1>;
> +                mboxes = <&ipi_mailbox_rpu0 0>, <&ipi_mailbox_rpu0 1>;
> +                mbox-names = "tx", "rx";
> +            };
> +
> +            r5f@1 {
> +                compatible = "xlnx,zynqmp-r5f";
> +                reg = <0x1 0x0 0x0 0x10000>, <0x1 0x20000 0x0 0x10000>;
> +                reg-names = "atcm0", "btcm0";
> +                power-domains = <&zynqmp_firmware PD_RPU_1>,
> +                                <&zynqmp_firmware PD_R5_1_ATCM>,
> +                                <&zynqmp_firmware PD_R5_1_BTCM>;
> +                memory-region = <&rproc_1_fw_image>, <&rpu1vdev0buffer>,
> +                                <&rpu1vdev0vring0>, <&rpu1vdev0vring1>;
> +                mboxes = <&ipi_mailbox_rpu1 0>, <&ipi_mailbox_rpu1 1>;
> +                mbox-names = "tx", "rx";
> +            };
>          };
> +    };
> +
> +  - |
> +    //Lockstep configuration
> +    soc {
> +        #address-cells = <2>;
> +        #size-cells = <2>;
> +
> +        remoteproc@ffe00000 {
> +            compatible = "xlnx,zynqmp-r5fss";
> +            xlnx,cluster-mode = <1>;
> +
> +            #address-cells = <2>;
> +            #size-cells = <2>;
> +            ranges = <0x0 0x0 0x0 0xffe00000 0x0 0x10000>,
> +                     <0x0 0x20000 0x0 0xffe20000 0x0 0x10000>,
> +                     <0x0 0x10000 0x0 0xffe10000 0x0 0x10000>,
> +                     <0x0 0x30000 0x0 0xffe30000 0x0 0x10000>;
> +
> +            r5f@0 {
> +                compatible = "xlnx,zynqmp-r5f";
> +                reg = <0x0 0x0 0x0 0x10000>,
> +                      <0x0 0x20000 0x0 0x10000>,
> +                      <0x0 0x10000 0x0 0x10000>,
> +                      <0x0 0x30000 0x0 0x10000>;
> +                reg-names = "atcm0", "btcm0", "atcm1", "btcm1";
> +                power-domains = <&zynqmp_firmware PD_RPU_0>,
> +                                <&zynqmp_firmware PD_R5_0_ATCM>,
> +                                <&zynqmp_firmware PD_R5_0_BTCM>,
> +                                <&zynqmp_firmware PD_R5_1_ATCM>,
> +                                <&zynqmp_firmware PD_R5_1_BTCM>;
> +                memory-region = <&rproc_0_fw_image>, <&rpu0vdev0buffer>,
> +                                <&rpu0vdev0vring0>, <&rpu0vdev0vring1>;
> +                mboxes = <&ipi_mailbox_rpu0 0>, <&ipi_mailbox_rpu0 1>;
> +                mbox-names = "tx", "rx";
> +            };
>  
> -        r5f-1 {
> -            compatible = "xlnx,zynqmp-r5f";
> -            power-domains = <&zynqmp_firmware 0x8>;
> -            memory-region = <&rproc_1_fw_image>, <&rpu1vdev0buffer>, <&rpu1vdev0vring0>, <&rpu1vdev0vring1>;
> -            mboxes = <&ipi_mailbox_rpu1 0>, <&ipi_mailbox_rpu1 1>;
> -            mbox-names = "tx", "rx";
> +            r5f@1 {
> +                compatible = "xlnx,zynqmp-r5f";
> +                reg = <0x1 0x0 0x0 0x10000>, <0x1 0x20000 0x0 0x10000>;
> +                reg-names = "atcm0", "btcm0";
> +                power-domains = <&zynqmp_firmware PD_RPU_1>,
> +                                <&zynqmp_firmware PD_R5_1_ATCM>,
> +                                <&zynqmp_firmware PD_R5_1_BTCM>;
> +                memory-region = <&rproc_1_fw_image>, <&rpu1vdev0buffer>,
> +                                <&rpu1vdev0vring0>, <&rpu1vdev0vring1>;
> +                mboxes = <&ipi_mailbox_rpu1 0>, <&ipi_mailbox_rpu1 1>;
> +                mbox-names = "tx", "rx";
> +            };
>          };
>      };
>  ...

  reply	other threads:[~2024-02-28 19:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 17:44 [PATCH v11 0/4] add zynqmp TCM bindings Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 1/4] remoteproc: zynqmp: fix lockstep mode memory region Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 2/4] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings Tanmay Shah
2024-02-28 19:20   ` Tanmay Shah [this message]
2024-02-29  9:59   ` Krzysztof Kozlowski
2024-02-29 23:45     ` Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 3/4] dts: zynqmp: add properties for TCM in remoteproc Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 4/4] remoteproc: zynqmp: parse TCM from device tree Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 0/4] add zynqmp TCM bindings Tanmay Shah
2024-02-19 17:55   ` Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 1/4] remoteproc: zynqmp: fix lockstep mode memory region Tanmay Shah
2024-02-28 17:08   ` Mathieu Poirier
2024-02-28 19:24     ` Tanmay Shah
2024-02-28 20:03       ` Mathieu Poirier
2024-02-19 17:44 ` [PATCH v11 2/4] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 3/4] dts: zynqmp: add properties for TCM in remoteproc Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 4/4] remoteproc: zynqmp: parse TCM from device tree Tanmay Shah
2024-02-28 17:06   ` Mathieu Poirier
2024-02-28 17:12     ` Tanmay Shah

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=ebf6eb21-8dd8-4ca7-afe1-7149817c8f34@amd.com \
    --to=tanmay.shah@amd.com \
    --cc=andersson@kernel.org \
    --cc=ben.levinsky@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=michal.simek@amd.com \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=robh+dt@kernel.org \
    /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