From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on To: Geert Uytterhoeven References: <1488295191-24038-1-git-send-email-pdeschrijver@nvidia.com> <4cf40c25-2ce9-737c-9ccb-06bc2cdb61d7@nvidia.com> <20170306083835.GF26640@tbergstrom-lnx.Nvidia.com> <6d4dd315-cab6-189d-f383-fb7523fc31bd@nvidia.com> <20170306142850.GJ26640@tbergstrom-lnx.Nvidia.com> CC: Peter De Schrijver , Prashant Gaikwad , Michael Turquette , "Stephen Boyd" , Stephen Warren , "Thierry Reding" , Alexandre Courbot , linux-clk , , "linux-kernel@vger.kernel.org" From: Jon Hunter Message-ID: <313f1245-02aa-496c-3545-5029ece652af@nvidia.com> Date: Wed, 8 Mar 2017 11:48:21 +0000 MIME-Version: 1.0 In-Reply-To: Return-Path: jonathanh@nvidia.com Content-Type: text/plain; charset="utf-8" List-ID: On 08/03/17 11:38, Geert Uytterhoeven wrote: > Hi Jon, > > On Wed, Mar 8, 2017 at 11:13 AM, Jon Hunter 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