The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: "J. Neuschäfer" <j.ne@posteo.net>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	Crystal Wood <oss@buserror.net>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	Naveen N Rao <naveen@kernel.org>,
	devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v4 1/4] dt-bindings: mtd: raw-nand-chip: Relax node name pattern
Date: Mon, 17 Mar 2025 11:01:37 -0500	[thread overview]
Message-ID: <174222729663.55568.3356685384531262945.robh@kernel.org> (raw)
In-Reply-To: <20250313-ppcyaml-elbc-v4-1-55903722d9ea@posteo.net>


On Thu, 13 Mar 2025 22:35:44 +0100, J. Neuschäfer wrote:
> In some scenarios, such as under the Freescale eLBC bus, there are raw
> NAND chips with a unit address that has a comma in it (cs,offset).
> For reasons of compatibility with historical device trees and
> readability of the unit addresses, this format is kept.
> 
> Relax the $nodename pattern in raw-nand-chip.yaml to allow such unit
> addresses. Unfortunately $nonenames defined in bindings that reference
> raw-nand
> 
> Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> ---
> 
> V4:
> - reintroduce patch to silence dtc validation error, after discussion
>   with Rob Herring and Miquèl Raynal
> - add some more detail to the commit message
> - remove unit address format rather than extending it
>   (old pattern: "^nand@[a-f0-9](,[0-9a-f]*)?$")
> 
> V3:
> - remove patch after discussion with Miquèl Raynal
> 
> V2:
> - new patch
> ---
>  Documentation/devicetree/bindings/mtd/raw-nand-chip.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2025-03-17 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 21:35 [PATCH v4 0/4] Freescale Enhanced Local Bus Controller (eLBC) binding YAML conversion J. Neuschäfer via B4 Relay
2025-03-13 21:35 ` [PATCH v4 1/4] dt-bindings: mtd: raw-nand-chip: Relax node name pattern J. Neuschäfer via B4 Relay
2025-03-17 16:01   ` Rob Herring (Arm) [this message]
2025-03-13 21:35 ` [PATCH v4 2/4] dt-bindings: memory-controllers: Add fsl,elbc-gpcm-uio J. Neuschäfer via B4 Relay
2025-03-13 21:35 ` [PATCH v4 3/4] dt-bindings: nand: Add fsl,elbc-fcm-nand J. Neuschäfer via B4 Relay
2025-03-17 16:03   ` Rob Herring (Arm)
2025-03-13 21:35 ` [PATCH v4 4/4] dt-bindings: memory-controllers: Convert fsl,elbc to YAML J. Neuschäfer via B4 Relay
2025-03-13 22:51   ` 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=174222729663.55568.3356685384531262945.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j.ne@posteo.net \
    --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=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