From: sashiko-bot@kernel.org
To: "Gabriel Fernandez" <gabriel.fernandez@foss.st.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: arm: stm32: Add clock-controller sub-node to STM32MP2 SYSCFG
Date: Tue, 10 Nov 2026 10:49:13 +0000 [thread overview]
Message-ID: <sashiko-outbox-206890@kernel.org> (raw)
In-Reply-To: <20261110-ups_mp25_clk_syscfg-v1-2-667829cd290a@foss.st.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dt-bindings: arm: stm32: split STM32MP23/25 SYSCFG into separate
schema
--
commit a55565d107267a4ad1a075c0905a54ac3317622d
Author: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
dt-bindings: arm: stm32: Add clock-controller sub-node to STM32MP2 SYSCFG
This commit adds a clock-controller sub-node to the STM32 SYSCFG binding,
requiring it on st,stm32mp23-syscfg and st,stm32mp25-syscfg and forbidding
it on all other variants.
> diff --git a/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml b/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> index a559f8b03b842..38c844e8f19db 100644
> --- a/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> +++ b/Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml
> @@ -45,6 +45,10 @@ properties:
> "#size-cells":
> const: 1
>
> + clock-controller:
> + type: object
> + $ref: /schemas/clock/st,stm32mp25-syscfg-clk.yaml#
> +
> patternProperties:
> "^phy@2[48]00$":
> type: object
> @@ -80,6 +84,7 @@ allOf:
> - "#address-cells"
> - "#clock-cells"
> - "#size-cells"
> + - clock-controller
> - phy@2400
> - phy@2800
> else:
> @@ -87,6 +92,7 @@ allOf:
> '#address-cells': false
> '#clock-cells': false
> '#size-cells': false
> + clock-controller: false
> phy@2400: false
> phy@2800: false
[Severity: Low]
Should st,stm32mp23-syscfg and st,stm32mp25-syscfg be split into a
separate binding schema?
Unlike the other seven compatibles in st,stm32-syscon.yaml, which only
take compatible, reg and optionally clocks, the STM32MP23/25 variants
forbid clocks and require six dedicated properties and sub-nodes
(#address-cells, #clock-cells, #size-cells, clock-controller, phy@2400
and phy@2800) that have to be explicitly set to false for every other SoC.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-ups_mp25_clk_syscfg-v1-0-667829cd290a@foss.st.com?part=2
next prev parent reply other threads:[~2026-11-10 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 10:42 [PATCH 0/5] clk: stm32: Add the STM32MP2 SYSCFG LTDC pixel clock mux Gabriel Fernandez
2026-11-10 10:42 ` [PATCH 1/5] dt-bindings: clock: Add STM32MP25 SYSCFG clock controller Gabriel Fernandez
2026-11-10 10:53 ` sashiko-bot
2026-11-10 10:42 ` [PATCH 2/5] dt-bindings: arm: stm32: Add clock-controller sub-node to STM32MP2 SYSCFG Gabriel Fernandez
2026-11-10 10:49 ` sashiko-bot [this message]
2026-11-10 18:54 ` Conor Dooley
2026-11-10 10:42 ` [PATCH 3/5] clk: stm32: Add STM32MP25 SYSCFG clock driver Gabriel Fernandez
2026-11-10 10:42 ` [PATCH 4/5] arm64: dts: st: add LTDC pixel clock controller on stm32mp23 Gabriel Fernandez
2026-11-10 10:42 ` [PATCH 5/5] arm64: dts: st: add LTDC pixel clock controller on stm32mp25 Gabriel Fernandez
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=sashiko-outbox-206890@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@foss.st.com \
--cc=linux-clk@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox