From: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>
To: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>
Subject: [PATCH 0/2] arm64: dts: intel: fix dw-apb-timer clock initialisation on Agilex and Agilex5
Date: Tue, 26 May 2026 17:00:50 +0800 [thread overview]
Message-ID: <cover.1779785788.git.adrian.ho.yin.ng@altera.com> (raw)
The DesignWare APB timers on Intel Agilex and Agilex5 SoCs fail to
initialise because their clock managers are platform drivers registered
at core_initcall, which runs after time_init() where TIMER_OF_DECLARE
callbacks fire. With clocks/clock-names in the DTS, the timer driver
calls clk_get() at a point when the clock provider is not yet
registered, causing the timers to never come up.
Replace the clocks/clock-names reference in both DTSIs with a static
clock-frequency of 100 MHz, which is the L4_SP clock rate configured
by the bootloader. The dw-apb-timer binding explicitly supports this
as an alternative when the clock framework is unavailable at probe time.
Adrian Ng Ho Yin (2):
arm64: dts: socfpga: agilex5: replace clocks reference with
clock-frequency for dw-apb-timer
arm64: dts: socfpga: agilex: replace clocks reference with
clock-frequency for dw-apb-timer
arch/arm64/boot/dts/intel/socfpga_agilex.dtsi | 12 ++++--------
arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 12 ++++--------
2 files changed, 8 insertions(+), 16 deletions(-)
--
2.49.GIT
next reply other threads:[~2026-05-26 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:00 Adrian Ng Ho Yin [this message]
2026-05-26 9:00 ` [PATCH 1/2] arm64: dts: socfpga: agilex5: replace clocks reference with clock-frequency for dw-apb-timer Adrian Ng Ho Yin
2026-05-26 9:00 ` [PATCH 2/2] arm64: dts: socfpga: agilex: " Adrian Ng Ho Yin
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=cover.1779785788.git.adrian.ho.yin.ng@altera.com \
--to=adrian.ho.yin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®