All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Quanyang Wang <quanyang.wang@windriver.com>,
	linux-clk@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@xilinx.com>,
	Rajan Vaja <rajan.vaja@xilinx.com>,
	Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH] clk: zynqmp: pll: Fix divider calculation to avoid out-of-range rate
Date: Fri, 30 Sep 2022 17:05:01 -0700	[thread overview]
Message-ID: <20221001000503.23268C433D6@smtp.kernel.org> (raw)
In-Reply-To: <11481209-7c8f-7543-1e04-5723ffc2ccd4@windriver.com>

+Maxime

Quoting Quanyang Wang (2022-09-28 18:05:10)
> Hi Laurent,
> 
> I have sent a patch as below to fix this issue which set rate failed and 
> it's in linux-next repo now.
> 
> https://lore.kernel.org/linux-arm-kernel/20220826142030.213805-1-quanyang.wang@windriver.com/T/
> 
> 
> As for the frequency gap between the requested rate and the actual, it's 
> because of the commit:
> 
> commit 948fb0969eae8
> Author: Maxime Ripard <maxime@cerno.tech>
> Date:   Fri Feb 25 15:35:26 2022 +0100
> 
>      clk: Always clamp the rounded rate
> 
> And I haven't figured out how to fix it.
> 

Maxime has some more patches to fix this and they're in linux-next.
Maybe those fix this problem?

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Quanyang Wang <quanyang.wang@windriver.com>,
	linux-clk@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@xilinx.com>,
	Rajan Vaja <rajan.vaja@xilinx.com>,
	Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH] clk: zynqmp: pll: Fix divider calculation to avoid out-of-range rate
Date: Fri, 30 Sep 2022 17:05:01 -0700	[thread overview]
Message-ID: <20221001000503.23268C433D6@smtp.kernel.org> (raw)
In-Reply-To: <11481209-7c8f-7543-1e04-5723ffc2ccd4@windriver.com>

+Maxime

Quoting Quanyang Wang (2022-09-28 18:05:10)
> Hi Laurent,
> 
> I have sent a patch as below to fix this issue which set rate failed and 
> it's in linux-next repo now.
> 
> https://lore.kernel.org/linux-arm-kernel/20220826142030.213805-1-quanyang.wang@windriver.com/T/
> 
> 
> As for the frequency gap between the requested rate and the actual, it's 
> because of the commit:
> 
> commit 948fb0969eae8
> Author: Maxime Ripard <maxime@cerno.tech>
> Date:   Fri Feb 25 15:35:26 2022 +0100
> 
>      clk: Always clamp the rounded rate
> 
> And I haven't figured out how to fix it.
> 

Maxime has some more patches to fix this and they're in linux-next.
Maybe those fix this problem?

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

  reply	other threads:[~2022-10-01  0:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 20:16 [PATCH] clk: zynqmp: pll: Fix divider calculation to avoid out-of-range rate Laurent Pinchart
2022-09-28 20:16 ` Laurent Pinchart
2022-09-29  1:05 ` Quanyang Wang
2022-09-29  1:05   ` Quanyang Wang
2022-10-01  0:05   ` Stephen Boyd [this message]
2022-10-01  0:05     ` Stephen Boyd
2022-10-01 10:40     ` Maxime Ripard
2022-10-01 10:40       ` Maxime Ripard
2022-10-02  2:17       ` Quanyang Wang
2022-10-02  2:17         ` Quanyang Wang
2022-10-03  0:06         ` Laurent Pinchart
2022-10-03  0:06           ` Laurent Pinchart
2022-10-10  8:49         ` Maxime Ripard
2022-10-10  8:49           ` Maxime Ripard
2022-10-10 12:12           ` Quanyang Wang
2022-10-10 12:12             ` Quanyang Wang
2022-10-10 12:49             ` Maxime Ripard
2022-10-10 12:49               ` Maxime Ripard
2022-10-11  3:11               ` Quanyang Wang
2022-10-11  3:11                 ` Quanyang Wang
2022-10-11 12:27                 ` Maxime Ripard
2022-10-11 12:27                   ` Maxime Ripard
2022-10-02 23:45   ` Laurent Pinchart
2022-10-02 23:45     ` Laurent Pinchart

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=20221001000503.23268C433D6@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=michal.simek@xilinx.com \
    --cc=quanyang.wang@windriver.com \
    --cc=rajan.vaja@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.