From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: use pll_ref as the pll_e parent
Date: Wed, 30 Oct 2013 16:44:10 +0100 [thread overview]
Message-ID: <1383147850.4095.3.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <527128B5.2020101@wwwdotorg.org>
Am Mittwoch, den 30.10.2013, 09:41 -0600 schrieb Stephen Warren:
> On 10/29/2013 06:41 PM, Peter De Schrijver wrote:
> > Use pll_ref instead of pll_re_vco as the pll_e parent on Tegra114 and
> > Tegra124. Also add a pll_ref table entry for pll_e for Tegra114.
>
> Why? What benefit does this give, or what bug does this fix?
>
> > diff --git a/drivers/clk/tegra/clk-pll.c b/drivers/clk/tegra/clk-pll.c
>
> > val_aux = pll_readl(pll_params->aux_reg, pll);
> >
> > if (val & PLL_BASE_ENABLE) {
> > - if (!(val_aux & PLLE_AUX_PLLRE_SEL))
> > + if ((val_aux & PLLE_AUX_PLLRE_SEL) || (val_aux & val_aux))
>
> Isn't "|| (val_aux & val_aux)" always true, at least if the value is
> non-zero? Either this should be simply "|| val_aux", or one of those two
> "val_aux" is the wrong thing.
>
> > WARN(1, "pll_e enabled with unsupported parent %s\n",
> > - (val & PLLE_AUX_PLLP_SEL) ? "pllp_out0" : "pll_ref");
> > + (val_aux & PLLE_AUX_PLLP_SEL) ? "pllp_out0" :
> > + "pll_re_vco");
> > } else {
> > - val_aux |= PLLE_AUX_PLLRE_SEL;
> > + val_aux &= ~(PLLE_AUX_PLLRE_SEL | PLLE_AUX_PLLP_SEL);
> > pll_writel(val, pll_params->aux_reg, pll);
> > }
>
> > diff --git a/drivers/clk/tegra/clk-tegra114.c b/drivers/clk/tegra/clk-tegra114.c
>
> > @@ -560,6 +560,7 @@ static struct tegra_clk_pll_freq_table pll_e_freq_table[] = {
> > /* PLLE special case: use cpcon field to store cml divider value */
> > {336000000, 100000000, 100, 21, 16, 11},
> > {312000000, 100000000, 200, 26, 24, 13},
> > + {12000000, 100000000, 200, 1, 24, 13},
>
> Presumably this is because pll_ref is the crystal, which runs at 12MHz.
> What if it doesn't; Tegra supports a bunch of other crystal rates. Don't
> we need entries for all the other potential crystal rates too?
The TRM states that PCIe and thus PLLE are only supported with 12MHz
external crystal rate.
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5076 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-10-30 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 0:41 [PATCH] clk: tegra: use pll_ref as the pll_e parent Peter De Schrijver
2013-10-30 15:41 ` Stephen Warren
2013-10-30 15:44 ` Lucas Stach [this message]
2013-10-30 22:19 ` Peter De Schrijver
2013-10-30 22:18 ` Peter De Schrijver
2013-10-30 22:50 ` Stephen Warren
2013-10-31 15:41 ` Peter De Schrijver
2013-10-31 16:41 ` Stephen Warren
2013-11-22 13:40 ` Peter De Schrijver
2013-11-25 12:42 ` Peter De Schrijver
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=1383147850.4095.3.camel@weser.hi.pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).