mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: perachet7@gmail.com
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/1] rk3188: don't set same clk rate twice
Date: Fri, 9 Nov 2018 08:18:06 +0100	[thread overview]
Message-ID: <20181109071806.6l4us6ahcn2vvwwg@pengutronix.de> (raw)
In-Reply-To: <2337209.lTZxGkHaYR@think-future.de>

Hi,

On Thu, Nov 08, 2018 at 03:34:29PM +0100, perachet7@gmail.com wrote:
> Hi,
> 
> We found setting a clock rate which has already been set, rk3188 (radxa rock 
> pro) bails out. This is a quick fix only. Underlying situation not (yet) 
> investigated: why it is even trying to set it to the same rate again. It 
> remains to state that some but not all rrpro boards exhibit this behaviour, no 
> other rk3188 boards have been tested.
> 
> Signed-off-by: P. Rachet <perachet7@gmail.com>
> ---
>  drivers/clk/rockchip/clk-pll.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/clk/rockchip/clk-pll.c b/drivers/clk/rockchip/clk-pll.c
> index f0dc12091..690da4afb 100644
> --- a/drivers/clk/rockchip/clk-pll.c
> +++ b/drivers/clk/rockchip/clk-pll.c
> @@ -164,6 +164,11 @@ static int rockchip_rk3066_pll_set_rate(struct clk *hw, 
> unsigned long drate,
>   int cur_parent;
>   int ret;
> 
> +  if (old_rate == drate) {
> +    pr_debug("%s: not changing rate, old == new rate (clk/old/new/parent): 
> %s/%lu/%lu/%lu\n", __func__, __clk_get_name(hw), old_rate, drate, prate);
> +    return 0;
> +  }
> +

The patch is whitespace damaged. I applied it manually this time, but
please consider using git-send-email next time. It just does it right™

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2018-11-09  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 14:34 perachet7
2018-11-09  7:18 ` Sascha Hauer [this message]

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=20181109071806.6l4us6ahcn2vvwwg@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=perachet7@gmail.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