From: Matthias Kaehlcke <mka@chromium.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Andy Gross <andy.gross@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
girishm@codeaurora.org, dkota@codeaurora.org,
evgreen@chromium.org, swboyd@chromium.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
David Brown <david.brown@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] soc: qcom: geni: Don't ignore clk_round_rate() errors in geni_se_clk_tbl_get()
Date: Wed, 5 Sep 2018 16:37:57 -0700 [thread overview]
Message-ID: <20180905233757.GB22824@google.com> (raw)
In-Reply-To: <20180830183612.169572-1-dianders@chromium.org>
On Thu, Aug 30, 2018 at 11:36:11AM -0700, Douglas Anderson wrote:
> The function clk_round_rate() is defined to return a "long", not an
> "unsigned long". That's because it might return a negative error
> code. Change the call in geni_se_clk_tbl_get() to check for errors.
>
> NOTE: overall the idea that we should iterate over clk_round_rate() to
> try to reconstruct a table already present in the clock driver is
> questionable. Specifically:
> - This method relies on "clk_round_rate()" rounding up.
> - This method only works if the table is sorted and has no duplicates.
> ...this patch doesn't try to fix those problems, it just makes the
> error handling more correct.
>
> Fixes: eddac5af0654 ("soc: qcom: Add GENI based QUP Wrapper driver")
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
>
> drivers/soc/qcom/qcom-geni-se.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/qcom/qcom-geni-se.c b/drivers/soc/qcom/qcom-geni-se.c
> index feed3db21c10..1b19b8428c4a 100644
> --- a/drivers/soc/qcom/qcom-geni-se.c
> +++ b/drivers/soc/qcom/qcom-geni-se.c
> @@ -513,7 +513,7 @@ EXPORT_SYMBOL(geni_se_resources_on);
> */
> int geni_se_clk_tbl_get(struct geni_se *se, unsigned long **tbl)
> {
> - unsigned long freq = 0;
> + long freq = 0;
nit: Since you are already touching this you could also remove the
pointless initialization, 'freq' is always assigned before it is used.
> int i;
>
> if (se->clk_perf_tbl) {
> @@ -529,7 +529,7 @@ int geni_se_clk_tbl_get(struct geni_se *se, unsigned long **tbl)
>
> for (i = 0; i < MAX_CLK_PERF_LEVEL; i++) {
> freq = clk_round_rate(se->clk, freq + 1);
> - if (!freq || freq == se->clk_perf_tbl[i - 1])
> + if (freq <= 0 || freq == se->clk_perf_tbl[i - 1])
> break;
> se->clk_perf_tbl[i] = freq;
> }
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2018-09-05 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 18:36 [PATCH 1/2] soc: qcom: geni: Don't ignore clk_round_rate() errors in geni_se_clk_tbl_get() Douglas Anderson
2018-08-30 18:36 ` [PATCH 2/2] soc: qcom: geni: geni_se_clk_freq_match() should always accept multiples Douglas Anderson
2018-09-06 0:20 ` Matthias Kaehlcke
2018-09-06 16:33 ` Doug Anderson
2018-09-05 23:37 ` Matthias Kaehlcke [this message]
2018-09-06 16:33 ` [PATCH 1/2] soc: qcom: geni: Don't ignore clk_round_rate() errors in geni_se_clk_tbl_get() Doug Anderson
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=20180905233757.GB22824@google.com \
--to=mka@chromium.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=dianders@chromium.org \
--cc=dkota@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=girishm@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=swboyd@chromium.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).