From: sashiko-bot@kernel.org
To: "Zoltan HERPAI" <wigyori@uid0.hu>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm64: fsl: add Olimex i.MX8MP boards
Date: Fri, 18 Sep 2026 20:04:32 +0000 [thread overview]
Message-ID: <20260918200432.C3A811F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918195559.130443-2-wigyori@uid0.hu>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: broken compatible string sequence for Olimex i.MX8MP
--
commit fac5462a0966914cfbc1e0773b00c8f06fddde88
Author: Zoltan HERPAI <wigyori@uid0.hu>
dt-bindings: arm64: fsl: add Olimex i.MX8MP boards
Document board compatible bindings for the Olimex i.MX8MP-SOM and
-EVB boards.
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 656f2596e1d53..aef15322293e1 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -1146,6 +1146,8 @@ properties:
> - gateworks,imx8mp-gw74xx # i.MX8MP Gateworks Board
> - gateworks,imx8mp-gw75xx-2x # i.MX8MP Gateworks Board
> - gateworks,imx8mp-gw82xx-2x # i.MX8MP Gateworks Board
> + - olimex,imx8mp-som # Olimex i.MX8MP-SOM
> + - olimex,imx8mp-som-evb # Olimex i.MX8MP-SOM-EVB
[Severity: Low]
Does adding the EVB string directly to this enum permit it to bypass the SoM
component string dependency? It seems this validates a 2-item sequence instead
of the standard 3-item sequence (Carrier -> SoM -> SoC) expected for SoM-based
carrier boards.
> - prt,prt8ml # Protonic PRT8ML
> - skov,imx8mp-skov-basic # SKOV i.MX8MP baseboard without frontplate
[ ... ]
> @@ -1225,6 +1227,11 @@ properties:
> - const: kontron,imx8mp-osm-s # Kontron i.MX8MP OSM-S SoM
> - const: fsl,imx8mp
>
> + - description: Olimex i.MX8MP boards
> + items:
> + - const: olimex,imx8mp-som # Olimex i.MX8MP-SOM
> + - const: olimex,imx8mp-som-evb # Olimex i.MX8MP-SOM-EVB
[Severity: Low]
Does this block enforce a backwards 2-item sequence with the most specific
board listed last?
Also, it appears the mandatory SoC fallback (fsl,imx8mp) is entirely omitted
here. Will this cause dt_binding_check or dtbs_check to fail when run on a
properly constructed 3-item compatible array?
> +
> - description: PHYTEC phyCORE-i.MX8MP FPSC based boards
> items:
> - enum:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918195559.130443-1-wigyori@uid0.hu?part=1
next prev parent reply other threads:[~2026-09-18 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 19:55 [PATCH 0/2] arm64: add support for Olimex i.MX8MP-SOM-EVB kit Zoltan HERPAI
2026-09-18 19:55 ` [PATCH 1/2] dt-bindings: arm64: fsl: add Olimex i.MX8MP boards Zoltan HERPAI
2026-09-18 20:04 ` sashiko-bot [this message]
2026-09-19 7:11 ` Krzysztof Kozlowski
2026-09-18 19:55 ` [PATCH 2/2] arm64: dts: imx8mp: add Olimex i.MX8MP-SOM-EVB kit Zoltan HERPAI
2026-09-18 20:07 ` sashiko-bot
2026-09-19 7:10 ` Krzysztof Kozlowski
2026-09-20 15:04 ` Andrew Lunn
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=20260918200432.C3A811F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wigyori@uid0.hu \
/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