mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Brian Masney <bmasney@redhat.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Brian Masney <bmasney+clk@redhat.com>,
	Jerome Brunet <jbrunet+clk@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: disable unused clocks registered after boot
Date: Thu, 17 Sep 2026 19:23:36 +0200	[thread overview]
Message-ID: <2026091717233613a5b6a3@mail.local> (raw)
In-Reply-To: <aqwO5sAN9qbvK8LF@redhat.com>

Hello,

On 17/09/2026 12:01:42-0400, Brian Masney wrote:
> Hi Alexandre,
> 
> On Thu, Sep 17, 2026 at 04:40:10PM +0200, alexandre.belloni@bootlin.com wrote:
> > From: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > 
> > clk_disable_unused() only runs once as a late_initcall, so clocks
> > registered afterwards by loading a module are never checked and may be left
> > running needlessly.
> > 
> > So record when clk_disable_unused has run and afterwards, schedule a
> > delayed work to run the scan when new clocks are registered.
> > 
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> 
> We're actually in the process of redoing the way clk_disable_unused is
> handled. I posted a series to add sync_state support to the clk
> framework:
> 
> https://lore.kernel.org/linux-clk/20260626-clk-sync-state-v1-0-4156d8196dc8@redhat.com/
> 
> Will you be at Linux Plumbers in Prague in 2.5 weeks? If so, come to
> this talk where we will talk about the clk subsystem.
> 
>     Evolving support for sync_state to subsystems beyond genpd 
>     https://lpc.events/event/20/contributions/2504/
> 

I will be at plumbers and I'll try to attend, thanks!

For reference, this is the reason for the patch:
https://lore.kernel.org/all/2ce03d3b4cd9cce8e32fe1fe1ffbea5760bf9ef3.camel@siemens.com/

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-09-17 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 14:40 alexandre.belloni
2026-09-17 16:01 ` Brian Masney
2026-09-17 17:23   ` Alexandre Belloni [this message]
2026-09-17 17:36     ` Brian Masney

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=2026091717233613a5b6a3@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=bmasney+clk@redhat.com \
    --cc=bmasney@redhat.com \
    --cc=jbrunet+clk@baylibre.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®