From: Jon Hunter <jonathanh@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
"Michael Turquette" <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: <linux-clk@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] clk: tegra: Mark APB clock as critical
Date: Thu, 30 Nov 2017 11:31:12 +0000 [thread overview]
Message-ID: <e69dc6c8-cbca-0498-c9d8-23e9a7ac1ad6@nvidia.com> (raw)
In-Reply-To: <a96d03da-c2a3-1e44-f227-02577f972df6@gmail.com>
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.
Jon
--
nvpublic
next prev parent reply other threads:[~2017-11-30 11:31 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
2017-10-23 11:57 ` Peter De Schrijver
2017-11-28 23:30 ` Dmitry Osipenko
2017-11-29 0:09 ` Dmitry Osipenko
2017-11-29 10:12 ` Jon Hunter
2017-11-29 15:08 ` Dmitry Osipenko
2017-11-29 22:55 ` Jon Hunter
2017-11-29 23:13 ` Dmitry Osipenko
2017-11-30 11:31 ` Jon Hunter [this message]
2017-11-30 13:24 ` Dmitry Osipenko
2017-11-30 16:39 ` Jon Hunter
2017-11-30 16:45 ` Dmitry Osipenko
2017-11-30 16:51 ` Jon Hunter
2017-11-30 16:53 ` Dmitry Osipenko
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
2017-12-05 9:06 ` Peter De Schrijver
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=e69dc6c8-cbca-0498-c9d8-23e9a7ac1ad6@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=digetx@gmail.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