2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* kernel/power/disk.c - Suspend-to-disk support.
|
|
|
|
*
|
|
|
|
* Copyright (c) 2003 Patrick Mochel
|
|
|
|
* Copyright (c) 2003 Open Source Development Lab
|
|
|
|
* Copyright (c) 2004 Pavel Machek <pavel@suse.cz>
|
|
|
|
*
|
|
|
|
* This file is released under the GPLv2.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/suspend.h>
|
|
|
|
#include <linux/syscalls.h>
|
|
|
|
#include <linux/reboot.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/device.h>
|
2008-10-15 23:01:21 -06:00
|
|
|
#include <linux/kmod.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/fs.h>
|
2005-07-12 14:58:07 -06:00
|
|
|
#include <linux/mount.h>
|
2005-09-22 22:43:46 -06:00
|
|
|
#include <linux/pm.h>
|
2006-10-11 02:20:45 -06:00
|
|
|
#include <linux/console.h>
|
2006-09-26 00:32:48 -06:00
|
|
|
#include <linux/cpu.h>
|
2006-12-06 21:34:23 -07:00
|
|
|
#include <linux/freezer.h>
|
2005-07-12 14:58:07 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
#include "power.h"
|
|
|
|
|
|
|
|
|
|
|
|
static int noresume = 0;
|
2008-02-04 23:30:06 -07:00
|
|
|
static char resume_file[256] = CONFIG_PM_STD_PARTITION;
|
2005-04-16 16:20:36 -06:00
|
|
|
dev_t swsusp_resume_device;
|
2006-12-06 21:34:12 -07:00
|
|
|
sector_t swsusp_resume_block;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-05-09 03:33:18 -06:00
|
|
|
enum {
|
|
|
|
HIBERNATION_INVALID,
|
|
|
|
HIBERNATION_PLATFORM,
|
|
|
|
HIBERNATION_TEST,
|
|
|
|
HIBERNATION_TESTPROC,
|
|
|
|
HIBERNATION_SHUTDOWN,
|
|
|
|
HIBERNATION_REBOOT,
|
|
|
|
/* keep last */
|
|
|
|
__HIBERNATION_AFTER_LAST
|
|
|
|
};
|
|
|
|
#define HIBERNATION_MAX (__HIBERNATION_AFTER_LAST-1)
|
|
|
|
#define HIBERNATION_FIRST (HIBERNATION_INVALID + 1)
|
|
|
|
|
|
|
|
static int hibernation_mode = HIBERNATION_SHUTDOWN;
|
|
|
|
|
2007-10-18 04:04:43 -06:00
|
|
|
static struct platform_hibernation_ops *hibernation_ops;
|
2007-05-09 03:33:18 -06:00
|
|
|
|
|
|
|
/**
|
|
|
|
* hibernation_set_ops - set the global hibernate operations
|
|
|
|
* @ops: the hibernation operations to use in subsequent hibernation transitions
|
|
|
|
*/
|
|
|
|
|
2007-10-18 04:04:43 -06:00
|
|
|
void hibernation_set_ops(struct platform_hibernation_ops *ops)
|
2007-05-09 03:33:18 -06:00
|
|
|
{
|
2008-01-07 16:08:44 -07:00
|
|
|
if (ops && !(ops->begin && ops->end && ops->pre_snapshot
|
|
|
|
&& ops->prepare && ops->finish && ops->enter && ops->pre_restore
|
2007-10-18 04:04:42 -06:00
|
|
|
&& ops->restore_cleanup)) {
|
2007-05-09 03:33:18 -06:00
|
|
|
WARN_ON(1);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
mutex_lock(&pm_mutex);
|
|
|
|
hibernation_ops = ops;
|
|
|
|
if (ops)
|
|
|
|
hibernation_mode = HIBERNATION_PLATFORM;
|
|
|
|
else if (hibernation_mode == HIBERNATION_PLATFORM)
|
|
|
|
hibernation_mode = HIBERNATION_SHUTDOWN;
|
|
|
|
|
|
|
|
mutex_unlock(&pm_mutex);
|
|
|
|
}
|
|
|
|
|
2009-01-19 12:54:54 -07:00
|
|
|
static bool entering_platform_hibernation;
|
|
|
|
|
|
|
|
bool system_entering_hibernation(void)
|
|
|
|
{
|
|
|
|
return entering_platform_hibernation;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(system_entering_hibernation);
|
|
|
|
|
2007-11-19 15:42:31 -07:00
|
|
|
#ifdef CONFIG_PM_DEBUG
|
|
|
|
static void hibernation_debug_sleep(void)
|
|
|
|
{
|
|
|
|
printk(KERN_INFO "hibernation debug: Waiting for 5 seconds.\n");
|
|
|
|
mdelay(5000);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int hibernation_testmode(int mode)
|
|
|
|
{
|
|
|
|
if (hibernation_mode == mode) {
|
|
|
|
hibernation_debug_sleep();
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int hibernation_test(int level)
|
|
|
|
{
|
|
|
|
if (pm_test_level == level) {
|
|
|
|
hibernation_debug_sleep();
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
#else /* !CONFIG_PM_DEBUG */
|
|
|
|
static int hibernation_testmode(int mode) { return 0; }
|
|
|
|
static int hibernation_test(int level) { return 0; }
|
|
|
|
#endif /* !CONFIG_PM_DEBUG */
|
|
|
|
|
2007-10-18 04:04:42 -06:00
|
|
|
/**
|
2008-01-07 16:08:44 -07:00
|
|
|
* platform_begin - tell the platform driver that we're starting
|
2007-10-18 04:04:42 -06:00
|
|
|
* hibernation
|
|
|
|
*/
|
|
|
|
|
2008-01-07 16:08:44 -07:00
|
|
|
static int platform_begin(int platform_mode)
|
2007-10-18 04:04:42 -06:00
|
|
|
{
|
|
|
|
return (platform_mode && hibernation_ops) ?
|
2008-01-07 16:08:44 -07:00
|
|
|
hibernation_ops->begin() : 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* platform_end - tell the platform driver that we've entered the
|
|
|
|
* working state
|
|
|
|
*/
|
|
|
|
|
|
|
|
static void platform_end(int platform_mode)
|
|
|
|
{
|
|
|
|
if (platform_mode && hibernation_ops)
|
|
|
|
hibernation_ops->end();
|
2007-10-18 04:04:42 -06:00
|
|
|
}
|
2007-05-09 03:33:18 -06:00
|
|
|
|
2006-12-06 21:34:21 -07:00
|
|
|
/**
|
2007-10-18 04:04:42 -06:00
|
|
|
* platform_pre_snapshot - prepare the machine for hibernation using the
|
2006-12-06 21:34:21 -07:00
|
|
|
* platform driver if so configured and return an error code if it fails
|
|
|
|
*/
|
|
|
|
|
2007-10-18 04:04:42 -06:00
|
|
|
static int platform_pre_snapshot(int platform_mode)
|
2006-12-06 21:34:21 -07:00
|
|
|
{
|
2007-07-19 02:47:29 -06:00
|
|
|
return (platform_mode && hibernation_ops) ?
|
2007-10-18 04:04:42 -06:00
|
|
|
hibernation_ops->pre_snapshot() : 0;
|
2007-05-09 03:33:18 -06:00
|
|
|
}
|
2006-12-06 21:34:21 -07:00
|
|
|
|
2007-10-18 04:04:55 -06:00
|
|
|
/**
|
|
|
|
* platform_leave - prepare the machine for switching to the normal mode
|
|
|
|
* of operation using the platform driver (called with interrupts disabled)
|
|
|
|
*/
|
|
|
|
|
|
|
|
static void platform_leave(int platform_mode)
|
|
|
|
{
|
|
|
|
if (platform_mode && hibernation_ops)
|
|
|
|
hibernation_ops->leave();
|
|
|
|
}
|
|
|
|
|
2007-05-09 03:33:18 -06:00
|
|
|
/**
|
|
|
|
* platform_finish - switch the machine to the normal mode of operation
|
|
|
|
* using the platform driver (must be called after platform_prepare())
|
|
|
|
*/
|
|
|
|
|
2007-07-19 02:47:29 -06:00
|
|
|
static void platform_finish(int platform_mode)
|
2007-05-09 03:33:18 -06:00
|
|
|
{
|
2007-07-19 02:47:29 -06:00
|
|
|
if (platform_mode && hibernation_ops)
|
2007-05-09 03:33:18 -06:00
|
|
|
hibernation_ops->finish();
|
2006-12-06 21:34:21 -07:00
|
|
|
}
|
|
|
|
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
/**
|
|
|
|
* platform_pre_restore - prepare the platform for the restoration from a
|
|
|
|
* hibernation image. If the restore fails after this function has been
|
|
|
|
* called, platform_restore_cleanup() must be called.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int platform_pre_restore(int platform_mode)
|
|
|
|
{
|
|
|
|
return (platform_mode && hibernation_ops) ?
|
|
|
|
hibernation_ops->pre_restore() : 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* platform_restore_cleanup - switch the platform to the normal mode of
|
|
|
|
* operation after a failing restore. If platform_pre_restore() has been
|
|
|
|
* called before the failing restore, this function must be called too,
|
|
|
|
* regardless of the result of platform_pre_restore().
|
|
|
|
*/
|
|
|
|
|
|
|
|
static void platform_restore_cleanup(int platform_mode)
|
|
|
|
{
|
|
|
|
if (platform_mode && hibernation_ops)
|
|
|
|
hibernation_ops->restore_cleanup();
|
|
|
|
}
|
|
|
|
|
2008-06-12 15:24:06 -06:00
|
|
|
/**
|
|
|
|
* platform_recover - recover the platform from a failure to suspend
|
|
|
|
* devices.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static void platform_recover(int platform_mode)
|
|
|
|
{
|
|
|
|
if (platform_mode && hibernation_ops && hibernation_ops->recover)
|
|
|
|
hibernation_ops->recover();
|
|
|
|
}
|
|
|
|
|
2007-10-18 04:04:55 -06:00
|
|
|
/**
|
|
|
|
* create_image - freeze devices that need to be frozen with interrupts
|
|
|
|
* off, create the hibernation image and thaw those devices. Control
|
|
|
|
* reappears in this routine after a restore.
|
|
|
|
*/
|
|
|
|
|
2008-02-04 23:30:06 -07:00
|
|
|
static int create_image(int platform_mode)
|
2007-10-18 04:04:55 -06:00
|
|
|
{
|
|
|
|
int error;
|
|
|
|
|
|
|
|
error = arch_prepare_suspend();
|
|
|
|
if (error)
|
|
|
|
return error;
|
|
|
|
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_pm_lock();
|
2007-10-18 04:04:55 -06:00
|
|
|
local_irq_disable();
|
|
|
|
/* At this point, device_suspend() has been called, but *not*
|
|
|
|
* device_power_down(). We *must* call device_power_down() now.
|
|
|
|
* Otherwise, drivers for some devices (e.g. interrupt controllers)
|
|
|
|
* become desynchronized with the actual state of the hardware
|
|
|
|
* at resume time, and evil weirdness ensues.
|
|
|
|
*/
|
|
|
|
error = device_power_down(PMSG_FREEZE);
|
|
|
|
if (error) {
|
2007-12-07 18:09:43 -07:00
|
|
|
printk(KERN_ERR "PM: Some devices failed to power down, "
|
|
|
|
"aborting hibernation\n");
|
2007-10-18 04:04:55 -06:00
|
|
|
goto Enable_irqs;
|
|
|
|
}
|
2009-02-22 10:38:50 -07:00
|
|
|
sysdev_suspend(PMSG_FREEZE);
|
|
|
|
if (error) {
|
|
|
|
printk(KERN_ERR "PM: Some devices failed to power down, "
|
|
|
|
"aborting hibernation\n");
|
|
|
|
goto Power_up_devices;
|
|
|
|
}
|
2007-10-18 04:04:55 -06:00
|
|
|
|
2007-11-19 15:42:31 -07:00
|
|
|
if (hibernation_test(TEST_CORE))
|
|
|
|
goto Power_up;
|
|
|
|
|
|
|
|
in_suspend = 1;
|
2007-10-18 04:04:55 -06:00
|
|
|
save_processor_state();
|
|
|
|
error = swsusp_arch_suspend();
|
|
|
|
if (error)
|
2007-12-07 18:09:43 -07:00
|
|
|
printk(KERN_ERR "PM: Error %d creating hibernation image\n",
|
|
|
|
error);
|
2007-10-18 04:04:55 -06:00
|
|
|
/* Restore control flow magically appears here */
|
|
|
|
restore_processor_state();
|
|
|
|
if (!in_suspend)
|
|
|
|
platform_leave(platform_mode);
|
2007-11-19 15:42:31 -07:00
|
|
|
Power_up:
|
2009-02-22 10:38:50 -07:00
|
|
|
sysdev_resume();
|
2007-10-18 04:04:55 -06:00
|
|
|
/* NOTE: device_power_up() is just a resume() for devices
|
|
|
|
* that suspended with irqs off ... no overall powerup.
|
|
|
|
*/
|
2009-02-22 10:38:50 -07:00
|
|
|
Power_up_devices:
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_power_up(in_suspend ?
|
|
|
|
(error ? PMSG_RECOVER : PMSG_THAW) : PMSG_RESTORE);
|
2007-10-18 04:04:55 -06:00
|
|
|
Enable_irqs:
|
|
|
|
local_irq_enable();
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_pm_unlock();
|
2007-10-18 04:04:55 -06:00
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
2007-07-19 02:47:29 -06:00
|
|
|
/**
|
|
|
|
* hibernation_snapshot - quiesce devices and create the hibernation
|
|
|
|
* snapshot image.
|
|
|
|
* @platform_mode - if set, use the platform driver, if available, to
|
|
|
|
* prepare the platform frimware for the power transition.
|
|
|
|
*
|
|
|
|
* Must be called with pm_mutex held
|
|
|
|
*/
|
|
|
|
|
|
|
|
int hibernation_snapshot(int platform_mode)
|
|
|
|
{
|
2008-11-23 02:37:12 -07:00
|
|
|
int error;
|
2007-07-19 02:47:29 -06:00
|
|
|
|
2008-10-26 13:50:26 -06:00
|
|
|
error = platform_begin(platform_mode);
|
2007-07-19 02:47:29 -06:00
|
|
|
if (error)
|
2007-07-19 02:47:31 -06:00
|
|
|
return error;
|
2007-07-19 02:47:29 -06:00
|
|
|
|
2008-10-26 13:50:26 -06:00
|
|
|
/* Free memory before shutting down devices. */
|
|
|
|
error = swsusp_shrink_memory();
|
2007-10-18 04:04:42 -06:00
|
|
|
if (error)
|
2008-01-07 16:08:44 -07:00
|
|
|
goto Close;
|
2007-10-18 04:04:42 -06:00
|
|
|
|
2007-07-19 02:47:29 -06:00
|
|
|
suspend_console();
|
|
|
|
error = device_suspend(PMSG_FREEZE);
|
2007-07-19 02:47:31 -06:00
|
|
|
if (error)
|
2008-06-12 15:24:06 -06:00
|
|
|
goto Recover_platform;
|
2007-07-19 02:47:31 -06:00
|
|
|
|
2007-11-19 15:42:31 -07:00
|
|
|
if (hibernation_test(TEST_DEVICES))
|
2008-06-12 15:24:06 -06:00
|
|
|
goto Recover_platform;
|
2007-07-19 02:47:29 -06:00
|
|
|
|
2007-11-19 15:42:31 -07:00
|
|
|
error = platform_pre_snapshot(platform_mode);
|
|
|
|
if (error || hibernation_test(TEST_PLATFORM))
|
|
|
|
goto Finish;
|
|
|
|
|
2007-07-19 02:47:29 -06:00
|
|
|
error = disable_nonboot_cpus();
|
|
|
|
if (!error) {
|
2007-11-19 15:42:31 -07:00
|
|
|
if (hibernation_test(TEST_CPUS))
|
|
|
|
goto Enable_cpus;
|
|
|
|
|
|
|
|
if (hibernation_testmode(HIBERNATION_TEST))
|
|
|
|
goto Enable_cpus;
|
|
|
|
|
|
|
|
error = create_image(platform_mode);
|
|
|
|
/* Control returns here after successful restore */
|
2007-07-19 02:47:29 -06:00
|
|
|
}
|
2007-11-19 15:42:31 -07:00
|
|
|
Enable_cpus:
|
2007-07-19 02:47:29 -06:00
|
|
|
enable_nonboot_cpus();
|
2007-11-19 15:42:31 -07:00
|
|
|
Finish:
|
2007-07-19 02:47:29 -06:00
|
|
|
platform_finish(platform_mode);
|
2007-11-19 15:42:31 -07:00
|
|
|
Resume_devices:
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_resume(in_suspend ?
|
|
|
|
(error ? PMSG_RECOVER : PMSG_THAW) : PMSG_RESTORE);
|
2007-07-19 02:47:29 -06:00
|
|
|
resume_console();
|
2008-01-07 16:08:44 -07:00
|
|
|
Close:
|
|
|
|
platform_end(platform_mode);
|
2007-07-19 02:47:29 -06:00
|
|
|
return error;
|
2008-06-12 15:24:06 -06:00
|
|
|
|
|
|
|
Recover_platform:
|
|
|
|
platform_recover(platform_mode);
|
|
|
|
goto Resume_devices;
|
2007-07-19 02:47:29 -06:00
|
|
|
}
|
|
|
|
|
2007-12-07 18:04:21 -07:00
|
|
|
/**
|
|
|
|
* resume_target_kernel - prepare devices that need to be suspended with
|
|
|
|
* interrupts off, restore the contents of highmem that have not been
|
|
|
|
* restored yet from the image and run the low level code that will restore
|
|
|
|
* the remaining contents of memory and switch to the just restored target
|
|
|
|
* kernel.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int resume_target_kernel(void)
|
|
|
|
{
|
|
|
|
int error;
|
|
|
|
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_pm_lock();
|
2007-12-07 18:04:21 -07:00
|
|
|
local_irq_disable();
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
error = device_power_down(PMSG_QUIESCE);
|
2007-12-07 18:04:21 -07:00
|
|
|
if (error) {
|
2007-12-07 18:09:43 -07:00
|
|
|
printk(KERN_ERR "PM: Some devices failed to power down, "
|
2007-12-07 18:04:21 -07:00
|
|
|
"aborting resume\n");
|
|
|
|
goto Enable_irqs;
|
|
|
|
}
|
2009-02-22 10:38:50 -07:00
|
|
|
sysdev_suspend(PMSG_QUIESCE);
|
2007-12-07 18:04:21 -07:00
|
|
|
/* We'll ignore saved state, but this gets preempt count (etc) right */
|
|
|
|
save_processor_state();
|
|
|
|
error = restore_highmem();
|
|
|
|
if (!error) {
|
|
|
|
error = swsusp_arch_resume();
|
|
|
|
/*
|
|
|
|
* The code below is only ever reached in case of a failure.
|
|
|
|
* Otherwise execution continues at place where
|
|
|
|
* swsusp_arch_suspend() was called
|
|
|
|
*/
|
|
|
|
BUG_ON(!error);
|
|
|
|
/* This call to restore_highmem() undos the previous one */
|
|
|
|
restore_highmem();
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* The only reason why swsusp_arch_resume() can fail is memory being
|
|
|
|
* very tight, so we have to free it as soon as we can to avoid
|
|
|
|
* subsequent failures
|
|
|
|
*/
|
|
|
|
swsusp_free();
|
|
|
|
restore_processor_state();
|
|
|
|
touch_softlockup_watchdog();
|
2009-02-22 10:38:50 -07:00
|
|
|
sysdev_resume();
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_power_up(PMSG_RECOVER);
|
2007-12-07 18:04:21 -07:00
|
|
|
Enable_irqs:
|
|
|
|
local_irq_enable();
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_pm_unlock();
|
2007-12-07 18:04:21 -07:00
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
2007-07-19 02:47:29 -06:00
|
|
|
/**
|
|
|
|
* hibernation_restore - quiesce devices and restore the hibernation
|
|
|
|
* snapshot image. If successful, control returns in hibernation_snaphot()
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
* @platform_mode - if set, use the platform driver, if available, to
|
|
|
|
* prepare the platform frimware for the transition.
|
2007-07-19 02:47:29 -06:00
|
|
|
*
|
|
|
|
* Must be called with pm_mutex held
|
|
|
|
*/
|
|
|
|
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
int hibernation_restore(int platform_mode)
|
2007-07-19 02:47:29 -06:00
|
|
|
{
|
2008-11-23 02:37:12 -07:00
|
|
|
int error;
|
2007-07-19 02:47:29 -06:00
|
|
|
|
|
|
|
pm_prepare_console();
|
|
|
|
suspend_console();
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
error = device_suspend(PMSG_QUIESCE);
|
2007-07-19 02:47:29 -06:00
|
|
|
if (error)
|
|
|
|
goto Finish;
|
|
|
|
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
error = platform_pre_restore(platform_mode);
|
|
|
|
if (!error) {
|
|
|
|
error = disable_nonboot_cpus();
|
|
|
|
if (!error)
|
2007-12-07 18:04:21 -07:00
|
|
|
error = resume_target_kernel();
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
enable_nonboot_cpus();
|
|
|
|
}
|
|
|
|
platform_restore_cleanup(platform_mode);
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_resume(PMSG_RECOVER);
|
2007-07-19 02:47:31 -06:00
|
|
|
Finish:
|
2007-07-19 02:47:29 -06:00
|
|
|
resume_console();
|
|
|
|
pm_restore_console();
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hibernation_platform_enter - enter the hibernation state using the
|
|
|
|
* platform driver (if available)
|
|
|
|
*/
|
|
|
|
|
|
|
|
int hibernation_platform_enter(void)
|
|
|
|
{
|
2008-11-23 02:37:12 -07:00
|
|
|
int error;
|
2007-07-19 02:47:31 -06:00
|
|
|
|
2007-10-18 04:04:56 -06:00
|
|
|
if (!hibernation_ops)
|
|
|
|
return -ENOSYS;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We have cancelled the power transition by running
|
|
|
|
* hibernation_ops->finish() before saving the image, so we should let
|
|
|
|
* the firmware know that we're going to enter the sleep state after all
|
|
|
|
*/
|
2008-01-07 16:08:44 -07:00
|
|
|
error = hibernation_ops->begin();
|
2007-10-18 04:04:56 -06:00
|
|
|
if (error)
|
2008-01-07 16:08:44 -07:00
|
|
|
goto Close;
|
2007-10-18 04:04:56 -06:00
|
|
|
|
2009-01-19 12:54:54 -07:00
|
|
|
entering_platform_hibernation = true;
|
2007-10-18 04:04:56 -06:00
|
|
|
suspend_console();
|
2008-02-23 11:13:25 -07:00
|
|
|
error = device_suspend(PMSG_HIBERNATE);
|
2008-06-12 15:24:06 -06:00
|
|
|
if (error) {
|
|
|
|
if (hibernation_ops->recover)
|
|
|
|
hibernation_ops->recover();
|
|
|
|
goto Resume_devices;
|
|
|
|
}
|
2007-10-18 04:04:56 -06:00
|
|
|
|
|
|
|
error = hibernation_ops->prepare();
|
|
|
|
if (error)
|
|
|
|
goto Resume_devices;
|
|
|
|
|
|
|
|
error = disable_nonboot_cpus();
|
|
|
|
if (error)
|
|
|
|
goto Finish;
|
|
|
|
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_pm_lock();
|
2007-10-18 04:04:56 -06:00
|
|
|
local_irq_disable();
|
2008-02-23 11:13:25 -07:00
|
|
|
error = device_power_down(PMSG_HIBERNATE);
|
2007-10-18 04:04:56 -06:00
|
|
|
if (!error) {
|
2009-02-22 10:38:50 -07:00
|
|
|
sysdev_suspend(PMSG_HIBERNATE);
|
2007-10-18 04:04:56 -06:00
|
|
|
hibernation_ops->enter();
|
|
|
|
/* We should never get here */
|
|
|
|
while (1);
|
2007-07-19 02:47:29 -06:00
|
|
|
}
|
2007-10-18 04:04:56 -06:00
|
|
|
local_irq_enable();
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_pm_unlock();
|
2007-10-18 04:04:56 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We don't need to reenable the nonboot CPUs or resume consoles, since
|
|
|
|
* the system is going to be halted anyway.
|
|
|
|
*/
|
|
|
|
Finish:
|
|
|
|
hibernation_ops->finish();
|
|
|
|
Resume_devices:
|
2009-01-19 12:54:54 -07:00
|
|
|
entering_platform_hibernation = false;
|
Introduce new top level suspend and hibernation callbacks
Introduce 'struct pm_ops' and 'struct pm_ext_ops' ('ext' meaning
'extended') representing suspend and hibernation operations for bus
types, device classes, device types and device drivers.
Modify the PM core to use 'struct pm_ops' and 'struct pm_ext_ops'
objects, if defined, instead of the ->suspend(), ->resume(),
->suspend_late(), and ->resume_early() callbacks (the old callbacks
will be considered as legacy and gradually phased out).
The main purpose of doing this is to separate suspend (aka S2RAM and
standby) callbacks from hibernation callbacks in such a way that the
new callbacks won't take arguments and the semantics of each of them
will be clearly specified. This has been requested for multiple
times by many people, including Linus himself, and the reason is that
within the current scheme if ->resume() is called, for example, it's
difficult to say why it's been called (ie. is it a resume from RAM or
from hibernation or a suspend/hibernation failure etc.?).
The second purpose is to make the suspend/hibernation callbacks more
flexible so that device drivers can handle more than they can within
the current scheme. For example, some drivers may need to prevent
new children of the device from being registered before their
->suspend() callbacks are executed or they may want to carry out some
operations requiring the availability of some other devices, not
directly bound via the parent-child relationship, in order to prepare
for the execution of ->suspend(), etc.
Ultimately, we'd like to stop using the freezing of tasks for suspend
and therefore the drivers' suspend/hibernation code will have to take
care of the handling of the user space during suspend/hibernation.
That, in turn, would be difficult within the current scheme, without
the new ->prepare() and ->complete() callbacks.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2008-05-20 15:00:01 -06:00
|
|
|
device_resume(PMSG_RESTORE);
|
2007-10-18 04:04:56 -06:00
|
|
|
resume_console();
|
2008-01-07 16:08:44 -07:00
|
|
|
Close:
|
|
|
|
hibernation_ops->end();
|
2007-07-19 02:47:31 -06:00
|
|
|
return error;
|
2007-07-19 02:47:29 -06:00
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/**
|
2007-05-09 03:33:18 -06:00
|
|
|
* power_down - Shut the machine down for hibernation.
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
* Use the platform driver, if configured so; otherwise try
|
|
|
|
* to power off or reboot.
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
static void power_down(void)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2007-05-09 03:33:18 -06:00
|
|
|
switch (hibernation_mode) {
|
|
|
|
case HIBERNATION_TEST:
|
|
|
|
case HIBERNATION_TESTPROC:
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
break;
|
2007-05-09 03:33:18 -06:00
|
|
|
case HIBERNATION_REBOOT:
|
2005-07-26 12:01:17 -06:00
|
|
|
kernel_restart(NULL);
|
2005-04-16 16:20:36 -06:00
|
|
|
break;
|
2007-05-09 03:33:18 -06:00
|
|
|
case HIBERNATION_PLATFORM:
|
2007-07-19 02:47:29 -06:00
|
|
|
hibernation_platform_enter();
|
2007-10-18 04:04:56 -06:00
|
|
|
case HIBERNATION_SHUTDOWN:
|
|
|
|
kernel_power_off();
|
|
|
|
break;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2005-07-26 12:01:17 -06:00
|
|
|
kernel_halt();
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
/*
|
|
|
|
* Valid image is on the disk, if we continue we risk serious data
|
|
|
|
* corruption after resume.
|
|
|
|
*/
|
2007-12-07 18:09:43 -07:00
|
|
|
printk(KERN_CRIT "PM: Please power down manually\n");
|
2005-04-16 16:20:36 -06:00
|
|
|
while(1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int prepare_processes(void)
|
|
|
|
{
|
2006-11-02 23:07:19 -07:00
|
|
|
int error = 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
if (freeze_processes()) {
|
|
|
|
error = -EBUSY;
|
2008-01-10 17:25:21 -07:00
|
|
|
thaw_processes();
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2005-06-25 15:55:06 -06:00
|
|
|
return error;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2007-05-09 03:33:18 -06:00
|
|
|
* hibernate - The granpappy of the built-in hibernation management
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
|
2007-05-09 03:33:18 -06:00
|
|
|
int hibernate(void)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
int error;
|
|
|
|
|
2007-07-19 02:47:36 -06:00
|
|
|
mutex_lock(&pm_mutex);
|
2007-05-06 15:50:45 -06:00
|
|
|
/* The snapshot device should not be opened while we're running */
|
2007-07-19 02:47:36 -06:00
|
|
|
if (!atomic_add_unless(&snapshot_device_available, -1, 0)) {
|
|
|
|
error = -EBUSY;
|
|
|
|
goto Unlock;
|
|
|
|
}
|
|
|
|
|
2008-01-10 17:25:21 -07:00
|
|
|
pm_prepare_console();
|
2007-07-19 02:47:36 -06:00
|
|
|
error = pm_notifier_call_chain(PM_HIBERNATION_PREPARE);
|
|
|
|
if (error)
|
|
|
|
goto Exit;
|
2007-05-06 15:50:45 -06:00
|
|
|
|
2008-10-15 23:01:21 -06:00
|
|
|
error = usermodehelper_disable();
|
|
|
|
if (error)
|
|
|
|
goto Exit;
|
|
|
|
|
2007-05-06 15:50:45 -06:00
|
|
|
/* Allocate memory management structures */
|
|
|
|
error = create_basic_memory_bitmaps();
|
|
|
|
if (error)
|
|
|
|
goto Exit;
|
|
|
|
|
2007-12-07 18:09:43 -07:00
|
|
|
printk(KERN_INFO "PM: Syncing filesystems ... ");
|
2007-10-18 04:04:44 -06:00
|
|
|
sys_sync();
|
|
|
|
printk("done.\n");
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
error = prepare_processes();
|
2005-06-25 15:55:06 -06:00
|
|
|
if (error)
|
2007-05-06 15:50:45 -06:00
|
|
|
goto Finish;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-11-19 15:42:31 -07:00
|
|
|
if (hibernation_test(TEST_FREEZER))
|
2007-02-10 02:43:32 -07:00
|
|
|
goto Thaw;
|
2007-11-19 15:42:31 -07:00
|
|
|
|
|
|
|
if (hibernation_testmode(HIBERNATION_TESTPROC))
|
|
|
|
goto Thaw;
|
|
|
|
|
2007-07-19 02:47:29 -06:00
|
|
|
error = hibernation_snapshot(hibernation_mode == HIBERNATION_PLATFORM);
|
|
|
|
if (in_suspend && !error) {
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
unsigned int flags = 0;
|
|
|
|
|
|
|
|
if (hibernation_mode == HIBERNATION_PLATFORM)
|
|
|
|
flags |= SF_PLATFORM_MODE;
|
2005-04-16 16:20:36 -06:00
|
|
|
pr_debug("PM: writing image.\n");
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
error = swsusp_write(flags);
|
2007-07-19 02:47:29 -06:00
|
|
|
swsusp_free();
|
2005-04-16 16:20:36 -06:00
|
|
|
if (!error)
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
power_down();
|
2006-11-02 23:07:19 -07:00
|
|
|
} else {
|
2005-04-16 16:20:36 -06:00
|
|
|
pr_debug("PM: Image restored successfully.\n");
|
2007-07-19 02:47:29 -06:00
|
|
|
swsusp_free();
|
2006-11-02 23:07:19 -07:00
|
|
|
}
|
|
|
|
Thaw:
|
2008-01-10 17:25:21 -07:00
|
|
|
thaw_processes();
|
2007-05-06 15:50:45 -06:00
|
|
|
Finish:
|
|
|
|
free_basic_memory_bitmaps();
|
2008-10-15 23:01:21 -06:00
|
|
|
usermodehelper_enable();
|
2007-05-06 15:50:45 -06:00
|
|
|
Exit:
|
2007-07-19 02:47:36 -06:00
|
|
|
pm_notifier_call_chain(PM_POST_HIBERNATION);
|
2008-01-10 17:25:21 -07:00
|
|
|
pm_restore_console();
|
2007-05-06 15:50:45 -06:00
|
|
|
atomic_inc(&snapshot_device_available);
|
2007-07-19 02:47:36 -06:00
|
|
|
Unlock:
|
|
|
|
mutex_unlock(&pm_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
return error;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
* software_resume - Resume from a saved image.
|
|
|
|
*
|
|
|
|
* Called as a late_initcall (so all devices are discovered and
|
|
|
|
* initialized), we call swsusp to see if we have a saved image or not.
|
|
|
|
* If so, we quiesce devices, the restore the saved image. We will
|
2007-05-09 03:33:18 -06:00
|
|
|
* return above (in hibernate() ) if everything goes well.
|
2005-04-16 16:20:36 -06:00
|
|
|
* Otherwise, we fail gracefully and return to the normally
|
|
|
|
* scheduled program.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int software_resume(void)
|
|
|
|
{
|
|
|
|
int error;
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
unsigned int flags;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2009-02-13 18:00:19 -07:00
|
|
|
/*
|
|
|
|
* If the user said "noresume".. bail out early.
|
|
|
|
*/
|
|
|
|
if (noresume)
|
|
|
|
return 0;
|
|
|
|
|
2007-11-14 18:00:16 -07:00
|
|
|
/*
|
|
|
|
* name_to_dev_t() below takes a sysfs buffer mutex when sysfs
|
|
|
|
* is configured into the kernel. Since the regular hibernate
|
|
|
|
* trigger path is via sysfs which takes a buffer mutex before
|
|
|
|
* calling hibernate functions (which take pm_mutex) this can
|
|
|
|
* cause lockdep to complain about a possible ABBA deadlock
|
|
|
|
* which cannot happen since we're in the boot code here and
|
|
|
|
* sysfs can't be invoked yet. Therefore, we use a subclass
|
|
|
|
* here to avoid lockdep complaining.
|
|
|
|
*/
|
|
|
|
mutex_lock_nested(&pm_mutex, SINGLE_DEPTH_NESTING);
|
2005-07-07 18:56:43 -06:00
|
|
|
if (!swsusp_resume_device) {
|
2005-09-03 16:57:04 -06:00
|
|
|
if (!strlen(resume_file)) {
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_unlock(&pm_mutex);
|
2005-07-07 18:56:43 -06:00
|
|
|
return -ENOENT;
|
2005-09-03 16:57:04 -06:00
|
|
|
}
|
2009-02-13 18:00:19 -07:00
|
|
|
/*
|
|
|
|
* Some device discovery might still be in progress; we need
|
|
|
|
* to wait for this to finish.
|
|
|
|
*/
|
|
|
|
wait_for_device_probe();
|
2005-07-07 18:56:43 -06:00
|
|
|
swsusp_resume_device = name_to_dev_t(resume_file);
|
2007-12-07 18:09:43 -07:00
|
|
|
pr_debug("PM: Resume from partition %s\n", resume_file);
|
2005-07-07 18:56:43 -06:00
|
|
|
} else {
|
2007-12-07 18:09:43 -07:00
|
|
|
pr_debug("PM: Resume from partition %d:%d\n",
|
|
|
|
MAJOR(swsusp_resume_device),
|
|
|
|
MINOR(swsusp_resume_device));
|
2005-07-07 18:56:43 -06:00
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (noresume) {
|
|
|
|
/**
|
2007-12-07 18:06:57 -07:00
|
|
|
* FIXME: If noresume is specified, we need to find the
|
|
|
|
* partition and reset it back to normal swap space.
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_unlock(&pm_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2007-12-07 18:09:43 -07:00
|
|
|
pr_debug("PM: Checking hibernation image.\n");
|
2007-02-10 02:43:32 -07:00
|
|
|
error = swsusp_check();
|
|
|
|
if (error)
|
2007-05-06 15:50:43 -06:00
|
|
|
goto Unlock;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-05-06 15:50:45 -06:00
|
|
|
/* The snapshot device should not be opened while we're running */
|
|
|
|
if (!atomic_add_unless(&snapshot_device_available, -1, 0)) {
|
|
|
|
error = -EBUSY;
|
|
|
|
goto Unlock;
|
|
|
|
}
|
|
|
|
|
2008-01-10 17:25:21 -07:00
|
|
|
pm_prepare_console();
|
2007-11-19 15:38:25 -07:00
|
|
|
error = pm_notifier_call_chain(PM_RESTORE_PREPARE);
|
|
|
|
if (error)
|
|
|
|
goto Finish;
|
|
|
|
|
2008-10-15 23:01:21 -06:00
|
|
|
error = usermodehelper_disable();
|
|
|
|
if (error)
|
|
|
|
goto Finish;
|
|
|
|
|
2007-05-06 15:50:43 -06:00
|
|
|
error = create_basic_memory_bitmaps();
|
|
|
|
if (error)
|
2007-05-06 15:50:45 -06:00
|
|
|
goto Finish;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-05-06 15:50:43 -06:00
|
|
|
pr_debug("PM: Preparing processes for restore.\n");
|
2007-02-10 02:43:32 -07:00
|
|
|
error = prepare_processes();
|
|
|
|
if (error) {
|
2007-10-08 11:21:10 -06:00
|
|
|
swsusp_close(FMODE_READ);
|
2005-06-25 15:55:06 -06:00
|
|
|
goto Done;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2007-12-07 18:09:43 -07:00
|
|
|
pr_debug("PM: Reading hibernation image.\n");
|
2005-04-16 16:20:36 -06:00
|
|
|
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
error = swsusp_read(&flags);
|
2007-02-10 02:43:32 -07:00
|
|
|
if (!error)
|
swsusp: introduce restore platform operations
At least on some machines it is necessary to prepare the ACPI firmware for the
restoration of the system memory state from the hibernation image if the
"platform" mode of hibernation has been used. Namely, in that cases we need
to disable the GPEs before replacing the "boot" kernel with the "frozen"
kernel (cf. http://bugzilla.kernel.org/show_bug.cgi?id=7887). After the
restore they will be re-enabled by hibernation_ops->finish(), but if the
restore fails, they have to be re-enabled by the restore code explicitly.
For this purpose we can introduce two additional hibernation operations,
called pre_restore() and restore_cleanup() and call them from the restore code
path. Still, they should be called if the "platform" mode of hibernation has
been used, so we need to pass the information about the hibernation mode from
the "frozen" kernel to the "boot" kernel in the image header.
Apparently, we can't drop the disabling of GPEs before the restore because of
Bug #7887 . Â We also can't do it unconditionally, because the GPEs wouldn't
have been enabled after a successful restore if the suspend had been done in
the 'shutdown' or 'reboot' mode.
In principle we could (and probably should) unconditionally disable the GPEs
before each snapshot creation *and* before the restore, but then we'd have to
unconditionally enable them after the snapshot creation as well as after the
restore (or restore failure) Â Still, for this purpose we'd need to modify
acpi_enter_sleep_state_prep() and acpi_leave_sleep_state() and we'd have to
introduce some mechanism synchronizing the disablind/enabling of the GPEs with
the device drivers' .suspend()/.resume() routines and with
disable_/enable_nonboot_cpus(). Â However, this would have affected the
suspend (ie. s2ram) code as well as the hibernation, which I'd like to avoid
in this patch series.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-19 02:47:30 -06:00
|
|
|
hibernation_restore(flags & SF_PLATFORM_MODE);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-02-10 02:43:32 -07:00
|
|
|
printk(KERN_ERR "PM: Restore failed, recovering.\n");
|
2007-07-19 02:47:29 -06:00
|
|
|
swsusp_free();
|
2008-01-10 17:25:21 -07:00
|
|
|
thaw_processes();
|
2005-04-16 16:20:36 -06:00
|
|
|
Done:
|
2007-05-06 15:50:43 -06:00
|
|
|
free_basic_memory_bitmaps();
|
2008-10-15 23:01:21 -06:00
|
|
|
usermodehelper_enable();
|
2007-05-06 15:50:45 -06:00
|
|
|
Finish:
|
2007-11-19 15:38:25 -07:00
|
|
|
pm_notifier_call_chain(PM_POST_RESTORE);
|
2008-01-10 17:25:21 -07:00
|
|
|
pm_restore_console();
|
2007-05-06 15:50:45 -06:00
|
|
|
atomic_inc(&snapshot_device_available);
|
2005-09-03 16:57:04 -06:00
|
|
|
/* For success case, the suspend path will release the lock */
|
2007-05-06 15:50:43 -06:00
|
|
|
Unlock:
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_unlock(&pm_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
pr_debug("PM: Resume from disk failed.\n");
|
2007-07-19 02:47:29 -06:00
|
|
|
return error;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
late_initcall(software_resume);
|
|
|
|
|
|
|
|
|
2007-05-09 03:33:18 -06:00
|
|
|
static const char * const hibernation_modes[] = {
|
|
|
|
[HIBERNATION_PLATFORM] = "platform",
|
|
|
|
[HIBERNATION_SHUTDOWN] = "shutdown",
|
|
|
|
[HIBERNATION_REBOOT] = "reboot",
|
|
|
|
[HIBERNATION_TEST] = "test",
|
|
|
|
[HIBERNATION_TESTPROC] = "testproc",
|
2005-04-16 16:20:36 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
2007-05-09 03:33:18 -06:00
|
|
|
* disk - Control hibernation mode
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2007-04-30 16:09:53 -06:00
|
|
|
* Suspend-to-disk can be handled in several ways. We have a few options
|
|
|
|
* for putting the system to sleep - using the platform driver (e.g. ACPI
|
2007-05-09 03:33:18 -06:00
|
|
|
* or other hibernation_ops), powering off the system or rebooting the
|
|
|
|
* system (for testing) as well as the two test modes.
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2007-04-30 16:09:53 -06:00
|
|
|
* The system can support 'platform', and that is known a priori (and
|
2007-05-09 03:33:18 -06:00
|
|
|
* encoded by the presence of hibernation_ops). However, the user may
|
|
|
|
* choose 'shutdown' or 'reboot' as alternatives, as well as one fo the
|
|
|
|
* test modes, 'test' or 'testproc'.
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
|
|
|
* show() will display what the mode is currently set to.
|
|
|
|
* store() will accept one of
|
|
|
|
*
|
|
|
|
* 'platform'
|
|
|
|
* 'shutdown'
|
|
|
|
* 'reboot'
|
2007-04-30 16:09:53 -06:00
|
|
|
* 'test'
|
|
|
|
* 'testproc'
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2007-04-30 16:09:53 -06:00
|
|
|
* It will only change to 'platform' if the system
|
2007-05-09 03:33:18 -06:00
|
|
|
* supports it (as determined by having hibernation_ops).
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
|
2007-11-02 06:47:53 -06:00
|
|
|
static ssize_t disk_show(struct kobject *kobj, struct kobj_attribute *attr,
|
|
|
|
char *buf)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2007-05-06 15:50:50 -06:00
|
|
|
int i;
|
|
|
|
char *start = buf;
|
|
|
|
|
2007-05-09 03:33:18 -06:00
|
|
|
for (i = HIBERNATION_FIRST; i <= HIBERNATION_MAX; i++) {
|
|
|
|
if (!hibernation_modes[i])
|
2007-05-06 15:50:50 -06:00
|
|
|
continue;
|
|
|
|
switch (i) {
|
2007-05-09 03:33:18 -06:00
|
|
|
case HIBERNATION_SHUTDOWN:
|
|
|
|
case HIBERNATION_REBOOT:
|
|
|
|
case HIBERNATION_TEST:
|
|
|
|
case HIBERNATION_TESTPROC:
|
2007-05-06 15:50:50 -06:00
|
|
|
break;
|
2007-05-09 03:33:18 -06:00
|
|
|
case HIBERNATION_PLATFORM:
|
|
|
|
if (hibernation_ops)
|
2007-05-06 15:50:50 -06:00
|
|
|
break;
|
|
|
|
/* not a valid mode, continue with loop */
|
|
|
|
continue;
|
|
|
|
}
|
2007-05-09 03:33:18 -06:00
|
|
|
if (i == hibernation_mode)
|
|
|
|
buf += sprintf(buf, "[%s] ", hibernation_modes[i]);
|
2007-05-06 15:50:50 -06:00
|
|
|
else
|
2007-05-09 03:33:18 -06:00
|
|
|
buf += sprintf(buf, "%s ", hibernation_modes[i]);
|
2007-05-06 15:50:50 -06:00
|
|
|
}
|
|
|
|
buf += sprintf(buf, "\n");
|
|
|
|
return buf-start;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-11-02 06:47:53 -06:00
|
|
|
static ssize_t disk_store(struct kobject *kobj, struct kobj_attribute *attr,
|
|
|
|
const char *buf, size_t n)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
int error = 0;
|
|
|
|
int i;
|
|
|
|
int len;
|
|
|
|
char *p;
|
2007-05-09 03:33:18 -06:00
|
|
|
int mode = HIBERNATION_INVALID;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
p = memchr(buf, '\n', n);
|
|
|
|
len = p ? p - buf : n;
|
|
|
|
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_lock(&pm_mutex);
|
2007-05-09 03:33:18 -06:00
|
|
|
for (i = HIBERNATION_FIRST; i <= HIBERNATION_MAX; i++) {
|
2007-05-16 23:11:19 -06:00
|
|
|
if (len == strlen(hibernation_modes[i])
|
|
|
|
&& !strncmp(buf, hibernation_modes[i], len)) {
|
2005-04-16 16:20:36 -06:00
|
|
|
mode = i;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2007-05-09 03:33:18 -06:00
|
|
|
if (mode != HIBERNATION_INVALID) {
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
switch (mode) {
|
2007-05-09 03:33:18 -06:00
|
|
|
case HIBERNATION_SHUTDOWN:
|
|
|
|
case HIBERNATION_REBOOT:
|
|
|
|
case HIBERNATION_TEST:
|
|
|
|
case HIBERNATION_TESTPROC:
|
|
|
|
hibernation_mode = mode;
|
rework pm_ops pm_disk_mode, kill misuse
This patch series cleans up some misconceptions about pm_ops. Some users of
the pm_ops structure attempt to use it to stop the user from entering suspend
to disk, this, however, is not possible since the user can always use
"shutdown" in /sys/power/disk and then the pm_ops are never invoked. Also,
platforms that don't support suspend to disk simply should not allow
configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
suspend to disk and nothing else, all the other stuff depends on PM).
The pm_ops structure is actually intended to provide a way to enter
platform-defined sleep states (currently supported states are "standby" and
"mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
allows a platform to support a platform specific way to enter low-power mode
once everything has been saved to disk. This is currently only used by ACPI
(S4).
This patch:
The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
seems to understand what it actually does.
This patch clarifies the pm_disk_mode description.
It also removes all the arm and sh users that think they can veto suspend to
disk via pm_ops; not so since the user can always do echo shutdown >
/sys/power/disk, they need to find a better way involving Kconfig or such.
ACPI is the only user left with a non-zero pm_disk_mode.
The patch also sets the default mode to shutdown again, but when a new pm_ops
is registered its pm_disk_mode is selected as default, that way the default
stays for ACPI where it is apparently required.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: David Brownell <david-b@pacbell.net>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: <linux-pm@lists.linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Acked-by: Russell King <rmk@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Acked-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-30 16:09:51 -06:00
|
|
|
break;
|
2007-05-09 03:33:18 -06:00
|
|
|
case HIBERNATION_PLATFORM:
|
|
|
|
if (hibernation_ops)
|
|
|
|
hibernation_mode = mode;
|
2005-04-16 16:20:36 -06:00
|
|
|
else
|
|
|
|
error = -EINVAL;
|
|
|
|
}
|
2007-05-09 03:33:18 -06:00
|
|
|
} else
|
2005-04-16 16:20:36 -06:00
|
|
|
error = -EINVAL;
|
|
|
|
|
2007-05-09 03:33:18 -06:00
|
|
|
if (!error)
|
2007-12-07 18:09:43 -07:00
|
|
|
pr_debug("PM: Hibernation mode set to '%s'\n",
|
2007-05-09 03:33:18 -06:00
|
|
|
hibernation_modes[mode]);
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_unlock(&pm_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
return error ? error : n;
|
|
|
|
}
|
|
|
|
|
|
|
|
power_attr(disk);
|
|
|
|
|
2007-11-02 06:47:53 -06:00
|
|
|
static ssize_t resume_show(struct kobject *kobj, struct kobj_attribute *attr,
|
|
|
|
char *buf)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
return sprintf(buf,"%d:%d\n", MAJOR(swsusp_resume_device),
|
|
|
|
MINOR(swsusp_resume_device));
|
|
|
|
}
|
|
|
|
|
2007-11-02 06:47:53 -06:00
|
|
|
static ssize_t resume_store(struct kobject *kobj, struct kobj_attribute *attr,
|
|
|
|
const char *buf, size_t n)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
unsigned int maj, min;
|
|
|
|
dev_t res;
|
2006-01-06 01:09:50 -07:00
|
|
|
int ret = -EINVAL;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-01-06 01:09:50 -07:00
|
|
|
if (sscanf(buf, "%u:%u", &maj, &min) != 2)
|
|
|
|
goto out;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-01-06 01:09:50 -07:00
|
|
|
res = MKDEV(maj,min);
|
|
|
|
if (maj != MAJOR(res) || min != MINOR(res))
|
|
|
|
goto out;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_lock(&pm_mutex);
|
2006-01-06 01:09:50 -07:00
|
|
|
swsusp_resume_device = res;
|
2006-12-06 21:34:35 -07:00
|
|
|
mutex_unlock(&pm_mutex);
|
2007-12-07 18:09:43 -07:00
|
|
|
printk(KERN_INFO "PM: Starting manual resume from disk\n");
|
2006-01-06 01:09:50 -07:00
|
|
|
noresume = 0;
|
|
|
|
software_resume();
|
|
|
|
ret = n;
|
2006-12-06 21:34:44 -07:00
|
|
|
out:
|
2006-01-06 01:09:50 -07:00
|
|
|
return ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
power_attr(resume);
|
|
|
|
|
2007-11-02 06:47:53 -06:00
|
|
|
static ssize_t image_size_show(struct kobject *kobj, struct kobj_attribute *attr,
|
|
|
|
char *buf)
|
2006-01-06 01:15:56 -07:00
|
|
|
{
|
2006-02-01 04:05:07 -07:00
|
|
|
return sprintf(buf, "%lu\n", image_size);
|
2006-01-06 01:15:56 -07:00
|
|
|
}
|
|
|
|
|
2007-11-02 06:47:53 -06:00
|
|
|
static ssize_t image_size_store(struct kobject *kobj, struct kobj_attribute *attr,
|
|
|
|
const char *buf, size_t n)
|
2006-01-06 01:15:56 -07:00
|
|
|
{
|
2006-02-01 04:05:07 -07:00
|
|
|
unsigned long size;
|
2006-01-06 01:15:56 -07:00
|
|
|
|
2006-02-01 04:05:07 -07:00
|
|
|
if (sscanf(buf, "%lu", &size) == 1) {
|
2006-01-06 01:15:56 -07:00
|
|
|
image_size = size;
|
|
|
|
return n;
|
|
|
|
}
|
|
|
|
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
power_attr(image_size);
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static struct attribute * g[] = {
|
|
|
|
&disk_attr.attr,
|
|
|
|
&resume_attr.attr,
|
2006-01-06 01:15:56 -07:00
|
|
|
&image_size_attr.attr,
|
2005-04-16 16:20:36 -06:00
|
|
|
NULL,
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static struct attribute_group attr_group = {
|
|
|
|
.attrs = g,
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static int __init pm_disk_init(void)
|
|
|
|
{
|
2007-11-27 12:28:26 -07:00
|
|
|
return sysfs_create_group(power_kobj, &attr_group);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
core_initcall(pm_disk_init);
|
|
|
|
|
|
|
|
|
|
|
|
static int __init resume_setup(char *str)
|
|
|
|
{
|
|
|
|
if (noresume)
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
strncpy( resume_file, str, 255 );
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2006-12-06 21:34:12 -07:00
|
|
|
static int __init resume_offset_setup(char *str)
|
|
|
|
{
|
|
|
|
unsigned long long offset;
|
|
|
|
|
|
|
|
if (noresume)
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
if (sscanf(str, "%llu", &offset) == 1)
|
|
|
|
swsusp_resume_block = offset;
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int __init noresume_setup(char *str)
|
|
|
|
{
|
|
|
|
noresume = 1;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
__setup("noresume", noresume_setup);
|
2006-12-06 21:34:12 -07:00
|
|
|
__setup("resume_offset=", resume_offset_setup);
|
2005-04-16 16:20:36 -06:00
|
|
|
__setup("resume=", resume_setup);
|