From: Brian Masney <bmasney@redhat.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Maxime Ripard <mripard@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Abel Vesa <abelvesa@kernel.org>,
Hans de Goede <hansg@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: add new Kconfig to control default behavior of disabling unused clocks
Date: Tue, 17 Mar 2026 10:13:08 -0400 [thread overview]
Message-ID: <ablhdKJgEhU8KmtO@redhat.com> (raw)
In-Reply-To: <2dsd7hq4bn25dibqk62a7o56tt2tecf645tq3upccneq4hby67@cmjjc5d6ximt>
On Tue, Mar 17, 2026 at 03:21:17PM +0200, Abel Vesa wrote:
> The solution has been already discussed for a long time now and it is:
> drop the clk_ignore_unused late_initcall entirely and then make a
> generic sync_state callback that the clock providers can use (or they
> could implement one themselves). This way, until sync_state is reached
> for a specific clock provider driver, all unused clocks remain as is.
I'm willing to work on the sync state support once my clk scaling
series [1] lands upstream. I believe that Saravana posted a series
related to clk sync state, and I need to look at that.
FWIW, the only reason I posted this patch is because at the end of
Stephen's LPC talk I got the impression that this was also an acceptable
change. I'm fine with dropping this change.
[1] https://lore.kernel.org/linux-clk/20260313-clk-scaling-v6-0-ce89968c5247@redhat.com/
Brian
next prev parent reply other threads:[~2026-03-17 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 22:33 [PATCH] clk: add new Kconfig to control default behavior of disabling unused clocks Brian Masney
2026-03-17 7:30 ` Maxime Ripard
2026-03-17 11:53 ` Hans de Goede
2026-03-17 12:20 ` Brian Masney
2026-03-17 13:32 ` Maxime Ripard
2026-03-17 13:51 ` Abel Vesa
2026-03-17 14:02 ` Hans de Goede
2026-03-17 12:14 ` Abel Vesa
2026-03-17 12:16 ` Hans de Goede
2026-03-17 12:26 ` Brian Masney
2026-03-17 13:03 ` Abel Vesa
2026-03-17 13:18 ` Maxime Ripard
2026-03-17 13:22 ` Abel Vesa
2026-03-17 12:57 ` Abel Vesa
2026-03-17 13:15 ` Maxime Ripard
2026-03-17 13:21 ` Abel Vesa
2026-03-17 13:40 ` Maxime Ripard
2026-03-17 14:13 ` Brian Masney [this message]
2026-03-17 14:20 ` Abel Vesa
2026-03-17 15:00 ` Brian Masney
2026-03-17 15:14 ` Hans de Goede
2026-03-19 5:40 ` Jagadeesh Kona
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=ablhdKJgEhU8KmtO@redhat.com \
--to=bmasney@redhat.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=corbet@lwn.net \
--cc=hansg@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=saravanak@kernel.org \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.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