From: Dmitry Osipenko <digetx@gmail.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: Mark APB clock as critical
Date: Sat, 2 Dec 2017 15:47:32 +0300 [thread overview]
Message-ID: <803890bc-e3fe-134a-2127-3363187d04f2@gmail.com> (raw)
In-Reply-To: <20171201084818.GI32106@tbergstrom-lnx.Nvidia.com>
On 01.12.2017 11:48, Peter De Schrijver wrote:
> On Thu, Nov 30, 2017 at 04:39:22PM +0000, Jon Hunter wrote:
>>
>> On 30/11/17 13:24, Dmitry Osipenko wrote:
>>> On 30.11.2017 14:31, Jon Hunter wrote:
>>>>
>>>> On 29/11/17 23:13, Dmitry Osipenko wrote:
>>>>> On 30.11.2017 01:55, Jon Hunter wrote:
>>>>
>>>> ...
>>>>
>>>>> I've asked you to re-test Tegra114/124 or whatever was failing for you with the
>>>>> PLL_M being marked as critical instead of PCLK. Maybe it was PLL_M that actually
>>>>> caused trouble on Tegra114/124.
>>>>
>>>> Please share the exact change you would like me to test and I will.
>>>
>>> Please try this:
>>
>> I tried the patch, but this does not work for Tegra124 it still hangs.
>> Tracing the clk calls the last thing I see is ...
>>
>> [ 2.687846] tegra124-dfll 70110000.clock: couldn't get vdd_cpu regulator
>> [ 2.694403] clk_prepare: hclk_div
>> [ 2.695929] clk_prepare_complete: hclk_div
>> [ 2.700027] clk_prepare: hclk
>> [ 2.702947] clk_prepare_complete: hclk
>> [ 2.706673] clk_prepare: pclk_div
>> [ 2.709986] clk_prepare_complete: pclk_div
>> [ 2.714039] clk_prepare: pclk
>> [ 2.716985] clk_prepare_complete: pclk
>> [ 2.720739] clk_prepare: apbdma
>> [ 2.723833] clk_prepare_complete: apbdma
>> [ 2.727736] clk_enable: hclk_div
>> [ 2.730940] clk_enable_complete: hclk_div
>> [ 2.734926] clk_enable: hclk
>> [ 2.737788] clk_enable_complete: hclk
>> [ 2.741426] clk_enable: pclk_div
>> [ 2.744633] clk_enable_complete: pclk_div
>> [ 2.748619] clk_enable: pclk
>> [ 2.751481] clk_enable_complete: pclk
>> [ 2.755120] clk_enable: apbdma
>> [ 2.758153] clk_enable_complete: apbdma
>> [ 2.762390] clk_disable: apbdma
>> [ 2.765088] clk_disable_complete: apbdma
>> [ 2.768986] clk
>>
>> So I believe this change is correct and that Peter's analysis on IRC
>> seems correct, that this change has exposed another issue with the clock
>> driver.
>>
>> Peter, can you summarise which other clocks should be made critical?
>
> The following clocks should be critical:
>
> pclk
> hclk
> sclk
> emc
> mc
> pll_p
>
> I think that's it.
Could you please elaborate why pll_p should be critical? Is it applicable to all
Tegra generations?
next prev parent reply other threads:[~2017-12-02 12:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 11:12 [PATCH] clk: tegra: Mark APB clock as critical Jon Hunter
[not found] ` <1508757172-13030-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-10-23 11:57 ` Peter De Schrijver
2017-11-28 23:30 ` Dmitry Osipenko
[not found] ` <18f57c1f-add0-908a-6a26-7cc81f29d7d9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-29 0:09 ` Dmitry Osipenko
[not found] ` <f940d9f1-aaec-cf25-24d2-956df63bbbd1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-29 10:12 ` Jon Hunter
2017-11-29 15:08 ` Dmitry Osipenko
[not found] ` <95c14859-a2c7-1c61-adba-bd6c16155c01-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-29 22:55 ` Jon Hunter
2017-11-29 23:13 ` Dmitry Osipenko
[not found] ` <a96d03da-c2a3-1e44-f227-02577f972df6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-30 11:31 ` Jon Hunter
2017-11-30 13:24 ` Dmitry Osipenko
[not found] ` <6264cf17-0850-37dd-ca92-9362521d2db6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-30 16:39 ` Jon Hunter
[not found] ` <236aa250-3b9b-94de-0978-0fb8546d504d-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-30 16:45 ` Dmitry Osipenko
2017-11-30 16:51 ` Jon Hunter
[not found] ` <43e293c3-daf2-7b2e-2524-f14de3811f44-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-30 16:53 ` Dmitry Osipenko
[not found] ` <6378f92d-54a9-590a-5fdb-88a7bfa96fc1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-30 17:22 ` Jon Hunter
2017-11-30 17:49 ` Dmitry Osipenko
2017-12-01 8:48 ` Peter De Schrijver
2017-12-02 12:47 ` Dmitry Osipenko [this message]
[not found] ` <803890bc-e3fe-134a-2127-3363187d04f2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-05 9:06 ` Peter De Schrijver
[not found] ` <20171205090635.GL32106-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2017-12-05 18:22 ` Dmitry Osipenko
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=803890bc-e3fe-134a-2127-3363187d04f2@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@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=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