From: Jon Hunter <jonathanh@nvidia.com>
To: Rhyland Klein <rklein@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>, <linux-clk@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, Bill Huang <bilhuang@nvidia.com>
Subject: Re: [PATCH] clk: tegra210: Add SLCG override gate clocks
Date: Tue, 15 Mar 2016 08:40:25 +0000 [thread overview]
Message-ID: <56E7CA79.7060106@nvidia.com> (raw)
In-Reply-To: <56E6E20C.6020807@nvidia.com>
On 14/03/16 16:08, Rhyland Klein wrote:
> On 3/14/2016 12:05 PM, Thierry Reding wrote:
>> * PGP Signed by an unknown key
>>
>> On Thu, Mar 10, 2016 at 02:38:05PM -0500, Rhyland Klein wrote:
>>> From: Bill Huang <bilhuang@nvidia.com>
>>>
>>> Add some SLCG (Second Level Clock Gating) override clocks to control
>>> gating and un-gating their logics.
>>>
>>> Signed-off-by: Bill Huang <bilhuang@nvidia.com>
>>> Signed-off-by: Rhyland Klein <rklein@nvidia.com>
>>> ---
>>> drivers/clk/tegra/clk-id.h | 16 ++++++
>>> drivers/clk/tegra/clk-tegra210.c | 91 ++++++++++++++++++++++++++++++++
>>> include/dt-bindings/clock/tegra210-car.h | 32 +++++------
>>> 3 files changed, 123 insertions(+), 16 deletions(-)
>>
>> There's no rationale given here about why we need this. What will these
>> second level clock gates be used for? Why do we need these (seemingly)
>> duplicate clock entries.
>>
>
> These are going to be used in the to-be posted patchset around
> powergating. As of now they are unused, which is why I hadn't added them
> previously. I just wanted to try to get this dependency in before the
> powergate series was posted.
Yes we are using these on the Pixel C (aka. Smaug) and I suggested to
Rhyland that we upstream them. Eventually we will use them but only
after the core GenPD changes for Tegra are merged. From my perspective I
was thinking it is better to reduce the changes between the chromeos
3.18 kernel and mainline. However, if you wish to wait until we need
them I guess we can. Otherwise ...
Acked-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
next prev parent reply other threads:[~2016-03-15 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 19:38 [PATCH] clk: tegra210: Add SLCG override gate clocks Rhyland Klein
2016-03-14 16:05 ` Thierry Reding
2016-03-14 16:08 ` Rhyland Klein
2016-03-15 8:40 ` Jon Hunter [this message]
2016-03-25 18:21 ` Rhyland Klein
2016-04-12 15:20 ` Thierry Reding
2016-04-12 17:41 ` Jon Hunter
2016-04-22 11:12 ` Thierry Reding
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=56E7CA79.7060106@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=bilhuang@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=rklein@nvidia.com \
--cc=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).