From: Stephen Boyd <sboyd@kernel.org>
To: Dr. David Alan Gilbert <linux@treblig.org>, mturquette@baylibre.com
Cc: linux-clk@vger.kernel.org
Subject: Re: Of clk_hw_unregister_fractional_divider
Date: Wed, 09 Oct 2024 13:29:54 -0700 [thread overview]
Message-ID: <27ac7ba804d260ca9e1397a17b9e8696.sboyd@kernel.org> (raw)
In-Reply-To: <ZwXUQOr-afniO-2u@gallifrey>
Quoting Dr. David Alan Gilbert (2024-10-08 17:54:24)
> Hi,
> One of my scripts noticed that clk_hw_unregister_fractional_divider
> was unused and I was thinking of dead coding it, but thought it worth
> asking whether it's actually a missing call to it.
>
> It was added in 2016 by:
>
> commit 39b44cff4ad4af6d7abd9dd2acb288b005c26503
> Author: Stephen Boyd <sboyd@codeaurora.org>
> Date: Sun Feb 7 00:15:09 2016 -0800
>
> clk: fractional-divider: Add hw based registration APIs
>
> and I can see clk_hw_register_fractional_divider is called from
> clk_register_fractional_divider.
>
> Is that just consequence of them being system devices that never
> get unregistered or something else?
>
I don't know what you mean by system devices.
The clk_hw prefixed functions and clk_hw based APIs should be used
instead of struct clk APIs for clk providers in general. I'd accept a
patch that migrates the two calls to clk_register_fractional_divider()
with a call to clk_hw_register_fractional_divider() instead. If that's
done we can remove clk_register_fractional_divider(), which is the
overall plan but nobody got around to it so far.
next prev parent reply other threads:[~2024-10-09 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 0:54 Of clk_hw_unregister_fractional_divider Dr. David Alan Gilbert
2024-10-09 20:29 ` Stephen Boyd [this message]
2024-10-10 0:58 ` Dr. David Alan Gilbert
2024-10-10 1:23 ` Stephen Boyd
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=27ac7ba804d260ca9e1397a17b9e8696.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mturquette@baylibre.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.