linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Peter Geis <pgwipeout@gmail.com>,
	Nicolas Chauvet <kwizart@gmail.com>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 07/11] cpufreq: dt-platdev: Blacklist NVIDIA Tegra20 and Tegra30 SoCs
Date: Fri, 13 Dec 2019 16:27:47 +0300	[thread overview]
Message-ID: <aee736a0-444c-3d1a-1e51-c5b5259eb1b5@gmail.com> (raw)
In-Reply-To: <2776e3c7-999e-5e6f-3a0e-211226dc30e6@gmail.com>

18.11.2019 19:51, Dmitry Osipenko пишет:
> 18.11.2019 19:45, Dmitry Osipenko пишет:
>> Both NVIDIA Tegra20 and Tegra30 SoCs should be blacklisted because CPU
>> OPPs use supported_hw and thus platdev isn't suitable for these SoCs.
>> Currently cpufreq-dt driver produces a bit annoying warning splats
>> during boot because valid OPPs are not found, this will be fixed once
>> tegra20-cpufreq driver will be update to support cpufreq-dt. The warnings
>> will also happen on older stable kernels using newer device-trees, thus
>> this patch should be backported to stable kernels as well.
>>
>> Cc: <stable@vger.kernel.org>
>> Reported-by: Jon Hunter <jonathanh@nvidia.com>
>> Fixes: 4053aa65c517 ("ARM: tegra: cardhu-a04: Add CPU Operating Performance Points")
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>> ---
>>  drivers/cpufreq/cpufreq-dt-platdev.c | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
>> index f1d170dcf4d3..aba591d57c67 100644
>> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
>> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
>> @@ -121,6 +121,8 @@ static const struct of_device_id blacklist[] __initconst = {
>>  	{ .compatible = "mediatek,mt8176", },
>>  	{ .compatible = "mediatek,mt8183", },
>>  
>> +	{ .compatible = "nvidia,tegra20", },
>> +	{ .compatible = "nvidia,tegra30", },
>>  	{ .compatible = "nvidia,tegra124", },
>>  	{ .compatible = "nvidia,tegra210", },
>>  
>>
> 
> Hello Viresh,
> 
> Could you please pick up this patch for v5.5 fixes? Thanks in advance!
> 

Viresh / Rafael? Maybe I should send that patch separately?

  reply	other threads:[~2019-12-13 20:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 16:45 [PATCH v5 00/11] NVIDIA Tegra20 CPUFreq driver major update Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 01/11] clk: tegra: Add custom CCLK implementation Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 02/11] clk: tegra: pll: Add pre/post rate-change hooks Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 03/11] clk: tegra: cclk: Add helpers for handling PLLX rate changes Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 04/11] clk: tegra20: Use custom CCLK implementation Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 05/11] clk: tegra30: " Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 06/11] dt-bindings: cpufreq: Add binding for NVIDIA Tegra20/30 Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 07/11] cpufreq: dt-platdev: Blacklist NVIDIA Tegra20 and Tegra30 SoCs Dmitry Osipenko
2019-11-18 16:51   ` Dmitry Osipenko
2019-12-13 13:27     ` Dmitry Osipenko [this message]
2019-12-16  4:05   ` Viresh Kumar
2019-12-16  4:08     ` Viresh Kumar
2019-12-16 14:11       ` Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 08/11] cpufreq: tegra20: Use generic cpufreq-dt driver (Tegra30 supported now) Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 09/11] ARM: tegra: Create tegra20-cpufreq platform device on Tegra30 Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 10/11] ARM: dts: tegra30: beaver: Set up voltage regulators for DVFS Dmitry Osipenko
2019-11-18 16:45 ` [PATCH v5 11/11] ARM: dts: tegra30: beaver: Add CPU Operating Performance Points 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=aee736a0-444c-3d1a-1e51-c5b5259eb1b5@gmail.com \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kwizart@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=mturquette@baylibre.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=pgwipeout@gmail.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=viresh.kumar@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).