From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] ARC: clk: introduce HSDKv1 pll driver
Date: Wed, 9 Aug 2017 16:43:49 +0000 [thread overview]
Message-ID: <1502297028.2586.4.camel@synopsys.com> (raw)
In-Reply-To: <20170804015351.GW2146@codeaurora.org>
Hi Stephen,?
thanks for respond, my comments are inlined below.
On Thu, 2017-08-03@18:53 -0700, Stephen Boyd wrote:
> On 07/14, Eugeniy Paltsev wrote:
> [...]
> > + dev_dbg(clk->dev, "write configurarion: 0x%x", val);
>?
> Or just use %#x to add the 0x part.
Thanks, I don't know about this option.
>?
> [...]
>
> > + /* input divider = reg.idiv + 1 */
> > + idiv = 1 + ((val & CGU_PLL_CTRL_IDIV_MASK) >>
> > CGU_PLL_CTRL_IDIV_SHIFT);
> > + /* fb divider = 2*(reg.fbdiv + 1) */
> > + fbdiv = 2 * (1 + ((val & CGU_PLL_CTRL_FBDIV_MASK) >>
> > CGU_PLL_CTRL_FBDIV_SHIFT));
> > + /* output divider = 2^(reg.odiv) */
> > + odiv = 1 << ((val & CGU_PLL_CTRL_ODIV_MASK) >>
> > CGU_PLL_CTRL_ODIV_SHIFT);
>
> Maybe just drop these comments. They're just repeating the code.
Actually I would prefer to keep them, as "2^(reg.odiv)" is more?
human-readable then
"1 << ((val & CGU_PLL_CTRL_ODIV_MASK) >> CGU_PLL_CTRL_ODIV_SHIFT)"
> > +
> > + rate = (u64)parent_rate * fbdiv;
> > + do_div(rate, idiv * odiv);
> > +
> > + return rate;
> > +}
> > +
> > +static long hsdk_pll_round_rate(struct clk_hw *hw, unsigned long
> > rate,
> > + unsigned long *prate)
> > +{
> > + int i;
> > + long best_rate;
> > + struct hsdk_pll_clk *clk = to_hsdk_pll_clk(hw);
> > + const struct hsdk_pll_cfg *pll_cfg = clk->pll_cfg;
> > +
> > + if (pll_cfg[0].rate == 0)
> > + return -EINVAL;
>?
> This happens?
Only if we add bad hsdk_pll_cfg table. But it is quite cold code - we
change pll configuration quite rare, so maybe it's better to keep this
assert?
> > +
> > + best_rate = pll_cfg[0].rate;
> > +
> > + for (i = 1; pll_cfg[i].rate != 0; i++) {
> > + if (abs(rate - pll_cfg[i].rate) < abs(rate -
> > best_rate))
>?
> Alright, rate is unsigned long, and best_rate is long. abs() does
> the right thing here, but it makes me have to think twice if
> best_rate can be negative and then this is a larger number, not a
> smaller one. Can we make best_rate unsigned long in this
> function?
Yes, we can.
Anyway it's a bit strange what rate is unsigned long and round_rate
return value is long.
--?
?Eugeniy Paltsev
next prev parent reply other threads:[~2017-08-09 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 15:31 [PATCH] ARC: clk: introduce HSDKv1 pll driver Eugeniy Paltsev
2017-07-27 7:50 ` Vineet Gupta
2017-07-28 1:24 ` Stephen Boyd
2017-08-04 1:53 ` Stephen Boyd
2017-08-09 16:43 ` Eugeniy Paltsev [this message]
2017-08-09 17:22 ` sboyd
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=1502297028.2586.4.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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