From: Thierry Reding <thierry.reding@gmail.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: 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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on
Date: Mon, 20 Mar 2017 15:18:47 +0100 [thread overview]
Message-ID: <20170320141847.GD28203@ulmo.ba.sec> (raw)
In-Reply-To: <1488295191-24038-1-git-send-email-pdeschrijver@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Tue, Feb 28, 2017 at 05:19:50PM +0200, Peter De Schrijver wrote:
> This is needed to make the JTAG debugging interface work.
>
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
> drivers/clk/tegra/clk-tegra210.c | 1 +
> 1 file changed, 1 insertion(+)
Let's revisit the power-saving aspects of this when we're actually good
at saving power. I suspect that the power consumption of DBGAPB is
dwarfed by the rest of the SoC. I've added a TODO comment as a reminder.
Applied to for-4.12/clk, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-20 14:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:19 [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Peter De Schrijver
2017-02-28 15:19 ` Peter De Schrijver
2017-03-02 17:56 ` Jon Hunter
2017-03-02 17:56 ` Jon Hunter
2017-03-06 8:38 ` Peter De Schrijver
2017-03-06 8:38 ` Peter De Schrijver
2017-03-06 9:58 ` Jon Hunter
2017-03-06 9:58 ` Jon Hunter
2017-03-06 14:28 ` Peter De Schrijver
2017-03-06 14:28 ` Peter De Schrijver
2017-03-06 15:46 ` Jon Hunter
2017-03-06 15:46 ` Jon Hunter
2017-03-06 15:53 ` Geert Uytterhoeven
2017-03-06 15:53 ` Geert Uytterhoeven
2017-03-07 20:27 ` Jon Hunter
2017-03-07 20:27 ` Jon Hunter
2017-03-08 8:23 ` Geert Uytterhoeven
2017-03-08 8:23 ` Geert Uytterhoeven
2017-03-08 10:13 ` Jon Hunter
2017-03-08 10:13 ` Jon Hunter
2017-03-08 11:38 ` Geert Uytterhoeven
2017-03-08 11:48 ` Jon Hunter
2017-03-08 11:48 ` Jon Hunter
2017-03-13 10:45 ` Peter De Schrijver
2017-03-13 10:45 ` Peter De Schrijver
2017-03-13 11:03 ` Jon Hunter
2017-03-13 11:03 ` Jon Hunter
2017-03-13 14:18 ` Peter De Schrijver
2017-03-13 14:18 ` Peter De Schrijver
2017-03-13 10:47 ` Peter De Schrijver
2017-03-13 10:47 ` Peter De Schrijver
2017-03-20 14:18 ` Thierry Reding [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=20170320141847.GD28203@ulmo.ba.sec \
--to=thierry.reding@gmail.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=pgaikwad@nvidia.com \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.