mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 3/4] ARM: dts: stm32: use hex reg for timer2 on stm32mp15xx-dhcom-overlay
Date: Mon, 9 Nov 2026 17:25:05 +0100	[thread overview]
Message-ID: <20261109-timer-use-hex-unit-addr-v1-3-b4abfa457adb@foss.st.com> (raw)
In-Reply-To: <20261109-timer-use-hex-unit-addr-v1-0-b4abfa457adb@foss.st.com>

Use hexadecimal format for reg property. This has been raised since
("dt-bindings: Use hex unit address patterns"). The SoC dtsi file has
been updated to adopt hex for unit addresses and reg properties. So
update reg property in stm32mp15xx-dhcom-overlay too.

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/stm32mp15xx-dhcom-overlay-panel-dpi.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/st/stm32mp15xx-dhcom-overlay-panel-dpi.dtsi b/arch/arm/boot/dts/st/stm32mp15xx-dhcom-overlay-panel-dpi.dtsi
index 41229ec680cc..e9a58a8ea61e 100644
--- a/arch/arm/boot/dts/st/stm32mp15xx-dhcom-overlay-panel-dpi.dtsi
+++ b/arch/arm/boot/dts/st/stm32mp15xx-dhcom-overlay-panel-dpi.dtsi
@@ -56,7 +56,7 @@ pwm2: pwm {
 	};
 
 	timer@1 {
-		reg = <1>;
+		reg = <0x1>;
 		status = "okay";
 	};
 };

-- 
2.43.0


  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 ` [PATCH 2/4] ARM: dts: stm32: Use hex timer addresses on stm32mp15 Fabrice Gasnier
2026-11-09 16:25 ` Fabrice Gasnier [this message]
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-3-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®