From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: imx@lists.linux.dev, conor+dt@kernel.org, robh@kernel.org,
devicetree@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: soc: imx: Add fsl,eim-bus
Date: Wed, 08 Jul 2026 20:10:18 +0000 [thread overview]
Message-ID: <20260708201018.C7C2A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708-imx53-eim-v1-1-913b4559e5b5@nxp.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The updated `$nodename` regex explicitly allows `eim-bus` but mathematically fails to match the actual node name `eim-cs1` used in the device tree, resulting in a new schema validation warning instead of fixing the issue.
- [Low] The commit message incorrectly attributes the compatible string to i.MX51 variants instead of i.MX53.
--
--- Patch [1]: [PATCH 1/2] dt-bindings: soc: imx: Add fsl,eim-bus ---
commit c123bec5543c2323c455145cf374a9559692a3a5
Author: Frank Li <Frank.Li@nxp.com>
dt-bindings: soc: imx: Add fsl,eim-bus
This commit adds the fsl,eim-bus compatible string to the fsl,spba-bus
binding to resolve schema validation warnings for legacy i.MX devices. It
also updates the nodename pattern in the schema.
> dt-bindings: soc: imx: Add fsl,eim-bus
>
> Add the fsl,eim-bus compatible strings for i.MX51 variants.
[Severity: Low]
This isn't a bug, but is the reference to i.MX51 variants accurate in the
commit message? The CHECK_DTBS warning listed below is specifically for
imx53-ard.dtb, which suggests this compatible is actually targeting i.MX53
variants rather than i.MX51.
[ ... ]
> diff --git a/Documentation/devicetree/bindings/bus/fsl,spba-bus.yaml b/Documentation/devicetree/bindings/bus/fsl,spba-bus.yaml
> --- a/Documentation/devicetree/bindings/bus/fsl,spba-bus.yaml
> +++ b/Documentation/devicetree/bindings/bus/fsl,spba-bus.yaml
[ ... ]
> @@ -36,13 +37,14 @@ select:
>
> properties:
> $nodename:
> - pattern: "^((spba|emi)-bus|bus)(@[0-9a-f]+)?$"
> + pattern: "^((spba|emi|eim)-bus|bus)(@[0-9a-f]+)?$"
[Severity: Medium]
Will this regex change successfully clear the validation warning?
The commit message states we are fixing a warning for the node
eim-cs1@f4000000. However, the updated pattern permits eim-bus but
structurally fails to match eim-cs1. Does this mean make dtbs_check
will simply evaluate the regex against the eim-cs1@f4000000 node and emit
a new schema validation warning for the nodename?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260708-imx53-eim-v1-0-913b4559e5b5@nxp.com?part=1
next prev parent reply other threads:[~2026-07-08 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 20:00 [PATCH 0/2] ARM: dts: imx: clean up fsl,emi-bus related CHECK_DTBS warnings Frank.Li
2026-07-08 20:00 ` [PATCH 1/2] dt-bindings: soc: imx: Add fsl,eim-bus Frank.Li
2026-07-08 20:10 ` sashiko-bot [this message]
2026-07-08 20:00 ` [PATCH 2/2] ARM: dts: imx53-ard: change node name eim-cs1 to eim-cs1-bus Frank.Li
2026-07-08 20:07 ` sashiko-bot
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=20260708201018.C7C2A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.