From: "Rob Herring (Arm)" <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] ARM: dts: imx31: Use nand-controller as node name
Date: Thu, 20 Feb 2025 15:29:16 -0600 [thread overview]
Message-ID: <174008661713.4046746.867347616355576496.robh@kernel.org> (raw)
In-Reply-To: <20250220130345.2375204-1-festevam@gmail.com>
On Thu, 20 Feb 2025 10:03:45 -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> According to mxc-nand.yaml, the correct node name must be
> 'nand-controller'.
>
> Change it accordingly to fix the following dt-schema warning:
>
> $nodename:0: 'nand@b8000000' does not match '^nand-controller(@.*)?'
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> arch/arm/boot/dts/nxp/imx/imx31.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/nxp/' for 20250220130345.2375204-1-festevam@gmail.com:
arch/arm/boot/dts/nxp/imx/imx31-bug.dtb: nand-controller@b8000000: #size-cells: 0 was expected
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-bug.dtb: nand-controller@b8000000: compatible:0: 'fsl,imx27-nand' was expected
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-bug.dtb: nand-controller@b8000000: compatible: ['fsl,imx31-nand', 'fsl,imx27-nand'] is too long
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-bug.dtb: nand-controller@b8000000: #size-cells: 0 was expected
from schema $id: http://devicetree.org/schemas/mtd/nand-controller.yaml#
arch/arm/boot/dts/nxp/imx/imx31-bug.dtb: /soc/emi@b8000000/nand-controller@b8000000: failed to match any schema with compatible: ['fsl,imx31-nand', 'fsl,imx27-nand']
arch/arm/boot/dts/nxp/imx/imx31-lite.dtb: nand-controller@b8000000: #size-cells: 0 was expected
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-lite.dtb: nand-controller@b8000000: compatible:0: 'fsl,imx27-nand' was expected
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-lite.dtb: nand-controller@b8000000: compatible: ['fsl,imx31-nand', 'fsl,imx27-nand'] is too long
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-lite.dtb: nand-controller@b8000000: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'clocks', 'compatible', 'dma-names', 'dmas', 'nand-bus-width', 'nand-ecc-mode', 'nand-on-flash-bbt' were unexpected)
from schema $id: http://devicetree.org/schemas/mtd/mxc-nand.yaml#
arch/arm/boot/dts/nxp/imx/imx31-lite.dtb: nand-controller@b8000000: #size-cells: 0 was expected
from schema $id: http://devicetree.org/schemas/mtd/nand-controller.yaml#
arch/arm/boot/dts/nxp/imx/imx31-lite.dtb: /soc/emi@b8000000/nand-controller@b8000000: failed to match any schema with compatible: ['fsl,imx31-nand', 'fsl,imx27-nand']
next prev parent reply other threads:[~2025-02-20 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:03 [PATCH] ARM: dts: imx31: Use nand-controller as node name Fabio Estevam
2025-02-20 21:29 ` Rob Herring (Arm) [this message]
2025-03-11 1:56 ` Shawn Guo
2025-03-17 11:19 ` Krzysztof Kozlowski
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=174008661713.4046746.867347616355576496.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawnguo@kernel.org \
/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