diff options
author | Maxime Ripard <maxime@cerno.tech> | 2022-02-25 15:35:28 +0100 |
---|---|---|
committer | Stephen Boyd <sboyd@kernel.org> | 2022-03-12 04:15:02 +0100 |
commit | c80ac50cbb378a4029129a596251747386e3c8e9 (patch) | |
tree | 38c34702f1216c361b496d445793525abd71bce5 /scripts | |
parent | clk: Use clamp instead of open-coding our own (diff) | |
download | linux-c80ac50cbb378a4029129a596251747386e3c8e9.tar.xz linux-c80ac50cbb378a4029129a596251747386e3c8e9.zip |
clk: Always set the rate on clk_set_range_rate
When we change a clock minimum or maximum using clk_set_rate_range(),
clk_set_min_rate() or clk_set_max_rate(), the current code will only
trigger a new rate change if the rate is outside of the new boundaries.
However, a clock driver might want to always keep the clock rate to
one of its boundary, for example the minimum to keep the power
consumption as low as possible.
Since they don't always get called though, clock providers don't have the
opportunity to implement this behaviour.
Let's trigger a clk_set_rate() on the previous requested rate every time
clk_set_rate_range() is called. That way, providers that care about the
new boundaries have a chance to adjust the rate, while providers that
don't care about those new boundaries will return the same rate than
before, which will be ignored by clk_set_rate() and won't result in a
new rate change.
Suggested-by: Stephen Boyd <sboyd@kernel.org>
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Link: https://lore.kernel.org/r/20220225143534.405820-7-maxime@cerno.tech
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions