summaryrefslogtreecommitdiffstats
path: root/include/linux/suspend.h
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2019-05-16 06:43:19 -0400
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2019-05-27 04:51:45 -0400
commitbb1869012d7b78d1474808cb4c8bd8b272645876 (patch)
tree1df9a6c5b0a5511970caff3c491de0beac10e579 /include/linux/suspend.h
parent9a51c6b1f9e0239a9435db036b212498a2a3b75c (diff)
ACPI: PM: Call pm_set_suspend_via_firmware() during hibernation
On systems with ACPI platform firmware the last stage of hibernation is analogous to system suspend to S3 (suspend-to-RAM), so it should be handled analogously. In particular, pm_suspend_via_firmware() should return 'true' in that stage to let the callers of it know that control will be passed to the platform firmware going forward, so pm_set_suspend_via_firmware() needs to be called then in analogy with acpi_suspend_begin(). However, the platform hibernation ->begin() callback is invoked during the "freeze" transition (before creating a snapshot image of system memory) as well as during the "hibernate" transition which is the last stage of it and pm_set_suspend_via_firmware() should be invoked by that callback in the latter stage only. In order to implement that redefine the hibernation ->begin() callback to take a pm_message_t argument to indicate which stage of hibernation is taking place and rework acpi_hibernation_begin() and acpi_hibernation_begin_old() to take it into account as needed. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include/linux/suspend.h')
-rw-r--r--include/linux/suspend.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/suspend.h b/include/linux/suspend.h
index 6b3ea9ea6a9e..4a2ffd678887 100644
--- a/include/linux/suspend.h
+++ b/include/linux/suspend.h
@@ -359,7 +359,7 @@ extern void mark_free_pages(struct zone *zone);
359 * platforms which require special recovery actions in that situation. 359 * platforms which require special recovery actions in that situation.
360 */ 360 */
361struct platform_hibernation_ops { 361struct platform_hibernation_ops {
362 int (*begin)(void); 362 int (*begin)(pm_message_t stage);
363 void (*end)(void); 363 void (*end)(void);
364 int (*pre_snapshot)(void); 364 int (*pre_snapshot)(void);
365 void (*finish)(void); 365 void (*finish)(void);