From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Christophe Roullier <christophe.roullier@foss.st.com>
Cc: "Philippe Cornu" <philippe.cornu@foss.st.com>,
"Yannick Fertre" <yannick.fertre@foss.st.com>,
"Raphaël Gallais-Pou" <rgallaispou@gmail.com>,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 5/9] arm64: dts: st: add clock-cells to syscfg node on stm32mp231
Date: Tue, 10 Feb 2026 11:03:58 +0100 [thread overview]
Message-ID: <20260210-display-v2-5-0592bd514958@foss.st.com> (raw)
In-Reply-To: <20260210-display-v2-0-0592bd514958@foss.st.com>
Make the syscfg node a clock provider so clock consumers can reach child
clocks through device-tree.
Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
---
arch/arm64/boot/dts/st/stm32mp231.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/st/stm32mp231.dtsi b/arch/arm64/boot/dts/st/stm32mp231.dtsi
index 05055bc523850282a2e2b217b180930b39231189..74df739d8f8cdc82922cad9993486b97c50d9084 100644
--- a/arch/arm64/boot/dts/st/stm32mp231.dtsi
+++ b/arch/arm64/boot/dts/st/stm32mp231.dtsi
@@ -961,6 +961,7 @@ exti1: interrupt-controller@44220000 {
syscfg: syscon@44230000 {
compatible = "st,stm32mp23-syscfg", "syscon";
reg = <0x44230000 0x10000>;
+ #clock-cells = <0>;
};
pinctrl: pinctrl@44240000 {
--
2.43.0
next prev parent reply other threads:[~2026-02-10 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 10:03 [PATCH v2 0/9] Enable display support for STM32MP257F-DK and STM32MP235F-DK Raphael Gallais-Pou
2026-02-10 10:03 ` [PATCH v2 1/9] arm64: dts: st: add i2c2 pins for stm32mp25 Raphael Gallais-Pou
2026-02-10 10:03 ` [PATCH v2 2/9] arm64: dts: st: add ltdc support on stm32mp231 Raphael Gallais-Pou
2026-02-10 10:03 ` [PATCH v2 3/9] arm64: dts: st: add ltdc support on stm32mp235 Raphael Gallais-Pou
2026-02-10 10:03 ` [PATCH v2 4/9] arm64: dts: st: add lvds " Raphael Gallais-Pou
2026-02-10 10:03 ` Raphael Gallais-Pou [this message]
2026-02-10 10:03 ` [PATCH v2 6/9] arm64: dts: st: describe power supplies for stm32mp235f-dk board Raphael Gallais-Pou
2026-02-10 10:04 ` [PATCH v2 7/9] arm64: dts: st: enable display support on " Raphael Gallais-Pou
2026-02-10 10:04 ` [PATCH v2 8/9] arm64: dts: st: describe power supplies for stm32mp257f-dk board Raphael Gallais-Pou
2026-02-10 10:04 ` [PATCH v2 9/9] arm64: dts: st: enable display support on " Raphael Gallais-Pou
2026-03-05 13:06 ` [Linux-stm32] [PATCH v2 0/9] Enable display support for STM32MP257F-DK and STM32MP235F-DK Raphael Gallais-Pou
2026-03-25 14:45 ` Alexandre TORGUE
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=20260210-display-v2-5-0592bd514958@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@foss.st.com \
--cc=rgallaispou@gmail.com \
--cc=robh@kernel.org \
--cc=yannick.fertre@foss.st.com \
/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