[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hivxQjA2AZpPxVadzaM7gB+L3BRnoNyeD7hyvr-3Fh4g@mail.gmail.com>
Date: Fri, 23 Apr 2021 14:27:05 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Sowjanya Komatineni <skomatineni@...dia.com>
Cc: Sudeep Holla <sudeep.holla@....com>,
Souvik Chakravarty <souvik.chakravarty@....com>,
Thierry Reding <thierry.reding@...il.com>,
Mark Rutland <mark.rutland@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Jon Hunter <jonathanh@...dia.com>, ksitaraman@...dia.com,
sanjayc@...dia.com,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-tegra <linux-tegra@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>
Subject: Re: [RFC PATCH 0/4] Support for passing runtime state idle time to TF-A
On Thu, Apr 22, 2021 at 10:31 PM Sowjanya Komatineni
<skomatineni@...dia.com> wrote:
>
> Tegra194 and Tegra186 platforms use separate MCE firmware for CPUs which is
> in charge of deciding on state transition based on target state, state idle
> time, and some other Tegra CPU core cluster states information.
>
> Current PSCI specification don't have function defined for passing runtime
> state idle time predicted by governor (based on next events and state target
> residency) to ARM trusted firmware.
Presumably that's because this is not a good idea.
A basic design principle of cpuidle is that it should be possible to
use every governor with every driver and the changes in this series
make the platforms in question only work with menu AFAICS.
Powered by blists - more mailing lists