[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <313f1245-02aa-496c-3545-5029ece652af@nvidia.com>
Date: Wed, 8 Mar 2017 11:48:21 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
CC: Peter De Schrijver <pdeschrijver@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>,
Michael Turquette <mturquette@...libre.com>,
"Stephen Boyd" <sboyd@...eaurora.org>,
Stephen Warren <swarren@...dotorg.org>,
"Thierry Reding" <thierry.reding@...il.com>,
Alexandre Courbot <gnurou@...il.com>,
linux-clk <linux-clk@...r.kernel.org>,
<linux-tegra@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on
On 08/03/17 11:38, Geert Uytterhoeven wrote:
> Hi Jon,
>
> On Wed, Mar 8, 2017 at 11:13 AM, Jon Hunter <jonathanh@...dia.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
Powered by blists - more mailing lists