mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: adrian.ho.yin.ng@altera.com,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] clk: socfpga: convert clock managers to CLK_OF_DECLARE()
Date: Fri, 18 Sep 2026 11:56:54 -0500	[thread overview]
Message-ID: <bbfa8707-7362-44fb-bd8e-5f948be02e8f@kernel.org> (raw)
In-Reply-To: <cover.1789096458.git.adrian.ho.yin.ng@altera.com>



On 9/11/26 02:01, adrian.ho.yin.ng@altera.com wrote:
> From: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>
> 
> The SoCFPGA Stratix10, Agilex, and Agilex5 clock managers are currently
> registered as platform drivers via core_initcall(). That is too late for
> early OF clock consumers: TIMER_OF_DECLARE callbacks run from time_init()
> before those drivers probe, and the DW APB timer cannot defer, so
> clk_get() fails and the timer is never brought up.
> 
> As discussed on the list [1], convert these drivers to CLK_OF_DECLARE()
> so the providers are registered from of_clk_init() and clocks are
> available before platform devices probe.
> 
> This series applies the same conversion to Agilex (including eASIC N5X),
> Agilex5, and Stratix10.
> 
> Boot-tested on Agilex7 (agilex7dksiagf014eb): dw_apb_timer registers as
> clocksource early, with no clk_get() failures.
> 
Please provide these details in each of the commits.

Thanks,
Dinh

      parent reply	other threads:[~2026-09-18 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  7:01 adrian.ho.yin.ng
2026-09-11  7:01 ` [PATCH 1/3] clk: socfpga: agilex: convert " adrian.ho.yin.ng
2026-09-18 22:42   ` Brian Masney
2026-09-11  7:01 ` [PATCH 2/3] clk: socfpga: agilex5: " adrian.ho.yin.ng
2026-09-11  7:01 ` [PATCH 3/3] clk: socfpga: stratix10: " adrian.ho.yin.ng
2026-09-18 16:56 ` Dinh Nguyen [this message]

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=bbfa8707-7362-44fb-bd8e-5f948be02e8f@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.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

all inboxes | Powered by JetHome®