From: "Rob Herring (Arm)" <robh@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: mtd: convert IBM NDFC binding to YAML
Date: Mon, 28 Sep 2026 16:20:47 -0500 [thread overview]
Message-ID: <179063044641.731990.2506893904840369119.robh@kernel.org> (raw)
In-Reply-To: <20260926014802.87255-1-rosenp@gmail.com>
On Fri, 25 Sep 2026 18:48:02 -0700, Rosen Penev wrote:
> The NDFC NAND flash controller was only described in a legacy text file,
> so dtbs_check reported "failed to match any schema with compatible:
> ['ibm,ndfc']" for the ndfc nodes of the bluestone, canyonlands, eiger,
> glacier, sequoia and warp device trees.
>
> Convert the binding to the YAML format so those nodes match the generic
> nand-controller-legacy schema. Describe the node's reg, ccr and
> bank-settings properties, along with its "nand" chip node which carries
> the legacy partition layout.
>
> The "nand" chip node carries no unit address, so the "nand@[a-f0-9]"
> pattern of nand-controller-legacy.yaml never matches it and
> raw-nand-chip.yaml is never applied. Describe it with mtd.yaml,
> nand-property.yaml and raw-nand-property.yaml instead, the way the
> controller level does, so that both the deprecated partition@ nodes and
> a modern "partitions" subnode are accepted. The node name does not
> matter, the driver picks the first child of the controller node.
>
> Assisted-by: LLM
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> v4: allow modern partitions
> v3: fix wrong regex
> v2: fix reg value
> .../devicetree/bindings/mtd/ibm,ndfc.txt | 39 ------
> .../devicetree/bindings/mtd/ibm,ndfc.yaml | 128 ++++++++++++++++++
> 2 files changed, 128 insertions(+), 39 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mtd/ibm,ndfc.txt
> create mode 100644 Documentation/devicetree/bindings/mtd/ibm,ndfc.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2026-09-28 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 1:48 Rosen Penev
2026-09-28 21:20 ` Rob Herring (Arm) [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=179063044641.731990.2506893904840369119.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=rosenp@gmail.com \
--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
all inboxes | Powered by JetHome®