linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Emilio Lopez <emilio@elopez.com.ar>, Chen-Yu Tsai <wens@csie.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: sunxi: Accept a greater rate when setting a parent clock
Date: Tue, 29 Mar 2016 11:38:27 +0200	[thread overview]
Message-ID: <20160329093827.GH30977@lukather> (raw)
In-Reply-To: <20160321092549.4e6245e4f02839e29aeb86a9@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]

Hi,

On Mon, Mar 21, 2016 at 09:25:49AM +0100, Jean-Francois Moine wrote:
> On Mon, 21 Mar 2016 08:25:46 +0100
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> 
> > > -	/* find the parent that can help provide the fastest rate <= rate */
> > > +	/* find the parent that can help provide the fastest rate */
> > >  	num_parents = clk_hw_get_num_parents(hw);
> > >  	for (i = 0; i < num_parents; i++) {
> > >  		parent = clk_hw_get_parent_by_index(hw, i);
> > > @@ -100,7 +100,7 @@ static int clk_factors_determine_rate(struct clk_hw *hw,
> > >  		child_rate = clk_factors_round_rate(hw, req->rate,
> > >  						    &parent_rate);
> > >  
> > > -		if (child_rate <= req->rate && child_rate > best_child_rate) {
> > > +		if (child_rate > best_child_rate) {
> > 
> > I'm not sure this would work, since you'll end up picking the fastest
> > rate without considering whether it is the closest or not.
> > 
> > I guess what you want here is using the absolute difference between
> > the requested rate and the rate you're evaluating.
> > 
> > That being said, we had a similar discussion for SPI around a month
> > ago where we wanted a rate strictly lower than the requested one. I
> > guess it's time to add a flag to tell how you want to round.
> 
> You are right, I just removed half of the constraint, but I still wonder
> why does this sequence introduced by the commit 862b728387aef3a37
> (clk: sunxi: factors: automatic reparenting support) do
> 	"provide the fastest rate <= rate"
> instead of
> 	"provide the closest rate" ?

I guess it's a confusing wording, in this case where you try to have
the closest rate but below the requested rate, what you want is
actually the fastest rate that doesn't trip above the requested rate,
hence the comment I guess.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-29  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160310081658.B749246B@mail.free-electrons.com>
2016-03-21  7:25 ` [PATCH] clk: sunxi: Accept a greater rate when setting a parent clock Maxime Ripard
2016-03-21  8:25   ` Jean-Francois Moine
2016-03-29  9:38     ` Maxime Ripard [this message]
2016-03-29 10:08       ` Jean-Francois Moine
2016-03-30 20:49     ` Emilio López
2016-04-14 17:24       ` Maxime Ripard
2016-04-14 18:14         ` Jean-Francois Moine
2016-04-14 19:31           ` Maxime Ripard
     [not found] <E1advmk-0004Nt-Ba@bombadil.infradead.org>
2016-03-18  7:47 ` Jean-Francois Moine
2016-03-10  7:15 Jean-Francois Moine

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=20160329093827.GH30977@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=emilio@elopez.com.ar \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=sboyd@codeaurora.org \
    --cc=wens@csie.org \
    /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).