Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1599190
| From | Peter De Schrijver <pdeschrijver@nvidia.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on |
| Date | 2017-03-13 11:50 +0100 |
| Message-ID | <tkvI6-7IV-9@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <ti1XQ-146-39@gated-at.bofh.it> <ti49j-2x3-11@gated-at.bofh.it> <tiHX4-5QO-9@gated-at.bofh.it> <tiIgq-5ZP-13@gated-at.bofh.it> <tiIJr-6r7-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Mar 08, 2017 at 11:48:21AM +0000, Jon Hunter wrote: > > 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 ;-) We don't have a specific power domain for DFD on Tegra210. It's part of the non-powergateable core domain. Cheers, Peter.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-02 22:30 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Peter De Schrijver <pdeschrijver@nvidia.com> - 2017-03-06 09:40 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-06 11:10 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Peter De Schrijver <pdeschrijver@nvidia.com> - 2017-03-06 15:40 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-06 17:00 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Geert Uytterhoeven <geert@linux-m68k.org> - 2017-03-06 18:00 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-07 21:30 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Geert Uytterhoeven <geert@linux-m68k.org> - 2017-03-08 11:20 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-08 12:30 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Geert Uytterhoeven <geert@linux-m68k.org> - 2017-03-08 12:50 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-08 13:20 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Peter De Schrijver <pdeschrijver@nvidia.com> - 2017-03-13 11:50 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Jon Hunter <jonathanh@nvidia.com> - 2017-03-13 12:10 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Peter De Schrijver <pdeschrijver@nvidia.com> - 2017-03-13 15:20 +0100
Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on Peter De Schrijver <pdeschrijver@nvidia.com> - 2017-03-13 11:50 +0100
csiph-web