Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1595086
| From | Geert Uytterhoeven <geert@linux-m68k.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on |
| Date | 2017-03-08 12:50 +0100 |
| Message-ID | <tiIgq-5ZP-13@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <thWls-5tJ-17@gated-at.bofh.it> <thXKy-6FK-19@gated-at.bofh.it> <ti1XQ-146-39@gated-at.bofh.it> <ti49j-2x3-11@gated-at.bofh.it> <tiHX4-5QO-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
For R-Mobile A1 and APE6 I already have added such device nodes, as any access
to a debug register hangs when the debug power domain is powered down.
For SH-Mobile AG5, I hadn't, as the debug power domain needs to be powered
for JTAG functionality only.
For the latter, perhaps we also need a command line parameter to change
a device status from "disabled" to "enabled"?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
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