[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220517071440.DAC76C385B8@smtp.kernel.org>
Date: Tue, 17 May 2022 00:14:38 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Codrin.Ciubotariu@...rochip.com,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: mturquette@...libre.com, Nicolas.Ferre@...rochip.com,
alexandre.belloni@...tlin.com, Claudiu.Beznea@...rochip.com
Subject: Re: [PATCH] clk: at91: generated: consider range when calculating best rate
Quoting Codrin.Ciubotariu@...rochip.com (2022-04-26 00:24:15)
> On 22.04.2022 04:12, Stephen Boyd wrote:
> > Quoting Codrin Ciubotariu (2022-04-13 00:13:18)
> >> clk_generated_best_diff() helps in finding the parent and the divisor to
> >> compute a rate closest to the required one. However, it doesn't take into
> >> account the request's range for the new rate. Make sure the new rate
> >> is within the required range.
> >>
> >> Fixes: 8a8f4bf0c480 ("clk: at91: clk-generated: create function to find best_diff")
> >> Signed-off-by: Codrin Ciubotariu <codrin.ciubotariu@...rochip.com>
> >> ---
> >
> > Is this fixing anything real or it's just a thing that you noticed and
> > sent a patch to fix?
>
> It fixes the clk_set_min/max_rate() calls to a generated clock. Do you
> want me to add this fact in the commit description?
>
I wanted to know if there are clk_set_min/max_rate() calls on this clk.
Are there?
Powered by blists - more mailing lists