[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2984032.oZIAi2Obeo@aspire.rjw.lan>
Date: Sun, 10 Dec 2017 00:56:50 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Kevin Hilman <khilman@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: [PATCH 1/4] PM / core: Use dev_pm_skip_next_resume_phases() internally
From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
Make the PM core call dev_pm_skip_next_resume_phases() to skip the
"early resume" and "resume" phases of system-wide transitions to the
working state for a given device instead of clearing the relevant
status bits for it directly.
No intentional changes in functionality.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
---
drivers/base/power/main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: linux-pm/drivers/base/power/main.c
===================================================================
--- linux-pm.orig/drivers/base/power/main.c
+++ linux-pm/drivers/base/power/main.c
@@ -609,8 +609,7 @@ static int device_resume_noirq(struct de
* device again.
*/
pm_runtime_set_suspended(dev);
- dev->power.is_late_suspended = false;
- dev->power.is_suspended = false;
+ dev_pm_skip_next_resume_phases(dev);
}
Out:
Powered by blists - more mailing lists