From: sashiko-bot@kernel.org
To: "Marek Vasut" <marex@nabladev.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: stm32: Document st,stm32mp23/25-syscfg subnodes and cells
Date: Fri, 28 Aug 2026 15:27:17 +0000 [thread overview]
Message-ID: <20260828152717.6C67B1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260828151216.175020-1-marex@nabladev.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The conditional `if` block for `st,stm32mp23-syscfg` and `st,stm32mp25-syscfg` uses `enum` directly instead of `contains: enum`, which fails to match the array-typed `compatible` property and bypasses validation.
- [Medium] The schema examples section does not include a demonstration of the newly required properties and subnodes, leaving the new variant untested.
--
commit 756e633a3636918c549af9224be89571f86da4e0
Author: Marek Vasut <marex@nabladev.com>
Subject: dt-bindings: arm: stm32: Document st,stm32mp23/25-syscfg subnodes and cells
The st,stm32mp23-syscfg and st,stm32mp25-syscfg can have subnodes, which
represent the USB 2.0 FEMTO-PHY. Document subnodes pattern properties and
address/size cells.
> diff --git a/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml b/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> index 95d2319afe235..d82afa39960b9 100644
> --- a/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> +++ b/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
[ ... ]
> @@ -57,10 +68,14 @@ allOf:
> - if:
> properties:
> compatible:
> - const: st,stm32mp25-syscfg
> + enum:
> + - st,stm32mp23-syscfg
> + - st,stm32mp25-syscfg
[Severity: High]
Does checking the array-typed compatible property directly against enum fail
to match here?
Since the compatible property is defined globally as an array (e.g.,
["st,stm32mp25-syscfg", "syscon"]), wouldn't evaluating it against a string
enum evaluate to false and completely bypass the validation constraints?
Should this use contains: enum instead?
> then:
> required:
> - "#clock-cells"
> + - "#address-cells"
> + - "#size-cells"
[Severity: Medium]
Do the newly authored constraints and phy subnode need to be added to the
examples section?
Currently, the examples only cover the older st,stm32mp157-syscfg variant.
Does this mean the new requirements for mp23/mp25 aren't validated when
running make dt_binding_check?
>
> additionalProperties: false
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828151216.175020-1-marex@nabladev.com?part=1
next prev parent reply other threads:[~2026-08-28 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:11 [PATCH v4 1/2] dt-bindings: arm: stm32: Document st,stm32mp23/25-syscfg subnodes and cells Marek Vasut
2026-08-28 15:11 ` [PATCH v4 2/2] soc: st: Add STM32MP2 SYSCFG driver Marek Vasut
2026-08-28 15:27 ` sashiko-bot [this message]
2026-08-28 15:57 ` [PATCH v4 1/2] dt-bindings: arm: stm32: Document st,stm32mp23/25-syscfg subnodes and cells Conor Dooley
2026-08-28 16:05 ` Marek Vasut
2026-08-31 15:05 ` Conor Dooley
2026-08-31 16:27 ` Marek Vasut
2026-08-31 17:13 ` Conor Dooley
2026-08-31 17:38 ` Marek Vasut
2026-08-31 19:56 ` Conor Dooley
2026-09-01 11:53 ` Marek Vasut
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=20260828152717.6C67B1F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=marex@nabladev.com \
--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.