From: "Rob Herring (Arm)" <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: mtd: refactor NAND bindings and add nand-controller-legacy.yaml
Date: Tue, 24 Mar 2026 20:09:56 -0500 [thread overview]
Message-ID: <177440099590.2332534.9132007696467343522.robh@kernel.org> (raw)
In-Reply-To: <20260324221624.2424092-1-Frank.Li@nxp.com>
On Tue, 24 Mar 2026 18:16:18 -0400, Frank Li wrote:
> The modern NAND controller binding requires NAND chips to be described as
> child nodes of the controller, for example:
>
> nand-controller {
> ...
> nand@0 {
> /* raw NAND chip properties */
> };
> };
>
> However, many existing device trees place NAND chip properties directly
> within the controller node because those controllers support only a single
> chip. This layout is still widely used by older platforms and by other DT
> consumers such as U-Boot. Migrating all existing users to the new layout
> will take time.
>
> Several kernel drivers, such as ams-delta.c, davinci_nand.c and
> fsmc_nand.c, still expect the legacy layout where raw NAND properties are
> defined in the controller node.
>
> To support both layouts during the transition:
>
> - Extract NAND chip-related properties into separate schemas
> (nand-property.yaml and raw-nand-property.yaml) from
> nand-chip.yaml and raw-nand-chip.yaml.
> - Introduce nand-controller-legacy.yaml to allow both the
> legacy and modern layouts.
> - Add a select condition in nand-controller.yaml to prevent
> node name pattern matching for fsl,* NAND controllers.
>
> Keep compatibility with existing device trees while allowing gradual
> migration to the modern binding structure.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> change in v3
> - use select: false
> - s/under/within/
> - s/property/properties/
>
> two problem left:
> 1. about "^nand@[a-f0-9]$" in nand-controller-legacy.yaml
>
> allow dts to do mirgeration from legacy layout to modern layouts for different
> boards, which use the same compatible string.
>
> 2. ref to mtd.yaml
>
> mtd.yaml force node name as flash@, nand@ ..., but here is parent node
> name is nand-controller@. Only two properties, duplicate these should be
> simple and clean enough now.
>
> change in v2
> - none
>
> change dts layout break boot
> https://lore.kernel.org/imx/177281063848.253518.12995342124719933118.b4-ty@nxp.com/T/#t
> ---
> .../devicetree/bindings/mtd/nand-chip.yaml | 46 +-----------
> ...oller.yaml => nand-controller-legacy.yaml} | 46 +++++-------
> .../bindings/mtd/nand-controller.yaml | 2 +
> .../{nand-chip.yaml => nand-property.yaml} | 14 +---
> .../bindings/mtd/raw-nand-chip.yaml | 74 +------------------
> ...-nand-chip.yaml => raw-nand-property.yaml} | 15 +---
> 6 files changed, 27 insertions(+), 170 deletions(-)
> copy Documentation/devicetree/bindings/mtd/{nand-controller.yaml => nand-controller-legacy.yaml} (69%)
> copy Documentation/devicetree/bindings/mtd/{nand-chip.yaml => nand-property.yaml} (89%)
> copy Documentation/devicetree/bindings/mtd/{raw-nand-chip.yaml => raw-nand-property.yaml} (94%)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-03-25 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 22:16 [PATCH v3 1/3] dt-bindings: mtd: refactor NAND bindings and add nand-controller-legacy.yaml Frank Li
2026-03-24 22:16 ` [PATCH v3 2/3] dt-bindings: mtd: gpmi-nand: ref to nand-controller-legacy.yaml Frank Li
2026-03-24 22:16 ` [PATCH v3 3/3] dt-bindings: mtd: mxc-nand: add missing compatible string and " Frank Li
2026-03-25 1:09 ` Rob Herring (Arm) [this message]
2026-03-25 14:29 ` [PATCH v3 1/3] dt-bindings: mtd: refactor NAND bindings and add nand-controller-legacy.yaml Miquel Raynal
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=177440099590.2332534.9132007696467343522.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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