From: Stephen Boyd <sboyd@codeaurora.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yoshihiro Kaneko <ykaneko0929@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] clk: renesas: rcar-gen3: Add Z clock divider support
Date: Fri, 21 Apr 2017 18:27:36 -0700 [thread overview]
Message-ID: <20170422012736.GW7065@codeaurora.org> (raw)
In-Reply-To: <CAMuHMdWfouuGZqPGV7_-cXUmYe-SXd9popja8T43V5hPP+DQQw@mail.gmail.com>
On 04/21, Geert Uytterhoeven wrote:
>
> > --- a/drivers/clk/renesas/rcar-gen3-cpg.c
> > +++ b/drivers/clk/renesas/rcar-gen3-cpg.c
>
> > +static unsigned long cpg_z_clk_recalc_rate(struct clk_hw *hw,
> > + unsigned long parent_rate)
> > +{
> > + struct cpg_z_clk *zclk = to_z_clk(hw);
> > + unsigned int mult;
> > + unsigned int val;
> > + unsigned long rate;
> > +
> > + val = (clk_readl(zclk->reg) & CPG_FRQCRC_ZFC_MASK)
> > + >> CPG_FRQCRC_ZFC_SHIFT;
> > + mult = 32 - val;
> > +
> > + rate = div_u64((u64)parent_rate * mult + 16, 32);
> > + /* Round to closest value at 100MHz unit */
> > + rate = 100000000*DIV_ROUND_CLOSEST(rate, 100000000);
>
> Mike, Stephen: what's your opinion about such rounding tricks?
>
What's wrong with the true rate? I'd prefer we calculate the true
rate unless there's some reason. Typically that's what a comment
is for, not to explain what the code is doing which is usually
self evident from reading it.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-04-22 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 17:46 [PATCH] clk: renesas: rcar-gen3: Add Z clock divider support Yoshihiro Kaneko
2017-04-21 13:59 ` Geert Uytterhoeven
2017-04-22 1:27 ` Stephen Boyd [this message]
2017-04-23 20:20 ` Geert Uytterhoeven
2017-04-24 8:03 ` Peter De Schrijver
2017-04-24 8:09 ` Geert Uytterhoeven
2017-04-25 10:18 ` Peter De Schrijver
2017-04-25 10:28 ` Geert Uytterhoeven
2017-04-25 11:02 ` Peter De Schrijver
2017-04-25 11:39 ` Geert Uytterhoeven
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=20170422012736.GW7065@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=ykaneko0929@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;
as well as URLs for NNTP newsgroup(s).