From: Miquel Raynal <miquel.raynal@bootlin.com>
To: niravkumar.l.rabara@intel.com
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: cadence: convert cadence-nand-controller.txt to yaml
Date: Wed, 4 Oct 2023 09:44:55 +0200 [thread overview]
Message-ID: <20231004094455.1a6a19e1@xps-13> (raw)
In-Reply-To: <20231004061214.17176-1-niravkumar.l.rabara@intel.com>
Hello,
niravkumar.l.rabara@intel.com wrote on Wed, 4 Oct 2023 14:12:14 +0800:
> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>
> Convert cadence-nand-controller.txt to yaml format.
Looks good to me, one question below.
> Signed-off-by: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
> ---
> .../devicetree/bindings/mtd/cadence,nand.yaml | 73 +++++++++++++++++++
> .../bindings/mtd/cadence-nand-controller.txt | 53 --------------
> 2 files changed, 73 insertions(+), 53 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mtd/cadence,nand.yaml
> delete mode 100644 Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/cadence,nand.yaml b/Documentation/devicetree/bindings/mtd/cadence,nand.yaml
> new file mode 100644
> index 000000000000..781812ac702f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/cadence,nand.yaml
> @@ -0,0 +1,73 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mtd/cadence,nand.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Cadence NAND controller
> +
> +maintainers:
> + - Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
> +
> +allOf:
> + - $ref: nand-controller.yaml
> +
> +properties:
> + compatible:
> + items:
> + - const: cdns,hp-nfc
> +
> + reg:
> + items:
> + - description: Address and length of the controller register set
> + - description: Address and length of the Slave DMA data port
> +
> + reg-names:
> + items:
> + - const: reg
> + - const: sdma
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + dmas:
> + maxItems: 1
> +
> + cdns,board-delay-ps:
> + description: |
> + Estimated Board delay. The value includes the total round trip
> + delay for the signals and is used for deciding on values associated
> + with data read capture. The example formula for SDR mode is the
> + following.
> + board delay = RE#PAD delay + PCB trace to device + PCB trace from device
> + + DQ PAD delay
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - interrupts
> + - clocks
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + nand-controller@10b80000 {
> + compatible = "cdns,hp-nfc";
> + reg = <0x10b80000 0x10000>,
> + <0x10840000 0x10000>;
> + reg-names = "reg", "sdma";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + interrupts = <0 97 4>;
> + clocks = <&nf_clk>;
> + cdns,board-delay-ps = <4830>;
> +
> + nand@0 {
> + reg = <0>;
> + };
> + };
> diff --git a/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt b/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
> deleted file mode 100644
> index d2eada5044b2..000000000000
> --- a/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
> +++ /dev/null
> @@ -1,53 +0,0 @@
> -* Cadence NAND controller
> -
> -Required properties:
> - - compatible : "cdns,hp-nfc"
> - - reg : Contains two entries, each of which is a tuple consisting of a
> - physical address and length. The first entry is the address and
> - length of the controller register set. The second entry is the
> - address and length of the Slave DMA data port.
> - - reg-names: should contain "reg" and "sdma"
> - - #address-cells: should be 1. The cell encodes the chip select connection.
> - - #size-cells : should be 0.
> - - interrupts : The interrupt number.
> - - clocks: phandle of the controller core clock (nf_clk).
> -
> -Optional properties:
> - - dmas: shall reference DMA channel associated to the NAND controller
> - - cdns,board-delay-ps : Estimated Board delay. The value includes the total
> - round trip delay for the signals and is used for deciding on values
> - associated with data read capture. The example formula for SDR mode is
> - the following:
> - board delay = RE#PAD delay + PCB trace to device + PCB trace from device
> - + DQ PAD delay
> -
> -Child nodes represent the available NAND chips.
This is not fully pictured in the current schema, by referencing
nand-controller.yaml I believe you allow all kind of direct
partitioning (which is legacy, and not supposed to be supported here).
Can you try to define a partition directly within the controller node
in the example and see whether it still passes the checks?
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: niravkumar.l.rabara@intel.com
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: cadence: convert cadence-nand-controller.txt to yaml
Date: Wed, 4 Oct 2023 09:44:55 +0200 [thread overview]
Message-ID: <20231004094455.1a6a19e1@xps-13> (raw)
In-Reply-To: <20231004061214.17176-1-niravkumar.l.rabara@intel.com>
Hello,
niravkumar.l.rabara@intel.com wrote on Wed, 4 Oct 2023 14:12:14 +0800:
> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>
> Convert cadence-nand-controller.txt to yaml format.
Looks good to me, one question below.
> Signed-off-by: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
> ---
> .../devicetree/bindings/mtd/cadence,nand.yaml | 73 +++++++++++++++++++
> .../bindings/mtd/cadence-nand-controller.txt | 53 --------------
> 2 files changed, 73 insertions(+), 53 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mtd/cadence,nand.yaml
> delete mode 100644 Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/cadence,nand.yaml b/Documentation/devicetree/bindings/mtd/cadence,nand.yaml
> new file mode 100644
> index 000000000000..781812ac702f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/cadence,nand.yaml
> @@ -0,0 +1,73 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mtd/cadence,nand.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Cadence NAND controller
> +
> +maintainers:
> + - Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
> +
> +allOf:
> + - $ref: nand-controller.yaml
> +
> +properties:
> + compatible:
> + items:
> + - const: cdns,hp-nfc
> +
> + reg:
> + items:
> + - description: Address and length of the controller register set
> + - description: Address and length of the Slave DMA data port
> +
> + reg-names:
> + items:
> + - const: reg
> + - const: sdma
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + dmas:
> + maxItems: 1
> +
> + cdns,board-delay-ps:
> + description: |
> + Estimated Board delay. The value includes the total round trip
> + delay for the signals and is used for deciding on values associated
> + with data read capture. The example formula for SDR mode is the
> + following.
> + board delay = RE#PAD delay + PCB trace to device + PCB trace from device
> + + DQ PAD delay
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - interrupts
> + - clocks
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + nand-controller@10b80000 {
> + compatible = "cdns,hp-nfc";
> + reg = <0x10b80000 0x10000>,
> + <0x10840000 0x10000>;
> + reg-names = "reg", "sdma";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + interrupts = <0 97 4>;
> + clocks = <&nf_clk>;
> + cdns,board-delay-ps = <4830>;
> +
> + nand@0 {
> + reg = <0>;
> + };
> + };
> diff --git a/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt b/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
> deleted file mode 100644
> index d2eada5044b2..000000000000
> --- a/Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
> +++ /dev/null
> @@ -1,53 +0,0 @@
> -* Cadence NAND controller
> -
> -Required properties:
> - - compatible : "cdns,hp-nfc"
> - - reg : Contains two entries, each of which is a tuple consisting of a
> - physical address and length. The first entry is the address and
> - length of the controller register set. The second entry is the
> - address and length of the Slave DMA data port.
> - - reg-names: should contain "reg" and "sdma"
> - - #address-cells: should be 1. The cell encodes the chip select connection.
> - - #size-cells : should be 0.
> - - interrupts : The interrupt number.
> - - clocks: phandle of the controller core clock (nf_clk).
> -
> -Optional properties:
> - - dmas: shall reference DMA channel associated to the NAND controller
> - - cdns,board-delay-ps : Estimated Board delay. The value includes the total
> - round trip delay for the signals and is used for deciding on values
> - associated with data read capture. The example formula for SDR mode is
> - the following:
> - board delay = RE#PAD delay + PCB trace to device + PCB trace from device
> - + DQ PAD delay
> -
> -Child nodes represent the available NAND chips.
This is not fully pictured in the current schema, by referencing
nand-controller.yaml I believe you allow all kind of direct
partitioning (which is legacy, and not supposed to be supported here).
Can you try to define a partition directly within the controller node
in the example and see whether it still passes the checks?
Thanks,
Miquèl
next prev parent reply other threads:[~2023-10-04 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 6:12 [PATCH] dt-bindings: mtd: cadence: convert cadence-nand-controller.txt to yaml niravkumar.l.rabara
2023-10-04 6:12 ` niravkumar.l.rabara
2023-10-04 7:44 ` Miquel Raynal [this message]
2023-10-04 7:44 ` Miquel Raynal
2023-10-04 11:00 ` Rabara, Niravkumar L
2023-10-04 11:00 ` Rabara, Niravkumar L
2023-10-04 11:32 ` Miquel Raynal
2023-10-04 11:32 ` Miquel Raynal
2023-10-05 2:35 ` kernel test robot
2023-10-05 2:35 ` kernel test robot
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=20231004094455.1a6a19e1@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=niravkumar.l.rabara@intel.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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 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.