From: Anurag Dutta <a-dutta@ti.com>
To: <aaro.koskinen@iki.fi>, <andreas@kemnade.info>,
<khilman@baylibre.com>, <rogerq@kernel.org>, <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>, <vigneshr@ti.com>
Subject: [PATCH v2 2/2] ARM: dts: ti: omap: Use DMTimer as Clocksource instead of counter_32k
Date: Mon, 1 Sep 2025 15:45:25 +0530 [thread overview]
Message-ID: <20250901101525.1090334-3-a-dutta@ti.com> (raw)
In-Reply-To: <20250901101525.1090334-1-a-dutta@ti.com>
From: Sinthu Raja <sinthu.raja@ti.com>
Clock drift of approximately 500 ppm is observed with 'counter_32k'
as clocksource. Clock drift is seen because 'counter_32k' is running
with 32786Hz frequency instead it should run with 32768Hz. Use DMTimer as
clocksource, which is running at 32768Hz to fix the clock drift issue.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Signed-off-by: Anurag Dutta <a-dutta@ti.com>
---
arch/arm/boot/dts/ti/omap/am57xx-beagle-x15.dts | 9 +++++++++
arch/arm/boot/dts/ti/omap/dra7-l4.dtsi | 2 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/ti/omap/am57xx-beagle-x15.dts b/arch/arm/boot/dts/ti/omap/am57xx-beagle-x15.dts
index 0a8b16505ed9..83009883277e 100644
--- a/arch/arm/boot/dts/ti/omap/am57xx-beagle-x15.dts
+++ b/arch/arm/boot/dts/ti/omap/am57xx-beagle-x15.dts
@@ -36,3 +36,12 @@ &mmc2 {
&phy1 {
max-speed = <100>;
};
+
+&timer12_target {
+ ti,no-reset-on-init;
+ ti,no-idle;
+};
+
+&counter32k {
+ status = "disabled";
+};
diff --git a/arch/arm/boot/dts/ti/omap/dra7-l4.dtsi b/arch/arm/boot/dts/ti/omap/dra7-l4.dtsi
index ba7fdaae9c6e..0e0b5364be2b 100644
--- a/arch/arm/boot/dts/ti/omap/dra7-l4.dtsi
+++ b/arch/arm/boot/dts/ti/omap/dra7-l4.dtsi
@@ -4439,7 +4439,7 @@ segment@20000 { /* 0x4ae20000 */
<0x0000c000 0x0002c000 0x001000>, /* ap 29 */
<0x0000f000 0x0002f000 0x001000>; /* ap 32 */
- target-module@0 { /* 0x4ae20000, ap 19 08.0 */
+ timer12_target: target-module@0 { /* 0x4ae20000, ap 19 08.0 */
compatible = "ti,sysc-omap4-timer", "ti,sysc";
reg = <0x0 0x4>,
<0x10 0x4>;
--
2.34.1
next prev parent reply other threads:[~2025-09-01 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 10:15 [PATCH v2 0/2] AM57 timer fixes Anurag Dutta
2025-09-01 10:15 ` [PATCH v2 1/2] bus: ti-sysc: Add DRA7 SoC matching Anurag Dutta
2025-09-01 10:15 ` Anurag Dutta [this message]
2025-09-02 13:18 ` [PATCH v2 0/2] AM57 timer fixes Rob Herring (Arm)
2026-06-03 19:12 ` Jonathan Cormier
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=20250901101525.1090334-3-a-dutta@ti.com \
--to=a-dutta@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®