From: "J. Neuschäfer" <j.ne@posteo.net>
To: Rob Herring <robh@kernel.org>, Miquel Raynal <miquel.raynal@bootlin.com>
Cc: "J. Neuschäfer" <j.ne@posteo.net>,
"Richard Weinberger" <richard@nod.at>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, "Crystal Wood" <oss@buserror.net>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
devicetree@vger.kernel.org, "Frank Li" <Frank.Li@nxp.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Madhavan Srinivasan" <maddy@linux.ibm.com>,
linux-mtd@lists.infradead.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Naveen N Rao" <naveen@kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/3] dt-bindings: nand: Add fsl,elbc-fcm-nand
Date: Sat, 8 Mar 2025 18:40:43 +0000 [thread overview]
Message-ID: <Z8yPKx1U-sT1OGeb@probook> (raw)
In-Reply-To: <20250303140021.GA1732495-robh@kernel.org>
Miquel, what do you think about Rob's suggestion below?
On Mon, Mar 03, 2025 at 08:00:21AM -0600, Rob Herring wrote:
> On Wed, Feb 26, 2025 at 12:45:17PM -0600, Rob Herring (Arm) wrote:
> >
> > On Wed, 26 Feb 2025 18:01:41 +0100, J. Neuschäfer wrote:
> > > Formalize the binding already supported by the fsl_elbc_nand.c driver
> > > and used in several device trees in arch/powerpc/boot/dts/.
> > >
> > > raw-nand-chip.yaml is referenced in order to accommodate situations in
> > > which the ECC parameters settings are set in the device tree. One such
> > > example is in arch/powerpc/boot/dts/turris1x.dts:
> > >
> > > /* MT29F2G08ABAEAWP:E NAND */
> > > nand@1,0 {
> > > compatible = "fsl,p2020-fcm-nand", "fsl,elbc-fcm-nand";
> > > reg = <0x1 0x0 0x00040000>;
> > > nand-ecc-mode = "soft";
> > > nand-ecc-algo = "bch";
> > >
> > > partitions { ... };
> > > };
> > >
> > > Reviewed-by: Frank Li <Frank.Li@nxp.com>
> > > Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> > > ---
> > >
> > > V3:
> > > - remove unnecessary #address/size-cells from nand node in example
> > > - add Frank Li's review tag
> > > - add missing end of document marker (...)
> > > - explain choice to reference raw-nand-chip.yaml
> > >
> > > V2:
> > > - split out from fsl,elbc binding patch
> > > - constrain #address-cells and #size-cells
> > > - add a general description
> > > - use unevaluatedProperties=false instead of additionalProperties=false
> > > - fix property order to comply with dts coding style
> > > - include raw-nand-chip.yaml instead of nand-chip.yaml
> > > ---
> > > .../devicetree/bindings/mtd/fsl,elbc-fcm-nand.yaml | 68 ++++++++++++++++++++++
> > > 1 file changed, 68 insertions(+)
> > >
> >
> > My bot found errors running 'make dt_binding_check' on your patch:
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mtd/fsl,elbc-fcm-nand.example.dtb: nand@1,0: $nodename:0: 'nand@1,0' does not match '^nand@[a-f0-9]$'
> > from schema $id: http://devicetree.org/schemas/mtd/fsl,elbc-fcm-nand.yaml#
>
> Drop the unit address in raw-nand-chip.yaml. So:
>
> properties:
> $nodename:
> pattern: "^nand@"
>
^^^
Best Regards,
J. Neuschäfer
next prev parent reply other threads:[~2025-03-08 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 17:01 [PATCH v3 0/3] Freescale Enhanced Local Bus Controller (eLBC) binding YAML conversion J. Neuschäfer via B4 Relay
2025-02-26 17:01 ` [PATCH v3 1/3] dt-bindings: memory-controllers: Add fsl,elbc-gpcm-uio J. Neuschäfer via B4 Relay
2025-02-26 17:01 ` [PATCH v3 2/3] dt-bindings: nand: Add fsl,elbc-fcm-nand J. Neuschäfer via B4 Relay
2025-02-26 18:45 ` Rob Herring (Arm)
2025-03-03 14:00 ` Rob Herring
2025-03-08 18:40 ` J. Neuschäfer [this message]
2025-03-10 14:00 ` Miquel Raynal
2025-02-26 17:01 ` [PATCH v3 3/3] dt-bindings: memory-controllers: Convert fsl,elbc to YAML J. Neuschäfer via B4 Relay
2025-02-26 18:45 ` Rob Herring (Arm)
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=Z8yPKx1U-sT1OGeb@probook \
--to=j.ne@posteo.net \
--cc=Frank.Li@nxp.com \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=miquel.raynal@bootlin.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=oss@buserror.net \
--cc=richard@nod.at \
--cc=robh@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).