From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
linux-clk@vger.kernel.org,
"Grégory Clement" <gregory.clement@bootlin.com>,
"Tero Kristo" <kristo@kernel.org>
Subject: Re: Issue with Clock Parent Assignment on AM335x SoC (Watchdog Timer)
Date: Thu, 30 Apr 2026 06:40:34 +0300 [thread overview]
Message-ID: <20260430034034.GW39595@atomide.com> (raw)
In-Reply-To: <177742766345.5403.3603095308836655844@localhost.localdomain>
* Stephen Boyd <sboyd@kernel.org> [260429 03:46]:
> +Tony (author of commit)
>
> Quoting Mathieu Dubois-Briand (2026-04-28 05:03:16)
> > Hi,
> >
> > I believe I’ve identified an issue with clock management on the AM335x
> > SoC and possibly other TI SoC. It can be seen while using the SoC
> > watchdog timer, but I suspect other clocks or modules might be impacted.
> >
> > While I partially understand the issue, I struggle to find a correct
> > solution. I will describe my findings below.
> >
> > First, here is a quick way to reproduce it.
> > - Hardware: Beagle Bone Black.
> > - Linux kernel version: v7.1-rc1 (or anything after 5.19).
> > - Configuration: omap2plus_defconfig + CONFIG_OMAP_WATCHDOG=y
> > - In the bootloader, I select the 32KHz clock derived from the 24MHz one
> > as the watchdog clock source. This is controlled by bit 1 of
> > CLKSEL_WDT1_CLK.
> > This is probably the point that differs from most use cases, and why
> > it hasn't been observed before. On my final setup, I do not control
> > the bootloader and so cannot change this value.
> > In u-boot, this is: mw.l 0x44e00538 1
> > - Once the kernel is booted, I open the watchdog device node. I'm using
> > busybox "watchdog" command, but a simple "cat" will trigger the same
> > error.
> > watchdog /dev/watchdog0
> > - This will result in the bus clock failing to be enabled and a failure
> > to access the watchdog module:
> > [ 11.677752] l4-wkup-clkctrl:00d4:0: failed to enable
> > [ 11.686079] Unhandled fault: external abort on non-linefetch (0x1028) at 0xf9e35034
> > I'm attaching the full trace at the very end of my email.
> >
> > So, I tried to dig a bit into this issue and the reason why the
> > l4-wkup-clkctrl:00d4:0 clock can't be enabled.
Just a quick guess.. You can use assigned-clocks in the dts file to
configure how your board is wired up.
Please check the system timers configuration too, sounds like timers may
not be configured properly either. Some timer examples can be seen with:
$ git grep -A10 "Preferred " arch/arm/boot/dts/
Regards,
Tony
next prev parent reply other threads:[~2026-04-30 3:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 12:03 Issue with Clock Parent Assignment on AM335x SoC (Watchdog Timer) Mathieu Dubois-Briand
2026-04-29 1:54 ` Stephen Boyd
2026-04-30 3:40 ` Tony Lindgren [this message]
2026-04-30 12:29 ` Mathieu Dubois-Briand
2026-05-01 4:04 ` Tony Lindgren
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=20260430034034.GW39595@atomide.com \
--to=tony@atomide.com \
--cc=gregory.clement@bootlin.com \
--cc=kristo@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=sboyd@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