From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: niravkumar.l.rabara@intel.com,
Miquel Raynal <miquel.raynal@bootlin.com>,
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>
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: mtd: cadence: convert cadence-nand-controller.txt to yaml
Date: Sun, 8 Oct 2023 13:21:07 +0200 [thread overview]
Message-ID: <d1a24162-74e1-4a99-ab0f-b3976cd000d6@linaro.org> (raw)
In-Reply-To: <20231005051548.55122-1-niravkumar.l.rabara@intel.com>
On 05/10/2023 07:15, niravkumar.l.rabara@intel.com wrote:
> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>
> Convert cadence-nand-controller.txt to yaml format.
> Update cadence-nand-controller.txt to cadence,nand.yaml in MAINTAINER file.
>
> +allOf:
> + - $ref: nand-controller.yaml
> +
> +properties:
> + compatible:
> + items:
> + - const: cdns,hp-nfc
> +
> + reg:
> + items:
> + - description: Address and length of the controller register set
Just "Controller register set"
> + - description: Address and length of the Slave DMA data port
"Slave DMA data port"
or
"Slave DMA data port register set"
> +
> + 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 {
This does not look properly indented. Should start at | before. IOW:
Use 4 spaces for example indentation.
> + compatible = "cdns,hp-nfc";
> + reg = <0x10b80000 0x10000>,
> + <0x10840000 0x10000>;
Please align it properly with opening <
> + reg-names = "reg", "sdma";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + interrupts = <0 97 4>;
Use defines for interrupt flags.
> + clocks = <&nf_clk>;
> + cdns,board-delay-ps = <4830>;
> +
> + nand@0 {
> + reg = <0>;
> + };
> + };
Best regards,
Krzysztof
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-10-08 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 5:15 [PATCH v2] dt-bindings: mtd: cadence: convert cadence-nand-controller.txt to yaml niravkumar.l.rabara
2023-10-06 16:58 ` Rob Herring
2023-10-08 11:21 ` Krzysztof Kozlowski [this message]
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=d1a24162-74e1-4a99-ab0f-b3976cd000d6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=miquel.raynal@bootlin.com \
--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 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).