From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
"Paul Walmsley" <pwalmsley@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/5] clk: tegra: Add support for PLLSS
Date: Mon, 14 Oct 2013 18:03:17 +0300 [thread overview]
Message-ID: <20131014150317.GA19540@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20131010103915.GA6735@ulmo.nvidia.com>
On Thu, Oct 10, 2013 at 12:39:16PM +0200, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Fri, Oct 04, 2013 at 12:12:40PM +0300, Peter De Schrijver wrote:
> > Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
>
> This is missing a commit description.
>
> > diff --git a/drivers/clk/tegra/clk-pll.c b/drivers/clk/tegra/clk-pll.c
> [...]
> > +const struct clk_ops tegra_clk_pllss_ops = {
>
> static?
>
> > +struct clk *tegra_clk_register_pllss(const char *name, const char *parent_name,
> > + void __iomem *clk_base, unsigned long flags,
> > + unsigned long fixed_rate,
> > + struct tegra_clk_pll_params *pll_params,
> > + struct tegra_clk_pll_freq_table *freq_table,
> > + spinlock_t *lock)
> > +{
> [...]
> > + pll = _tegra_init_pll(clk_base, NULL, fixed_rate, pll_params,
> > + pll_flags, freq_table, lock);
> > +
> > + if (IS_ERR(pll))
>
> I'd leave out the blank line separating the assignment of pll and the
> check for validity. Grouping them together like that makes it
> immediately clear that they belong together.
>
> > + return ERR_CAST(pll);
> > +
> > + val = pll_readl_base(pll);
> > +
> > + if (val & (3 << 25)) {
>
> Same here. Also 3 << 25 could probably be a symbolic constant, something
> like PLLSS_REF_SRC_SEL_MASK perhaps?
>
> > + WARN(1, "Unknown parent selected for %s: %d\n", name,
> > + val >> 25);
>
> Similarly, this should be something like:
>
> (val & PLLSS_REF_SRC_SEL_MASK) >> PLLSS_REF_SRC_SEL_SHIFT
>
> > + kfree(pll);
> > + return ERR_PTR(-EINVAL);
> > + }
> > + _get_pll_mnp(pll, &cfg);
>
> Nit: I'd put a blank line before this, to separate the block and the
> function call. That is:
>
> }
>
> _get_pll_mnp(...);
>
> > +
> > + if (cfg.n > 1) {
> > + WARN(1, "%s should not be initialized\n", name);
> > + kfree(pll);
> > + return ERR_PTR(-EINVAL);
> > + }
>
> Is this really fatal? Can't we just configure the PLL from scratch?
>
> > + parent_rate = __clk_get_rate(parent);
> > +
> > + pll_params->vco_min = _clip_vco_min(pll_params->vco_min, parent_rate);
> > +
> > + cfg.m = _pll_fixed_mdiv(pll_params, parent_rate);
> > + cfg.n = cfg.m * pll_params->vco_min / parent_rate;
> > +
> > + for (i = 0; pll_params->pdiv_tohw[i].pdiv; i++)
> > + ;
> > + cfg.p = pll_params->pdiv_tohw[i-1].hw_val;
>
> Could use a blank line to separate them. Also what if .pdiv of the first
> entry is 0? The loop will terminate on the first run and i will be 0, so
> this would try to access pdiv_tohw[-1]. Can that ever happen?
>
That would be an error. This PLL type always has a post divider table.
I will add a check.
Cheers,
Peter.
next prev parent reply other threads:[~2013-10-14 15:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 9:12 [PATCH 0/5] Tegra124 clock support Peter De Schrijver
2013-10-04 9:12 ` [PATCH 1/5] clk: tegra: Add support for PLLSS Peter De Schrijver
2013-10-10 10:39 ` Thierry Reding
2013-10-10 10:59 ` Peter De Schrijver
2013-10-14 15:03 ` Peter De Schrijver [this message]
2013-10-04 9:12 ` [PATCH 2/5] clk: tegra: Add periph regs bank X Peter De Schrijver
2013-10-10 10:43 ` Thierry Reding
2013-10-10 11:00 ` Peter De Schrijver
2013-10-04 9:12 ` [PATCH 3/5] clk: tegra124: Add common clk IDs to clk-id.h Peter De Schrijver
2013-10-08 22:29 ` Stephen Warren
2013-10-04 9:12 ` [PATCH 4/5] clk: tegra124: Add new peripheral clocks Peter De Schrijver
2013-10-08 22:31 ` Stephen Warren
2013-10-09 8:11 ` Peter De Schrijver
2013-10-09 16:00 ` Stephen Warren
2013-10-10 8:51 ` Peter De Schrijver
2013-10-04 9:12 ` [PATCH 5/5] clk: tegra124: Add support for Tegra124 clocks Peter De Schrijver
2013-10-08 22:31 ` [PATCH 0/5] Tegra124 clock support Stephen Warren
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=20131014150317.GA19540@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=pgaikwad@nvidia.com \
--cc=pwalmsley@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®