[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aVwXdU3yEqkFBIHh@lizhi-Precision-Tower-5810>
Date: Mon, 5 Jan 2026 14:56:37 -0500
From: Frank Li <Frank.li@....com>
To: Peng Fan <peng.fan@....nxp.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, devicetree@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] ARM: dts: imx: cleanup most gpmi related CHECK_DTB
warning
On Wed, Nov 05, 2025 at 10:07:26AM +0800, Peng Fan wrote:
> On Tue, Nov 04, 2025 at 05:27:11PM -0500, Frank Li wrote:
> >Only few warning left because original data is wrong
> >arch/arm/boot/dts/nxp/imx/imx6ull-engicam-microgea-bmm.dtb: nand-controller@...6000 (fsl,imx6q-gpmi-nand): nand@0:nand-ecc-step-size: 0 is less than the minimum of 1
> >
> >driver will leave default value when these value is 0, but binding require
> >start from 1.
> >
> >Since 2019 year, commit
> > (212e496935929 dt-bindings: mtd: Add YAML schemas for the generic NAND options)
> > NAND related property is preferred located under nand@<n> even though only
> > one NAND chip supported.
> >
> >NAND related property should be located under nand@0. This format already
> >support quite long time, so it should be safe to switch to modern format.
> >
> >Signed-off-by: Frank Li <Frank.Li@....com>
> >---
> >Frank Li (3):
> > ARM: dts: imx6qdl: add '#address-cells' and '#size-cells' for gpmi-nand
> > ARM: dts: imx6sx: update gpmi #size-cells to 0
> > ARM: dts: imx: move nand related property under nand@0
> >
>
Shawn:
Do you have chance to check this?
Frank
> Reviewed-by: Peng Fan <peng.fan@....com>
Powered by blists - more mailing lists