From: Benjamin Bara <bbara93@gmail.com>
To: Maxime Ripard <mripard@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Frank Oltmanns <frank@oltmanns.dev>,
Adam Ford <aford173@gmail.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Bara <benjamin.bara@skidata.com>
Subject: [PATCH RFC 2/4] clk: reset new_rates for next run
Date: Mon, 02 Oct 2023 11:23:33 +0200 [thread overview]
Message-ID: <20231002-ccf-set-multiple-v1-2-2df5e9eb3738@skidata.com> (raw)
In-Reply-To: <20231002-ccf-set-multiple-v1-0-2df5e9eb3738@skidata.com>
From: Benjamin Bara <benjamin.bara@skidata.com>
During clk_set_rate(), new_rates are calculated for all clocks that are
part of the changed clock subtree. These values are temporary and only
valid during the current call. Therefore, reset them to prepare a clean
state for the next call.
Signed-off-by: Benjamin Bara <benjamin.bara@skidata.com>
---
drivers/clk/clk.c | 25 ++++++++++++++++++++++---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 82f954121e4d..5f183cba300c 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -2163,6 +2163,17 @@ static void clk_calc_subtree(struct clk_core *core, unsigned long new_rate,
}
}
+static void clk_reset_temp_rates(struct clk_core *core)
+{
+ struct clk_core *child;
+
+ core->new_rate = CLK_RATE_UNSET;
+
+ hlist_for_each_entry(child, &core->children, child_node) {
+ clk_reset_temp_rates(child);
+ }
+}
+
/*
* calculate the new rates returning the topmost clock that has to be
* changed.
@@ -2244,7 +2255,9 @@ static struct clk_core *clk_calc_new_rates(struct clk_core *core,
top = clk_calc_new_rates(parent, best_parent_rate);
out:
- clk_calc_subtree(core, new_rate, parent, p_index);
+ /* only set new_rates if we found a valid change path */
+ if (top)
+ clk_calc_subtree(core, new_rate, parent, p_index);
return top;
}
@@ -2347,6 +2360,7 @@ static void clk_change_rate(struct clk_core *core)
trace_clk_set_rate_complete(core, core->new_rate);
+ core->new_rate = CLK_RATE_UNSET;
core->rate = clk_recalc(core, best_parent_rate);
if (core->flags & CLK_SET_RATE_UNGATE) {
@@ -2361,7 +2375,7 @@ static void clk_change_rate(struct clk_core *core)
__clk_notify(core, POST_RATE_CHANGE, old_rate, core->rate);
if (core->flags & CLK_RECALC_NEW_RATES)
- (void)clk_calc_new_rates(core, core->new_rate);
+ (void)clk_calc_new_rates(core, core->rate);
/*
* Use safe iteration, as change_rate can actually swap parents
@@ -2437,8 +2451,10 @@ static int clk_core_set_rate_nolock(struct clk_core *core,
return -EINVAL;
ret = clk_pm_runtime_get(core);
- if (ret)
+ if (ret) {
+ clk_reset_temp_rates(top);
return ret;
+ }
/* notify that we are about to change rates */
fail_clk = clk_propagate_rate_change(top, PRE_RATE_CHANGE);
@@ -2454,6 +2470,8 @@ static int clk_core_set_rate_nolock(struct clk_core *core,
clk_change_rate(top);
err:
+ clk_reset_temp_rates(top);
+
clk_pm_runtime_put(core);
return ret;
@@ -3900,6 +3918,7 @@ static int __clk_core_init(struct clk_core *core)
rate = 0;
core->rate = rate;
core->req_rate = CLK_RATE_UNSET;
+ core->new_rate = CLK_RATE_UNSET;
/*
* Enable CLK_IS_CRITICAL clocks so newly added critical clocks
--
2.34.1
next prev parent reply other threads:[~2023-10-02 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 9:23 [PATCH RFC 0/4] clk: re-set required rates during clk_set_rate() Benjamin Bara
2023-10-02 9:23 ` [PATCH RFC 1/4] clk: only set req_rate if it is set by consumer Benjamin Bara
2023-10-02 9:23 ` Benjamin Bara [this message]
2023-10-02 9:23 ` [PATCH RFC 3/4] clk: introduce req_rate_tmp Benjamin Bara
2023-10-02 9:23 ` [PATCH RFC 4/4] clk: consider rates when calculating subtree Benjamin Bara
2023-10-02 12:26 ` [PATCH RFC 0/4] clk: re-set required rates during clk_set_rate() Maxime Ripard
2023-10-03 7:44 ` Benjamin Bara
2023-10-03 11:33 ` Maxime Ripard
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=20231002-ccf-set-multiple-v1-2-2df5e9eb3738@skidata.com \
--to=bbara93@gmail.com \
--cc=aford173@gmail.com \
--cc=benjamin.bara@skidata.com \
--cc=frank@oltmanns.dev \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@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