linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rhyland Klein <rklein@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Alexandre Courbot <gnurou@gmail.com>, <linux-clk@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH v2 00/11] Switch to using CRITICAL clks for Tegra
Date: Tue, 21 Jun 2016 14:05:03 -0400	[thread overview]
Message-ID: <c2c42a27-d705-0db0-36ab-4660c9dbc848@nvidia.com> (raw)
In-Reply-To: <1464381494-27096-1-git-send-email-rklein@nvidia.com>

On 5/27/2016 4:38 PM, Rhyland Klein wrote:
> Switch to defining clks that need to be on as CRITICAL rather than
> using the init_tables defined to enable clks. Some of these may be
> able to be converted to HAND_OFF clks, when that is supported.
> 
> I added a patch to mark CRITICAL clks in the clk_summary table, figuring
> it would be handy to be able to easily tell what clks are CRITICAL
> through the table.
> 
> I added a warning for using the init_table to enable clks. I considered
> removing it entirely, but I thought phasing it out might be better.
> 
> Rhyland Klein (11):
>   clk: tegra: Switch to using critical clks
>   clk: tegra20: Mark required clks as CRITICAL
>   clk: tegra20: clean up init_table
>   clk: tegra30: Mark certain clks as critical
>   clk: tegra30: clean up init_table
>   clk: tegra114: clean up init_table
>   clk: tegra124: clean up init_table
>   clk: tegra210: Mark required clks as CRITICAL
>   clk: tegra210: clean up init_table
>   clk: Show CRITICAL clks in clk_summary output
>   clk: tegra: WARN if clk in the init_table has enable
> 
>  drivers/clk/clk.c                        |  7 ++++--
>  drivers/clk/tegra/clk-tegra-periph.c     | 21 ++++++++++------
>  drivers/clk/tegra/clk-tegra-super-gen4.c | 12 ++++++----
>  drivers/clk/tegra/clk-tegra114.c         | 11 ++++-----
>  drivers/clk/tegra/clk-tegra124.c         | 19 ++++++---------
>  drivers/clk/tegra/clk-tegra20.c          | 41 +++++++++++++++-----------------
>  drivers/clk/tegra/clk-tegra210.c         | 28 ++++++++--------------
>  drivers/clk/tegra/clk-tegra30.c          | 28 ++++++++--------------
>  drivers/clk/tegra/clk.c                  |  5 ++++
>  9 files changed, 81 insertions(+), 91 deletions(-)
> 

Has anyone had a change to take a look at these patches yet?

-rhyland

-- 
nvpublic

      parent reply	other threads:[~2016-06-21 18:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 20:38 [PATCH v2 00/11] Switch to using CRITICAL clks for Tegra Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 01/11] clk: tegra: Switch to using critical clks Rhyland Klein
2016-06-22 12:16   ` Thierry Reding
2016-06-27  8:35     ` Peter De Schrijver
2016-07-05 22:07     ` Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 02/11] clk: tegra20: Mark required clks as CRITICAL Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 03/11] clk: tegra20: clean up init_table Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 04/11] clk: tegra30: Mark certain clks as critical Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 05/11] clk: tegra30: clean up init_table Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 06/11] clk: tegra114: " Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 07/11] clk: tegra124: " Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 08/11] clk: tegra210: Mark required clks as CRITICAL Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 09/11] clk: tegra210: clean up init_table Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 10/11] clk: Show CRITICAL clks in clk_summary output Rhyland Klein
2016-06-22 12:24   ` Thierry Reding
2016-06-22 15:31     ` Rhyland Klein
2016-06-28 17:40       ` Stephen Boyd
2016-06-30 20:13         ` Rhyland Klein
2016-05-27 20:38 ` [PATCH v2 11/11] clk: tegra: WARN if clk in the init_table has enable Rhyland Klein
2016-06-21 18:05 ` Rhyland Klein [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=c2c42a27-d705-0db0-36ab-4660c9dbc848@nvidia.com \
    --to=rklein@nvidia.com \
    --cc=gnurou@gmail.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=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).