[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gVi3U2K-Sj-W0QtBbbEw+HOd3FDSAyL-ugbhuxLeLZUA@mail.gmail.com>
Date: Tue, 21 Feb 2023 16:40:01 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Kazuki Hashimoto <kazukih0205@...il.com>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Sudeep Holla <sudeep.holla@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Hector Martin <marcan@...can.st>,
Sven Peter <sven@...npeter.dev>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>
Subject: Re: [PATCH] PM: s2idle: Don't allow s2idle when cpuidle isn't supported
On Tue, Feb 14, 2023 at 11:04 PM Kazuki Hashimoto <kazukih0205@...il.com> wrote:
>
> s2idle isn't supported on platforms that don't support cpuidle as of
> 31a3409065d1 ("cpuidle / sleep: Do sanity checks in cpuidle_enter_freeze()
> too"), so update the suspend framework to reflect this in order to avoid
> breakages.
Hmm. Doesn't the cpuidle_not_available() check in cpuidle_idle_call()
trigger then?
The commit mentioned above hasn't changed that AFAICS.
Powered by blists - more mailing lists