From: Fabrice Gasnier <fabrice.gasnier@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>,
"Christoph Niedermaier" <cniedermaier@dh-electronics.com>,
"Marek Vasut" <marex@nabladev.com>,
"Goran Rađenović" <goran.radni@gmail.com>,
"Börge Strümpfel" <boerge.struempfel@gmail.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@dh-electronics.com>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Subject: [PATCH 2/4] ARM: dts: stm32: Use hex timer addresses on stm32mp15
Date: Mon, 9 Nov 2026 17:25:04 +0100 [thread overview]
Message-ID: <20261109-timer-use-hex-unit-addr-v1-2-b4abfa457adb@foss.st.com> (raw)
In-Reply-To: <20261109-timer-use-hex-unit-addr-v1-0-b4abfa457adb@foss.st.com>
Use hexadecimal unit addresses for timer subnodes. This has been raised
since ("dt-bindings: Use hex unit address patterns").
Also:
- adopt hexadecimal format for reg properties.
- update MP15 boards accordingly as they use timers 12 and 17.
Link: https://patch.msgid.link/linux-devicetree/20261102135330.2493332-1-robh@kernel.org/
Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
---
arch/arm/boot/dts/st/stm32mp151.dtsi | 46 +++++++++++-----------
arch/arm/boot/dts/st/stm32mp157c-ev1.dts | 2 +-
arch/arm/boot/dts/st/stm32mp157c-ultra-fly-sbc.dts | 2 +-
arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi | 2 +-
4 files changed, 26 insertions(+), 26 deletions(-)
diff --git a/arch/arm/boot/dts/st/stm32mp151.dtsi b/arch/arm/boot/dts/st/stm32mp151.dtsi
index ae3188373238..71f81f25af0e 100644
--- a/arch/arm/boot/dts/st/stm32mp151.dtsi
+++ b/arch/arm/boot/dts/st/stm32mp151.dtsi
@@ -632,7 +632,7 @@ pwm {
timer@1 {
compatible = "st,stm32h7-timer-trigger";
- reg = <1>;
+ reg = <0x1>;
status = "disabled";
};
@@ -669,7 +669,7 @@ pwm {
timer@2 {
compatible = "st,stm32h7-timer-trigger";
- reg = <2>;
+ reg = <0x2>;
status = "disabled";
};
@@ -704,7 +704,7 @@ pwm {
timer@3 {
compatible = "st,stm32h7-timer-trigger";
- reg = <3>;
+ reg = <0x3>;
status = "disabled";
};
@@ -741,7 +741,7 @@ pwm {
timer@4 {
compatible = "st,stm32h7-timer-trigger";
- reg = <4>;
+ reg = <0x4>;
status = "disabled";
};
@@ -772,7 +772,7 @@ counter {
timer@5 {
compatible = "st,stm32h7-timer-trigger";
- reg = <5>;
+ reg = <0x5>;
status = "disabled";
};
};
@@ -798,7 +798,7 @@ counter {
timer@6 {
compatible = "st,stm32h7-timer-trigger";
- reg = <6>;
+ reg = <0x6>;
status = "disabled";
};
};
@@ -826,9 +826,9 @@ pwm {
status = "disabled";
};
- timer@11 {
+ timer@b {
compatible = "st,stm32h7-timer-trigger";
- reg = <11>;
+ reg = <0xb>;
status = "disabled";
};
};
@@ -856,9 +856,9 @@ pwm {
status = "disabled";
};
- timer@12 {
+ timer@c {
compatible = "st,stm32h7-timer-trigger";
- reg = <12>;
+ reg = <0xc>;
status = "disabled";
};
};
@@ -886,9 +886,9 @@ pwm {
status = "disabled";
};
- timer@13 {
+ timer@d {
compatible = "st,stm32h7-timer-trigger";
- reg = <13>;
+ reg = <0xd>;
status = "disabled";
};
};
@@ -913,7 +913,7 @@ pwm {
trigger@0 {
compatible = "st,stm32-lptimer-trigger";
- reg = <0>;
+ reg = <0x0>;
status = "disabled";
};
@@ -1216,7 +1216,7 @@ pwm {
timer@0 {
compatible = "st,stm32h7-timer-trigger";
- reg = <0>;
+ reg = <0x0>;
status = "disabled";
};
@@ -1258,7 +1258,7 @@ pwm {
timer@7 {
compatible = "st,stm32h7-timer-trigger";
- reg = <7>;
+ reg = <0x7>;
status = "disabled";
};
@@ -1351,9 +1351,9 @@ pwm {
status = "disabled";
};
- timer@14 {
+ timer@e {
compatible = "st,stm32h7-timer-trigger";
- reg = <14>;
+ reg = <0xe>;
status = "disabled";
};
};
@@ -1384,9 +1384,9 @@ pwm {
status = "disabled";
};
- timer@15 {
+ timer@f {
compatible = "st,stm32h7-timer-trigger";
- reg = <15>;
+ reg = <0xf>;
status = "disabled";
};
};
@@ -1417,9 +1417,9 @@ pwm {
status = "disabled";
};
- timer@16 {
+ timer@10 {
compatible = "st,stm32h7-timer-trigger";
- reg = <16>;
+ reg = <0x10>;
status = "disabled";
};
};
@@ -1775,7 +1775,7 @@ pwm {
trigger@1 {
compatible = "st,stm32-lptimer-trigger";
- reg = <1>;
+ reg = <0x1>;
status = "disabled";
};
@@ -1805,7 +1805,7 @@ pwm {
trigger@2 {
compatible = "st,stm32-lptimer-trigger";
- reg = <2>;
+ reg = <0x2>;
status = "disabled";
};
};
diff --git a/arch/arm/boot/dts/st/stm32mp157c-ev1.dts b/arch/arm/boot/dts/st/stm32mp157c-ev1.dts
index c0e274eebf13..beba90ab1a2a 100644
--- a/arch/arm/boot/dts/st/stm32mp157c-ev1.dts
+++ b/arch/arm/boot/dts/st/stm32mp157c-ev1.dts
@@ -411,7 +411,7 @@ pwm {
pinctrl-names = "default", "sleep";
status = "okay";
};
- timer@11 {
+ timer@b {
status = "okay";
};
};
diff --git a/arch/arm/boot/dts/st/stm32mp157c-ultra-fly-sbc.dts b/arch/arm/boot/dts/st/stm32mp157c-ultra-fly-sbc.dts
index 2531f4bc8ca4..d7eeedbc6600 100644
--- a/arch/arm/boot/dts/st/stm32mp157c-ultra-fly-sbc.dts
+++ b/arch/arm/boot/dts/st/stm32mp157c-ultra-fly-sbc.dts
@@ -1058,7 +1058,7 @@ pwm17_4: pwm {
status = "okay";
};
- timer@16 {
+ timer@10 {
status = "okay";
};
};
diff --git a/arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi b/arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi
index 1a07ae09afb2..816669169474 100644
--- a/arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi
+++ b/arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi
@@ -747,7 +747,7 @@ pwm {
pinctrl-names = "default", "sleep";
status = "okay";
};
- timer@11 {
+ timer@b {
status = "okay";
};
};
--
2.43.0
next prev parent reply other threads:[~2026-11-09 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 16:25 [PATCH 0/4] ARM: dts: stm32: adopt hex format for timers Fabrice Gasnier
2026-11-09 16:25 ` [PATCH 1/4] ARM: dts: stm32: Use hex timer addresses on stm32mp13 Fabrice Gasnier
2026-11-09 16:25 ` Fabrice Gasnier [this message]
2026-11-09 16:25 ` [PATCH 3/4] ARM: dts: stm32: use hex reg for timer2 on stm32mp15xx-dhcom-overlay Fabrice Gasnier
2026-11-09 16:25 ` [PATCH 4/4] arm64: dts: stm32: Use hex timer addresses on stm32mp251 Fabrice Gasnier
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=20261109-timer-use-hex-unit-addr-v1-2-b4abfa457adb@foss.st.com \
--to=fabrice.gasnier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=boerge.struempfel@gmail.com \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=goran.radni@gmail.com \
--cc=kernel@dh-electronics.com \
--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=marex@nabladev.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®