linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Alex Frid <afrid@nvidia.com>,
	linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 3/3] clk: tegra: Do not enable PLL_RE_VCO on Tegra210
Date: Tue, 25 Jun 2019 16:13:20 -0700	[thread overview]
Message-ID: <20190625231321.AF5BD208CA@mail.kernel.org> (raw)
In-Reply-To: <20190613161225.2531-3-thierry.reding@gmail.com>

Quoting Thierry Reding (2019-06-13 09:12:25)
> From: Thierry Reding <treding@nvidia.com>
> 
> It turns out that this PLL is not used on Tegra210, so there's no need
> to enable it via the init table. Remove the init table entry for this
> PLL to avoid it getting enabled at boot time. If the bootloader enabled
> it and forgot to turn it off, the common clock framework will now know
> to disable it because it is unused.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---

Applied to clk-next


  parent reply	other threads:[~2019-06-25 23:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 16:12 [PATCH 1/3] clk: tegra: Do not warn unnecessarily Thierry Reding
2019-06-13 16:12 ` [PATCH 2/3] clk: tegra: Warn if an enabled PLL is in IDDQ Thierry Reding
2019-06-17 10:39   ` Jon Hunter
2019-06-17 11:14     ` Thierry Reding
2019-06-25 23:13   ` Stephen Boyd
2019-06-13 16:12 ` [PATCH 3/3] clk: tegra: Do not enable PLL_RE_VCO on Tegra210 Thierry Reding
2019-06-17 10:43   ` Jon Hunter
2019-06-25 23:13   ` Stephen Boyd [this message]
2019-06-17 10:32 ` [PATCH 1/3] clk: tegra: Do not warn unnecessarily Jon Hunter
2019-06-25 23:13 ` Stephen Boyd

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=20190625231321.AF5BD208CA@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=afrid@nvidia.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=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;
as well as URLs for NNTP newsgroup(s).