[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220530075256.lpw6bhupejy2dnqi@vireshk-i7>
Date: Mon, 30 May 2022 13:22:56 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Dmitry Osipenko <dmitry.osipenko@...labora.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Rafael Wysocki <rjw@...ysocki.net>,
Stephen Boyd <sboyd@...nel.org>, Nishanth Menon <nm@...com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/31] cpufreq: tegra20: Migrate to
dev_pm_opp_set_config()
On 29-05-22, 19:59, Dmitry Osipenko wrote:
> > Please keep the PTR_ERR_OR_ZERO.
Ahh, sorry about that. Fixed.
> > tegra20-cpufreq tegra20-cpufreq: failed to set OPP config: -1042688000
>
> With that fixed, now there is another error:
>
> [ 1.761945] cpu cpu0: _of_add_opp_table_v2: no supported OPPs
> [ 1.761960] cpu cpu0: OPP table can't be empty
So we failed to find any OPPs which work with the hardware version of
updated with dev_pm_opp_set_config(). I tried to follow the path and
see if there is something wrong here. Failed to find that :(
> I see this on Tegra30, but not on Tegra20. Apparently OPP table
> refcounting is broken on Tegra30 by this patchset. To make it clear,
> there are no error without these OPP patches applied. I may take a
> closer look if will be needed, just ping me.
Yes, it would be very helpful as I don't have the necessary hardware.
--
viresh
Powered by blists - more mailing lists