From: Stephen Boyd <sboyd@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] clk: tegra: pll: Improve PLLM enable-state detection
Date: Mon, 27 Jul 2020 18:21:29 -0700 [thread overview]
Message-ID: <159589928947.1360974.2291551893182994686@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200709172057.13951-1-digetx@gmail.com>
Quoting Dmitry Osipenko (2020-07-09 10:20:57)
> Power Management Controller (PMC) can override the PLLM clock settings,
> including the enable-state. Although PMC could only act as a second level
> gate, meaning that PLLM needs to be enabled by the Clock and Reset
> Controller (CaR) anyways if we want it to be enabled. Hence, when PLLM is
> overridden by PMC, it needs to be enabled by CaR and ungated by PMC in
> order to be functional. Please note that this patch doesn't fix any known
> problem, and thus, it's merely a minor improvement.
>
> Link: https://lore.kernel.org/linux-arm-kernel/20191210120909.GA2703785@ulmo/T/
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2020-07-28 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 17:20 [PATCH v4] clk: tegra: pll: Improve PLLM enable-state detection Dmitry Osipenko
[not found] ` <20200709172057.13951-1-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-14 8:20 ` Jon Hunter
[not found] ` <93106a4c-b0fb-3bbf-49cb-bfe348b1ffc7-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-07-14 9:36 ` Dmitry Osipenko
2020-07-17 16:55 ` Jon Hunter
[not found] ` <997361b8-4466-cdf0-beeb-eedcbeb48597-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-07-17 20:15 ` Dmitry Osipenko
2020-07-28 1:21 ` Stephen Boyd [this message]
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=159589928947.1360974.2291551893182994686@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@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).