[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <152123942933.242365.9527424154926596361@swboyd.mtv.corp.google.com>
Date: Fri, 16 Mar 2018 15:30:29 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Sudeep Holla <sudeep.holla@....com>,
open list <linux-kernel@...r.kernel.org>
Cc: Liviu Dudau <liviu.dudau@....com>,
Sudeep Holla <sudeep.holla@....com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>, linux-clk@...r.kernel.org
Subject: Re: [PATCH] clk: versatile: add min/max rate boundaries for vexpress osc
clock
Quoting Sudeep Holla (2018-02-19 07:55:37)
> On Fri, Nov 10, 2017 at 4:06 PM, Sudeep Holla <sudeep.holla@....com> wrote:
> > Clock framework has a provider API(clk_hw_set_rate_range) to set the
> > min/max rate of a clock. Use the same to set the boundaries for the
> > vexpress osc clock.
> >
> > Cc: Michael Turquette <mturquette@...libre.com>
> > Cc: Stephen Boyd <sboyd@...eaurora.org>
> > Cc: linux-clk@...r.kernel.org
> > Signed-off-by: Sudeep Holla <sudeep.holla@....com>
> > ---
> > drivers/clk/versatile/clk-vexpress-osc.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > Hi Stephen,
> >
> > Just a quick question, does the clk core ensure the round_rate request
> > to the clock provider is within this bounds ? A quick grep suggests it's
> > used after the call to round_rate in clk_calc_new_rates. I can't recall
> > the details from when you introduced clk_hw_set_rate_range.
> >
>
> Ping !
Pong !
Powered by blists - more mailing lists