From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] clk: change clk_ops' ->determine_rate() prototype
Date: Tue, 7 Jul 2015 17:57:48 -0700 [thread overview]
Message-ID: <20150708005748.GG30412@codeaurora.org> (raw)
In-Reply-To: <1436294888-25752-1-git-send-email-boris.brezillon@free-electrons.com>
On 07/07, Boris Brezillon wrote:
> Clock rates are stored in an unsigned long field, but ->determine_rate()
> (which returns a rounded rate from a requested one) returns a long
> value (errors are reported using negative error codes), which can lead
> to long overflow if the clock rate exceed 2Ghz.
>
> Change ->determine_rate() prototype to return 0 or an error code, and pass
> a pointer to a clk_rate_request structure containing the expected target
> rate and the rate constraints imposed by clk users.
>
> The clk_rate_request structure might be extended in the future to contain
> other kind of constraints like the rounding policy, the maximum clock
> inaccuracy or other things that are not yet supported by the CCF
> (power consumption constraints ?).
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> CC: Jonathan Corbet <corbet@lwn.net>
> CC: Tony Lindgren <tony@atomide.com>
> CC: Ralf Baechle <ralf@linux-mips.org>
> CC: "Emilio L?pez" <emilio@elopez.com.ar>
> CC: Maxime Ripard <maxime.ripard@free-electrons.com>
> CC: Tero Kristo <t-kristo@ti.com>
> CC: Peter De Schrijver <pdeschrijver@nvidia.com>
> CC: Prashant Gaikwad <pgaikwad@nvidia.com>
> CC: Stephen Warren <swarren@wwwdotorg.org>
> CC: Thierry Reding <thierry.reding@gmail.com>
> CC: Alexandre Courbot <gnurou@gmail.com>
> CC: linux-doc at vger.kernel.org
> CC: linux-kernel at vger.kernel.org
> CC: linux-arm-kernel at lists.infradead.org
> CC: linux-omap at vger.kernel.org
> CC: linux-mips at linux-mips.org
> CC: linux-tegra at vger.kernel.org
>
> ---
I'll throw this patch into -next now to see if any other problems
shake out. I'm hoping we get some more acks though, so it'll be
on it's own branch and become immutable in a week or so. One
question below.
> diff --git a/drivers/clk/clk-composite.c b/drivers/clk/clk-composite.c
> index 616f5ae..9e69f34 100644
> --- a/drivers/clk/clk-composite.c
> +++ b/drivers/clk/clk-composite.c
> @@ -99,33 +99,33 @@ static long clk_composite_determine_rate(struct clk_hw *hw, unsigned long rate,
>
> parent_rate = __clk_get_rate(parent);
>
> - tmp_rate = rate_ops->round_rate(rate_hw, rate,
> + tmp_rate = rate_ops->round_rate(rate_hw, req->rate,
> &parent_rate);
> if (tmp_rate < 0)
> continue;
>
> - rate_diff = abs(rate - tmp_rate);
> + rate_diff = abs(req->rate - tmp_rate);
>
> - if (!rate_diff || !*best_parent_p
> + if (!rate_diff || !req->best_parent_hw
> || best_rate_diff > rate_diff) {
> - *best_parent_p = __clk_get_hw(parent);
> - *best_parent_rate = parent_rate;
> + req->best_parent_hw = __clk_get_hw(parent);
> + req->best_parent_rate = parent_rate;
> best_rate_diff = rate_diff;
> best_rate = tmp_rate;
> }
>
> if (!rate_diff)
> - return rate;
> + return 0;
> }
>
> - return best_rate;
> + req->rate = best_rate;
> + return 0;
> } else if (mux_hw && mux_ops && mux_ops->determine_rate) {
> __clk_hw_set_clk(mux_hw, hw);
> - return mux_ops->determine_rate(mux_hw, rate, min_rate,
> - max_rate, best_parent_rate,
> - best_parent_p);
> + return mux_ops->determine_rate(mux_hw, req);
> } else {
> pr_err("clk: clk_composite_determine_rate function called, but no mux or rate callback set!\n");
> + req->rate = 0;
> return 0;
Shouldn't this return an error now? And then assigning req->rate
wouldn't be necessary. Sorry I must have missed this last round.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-07-08 0:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 18:48 [PATCH v5] clk: change clk_ops' ->determine_rate() prototype Boris Brezillon
2015-07-08 0:57 ` Stephen Boyd [this message]
2015-07-08 9:00 ` Boris Brezillon
2015-07-08 18:07 ` Stephen Boyd
2015-07-09 20:39 ` Boris Brezillon
2015-07-13 23:02 ` Stephen Boyd
2015-07-14 10:47 ` Boris Brezillon
2015-07-13 9:01 ` Tero Kristo
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=20150708005748.GG30412@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).