From: Jon Hunter <jonathanh@nvidia.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
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>,
"Thierry Reding" <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
linux-clk <linux-clk@vger.kernel.org>,
<linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on
Date: Wed, 8 Mar 2017 11:48:21 +0000 [thread overview]
Message-ID: <313f1245-02aa-496c-3545-5029ece652af@nvidia.com> (raw)
In-Reply-To: <CAMuHMdVRa3C4ikaoNDDU21NbRVcPTf0z6fPiJ1nF-VDd+3Dm0g@mail.gmail.com>
On 08/03/17 11:38, Geert Uytterhoeven wrote:
> Hi Jon,
>
> On Wed, Mar 8, 2017 at 11:13 AM, Jon Hunter <jonathanh@nvidia.com> wrote:
>>> I had a similar issue with SH-Mobile AG5, where the power domain containing
>>> the JTAG interface is powered down.
>>
>> This reminds me, does your patch assume that the DFD power domain is
>> enabled? I am guessing that it needs to be for JTAG to work.
>
> Yes. The pm-rmobile driver looks for "arm,coresight-etm3x" devices, and
> marks the corresponding PM Domain as always-on, as long as the
> Coresight code doesn't handle runtime PM.
Sorry Geert, but I was asking Peter specifically about the power-domain
on Tegra as I have a feeling we may have the same scenario ;-)
Jon
--
nvpublic
next prev parent reply other threads:[~2017-03-08 11:48 UTC|newest]
Thread overview: 17+ 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-03-02 17:56 ` Jon Hunter
2017-03-06 8:38 ` Peter De Schrijver
2017-03-06 9:58 ` Jon Hunter
2017-03-06 14:28 ` Peter De Schrijver
2017-03-06 15:46 ` Jon Hunter
2017-03-06 15:53 ` Geert Uytterhoeven
2017-03-07 20:27 ` Jon Hunter
2017-03-08 8:23 ` Geert Uytterhoeven
2017-03-08 10:13 ` Jon Hunter
2017-03-08 11:38 ` Geert Uytterhoeven
2017-03-08 11:48 ` Jon Hunter [this message]
2017-03-13 10:45 ` Peter De Schrijver
2017-03-13 11:03 ` Jon Hunter
2017-03-13 14:18 ` Peter De Schrijver
2017-03-13 10:47 ` Peter De Schrijver
2017-03-20 14:18 ` 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=313f1245-02aa-496c-3545-5029ece652af@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=geert@linux-m68k.org \
--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 \
--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