[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f4c0fba9-6f7d-3bc3-49cc-c239fba975ce@nvidia.com>
Date: Fri, 23 Apr 2021 11:33:41 -0700
From: Sowjanya Komatineni <skomatineni@...dia.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
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 2/4] cpuidle: menu: add idle_time to cpuidle_state
On 4/23/21 5:22 AM, Rafael J. Wysocki wrote:
> On Thu, Apr 22, 2021 at 10:31 PM Sowjanya Komatineni
> <skomatineni@...dia.com> wrote:
>> Some platforms use separate CPU firmware running in background to
>> handle state transitions which may need runtime idle time of the
>> corresponding target state from the kernel.
> How exactly does this work?
>
Explained this as part of other feedback in Patch-0
Thanks
Sowjanya
Powered by blists - more mailing lists