linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Michał Mirosław <mirq-linux@rere.qmqm.pl>,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] clk: at91: optimize clk_round_rate() for AUDIO_PLL
Date: Mon, 17 Dec 2018 15:22:50 -0800	[thread overview]
Message-ID: <154508897026.19322.14961293619238289668@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <772b3869cc992d894d8c1b4296f21100bcbed30d.1545075103.git.mirq-linux@rere.qmqm.pl>

Quoting Michał Mirosław (2018-12-17 11:37:05)
> This makes for 3 clk_round_rate() calls instead of 64 of them on
> SAMA5D2-based board when searching for 12.288MHz clock.

Ok, but is that better? Worse? Can you more clearly describe what you're
doing here? And it's not breaking some other corner case?

> 
> Signed-off-by: Micha\u0142 Miros\u0142aw <mirq-linux@rere.qmqm.pl>

This got all broken. Something on your end?

> ---
>  drivers/clk/at91/clk-audio-pll.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/at91/clk-audio-pll.c b/drivers/clk/at91/clk-audio-pll.c
> index 36d77146a3bd..3a358282784e 100644
> --- a/drivers/clk/at91/clk-audio-pll.c
> +++ b/drivers/clk/at91/clk-audio-pll.c
> @@ -340,7 +340,11 @@ static long clk_audio_pll_pmc_round_rate(struct clk_hw *hw, unsigned long rate,
>         pr_debug("A PLL/PMC: %s, rate = %lu (parent_rate = %lu)\n", __func__,
>                  rate, *parent_rate);
>  
> -       for (div = 1; div <= AUDIO_PLL_QDPMC_MAX; div++) {
> +       if (!rate)
> +               return 0;
> +
> +       best_parent_rate = clk_round_rate(pclk->clk, 1);
> +       for (div = max(best_parent_rate / rate, 1ul); div <= AUDIO_PLL_QDPMC_MAX; div++) {

Nitpick: Style is usually 1UL instead of lowercase 1ul.

>                 best_parent_rate = clk_round_rate(pclk->clk, rate * div);
>                 tmp_rate = best_parent_rate / div;
>                 tmp_diff = abs(rate - tmp_rate);
> @@ -350,6 +354,8 @@ static long clk_audio_pll_pmc_round_rate(struct clk_hw *hw, unsigned long rate,
>                         best_rate = tmp_rate;
>                         best_diff = tmp_diff;
>                         tmp_qd = div;
> +                       if (!best_diff)
> +                               break;  /* got exact match */

Seems sensible to break immediately if exact match is found.
`

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-17 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 19:37 [PATCH] clk: at91: optimize clk_round_rate() for AUDIO_PLL Michał Mirosław
2018-12-17 23:22 ` Stephen Boyd [this message]
2018-12-18 10:55   ` Michał Mirosław
2018-12-18 11:18   ` Uwe Kleine-König

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=154508897026.19322.14961293619238289668@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --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 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).