From: Tuomas Tynkkynen <tuomas@tuxera.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-clk@vger.kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v2 6/6] cpufreq: tegra124-cpufreq: extend to support Tegra210
Date: Tue, 6 Feb 2018 14:27:20 +0200 [thread overview]
Message-ID: <20180206142720.3a52b532@duuni> (raw)
In-Reply-To: <20180201092520.GV7031@tbergstrom-lnx.Nvidia.com>
(Attempting to post through Gmane - let's see if this works at all).
On Thu, 1 Feb 2018 11:25:20 +0200
Peter De Schrijver <pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> wrote:
> On Wed, Jan 31, 2018 at 11:06:36AM +0000, Jon Hunter wrote:
> >
> > On 24/01/18 12:45, Peter De Schrijver wrote:
> > > Tegra210 has a very similar CPU clocking scheme than Tegra124. So add
> > > support in this driver. Also allow for the case where the CPU voltage is
> > > controlled directly by the DFLL rather than by a separate regulator object.
> > >
> > > Signed-off-by: Peter De Schrijver <pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> > > ---
> > > drivers/cpufreq/tegra124-cpufreq.c | 13 ++++++-------
> > > 1 file changed, 6 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/drivers/cpufreq/tegra124-cpufreq.c b/drivers/cpufreq/tegra124-cpufreq.c
> > > index 4353025..d631dc4 100644
> > > --- a/drivers/cpufreq/tegra124-cpufreq.c
> > > +++ b/drivers/cpufreq/tegra124-cpufreq.c
> > > @@ -64,7 +64,8 @@ static void tegra124_cpu_switch_to_pllx(struct tegra124_cpufreq_priv *priv)
> > > {
> > > clk_set_parent(priv->cpu_clk, priv->pllp_clk);
> > > clk_disable_unprepare(priv->dfll_clk);
> > > - regulator_sync_voltage(priv->vdd_cpu_reg);
> > > + if (priv->vdd_cpu_reg)
> > > + regulator_sync_voltage(priv->vdd_cpu_reg);
> > > clk_set_parent(priv->cpu_clk, priv->pllx_clk);
> > > }
> > >
> > > @@ -89,10 +90,8 @@ static int tegra124_cpufreq_probe(struct platform_device *pdev)
> > > return -ENODEV;
> > >
> > > priv->vdd_cpu_reg = regulator_get(cpu_dev, "vdd-cpu");
> > > - if (IS_ERR(priv->vdd_cpu_reg)) {
> > > - ret = PTR_ERR(priv->vdd_cpu_reg);
> > > - goto out_put_np;
> > > - }
> > > + if (IS_ERR(priv->vdd_cpu_reg))
> > > + priv->vdd_cpu_reg = NULL;
> > >
> >
> > For Tegra124, don't we still want to return an error here?
>
> Not necessarily. Also on Tegra124 the DFLL can use PWM and I think jetson TK1
> can be reworked to use this.
>
> Peter.
>
Regardless of that, you need to bail out on -EPROBE_DEFER I think.
next prev parent reply other threads:[~2018-02-06 12:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 12:45 [PATCH v2 0/6] Tegra210 DFLL implementation Peter De Schrijver
2018-01-24 12:45 ` Peter De Schrijver
2018-01-24 12:45 ` [PATCH v2 1/6] clk: tegra: dfll registration for multiple SoCs Peter De Schrijver
2018-01-31 10:13 ` Jon Hunter
2018-01-24 12:45 ` [PATCH v2 2/6] clk: tegra: DT align parameter for CVB calculation Peter De Schrijver
2018-01-31 10:43 ` Jon Hunter
2018-02-01 10:30 ` Peter De Schrijver
2018-02-01 10:54 ` Jon Hunter
2018-02-01 11:02 ` Peter De Schrijver
2018-01-24 12:45 ` [PATCH v2 3/6] clk: tegra: add CVB tables for Tegra210 CPU DFLL Peter De Schrijver
2018-01-31 10:50 ` Jon Hunter
2018-02-01 10:39 ` Peter De Schrijver
2018-01-24 12:45 ` [PATCH v2 4/6] clk: tegra: dfll: support PWM regulator control Peter De Schrijver
2018-01-31 11:26 ` Jon Hunter
2018-02-01 10:57 ` Peter De Schrijver
2018-01-24 12:45 ` [PATCH v2 5/6] clk: tegra: build clk-dfll.c for Tegra124 and Tegra210 Peter De Schrijver
2018-01-31 11:03 ` Jon Hunter
2018-01-24 12:45 ` [PATCH v2 6/6] cpufreq: tegra124-cpufreq: extend to support Tegra210 Peter De Schrijver
2018-01-31 11:06 ` Jon Hunter
2018-02-01 9:25 ` Peter De Schrijver
2018-02-01 9:53 ` Jon Hunter
2018-02-01 10:15 ` Peter De Schrijver
2018-02-01 10:22 ` Jon Hunter
2018-02-01 10:31 ` Peter De Schrijver
2018-02-06 12:27 ` Tuomas Tynkkynen [this message]
2018-02-06 16:28 ` Peter De Schrijver
2018-01-31 11:28 ` [PATCH v2 0/6] Tegra210 DFLL implementation Jon Hunter
2018-02-01 9:30 ` 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=20180206142720.3a52b532@duuni \
--to=tuomas@tuxera.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=sboyd@kernel.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