[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1598943859-21857-1-git-send-email-claude.yen@mediatek.com>
Date: Tue, 1 Sep 2020 15:04:18 +0800
From: Claude Yen <claude.yen@...iatek.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stephen Boyd <swboyd@...omium.org>,
Douglas Anderson <dianders@...omium.org>
CC: <linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <wsd_upstream@...iatek.com>
Subject: [PATCH] PM: s2idle: Introduce syscore callbacks in s2idle flow
This series based on 5.9-rc1
This patch makes s2idle call existing syscore callbacks. Currently,
when s2idle is selected as system suspend method, callbacks hooked
by register_syscore_ops() will not be triggered. This may induce
unexpected results.
For example, sched_clock_suspend() was added to s2idle flow in
commit 3f2552f7e9c5 ("timers/sched_clock: Prevent generic sched_clock
wrap caused by tick_freeze()") to fix clock wrap problem. However,
sched_clock_suspend() is originally registered in syscore callback.
With this patch, if another syscore callback is needed in s2idle,
additional migration effort could be saved.
*** BLURB HERE ***
claude.yen (1):
PM: s2idle: Introduce syscore callbacks in s2idle flow
drivers/cpuidle/cpuidle.c | 36 ++++++++++++++++++++++++++++++++----
kernel/cpu_pm.c | 17 +++++++++++++++++
kernel/time/tick-common.c | 17 ++---------------
3 files changed, 51 insertions(+), 19 deletions(-)
--
1.7.9.5
Powered by blists - more mailing lists