[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211012055143.xmkbvhbnolspgjin@vireshk-i7>
Date: Tue, 12 Oct 2021 11:21:43 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Hector Martin <marcan@...can.st>,
Sibi Sankar <sibis@...eaurora.org>,
Saravana Kannan <saravanak@...gle.com>
Cc: linux-arm-kernel@...ts.infradead.org,
Alyssa Rosenzweig <alyssa@...enzweig.io>,
Sven Peter <sven@...npeter.dev>, Marc Zyngier <maz@...nel.org>,
Mark Kettenis <mark.kettenis@...all.nl>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Catalin Marinas <catalin.marinas@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Kevin Hilman <khilman@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 4/9] opp: core: Don't warn if required OPP device
does not exist
On 12-10-21, 14:34, Hector Martin wrote:
> The table *is* assigned to a genpd (the memory controller), it's just that
> that genpd isn't actually a parent of the CPU device. Without the patch you
> end up with:
>
> [ 3.040060] cpu cpu4: Failed to set performance rate of cpu4: 0 (-19)
> [ 3.042881] cpu cpu4: Failed to set required opps: -19
> [ 3.045508] cpufreq: __target_index: Failed to change cpu frequency: -19
Hmm, Saravana and Sibi were working on a similar problem earlier and decided to
solve this using devfreq instead. Don't remember the exact series which got
merged for this, Sibi ?
If this part fails, how do you actually set the performance state of the memory
controller's genpd ?
--
viresh
Powered by blists - more mailing lists