2019-05-27 09:55:05 +03:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-or-later */
|
2005-04-17 02:20:36 +04:00
|
|
|
/*
|
|
|
|
* pm.h - Power management interface
|
|
|
|
*
|
|
|
|
* Copyright (C) 2000 Andrew Henroid
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _LINUX_PM_H
|
|
|
|
#define _LINUX_PM_H
|
|
|
|
|
|
|
|
#include <linux/list.h>
|
2009-08-19 01:38:32 +04:00
|
|
|
#include <linux/workqueue.h>
|
|
|
|
#include <linux/spinlock.h>
|
|
|
|
#include <linux/wait.h>
|
|
|
|
#include <linux/timer.h>
|
2018-12-14 17:22:25 +03:00
|
|
|
#include <linux/hrtimer.h>
|
PM: Asynchronous suspend and resume of devices
Theoretically, the total time of system sleep transitions (suspend
to RAM, hibernation) can be reduced by running suspend and resume
callbacks of device drivers in parallel with each other. However,
there are dependencies between devices such that we're not allowed
to suspend the parent of a device before suspending the device
itself. Analogously, we're not allowed to resume a device before
resuming its parent.
The most straightforward way to take these dependencies into accout
is to start the async threads used for suspending and resuming
devices at the core level, so that async_schedule() is called for
each suspend and resume callback supposed to be executed
asynchronously.
For this purpose, introduce a new device flag, power.async_suspend,
used to mark the devices whose suspend and resume callbacks are to be
executed asynchronously (ie. in parallel with the main suspend/resume
thread and possibly in parallel with each other) and helper function
device_enable_async_suspend() allowing one to set power.async_suspend
for given device (power.async_suspend is unset by default for all
devices). For each device with the power.async_suspend flag set the
PM core will use async_schedule() to execute its suspend and resume
callbacks.
The async threads started for different devices as a result of
calling async_schedule() are synchronized with each other and with
the main suspend/resume thread with the help of completions, in the
following way:
(1) There is a completion, power.completion, for each device object.
(2) Each device's completion is reset before calling async_schedule()
for the device or, in the case of devices with the
power.async_suspend flags unset, before executing the device's
suspend and resume callbacks.
(3) During suspend, right before running the bus type, device type
and device class suspend callbacks for the device, the PM core
waits for the completions of all the device's children to be
completed.
(4) During resume, right before running the bus type, device type and
device class resume callbacks for the device, the PM core waits
for the completion of the device's parent to be completed.
(5) The PM core completes power.completion for each device right
after the bus type, device type and device class suspend (or
resume) callbacks executed for the device have returned.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-01-24 00:23:32 +03:00
|
|
|
#include <linux/completion.h>
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Callbacks for platform drivers to implement.
|
|
|
|
*/
|
|
|
|
extern void (*pm_power_off)(void);
|
2007-07-19 12:47:40 +04:00
|
|
|
extern void (*pm_power_off_prepare)(void);
|
2005-04-17 02:20:36 +04:00
|
|
|
|
2013-02-04 17:37:20 +04:00
|
|
|
struct device; /* we have a circular dep with device.h */
|
|
|
|
#ifdef CONFIG_VT_CONSOLE_SLEEP
|
|
|
|
extern void pm_vt_switch_required(struct device *dev, bool required);
|
|
|
|
extern void pm_vt_switch_unregister(struct device *dev);
|
|
|
|
#else
|
|
|
|
static inline void pm_vt_switch_required(struct device *dev, bool required)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
static inline void pm_vt_switch_unregister(struct device *dev)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
#endif /* CONFIG_VT_CONSOLE_SLEEP */
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
/*
|
|
|
|
* Device power management
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct device;
|
|
|
|
|
2010-09-26 01:35:15 +04:00
|
|
|
#ifdef CONFIG_PM
|
|
|
|
extern const char power_group_name[]; /* = "power" */
|
|
|
|
#else
|
|
|
|
#define power_group_name NULL
|
|
|
|
#endif
|
|
|
|
|
2005-09-04 02:56:57 +04:00
|
|
|
typedef struct pm_message {
|
|
|
|
int event;
|
|
|
|
} pm_message_t;
|
2005-04-17 02:20:36 +04:00
|
|
|
|
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-21 01:00:01 +04:00
|
|
|
/**
|
2017-02-02 03:30:49 +03:00
|
|
|
* struct dev_pm_ops - device PM callbacks.
|
2011-11-24 00:20:32 +04:00
|
|
|
*
|
|
|
|
* @prepare: The principal role of this callback is to prevent new children of
|
|
|
|
* the device from being registered after it has returned (the driver's
|
|
|
|
* subsystem and generally the rest of the kernel is supposed to prevent
|
|
|
|
* new calls to the probe method from being made too once @prepare() has
|
|
|
|
* succeeded). If @prepare() detects a situation it cannot handle (e.g.
|
|
|
|
* registration of a child already in progress), it may return -EAGAIN, so
|
|
|
|
* that the PM core can execute it once again (e.g. after a new child has
|
|
|
|
* been registered) to recover from the race condition.
|
|
|
|
* This method is executed for all kinds of suspend transitions and is
|
|
|
|
* followed by one of the suspend callbacks: @suspend(), @freeze(), or
|
PM / sleep: Mechanism to avoid resuming runtime-suspended devices unnecessarily
Currently, some subsystems (e.g. PCI and the ACPI PM domain) have to
resume all runtime-suspended devices during system suspend, mostly
because those devices may need to be reprogrammed due to different
wakeup settings for system sleep and for runtime PM.
For some devices, though, it's OK to remain in runtime suspend
throughout a complete system suspend/resume cycle (if the device was in
runtime suspend at the start of the cycle). We would like to do this
whenever possible, to avoid the overhead of extra power-up and power-down
events.
However, problems may arise because the device's descendants may require
it to be at full power at various points during the cycle. Therefore the
most straightforward way to do this safely is if the device and all its
descendants can remain runtime suspended until the complete stage of
system resume.
To this end, introduce a new device PM flag, power.direct_complete
and modify the PM core to use that flag as follows.
If the ->prepare() callback of a device returns a positive number,
the PM core will regard that as an indication that it may leave the
device runtime-suspended. It will then check if the system power
transition in progress is a suspend (and not hibernation in particular)
and if the device is, indeed, runtime-suspended. In that case, the PM
core will set the device's power.direct_complete flag. Otherwise it
will clear power.direct_complete for the device and it also will later
clear it for the device's parent (if there's one).
Next, the PM core will not invoke the ->suspend() ->suspend_late(),
->suspend_irq(), ->resume_irq(), ->resume_early(), or ->resume()
callbacks for all devices having power.direct_complete set. It
will invoke their ->complete() callbacks, however, and those
callbacks are then responsible for resuming the devices as
appropriate, if necessary. For example, in some cases they may
need to queue up runtime resume requests for the devices using
pm_request_resume().
Changelog partly based on an Alan Stern's description of the idea
(http://marc.info/?l=linux-pm&m=139940466625569&w=2).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
2014-05-16 04:46:50 +04:00
|
|
|
* @poweroff(). If the transition is a suspend to memory or standby (that
|
|
|
|
* is, not related to hibernation), the return value of @prepare() may be
|
|
|
|
* used to indicate to the PM core to leave the device in runtime suspend
|
|
|
|
* if applicable. Namely, if @prepare() returns a positive number, the PM
|
|
|
|
* core will understand that as a declaration that the device appears to be
|
|
|
|
* runtime-suspended and it may be left in that state during the entire
|
|
|
|
* transition and during the subsequent resume if all of its descendants
|
|
|
|
* are left in runtime suspend too. If that happens, @complete() will be
|
|
|
|
* executed directly after @prepare() and it must ensure the proper
|
|
|
|
* functioning of the device after the system resume.
|
|
|
|
* The PM core executes subsystem-level @prepare() for all devices before
|
|
|
|
* starting to invoke suspend callbacks for any of them, so generally
|
|
|
|
* devices may be assumed to be functional or to respond to runtime resume
|
|
|
|
* requests while @prepare() is being executed. However, device drivers
|
|
|
|
* may NOT assume anything about the availability of user space at that
|
|
|
|
* time and it is NOT valid to request firmware from within @prepare()
|
|
|
|
* (it's too late to do that). It also is NOT valid to allocate
|
2011-11-24 00:20:32 +04:00
|
|
|
* substantial amounts of memory from @prepare() in the GFP_KERNEL mode.
|
|
|
|
* [To work around these limitations, drivers may register suspend and
|
|
|
|
* hibernation notifiers to be executed before the freezing of tasks.]
|
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-21 01:00:01 +04:00
|
|
|
*
|
|
|
|
* @complete: Undo the changes made by @prepare(). This method is executed for
|
|
|
|
* all kinds of resume transitions, following one of the resume callbacks:
|
|
|
|
* @resume(), @thaw(), @restore(). Also called if the state transition
|
2011-11-24 00:20:32 +04:00
|
|
|
* fails before the driver's suspend callback: @suspend(), @freeze() or
|
|
|
|
* @poweroff(), can be executed (e.g. if the suspend callback fails for one
|
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-21 01:00:01 +04:00
|
|
|
* of the other devices that the PM core has unsuccessfully attempted to
|
|
|
|
* suspend earlier).
|
2011-11-24 00:20:32 +04:00
|
|
|
* The PM core executes subsystem-level @complete() after it has executed
|
PM / sleep: Mechanism to avoid resuming runtime-suspended devices unnecessarily
Currently, some subsystems (e.g. PCI and the ACPI PM domain) have to
resume all runtime-suspended devices during system suspend, mostly
because those devices may need to be reprogrammed due to different
wakeup settings for system sleep and for runtime PM.
For some devices, though, it's OK to remain in runtime suspend
throughout a complete system suspend/resume cycle (if the device was in
runtime suspend at the start of the cycle). We would like to do this
whenever possible, to avoid the overhead of extra power-up and power-down
events.
However, problems may arise because the device's descendants may require
it to be at full power at various points during the cycle. Therefore the
most straightforward way to do this safely is if the device and all its
descendants can remain runtime suspended until the complete stage of
system resume.
To this end, introduce a new device PM flag, power.direct_complete
and modify the PM core to use that flag as follows.
If the ->prepare() callback of a device returns a positive number,
the PM core will regard that as an indication that it may leave the
device runtime-suspended. It will then check if the system power
transition in progress is a suspend (and not hibernation in particular)
and if the device is, indeed, runtime-suspended. In that case, the PM
core will set the device's power.direct_complete flag. Otherwise it
will clear power.direct_complete for the device and it also will later
clear it for the device's parent (if there's one).
Next, the PM core will not invoke the ->suspend() ->suspend_late(),
->suspend_irq(), ->resume_irq(), ->resume_early(), or ->resume()
callbacks for all devices having power.direct_complete set. It
will invoke their ->complete() callbacks, however, and those
callbacks are then responsible for resuming the devices as
appropriate, if necessary. For example, in some cases they may
need to queue up runtime resume requests for the devices using
pm_request_resume().
Changelog partly based on an Alan Stern's description of the idea
(http://marc.info/?l=linux-pm&m=139940466625569&w=2).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
2014-05-16 04:46:50 +04:00
|
|
|
* the appropriate resume callbacks for all devices. If the corresponding
|
|
|
|
* @prepare() at the beginning of the suspend transition returned a
|
|
|
|
* positive number and the device was left in runtime suspend (without
|
|
|
|
* executing any suspend and resume callbacks for it), @complete() will be
|
|
|
|
* the only callback executed for the device during resume. In that case,
|
|
|
|
* @complete() must be prepared to do whatever is necessary to ensure the
|
|
|
|
* proper functioning of the device after the system resume. To this end,
|
|
|
|
* @complete() can check the power.direct_complete flag of the device to
|
|
|
|
* learn whether (unset) or not (set) the previous suspend and resume
|
|
|
|
* callbacks have been executed for it.
|
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-21 01:00:01 +04:00
|
|
|
*
|
|
|
|
* @suspend: Executed before putting the system into a sleep state in which the
|
2011-11-24 00:20:32 +04:00
|
|
|
* contents of main memory are preserved. The exact action to perform
|
|
|
|
* depends on the device's subsystem (PM domain, device type, class or bus
|
|
|
|
* type), but generally the device must be quiescent after subsystem-level
|
|
|
|
* @suspend() has returned, so that it doesn't do any I/O or DMA.
|
|
|
|
* Subsystem-level @suspend() is executed for all devices after invoking
|
|
|
|
* subsystem-level @prepare() for all of them.
|
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-21 01:00:01 +04:00
|
|
|
*
|
2012-01-29 23:38:29 +04:00
|
|
|
* @suspend_late: Continue operations started by @suspend(). For a number of
|
|
|
|
* devices @suspend_late() may point to the same callback routine as the
|
|
|
|
* runtime suspend callback.
|
|
|
|
*
|
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-21 01:00:01 +04:00
|
|
|
* @resume: Executed after waking the system up from a sleep state in which the
|
2011-11-24 00:20:32 +04:00
|
|
|
* contents of main memory were preserved. The exact action to perform
|
|
|
|
* depends on the device's subsystem, but generally the driver is expected
|
|
|
|
* to start working again, responding to hardware events and software
|
|
|
|
* requests (the device itself may be left in a low-power state, waiting
|
|
|
|
* for a runtime resume to occur). The state of the device at the time its
|
|
|
|
* driver's @resume() callback is run depends on the platform and subsystem
|
|
|
|
* the device belongs to. On most platforms, there are no restrictions on
|
|
|
|
* availability of resources like clocks during @resume().
|
|
|
|
* Subsystem-level @resume() is executed for all devices after invoking
|
|
|
|
* subsystem-level @resume_noirq() for all of them.
|
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-21 01:00:01 +04:00
|
|
|
*
|
2012-01-29 23:38:29 +04:00
|
|
|
* @resume_early: Prepare to execute @resume(). For a number of devices
|
|
|
|
* @resume_early() may point to the same callback routine as the runtime
|
|
|
|
* resume callback.
|
|
|
|
*
|
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-21 01:00:01 +04:00
|
|
|
* @freeze: Hibernation-specific, executed before creating a hibernation image.
|
2011-11-24 00:20:32 +04:00
|
|
|
* Analogous to @suspend(), but it should not enable the device to signal
|
|
|
|
* wakeup events or change its power state. The majority of subsystems
|
|
|
|
* (with the notable exception of the PCI bus type) expect the driver-level
|
|
|
|
* @freeze() to save the device settings in memory to be used by @restore()
|
|
|
|
* during the subsequent resume from hibernation.
|
|
|
|
* Subsystem-level @freeze() is executed for all devices after invoking
|
|
|
|
* subsystem-level @prepare() for all of them.
|
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-21 01:00:01 +04:00
|
|
|
*
|
2012-01-29 23:38:29 +04:00
|
|
|
* @freeze_late: Continue operations started by @freeze(). Analogous to
|
|
|
|
* @suspend_late(), but it should not enable the device to signal wakeup
|
|
|
|
* events or change its power state.
|
|
|
|
*
|
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-21 01:00:01 +04:00
|
|
|
* @thaw: Hibernation-specific, executed after creating a hibernation image OR
|
2011-11-24 00:20:32 +04:00
|
|
|
* if the creation of an image has failed. Also executed after a failing
|
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-21 01:00:01 +04:00
|
|
|
* attempt to restore the contents of main memory from such an image.
|
|
|
|
* Undo the changes made by the preceding @freeze(), so the device can be
|
|
|
|
* operated in the same way as immediately before the call to @freeze().
|
2011-11-24 00:20:32 +04:00
|
|
|
* Subsystem-level @thaw() is executed for all devices after invoking
|
|
|
|
* subsystem-level @thaw_noirq() for all of them. It also may be executed
|
|
|
|
* directly after @freeze() in case of a transition 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-21 01:00:01 +04:00
|
|
|
*
|
2012-01-29 23:38:29 +04:00
|
|
|
* @thaw_early: Prepare to execute @thaw(). Undo the changes made by the
|
|
|
|
* preceding @freeze_late().
|
|
|
|
*
|
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-21 01:00:01 +04:00
|
|
|
* @poweroff: Hibernation-specific, executed after saving a hibernation image.
|
2011-11-24 00:20:32 +04:00
|
|
|
* Analogous to @suspend(), but it need not save the device's settings in
|
|
|
|
* memory.
|
|
|
|
* Subsystem-level @poweroff() is executed for all devices after invoking
|
|
|
|
* subsystem-level @prepare() for all of them.
|
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-21 01:00:01 +04:00
|
|
|
*
|
2012-01-29 23:38:29 +04:00
|
|
|
* @poweroff_late: Continue operations started by @poweroff(). Analogous to
|
|
|
|
* @suspend_late(), but it need not save the device's settings in memory.
|
|
|
|
*
|
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-21 01:00:01 +04:00
|
|
|
* @restore: Hibernation-specific, executed after restoring the contents of main
|
2011-11-24 00:20:32 +04:00
|
|
|
* memory from a hibernation image, analogous to @resume().
|
|
|
|
*
|
2012-01-29 23:38:29 +04:00
|
|
|
* @restore_early: Prepare to execute @restore(), analogous to @resume_early().
|
|
|
|
*
|
2011-11-24 00:20:32 +04:00
|
|
|
* @suspend_noirq: Complete the actions started by @suspend(). Carry out any
|
|
|
|
* additional operations required for suspending the device that might be
|
|
|
|
* racing with its driver's interrupt handler, which is guaranteed not to
|
|
|
|
* run while @suspend_noirq() is being executed.
|
|
|
|
* It generally is expected that the device will be in a low-power state
|
|
|
|
* (appropriate for the target system sleep state) after subsystem-level
|
|
|
|
* @suspend_noirq() has returned successfully. If the device can generate
|
|
|
|
* system wakeup signals and is enabled to wake up the system, it should be
|
|
|
|
* configured to do so at that time. However, depending on the platform
|
2012-01-29 23:38:29 +04:00
|
|
|
* and device's subsystem, @suspend() or @suspend_late() may be allowed to
|
|
|
|
* put the device into the low-power state and configure it to generate
|
|
|
|
* wakeup signals, in which case it generally is not necessary to define
|
|
|
|
* @suspend_noirq().
|
2011-11-24 00:20:32 +04:00
|
|
|
*
|
|
|
|
* @resume_noirq: Prepare for the execution of @resume() by carrying out any
|
|
|
|
* operations required for resuming the device that might be racing with
|
|
|
|
* its driver's interrupt handler, which is guaranteed not to run while
|
|
|
|
* @resume_noirq() is being executed.
|
|
|
|
*
|
|
|
|
* @freeze_noirq: Complete the actions started by @freeze(). Carry out any
|
|
|
|
* additional operations required for freezing the device that might be
|
|
|
|
* racing with its driver's interrupt handler, which is guaranteed not to
|
|
|
|
* run while @freeze_noirq() is being executed.
|
2012-01-29 23:38:29 +04:00
|
|
|
* The power state of the device should not be changed by either @freeze(),
|
|
|
|
* or @freeze_late(), or @freeze_noirq() and it should not be configured to
|
|
|
|
* signal system wakeup by any of these callbacks.
|
2011-11-24 00:20:32 +04:00
|
|
|
*
|
|
|
|
* @thaw_noirq: Prepare for the execution of @thaw() by carrying out any
|
|
|
|
* operations required for thawing the device that might be racing with its
|
|
|
|
* driver's interrupt handler, which is guaranteed not to run while
|
|
|
|
* @thaw_noirq() is being executed.
|
|
|
|
*
|
|
|
|
* @poweroff_noirq: Complete the actions started by @poweroff(). Analogous to
|
|
|
|
* @suspend_noirq(), but it need not save the device's settings in memory.
|
|
|
|
*
|
|
|
|
* @restore_noirq: Prepare for the execution of @restore() by carrying out any
|
|
|
|
* operations required for thawing the device that might be racing with its
|
|
|
|
* driver's interrupt handler, which is guaranteed not to run while
|
|
|
|
* @restore_noirq() is being executed. Analogous to @resume_noirq().
|
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-21 01:00:01 +04:00
|
|
|
*
|
2009-08-19 01:38:32 +04:00
|
|
|
* @runtime_suspend: Prepare the device for a condition in which it won't be
|
|
|
|
* able to communicate with the CPU(s) and RAM due to power management.
|
2011-11-24 00:20:32 +04:00
|
|
|
* This need not mean that the device should be put into a low-power state.
|
2009-08-19 01:38:32 +04:00
|
|
|
* For example, if the device is behind a link which is about to be turned
|
|
|
|
* off, the device may remain at full power. If the device does go to low
|
2011-11-24 00:20:32 +04:00
|
|
|
* power and is capable of generating runtime wakeup events, remote wakeup
|
|
|
|
* (i.e., a hardware mechanism allowing the device to request a change of
|
|
|
|
* its power state via an interrupt) should be enabled for it.
|
2009-08-19 01:38:32 +04:00
|
|
|
*
|
|
|
|
* @runtime_resume: Put the device into the fully active state in response to a
|
2011-11-24 00:20:32 +04:00
|
|
|
* wakeup event generated by hardware or at the request of software. If
|
|
|
|
* necessary, put the device into the full-power state and restore its
|
2009-08-19 01:38:32 +04:00
|
|
|
* registers, so that it is fully operational.
|
|
|
|
*
|
2011-11-24 00:20:32 +04:00
|
|
|
* @runtime_idle: Device appears to be inactive and it might be put into a
|
2014-03-18 00:26:11 +04:00
|
|
|
* low-power state if all of the necessary conditions are satisfied.
|
|
|
|
* Check these conditions, and return 0 if it's appropriate to let the PM
|
|
|
|
* core queue a suspend request for the device.
|
2011-11-24 00:20:32 +04:00
|
|
|
*
|
2017-02-02 03:30:49 +03:00
|
|
|
* Several device power state transitions are externally visible, affecting
|
|
|
|
* the state of pending I/O queues and (for drivers that touch hardware)
|
|
|
|
* interrupts, wakeups, DMA, and other hardware state. There may also be
|
|
|
|
* internal transitions to various low-power modes which are transparent
|
|
|
|
* to the rest of the driver stack (such as a driver that's ON gating off
|
|
|
|
* clocks which are not in active use).
|
2011-11-24 00:20:32 +04:00
|
|
|
*
|
2017-02-02 03:30:49 +03:00
|
|
|
* The externally visible transitions are handled with the help of callbacks
|
|
|
|
* included in this structure in such a way that, typically, two levels of
|
|
|
|
* callbacks are involved. First, the PM core executes callbacks provided by PM
|
|
|
|
* domains, device types, classes and bus types. They are the subsystem-level
|
|
|
|
* callbacks expected to execute callbacks provided by device drivers, although
|
|
|
|
* they may choose not to do that. If the driver callbacks are executed, they
|
|
|
|
* have to collaborate with the subsystem-level callbacks to achieve the goals
|
|
|
|
* appropriate for the given system transition, given transition phase and the
|
|
|
|
* subsystem the device belongs to.
|
|
|
|
*
|
|
|
|
* All of the above callbacks, except for @complete(), return error codes.
|
|
|
|
* However, the error codes returned by @resume(), @thaw(), @restore(),
|
|
|
|
* @resume_noirq(), @thaw_noirq(), and @restore_noirq(), do not cause the PM
|
|
|
|
* core to abort the resume transition during which they are returned. The
|
|
|
|
* error codes returned in those cases are only printed to the system logs for
|
|
|
|
* debugging purposes. Still, it is recommended that drivers only return error
|
|
|
|
* codes from their resume methods in case of an unrecoverable failure (i.e.
|
|
|
|
* when the device being handled refuses to resume and becomes unusable) to
|
|
|
|
* allow the PM core to be modified in the future, so that it can avoid
|
|
|
|
* attempting to handle devices that failed to resume and their children.
|
|
|
|
*
|
|
|
|
* It is allowed to unregister devices while the above callbacks are being
|
|
|
|
* executed. However, a callback routine MUST NOT try to unregister the device
|
|
|
|
* it was called for, although it may unregister children of that device (for
|
|
|
|
* example, if it detects that a child was unplugged while the system was
|
|
|
|
* asleep).
|
|
|
|
*
|
|
|
|
* There also are callbacks related to runtime power management of devices.
|
|
|
|
* Again, as a rule these callbacks are executed by the PM core for subsystems
|
|
|
|
* (PM domains, device types, classes and bus types) and the subsystem-level
|
|
|
|
* callbacks are expected to invoke the driver callbacks. Moreover, the exact
|
|
|
|
* actions to be performed by a device driver's callbacks generally depend on
|
|
|
|
* the platform and subsystem the device belongs to.
|
|
|
|
*
|
2019-06-13 13:10:36 +03:00
|
|
|
* Refer to Documentation/power/runtime_pm.rst for more information about the
|
2017-02-02 03:30:49 +03:00
|
|
|
* role of the @runtime_suspend(), @runtime_resume() and @runtime_idle()
|
|
|
|
* callbacks in device runtime power management.
|
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-21 01:00:01 +04:00
|
|
|
*/
|
2008-10-07 00:46:05 +04:00
|
|
|
struct dev_pm_ops {
|
|
|
|
int (*prepare)(struct device *dev);
|
|
|
|
void (*complete)(struct device *dev);
|
|
|
|
int (*suspend)(struct device *dev);
|
|
|
|
int (*resume)(struct device *dev);
|
|
|
|
int (*freeze)(struct device *dev);
|
|
|
|
int (*thaw)(struct device *dev);
|
|
|
|
int (*poweroff)(struct device *dev);
|
|
|
|
int (*restore)(struct device *dev);
|
2012-01-29 23:38:29 +04:00
|
|
|
int (*suspend_late)(struct device *dev);
|
|
|
|
int (*resume_early)(struct device *dev);
|
|
|
|
int (*freeze_late)(struct device *dev);
|
|
|
|
int (*thaw_early)(struct device *dev);
|
|
|
|
int (*poweroff_late)(struct device *dev);
|
|
|
|
int (*restore_early)(struct device *dev);
|
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-21 01:00:01 +04:00
|
|
|
int (*suspend_noirq)(struct device *dev);
|
|
|
|
int (*resume_noirq)(struct device *dev);
|
|
|
|
int (*freeze_noirq)(struct device *dev);
|
|
|
|
int (*thaw_noirq)(struct device *dev);
|
|
|
|
int (*poweroff_noirq)(struct device *dev);
|
|
|
|
int (*restore_noirq)(struct device *dev);
|
2009-08-19 01:38:32 +04:00
|
|
|
int (*runtime_suspend)(struct device *dev);
|
|
|
|
int (*runtime_resume)(struct device *dev);
|
|
|
|
int (*runtime_idle)(struct device *dev);
|
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-21 01:00:01 +04:00
|
|
|
};
|
|
|
|
|
2010-03-06 23:28:37 +03:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
|
|
|
#define SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
|
|
|
|
.suspend = suspend_fn, \
|
|
|
|
.resume = resume_fn, \
|
|
|
|
.freeze = suspend_fn, \
|
|
|
|
.thaw = resume_fn, \
|
|
|
|
.poweroff = suspend_fn, \
|
|
|
|
.restore = resume_fn,
|
|
|
|
#else
|
|
|
|
#define SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn)
|
|
|
|
#endif
|
|
|
|
|
2013-12-10 17:37:42 +04:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
|
|
|
#define SET_LATE_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
|
|
|
|
.suspend_late = suspend_fn, \
|
|
|
|
.resume_early = resume_fn, \
|
|
|
|
.freeze_late = suspend_fn, \
|
|
|
|
.thaw_early = resume_fn, \
|
|
|
|
.poweroff_late = suspend_fn, \
|
|
|
|
.restore_early = resume_fn,
|
|
|
|
#else
|
|
|
|
#define SET_LATE_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn)
|
|
|
|
#endif
|
|
|
|
|
2015-04-27 21:24:30 +03:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
|
|
|
#define SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
|
|
|
|
.suspend_noirq = suspend_fn, \
|
|
|
|
.resume_noirq = resume_fn, \
|
|
|
|
.freeze_noirq = suspend_fn, \
|
|
|
|
.thaw_noirq = resume_fn, \
|
|
|
|
.poweroff_noirq = suspend_fn, \
|
|
|
|
.restore_noirq = resume_fn,
|
|
|
|
#else
|
|
|
|
#define SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn)
|
|
|
|
#endif
|
|
|
|
|
2014-12-04 02:34:11 +03:00
|
|
|
#ifdef CONFIG_PM
|
2010-03-06 23:28:37 +03:00
|
|
|
#define SET_RUNTIME_PM_OPS(suspend_fn, resume_fn, idle_fn) \
|
|
|
|
.runtime_suspend = suspend_fn, \
|
|
|
|
.runtime_resume = resume_fn, \
|
|
|
|
.runtime_idle = idle_fn,
|
|
|
|
#else
|
|
|
|
#define SET_RUNTIME_PM_OPS(suspend_fn, resume_fn, idle_fn)
|
|
|
|
#endif
|
|
|
|
|
2009-08-06 01:59:59 +04:00
|
|
|
/*
|
|
|
|
* Use this if you want to use the same suspend and resume callbacks for suspend
|
|
|
|
* to RAM and hibernation.
|
|
|
|
*/
|
|
|
|
#define SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \
|
2009-12-15 05:00:08 +03:00
|
|
|
const struct dev_pm_ops name = { \
|
2010-03-06 23:28:37 +03:00
|
|
|
SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Use this for defining a set of PM operations to be used in all situations
|
2014-02-20 12:00:32 +04:00
|
|
|
* (system suspend, hibernation or runtime PM).
|
2012-02-13 19:29:47 +04:00
|
|
|
* NOTE: In general, system suspend callbacks, .suspend() and .resume(), should
|
|
|
|
* be different from the corresponding runtime PM callbacks, .runtime_suspend(),
|
|
|
|
* and .runtime_resume(), because .runtime_suspend() always works on an already
|
|
|
|
* quiescent device, while .suspend() should assume that the device may be doing
|
|
|
|
* something when it is called (it should ensure that the device will be
|
|
|
|
* quiescent after it has returned). Therefore it's better to point the "late"
|
|
|
|
* suspend and "early" resume callback pointers, .suspend_late() and
|
|
|
|
* .resume_early(), to the same routines as .runtime_suspend() and
|
|
|
|
* .runtime_resume(), respectively (and analogously for hibernation).
|
2010-03-06 23:28:37 +03:00
|
|
|
*/
|
|
|
|
#define UNIVERSAL_DEV_PM_OPS(name, suspend_fn, resume_fn, idle_fn) \
|
|
|
|
const struct dev_pm_ops name = { \
|
|
|
|
SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
|
|
|
|
SET_RUNTIME_PM_OPS(suspend_fn, resume_fn, idle_fn) \
|
2009-08-06 01:59:59 +04:00
|
|
|
}
|
|
|
|
|
2017-02-02 03:30:49 +03:00
|
|
|
/*
|
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-21 01:00:01 +04:00
|
|
|
* PM_EVENT_ messages
|
|
|
|
*
|
|
|
|
* The following PM_EVENT_ messages are defined for the internal use of the PM
|
|
|
|
* core, in order to provide a mechanism allowing the high level suspend and
|
|
|
|
* hibernation code to convey the necessary information to the device PM core
|
|
|
|
* code:
|
|
|
|
*
|
|
|
|
* ON No transition.
|
|
|
|
*
|
2014-03-18 00:26:10 +04:00
|
|
|
* FREEZE System is going to hibernate, call ->prepare() and ->freeze()
|
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-21 01:00:01 +04:00
|
|
|
* for all devices.
|
|
|
|
*
|
|
|
|
* SUSPEND System is going to suspend, call ->prepare() and ->suspend()
|
|
|
|
* for all devices.
|
|
|
|
*
|
|
|
|
* HIBERNATE Hibernation image has been saved, call ->prepare() and
|
|
|
|
* ->poweroff() for all devices.
|
|
|
|
*
|
|
|
|
* QUIESCE Contents of main memory are going to be restored from a (loaded)
|
|
|
|
* hibernation image, call ->prepare() and ->freeze() for all
|
|
|
|
* devices.
|
|
|
|
*
|
|
|
|
* RESUME System is resuming, call ->resume() and ->complete() for all
|
|
|
|
* devices.
|
|
|
|
*
|
|
|
|
* THAW Hibernation image has been created, call ->thaw() and
|
|
|
|
* ->complete() for all devices.
|
|
|
|
*
|
|
|
|
* RESTORE Contents of main memory have been restored from a hibernation
|
|
|
|
* image, call ->restore() and ->complete() for all devices.
|
|
|
|
*
|
|
|
|
* RECOVER Creation of a hibernation image or restoration of the main
|
|
|
|
* memory contents from a hibernation image has failed, call
|
|
|
|
* ->thaw() and ->complete() for all devices.
|
2008-07-24 08:28:37 +04:00
|
|
|
*
|
|
|
|
* The following PM_EVENT_ messages are defined for internal use by
|
|
|
|
* kernel subsystems. They are never issued by the PM core.
|
|
|
|
*
|
|
|
|
* USER_SUSPEND Manual selective suspend was issued by userspace.
|
|
|
|
*
|
|
|
|
* USER_RESUME Manual selective resume was issued by userspace.
|
|
|
|
*
|
|
|
|
* REMOTE_WAKEUP Remote-wakeup request was received from the device.
|
|
|
|
*
|
|
|
|
* AUTO_SUSPEND Automatic (device idle) runtime suspend was
|
|
|
|
* initiated by the subsystem.
|
|
|
|
*
|
|
|
|
* AUTO_RESUME Automatic (device needed) runtime resume was
|
|
|
|
* requested by a driver.
|
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-21 01:00:01 +04:00
|
|
|
*/
|
|
|
|
|
2011-09-30 00:29:44 +04:00
|
|
|
#define PM_EVENT_INVALID (-1)
|
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-21 01:00:01 +04:00
|
|
|
#define PM_EVENT_ON 0x0000
|
2014-03-18 00:26:10 +04:00
|
|
|
#define PM_EVENT_FREEZE 0x0001
|
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-21 01:00:01 +04:00
|
|
|
#define PM_EVENT_SUSPEND 0x0002
|
|
|
|
#define PM_EVENT_HIBERNATE 0x0004
|
|
|
|
#define PM_EVENT_QUIESCE 0x0008
|
|
|
|
#define PM_EVENT_RESUME 0x0010
|
|
|
|
#define PM_EVENT_THAW 0x0020
|
|
|
|
#define PM_EVENT_RESTORE 0x0040
|
|
|
|
#define PM_EVENT_RECOVER 0x0080
|
2008-07-24 08:28:37 +04:00
|
|
|
#define PM_EVENT_USER 0x0100
|
|
|
|
#define PM_EVENT_REMOTE 0x0200
|
|
|
|
#define PM_EVENT_AUTO 0x0400
|
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-21 01:00:01 +04:00
|
|
|
|
2008-07-24 08:28:37 +04:00
|
|
|
#define PM_EVENT_SLEEP (PM_EVENT_SUSPEND | PM_EVENT_HIBERNATE)
|
|
|
|
#define PM_EVENT_USER_SUSPEND (PM_EVENT_USER | PM_EVENT_SUSPEND)
|
|
|
|
#define PM_EVENT_USER_RESUME (PM_EVENT_USER | PM_EVENT_RESUME)
|
2008-11-17 19:14:19 +03:00
|
|
|
#define PM_EVENT_REMOTE_RESUME (PM_EVENT_REMOTE | PM_EVENT_RESUME)
|
2008-07-24 08:28:37 +04:00
|
|
|
#define PM_EVENT_AUTO_SUSPEND (PM_EVENT_AUTO | PM_EVENT_SUSPEND)
|
|
|
|
#define PM_EVENT_AUTO_RESUME (PM_EVENT_AUTO | PM_EVENT_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-21 01:00:01 +04:00
|
|
|
|
2011-09-30 00:29:44 +04:00
|
|
|
#define PMSG_INVALID ((struct pm_message){ .event = PM_EVENT_INVALID, })
|
2008-07-24 08:28:37 +04:00
|
|
|
#define PMSG_ON ((struct pm_message){ .event = PM_EVENT_ON, })
|
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-21 01:00:01 +04:00
|
|
|
#define PMSG_FREEZE ((struct pm_message){ .event = PM_EVENT_FREEZE, })
|
|
|
|
#define PMSG_QUIESCE ((struct pm_message){ .event = PM_EVENT_QUIESCE, })
|
|
|
|
#define PMSG_SUSPEND ((struct pm_message){ .event = PM_EVENT_SUSPEND, })
|
|
|
|
#define PMSG_HIBERNATE ((struct pm_message){ .event = PM_EVENT_HIBERNATE, })
|
|
|
|
#define PMSG_RESUME ((struct pm_message){ .event = PM_EVENT_RESUME, })
|
|
|
|
#define PMSG_THAW ((struct pm_message){ .event = PM_EVENT_THAW, })
|
|
|
|
#define PMSG_RESTORE ((struct pm_message){ .event = PM_EVENT_RESTORE, })
|
|
|
|
#define PMSG_RECOVER ((struct pm_message){ .event = PM_EVENT_RECOVER, })
|
2008-11-17 19:14:19 +03:00
|
|
|
#define PMSG_USER_SUSPEND ((struct pm_message) \
|
2008-07-24 08:28:37 +04:00
|
|
|
{ .event = PM_EVENT_USER_SUSPEND, })
|
2008-11-17 19:14:19 +03:00
|
|
|
#define PMSG_USER_RESUME ((struct pm_message) \
|
2008-07-24 08:28:37 +04:00
|
|
|
{ .event = PM_EVENT_USER_RESUME, })
|
2008-11-17 19:14:19 +03:00
|
|
|
#define PMSG_REMOTE_RESUME ((struct pm_message) \
|
2008-07-24 08:28:37 +04:00
|
|
|
{ .event = PM_EVENT_REMOTE_RESUME, })
|
2008-11-17 19:14:19 +03:00
|
|
|
#define PMSG_AUTO_SUSPEND ((struct pm_message) \
|
2008-07-24 08:28:37 +04:00
|
|
|
{ .event = PM_EVENT_AUTO_SUSPEND, })
|
2008-11-17 19:14:19 +03:00
|
|
|
#define PMSG_AUTO_RESUME ((struct pm_message) \
|
2008-07-24 08:28:37 +04:00
|
|
|
{ .event = PM_EVENT_AUTO_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-21 01:00:01 +04:00
|
|
|
|
2011-08-20 01:49:48 +04:00
|
|
|
#define PMSG_IS_AUTO(msg) (((msg).event & PM_EVENT_AUTO) != 0)
|
|
|
|
|
2017-02-02 03:30:49 +03:00
|
|
|
/*
|
2009-08-19 01:38:32 +04:00
|
|
|
* Device run-time power management status.
|
|
|
|
*
|
|
|
|
* These status labels are used internally by the PM core to indicate the
|
|
|
|
* current status of a device with respect to the PM core operations. They do
|
|
|
|
* not reflect the actual power state of the device or its status as seen by the
|
|
|
|
* driver.
|
|
|
|
*
|
|
|
|
* RPM_ACTIVE Device is fully operational. Indicates that the device
|
|
|
|
* bus type's ->runtime_resume() callback has completed
|
|
|
|
* successfully.
|
|
|
|
*
|
|
|
|
* RPM_SUSPENDED Device bus type's ->runtime_suspend() callback has
|
|
|
|
* completed successfully. The device is regarded as
|
|
|
|
* suspended.
|
|
|
|
*
|
|
|
|
* RPM_RESUMING Device bus type's ->runtime_resume() callback is being
|
|
|
|
* executed.
|
|
|
|
*
|
|
|
|
* RPM_SUSPENDING Device bus type's ->runtime_suspend() callback is being
|
|
|
|
* executed.
|
|
|
|
*/
|
|
|
|
|
|
|
|
enum rpm_status {
|
|
|
|
RPM_ACTIVE = 0,
|
|
|
|
RPM_RESUMING,
|
|
|
|
RPM_SUSPENDED,
|
|
|
|
RPM_SUSPENDING,
|
|
|
|
};
|
|
|
|
|
2017-02-02 03:30:49 +03:00
|
|
|
/*
|
2009-08-19 01:38:32 +04:00
|
|
|
* Device run-time power management request types.
|
|
|
|
*
|
|
|
|
* RPM_REQ_NONE Do nothing.
|
|
|
|
*
|
|
|
|
* RPM_REQ_IDLE Run the device bus type's ->runtime_idle() callback
|
|
|
|
*
|
|
|
|
* RPM_REQ_SUSPEND Run the device bus type's ->runtime_suspend() callback
|
|
|
|
*
|
2010-09-26 01:35:21 +04:00
|
|
|
* RPM_REQ_AUTOSUSPEND Same as RPM_REQ_SUSPEND, but not until the device has
|
|
|
|
* been inactive for as long as power.autosuspend_delay
|
|
|
|
*
|
2009-08-19 01:38:32 +04:00
|
|
|
* RPM_REQ_RESUME Run the device bus type's ->runtime_resume() callback
|
|
|
|
*/
|
|
|
|
|
|
|
|
enum rpm_request {
|
|
|
|
RPM_REQ_NONE = 0,
|
|
|
|
RPM_REQ_IDLE,
|
|
|
|
RPM_REQ_SUSPEND,
|
2010-09-26 01:35:21 +04:00
|
|
|
RPM_REQ_AUTOSUSPEND,
|
2009-08-19 01:38:32 +04:00
|
|
|
RPM_REQ_RESUME,
|
|
|
|
};
|
|
|
|
|
2010-09-23 00:09:10 +04:00
|
|
|
struct wakeup_source;
|
PM / Wakeirq: Add automated device wake IRQ handling
Turns out we can automate the handling for the device_may_wakeup()
quite a bit by using the kernel wakeup source list as suggested
by Rafael J. Wysocki <rjw@rjwysocki.net>.
And as some hardware has separate dedicated wake-up interrupt
in addition to the IO interrupt, we can automate the handling by
adding a generic threaded interrupt handler that just calls the
device PM runtime to wake up the device.
This allows dropping code from device drivers as we currently
are doing it in multiple ways, and often wrong.
For most drivers, we should be able to drop the following
boilerplate code from runtime_suspend and runtime_resume
functions:
...
device_init_wakeup(dev, true);
...
if (device_may_wakeup(dev))
enable_irq_wake(irq);
...
if (device_may_wakeup(dev))
disable_irq_wake(irq);
...
device_init_wakeup(dev, false);
...
We can replace it with just the following init and exit
time code:
...
device_init_wakeup(dev, true);
dev_pm_set_wake_irq(dev, irq);
...
dev_pm_clear_wake_irq(dev);
device_init_wakeup(dev, false);
...
And for hardware with dedicated wake-up interrupts:
...
device_init_wakeup(dev, true);
dev_pm_set_dedicated_wake_irq(dev, irq);
...
dev_pm_clear_wake_irq(dev);
device_init_wakeup(dev, false);
...
Signed-off-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2015-05-19 01:40:29 +03:00
|
|
|
struct wake_irq;
|
2014-11-14 10:41:32 +03:00
|
|
|
struct pm_domain_data;
|
2011-08-25 17:34:12 +04:00
|
|
|
|
2011-08-25 17:33:50 +04:00
|
|
|
struct pm_subsys_data {
|
|
|
|
spinlock_t lock;
|
2011-08-25 17:34:01 +04:00
|
|
|
unsigned int refcount;
|
2011-08-25 17:33:50 +04:00
|
|
|
#ifdef CONFIG_PM_CLK
|
|
|
|
struct list_head clock_list;
|
|
|
|
#endif
|
2011-08-25 17:34:12 +04:00
|
|
|
#ifdef CONFIG_PM_GENERIC_DOMAINS
|
2011-09-26 22:22:02 +04:00
|
|
|
struct pm_domain_data *domain_data;
|
2011-08-25 17:34:12 +04:00
|
|
|
#endif
|
2011-08-25 17:33:50 +04:00
|
|
|
};
|
|
|
|
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 15:12:29 +03:00
|
|
|
/*
|
|
|
|
* Driver flags to control system suspend/resume behavior.
|
|
|
|
*
|
|
|
|
* These flags can be set by device drivers at the probe time. They need not be
|
|
|
|
* cleared by the drivers as the driver core will take care of that.
|
|
|
|
*
|
2017-11-18 17:31:49 +03:00
|
|
|
* NEVER_SKIP: Do not skip all system suspend/resume callbacks for the device.
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 15:12:29 +03:00
|
|
|
* SMART_PREPARE: Check the return value of the driver's ->prepare callback.
|
2017-10-26 13:12:08 +03:00
|
|
|
* SMART_SUSPEND: No need to resume the device from runtime suspend.
|
2017-11-18 17:31:49 +03:00
|
|
|
* LEAVE_SUSPENDED: Avoid resuming the device during system resume if possible.
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 15:12:29 +03:00
|
|
|
*
|
|
|
|
* Setting SMART_PREPARE instructs bus types and PM domains which may want
|
|
|
|
* system suspend/resume callbacks to be skipped for the device to return 0 from
|
|
|
|
* their ->prepare callbacks if the driver's ->prepare callback returns 0 (in
|
|
|
|
* other words, the system suspend/resume callbacks can only be skipped for the
|
|
|
|
* device if its driver doesn't object against that). This flag has no effect
|
|
|
|
* if NEVER_SKIP is set.
|
2017-10-26 13:12:08 +03:00
|
|
|
*
|
|
|
|
* Setting SMART_SUSPEND instructs bus types and PM domains which may want to
|
|
|
|
* runtime resume the device upfront during system suspend that doing so is not
|
|
|
|
* necessary from the driver's perspective. It also may cause them to skip
|
|
|
|
* invocations of the ->suspend_late and ->suspend_noirq callbacks provided by
|
|
|
|
* the driver if they decide to leave the device in runtime suspend.
|
2017-11-18 17:31:49 +03:00
|
|
|
*
|
|
|
|
* Setting LEAVE_SUSPENDED informs the PM core and middle-layer code that the
|
|
|
|
* driver prefers the device to be left in suspend after system resume.
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 15:12:29 +03:00
|
|
|
*/
|
2017-11-18 17:31:49 +03:00
|
|
|
#define DPM_FLAG_NEVER_SKIP BIT(0)
|
|
|
|
#define DPM_FLAG_SMART_PREPARE BIT(1)
|
|
|
|
#define DPM_FLAG_SMART_SUSPEND BIT(2)
|
|
|
|
#define DPM_FLAG_LEAVE_SUSPENDED BIT(3)
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 15:12:29 +03:00
|
|
|
|
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-21 01:00:01 +04:00
|
|
|
struct dev_pm_info {
|
|
|
|
pm_message_t power_state;
|
2009-08-19 01:38:32 +04:00
|
|
|
unsigned int can_wakeup:1;
|
2010-12-16 02:51:21 +03:00
|
|
|
unsigned int async_suspend:1;
|
driver core: Functional dependencies tracking support
Currently, there is a problem with taking functional dependencies
between devices into account.
What I mean by a "functional dependency" is when the driver of device
B needs device A to be functional and (generally) its driver to be
present in order to work properly. This has certain consequences
for power management (suspend/resume and runtime PM ordering) and
shutdown ordering of these devices. In general, it also implies that
the driver of A needs to be working for B to be probed successfully
and it cannot be unbound from the device before the B's driver.
Support for representing those functional dependencies between
devices is added here to allow the driver core to track them and act
on them in certain cases where applicable.
The argument for doing that in the driver core is that there are
quite a few distinct use cases involving device dependencies, they
are relatively hard to get right in a driver (if one wants to
address all of them properly) and it only gets worse if multiplied
by the number of drivers potentially needing to do it. Morever, at
least one case (asynchronous system suspend/resume) cannot be handled
in a single driver at all, because it requires the driver of A to
wait for B to suspend (during system suspend) and the driver of B to
wait for A to resume (during system resume).
For this reason, represent dependencies between devices as "links",
with the help of struct device_link objects each containing pointers
to the "linked" devices, a list node for each of them, status
information, flags, and an RCU head for synchronization.
Also add two new list heads, representing the lists of links to the
devices that depend on the given one (consumers) and to the devices
depended on by it (suppliers), and a "driver presence status" field
(needed for figuring out initial states of device links) to struct
device.
The entire data structure consisting of all of the lists of link
objects for all devices is protected by a mutex (for link object
addition/removal and for list walks during device driver probing
and removal) and by SRCU (for list walking in other case that will
be introduced by subsequent change sets). If CONFIG_SRCU is not
selected, however, an rwsem is used for protecting the entire data
structure.
In addition, each link object has an internal status field whose
value reflects whether or not drivers are bound to the devices
pointed to by the link or probing/removal of their drivers is in
progress etc. That field is only modified under the device links
mutex, but it may be read outside of it in some cases (introduced by
subsequent change sets), so modifications of it are annotated with
WRITE_ONCE().
New links are added by calling device_link_add() which takes three
arguments: pointers to the devices in question and flags. In
particular, if DL_FLAG_STATELESS is set in the flags, the link status
is not to be taken into account for this link and the driver core
will not manage it. In turn, if DL_FLAG_AUTOREMOVE is set in the
flags, the driver core will remove the link automatically when the
consumer device driver unbinds from it.
One of the actions carried out by device_link_add() is to reorder
the lists used for device shutdown and system suspend/resume to
put the consumer device along with all of its children and all of
its consumers (and so on, recursively) to the ends of those lists
in order to ensure the right ordering between all of the supplier
and consumer devices.
For this reason, it is not possible to create a link between two
devices if the would-be supplier device already depends on the
would-be consumer device as either a direct descendant of it or a
consumer of one of its direct descendants or one of its consumers
and so on.
There are two types of link objects, persistent and non-persistent.
The persistent ones stay around until one of the target devices is
deleted, while the non-persistent ones are removed automatically when
the consumer driver unbinds from its device (ie. they are assumed to
be valid only as long as the consumer device has a driver bound to
it). Persistent links are created by default and non-persistent
links are created when the DL_FLAG_AUTOREMOVE flag is passed
to device_link_add().
Both persistent and non-persistent device links can be deleted
with an explicit call to device_link_del().
Links created without the DL_FLAG_STATELESS flag set are managed
by the driver core using a simple state machine. There are 5 states
each link can be in: DORMANT (unused), AVAILABLE (the supplier driver
is present and functional), CONSUMER_PROBE (the consumer driver is
probing), ACTIVE (both supplier and consumer drivers are present and
functional), and SUPPLIER_UNBIND (the supplier driver is unbinding).
The driver core updates the link state automatically depending on
what happens to the linked devices and for each link state specific
actions are taken in addition to that.
For example, if the supplier driver unbinds from its device, the
driver core will also unbind the drivers of all of its consumers
automatically under the assumption that they cannot function
properly without the supplier. Analogously, the driver core will
only allow the consumer driver to bind to its device if the
supplier driver is present and functional (ie. the link is in
the AVAILABLE state). If that's not the case, it will rely on
the existing deferred probing mechanism to wait for the supplier
driver to become available.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-10-30 19:32:16 +03:00
|
|
|
bool in_dpm_list:1; /* Owned by the PM core */
|
2011-06-18 22:22:23 +04:00
|
|
|
bool is_prepared:1; /* Owned by the PM core */
|
2011-06-19 00:42:09 +04:00
|
|
|
bool is_suspended:1; /* Ditto */
|
2014-02-18 06:28:44 +04:00
|
|
|
bool is_noirq_suspended:1;
|
|
|
|
bool is_late_suspended:1;
|
2019-02-14 21:29:10 +03:00
|
|
|
bool no_pm:1;
|
2012-08-06 03:45:11 +04:00
|
|
|
bool early_init:1; /* Owned by the PM core */
|
PM / sleep: Mechanism to avoid resuming runtime-suspended devices unnecessarily
Currently, some subsystems (e.g. PCI and the ACPI PM domain) have to
resume all runtime-suspended devices during system suspend, mostly
because those devices may need to be reprogrammed due to different
wakeup settings for system sleep and for runtime PM.
For some devices, though, it's OK to remain in runtime suspend
throughout a complete system suspend/resume cycle (if the device was in
runtime suspend at the start of the cycle). We would like to do this
whenever possible, to avoid the overhead of extra power-up and power-down
events.
However, problems may arise because the device's descendants may require
it to be at full power at various points during the cycle. Therefore the
most straightforward way to do this safely is if the device and all its
descendants can remain runtime suspended until the complete stage of
system resume.
To this end, introduce a new device PM flag, power.direct_complete
and modify the PM core to use that flag as follows.
If the ->prepare() callback of a device returns a positive number,
the PM core will regard that as an indication that it may leave the
device runtime-suspended. It will then check if the system power
transition in progress is a suspend (and not hibernation in particular)
and if the device is, indeed, runtime-suspended. In that case, the PM
core will set the device's power.direct_complete flag. Otherwise it
will clear power.direct_complete for the device and it also will later
clear it for the device's parent (if there's one).
Next, the PM core will not invoke the ->suspend() ->suspend_late(),
->suspend_irq(), ->resume_irq(), ->resume_early(), or ->resume()
callbacks for all devices having power.direct_complete set. It
will invoke their ->complete() callbacks, however, and those
callbacks are then responsible for resuming the devices as
appropriate, if necessary. For example, in some cases they may
need to queue up runtime resume requests for the devices using
pm_request_resume().
Changelog partly based on an Alan Stern's description of the idea
(http://marc.info/?l=linux-pm&m=139940466625569&w=2).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
2014-05-16 04:46:50 +04:00
|
|
|
bool direct_complete:1; /* Owned by the PM core */
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 15:12:29 +03:00
|
|
|
u32 driver_flags;
|
2010-09-23 00:09:10 +04:00
|
|
|
spinlock_t lock;
|
2009-08-19 01:38:32 +04:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
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-21 01:00:01 +04:00
|
|
|
struct list_head entry;
|
PM: Asynchronous suspend and resume of devices
Theoretically, the total time of system sleep transitions (suspend
to RAM, hibernation) can be reduced by running suspend and resume
callbacks of device drivers in parallel with each other. However,
there are dependencies between devices such that we're not allowed
to suspend the parent of a device before suspending the device
itself. Analogously, we're not allowed to resume a device before
resuming its parent.
The most straightforward way to take these dependencies into accout
is to start the async threads used for suspending and resuming
devices at the core level, so that async_schedule() is called for
each suspend and resume callback supposed to be executed
asynchronously.
For this purpose, introduce a new device flag, power.async_suspend,
used to mark the devices whose suspend and resume callbacks are to be
executed asynchronously (ie. in parallel with the main suspend/resume
thread and possibly in parallel with each other) and helper function
device_enable_async_suspend() allowing one to set power.async_suspend
for given device (power.async_suspend is unset by default for all
devices). For each device with the power.async_suspend flag set the
PM core will use async_schedule() to execute its suspend and resume
callbacks.
The async threads started for different devices as a result of
calling async_schedule() are synchronized with each other and with
the main suspend/resume thread with the help of completions, in the
following way:
(1) There is a completion, power.completion, for each device object.
(2) Each device's completion is reset before calling async_schedule()
for the device or, in the case of devices with the
power.async_suspend flags unset, before executing the device's
suspend and resume callbacks.
(3) During suspend, right before running the bus type, device type
and device class suspend callbacks for the device, the PM core
waits for the completions of all the device's children to be
completed.
(4) During resume, right before running the bus type, device type and
device class resume callbacks for the device, the PM core waits
for the completion of the device's parent to be completed.
(5) The PM core completes power.completion for each device right
after the bus type, device type and device class suspend (or
resume) callbacks executed for the device have returned.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-01-24 00:23:32 +03:00
|
|
|
struct completion completion;
|
2010-09-23 00:09:10 +04:00
|
|
|
struct wakeup_source *wakeup;
|
2011-10-17 01:34:36 +04:00
|
|
|
bool wakeup_path:1;
|
2012-08-13 16:00:25 +04:00
|
|
|
bool syscore:1;
|
2016-01-07 18:46:14 +03:00
|
|
|
bool no_pm_callbacks:1; /* Owned by the PM core */
|
2017-11-18 17:31:49 +03:00
|
|
|
unsigned int must_resume:1; /* Owned by the PM core */
|
|
|
|
unsigned int may_skip_resume:1; /* Set by subsystems */
|
2011-02-24 13:10:01 +03:00
|
|
|
#else
|
|
|
|
unsigned int should_wakeup:1;
|
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-21 01:00:01 +04:00
|
|
|
#endif
|
2014-11-28 00:38:05 +03:00
|
|
|
#ifdef CONFIG_PM
|
2018-12-14 17:22:25 +03:00
|
|
|
struct hrtimer suspend_timer;
|
2009-08-19 01:38:32 +04:00
|
|
|
unsigned long timer_expires;
|
|
|
|
struct work_struct work;
|
|
|
|
wait_queue_head_t wait_queue;
|
PM / Wakeirq: Add automated device wake IRQ handling
Turns out we can automate the handling for the device_may_wakeup()
quite a bit by using the kernel wakeup source list as suggested
by Rafael J. Wysocki <rjw@rjwysocki.net>.
And as some hardware has separate dedicated wake-up interrupt
in addition to the IO interrupt, we can automate the handling by
adding a generic threaded interrupt handler that just calls the
device PM runtime to wake up the device.
This allows dropping code from device drivers as we currently
are doing it in multiple ways, and often wrong.
For most drivers, we should be able to drop the following
boilerplate code from runtime_suspend and runtime_resume
functions:
...
device_init_wakeup(dev, true);
...
if (device_may_wakeup(dev))
enable_irq_wake(irq);
...
if (device_may_wakeup(dev))
disable_irq_wake(irq);
...
device_init_wakeup(dev, false);
...
We can replace it with just the following init and exit
time code:
...
device_init_wakeup(dev, true);
dev_pm_set_wake_irq(dev, irq);
...
dev_pm_clear_wake_irq(dev);
device_init_wakeup(dev, false);
...
And for hardware with dedicated wake-up interrupts:
...
device_init_wakeup(dev, true);
dev_pm_set_dedicated_wake_irq(dev, irq);
...
dev_pm_clear_wake_irq(dev);
device_init_wakeup(dev, false);
...
Signed-off-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2015-05-19 01:40:29 +03:00
|
|
|
struct wake_irq *wakeirq;
|
2009-08-19 01:38:32 +04:00
|
|
|
atomic_t usage_count;
|
|
|
|
atomic_t child_count;
|
|
|
|
unsigned int disable_depth:3;
|
|
|
|
unsigned int idle_notification:1;
|
|
|
|
unsigned int request_pending:1;
|
|
|
|
unsigned int deferred_resume:1;
|
2010-01-24 00:02:51 +03:00
|
|
|
unsigned int runtime_auto:1;
|
2016-04-08 14:40:53 +03:00
|
|
|
bool ignore_children:1;
|
2010-09-26 01:35:15 +04:00
|
|
|
unsigned int no_callbacks:1;
|
2010-12-01 02:14:42 +03:00
|
|
|
unsigned int irq_safe:1;
|
2010-09-26 01:35:21 +04:00
|
|
|
unsigned int use_autosuspend:1;
|
|
|
|
unsigned int timer_autosuspends:1;
|
2013-02-23 04:34:11 +04:00
|
|
|
unsigned int memalloc_noio:1;
|
2016-10-30 19:32:43 +03:00
|
|
|
unsigned int links_count;
|
2009-08-19 01:38:32 +04:00
|
|
|
enum rpm_request request;
|
|
|
|
enum rpm_status runtime_status;
|
|
|
|
int runtime_error;
|
2010-09-26 01:35:21 +04:00
|
|
|
int autosuspend_delay;
|
2018-12-14 17:22:25 +03:00
|
|
|
u64 last_busy;
|
2019-01-23 10:50:14 +03:00
|
|
|
u64 active_time;
|
|
|
|
u64 suspended_time;
|
|
|
|
u64 accounting_timestamp;
|
2009-08-19 01:38:32 +04:00
|
|
|
#endif
|
2011-08-25 17:33:50 +04:00
|
|
|
struct pm_subsys_data *subsys_data; /* Owned by the subsystem. */
|
PM / QoS: Introcuce latency tolerance device PM QoS type
Add a new latency tolerance device PM QoS type to be use for
specifying active state (RPM_ACTIVE) memory access (DMA) latency
tolerance requirements for devices. It may be used to prevent
hardware from choosing overly aggressive energy-saving operation
modes (causing too much latency to appear) for the whole platform.
This feature reqiures hardware support, so it only will be
available for devices having a new .set_latency_tolerance()
callback in struct dev_pm_info populated, in which case the
routine pointed to by it should implement whatever is necessary
to transfer the effective requirement value to the hardware.
Whenever the effective latency tolerance changes for the device,
its .set_latency_tolerance() callback will be executed and the
effective value will be passed to it. If that value is negative,
which means that the list of latency tolerance requirements for
the device is empty, the callback is expected to switch the
underlying hardware latency tolerance control mechanism to an
autonomous mode if available. If that value is PM_QOS_LATENCY_ANY,
in turn, and the hardware supports a special "no requirement"
setting, the callback is expected to use it. That allows software
to prevent the hardware from automatically updating the device's
latency tolerance in response to its power state changes (e.g. during
transitions from D3cold to D0), which generally may be done in the
autonomous latency tolerance control mode.
If .set_latency_tolerance() is present for the device, a new
pm_qos_latency_tolerance_us attribute will be present in the
devivce's power directory in sysfs. Then, user space can use
that attribute to specify its latency tolerance requirement for
the device, if any. Writing "any" to it means "no requirement, but
do not let the hardware control latency tolerance" and writing
"auto" to it allows the hardware to be switched to the autonomous
mode if there are no other requirements from the kernel side in the
device's list.
This changeset includes a fix from Mika Westerberg.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2014-02-11 03:35:38 +04:00
|
|
|
void (*set_latency_tolerance)(struct device *, s32);
|
2012-10-23 03:07:27 +04:00
|
|
|
struct dev_pm_qos *qos;
|
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-21 01:00:01 +04:00
|
|
|
};
|
|
|
|
|
2011-08-25 17:34:01 +04:00
|
|
|
extern int dev_pm_get_subsys_data(struct device *dev);
|
2015-01-29 20:39:05 +03:00
|
|
|
extern void dev_pm_put_subsys_data(struct device *dev);
|
2010-07-19 04:01:06 +04:00
|
|
|
|
2017-02-02 03:30:49 +03:00
|
|
|
/**
|
|
|
|
* struct dev_pm_domain - power management domain representation.
|
driver core / PM: Add PM domain callbacks for device setup/cleanup
If PM domains are in use, it may be necessary to prepare the code
handling a PM domain for driver probing. For example, in some
cases device drivers rely on the ability to power on the devices
with the help of the IO runtime PM framework and the PM domain
code needs to be ready for that. Also, if that code has not been
fully initialized yet, the driver probing should be deferred.
Moreover, after the probing is complete, it may be necessary to
put the PM domain in question into the state reflecting the current
needs of the devices in it, for example, so that power is not drawn
in vain. The same should be done after removing a driver from
a device, as the PM domain state may need to be changed to reflect
the new situation.
For these reasons, introduce new PM domain callbacks, ->activate,
->sync and ->dismiss called, respectively, before probing for a
device driver, after the probing has completed successfully and
if the probing has failed or the driver has been removed.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Kevin Hilman <khilman@linaro.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-03-20 15:59:27 +03:00
|
|
|
*
|
2017-02-02 03:30:49 +03:00
|
|
|
* @ops: Power management operations associated with this domain.
|
driver core / PM: Add PM domain callbacks for device setup/cleanup
If PM domains are in use, it may be necessary to prepare the code
handling a PM domain for driver probing. For example, in some
cases device drivers rely on the ability to power on the devices
with the help of the IO runtime PM framework and the PM domain
code needs to be ready for that. Also, if that code has not been
fully initialized yet, the driver probing should be deferred.
Moreover, after the probing is complete, it may be necessary to
put the PM domain in question into the state reflecting the current
needs of the devices in it, for example, so that power is not drawn
in vain. The same should be done after removing a driver from
a device, as the PM domain state may need to be changed to reflect
the new situation.
For these reasons, introduce new PM domain callbacks, ->activate,
->sync and ->dismiss called, respectively, before probing for a
device driver, after the probing has completed successfully and
if the probing has failed or the driver has been removed.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Kevin Hilman <khilman@linaro.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-03-20 15:59:27 +03:00
|
|
|
* @detach: Called when removing a device from the domain.
|
|
|
|
* @activate: Called before executing probe routines for bus types and drivers.
|
|
|
|
* @sync: Called after successful driver probe.
|
|
|
|
* @dismiss: Called after unsuccessful driver probe and after driver removal.
|
2017-02-02 03:30:49 +03:00
|
|
|
*
|
|
|
|
* Power domains provide callbacks that are executed during system suspend,
|
|
|
|
* hibernation, system resume and during runtime PM transitions instead of
|
|
|
|
* subsystem-level and driver-level callbacks.
|
2011-02-16 23:53:17 +03:00
|
|
|
*/
|
2011-06-23 03:52:55 +04:00
|
|
|
struct dev_pm_domain {
|
2011-02-16 23:53:17 +03:00
|
|
|
struct dev_pm_ops ops;
|
2014-09-19 22:27:34 +04:00
|
|
|
void (*detach)(struct device *dev, bool power_off);
|
driver core / PM: Add PM domain callbacks for device setup/cleanup
If PM domains are in use, it may be necessary to prepare the code
handling a PM domain for driver probing. For example, in some
cases device drivers rely on the ability to power on the devices
with the help of the IO runtime PM framework and the PM domain
code needs to be ready for that. Also, if that code has not been
fully initialized yet, the driver probing should be deferred.
Moreover, after the probing is complete, it may be necessary to
put the PM domain in question into the state reflecting the current
needs of the devices in it, for example, so that power is not drawn
in vain. The same should be done after removing a driver from
a device, as the PM domain state may need to be changed to reflect
the new situation.
For these reasons, introduce new PM domain callbacks, ->activate,
->sync and ->dismiss called, respectively, before probing for a
device driver, after the probing has completed successfully and
if the probing has failed or the driver has been removed.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Kevin Hilman <khilman@linaro.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-03-20 15:59:27 +03:00
|
|
|
int (*activate)(struct device *dev);
|
|
|
|
void (*sync)(struct device *dev);
|
|
|
|
void (*dismiss)(struct device *dev);
|
2011-02-16 23:53:17 +03:00
|
|
|
};
|
2010-07-19 04:01:06 +04:00
|
|
|
|
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-21 01:00:01 +04:00
|
|
|
/*
|
|
|
|
* The PM_EVENT_ messages are also used by drivers implementing the legacy
|
|
|
|
* suspend framework, based on the ->suspend() and ->resume() callbacks common
|
|
|
|
* for suspend and hibernation transitions, according to the rules below.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Necessary, because several drivers use PM_EVENT_PRETHAW */
|
|
|
|
#define PM_EVENT_PRETHAW PM_EVENT_QUIESCE
|
|
|
|
|
|
|
|
/*
|
2006-08-15 10:11:04 +04:00
|
|
|
* One transition is triggered by resume(), after a suspend() call; the
|
|
|
|
* message is implicit:
|
|
|
|
*
|
|
|
|
* ON Driver starts working again, responding to hardware events
|
2014-03-18 00:26:10 +04:00
|
|
|
* and software requests. The hardware may have gone through
|
|
|
|
* a power-off reset, or it may have maintained state from the
|
|
|
|
* previous suspend() which the driver will rely on while
|
|
|
|
* resuming. On most platforms, there are no restrictions on
|
|
|
|
* availability of resources like clocks during resume().
|
2006-08-15 10:11:04 +04:00
|
|
|
*
|
|
|
|
* Other transitions are triggered by messages sent using suspend(). All
|
|
|
|
* these transitions quiesce the driver, so that I/O queues are inactive.
|
|
|
|
* That commonly entails turning off IRQs and DMA; there may be rules
|
|
|
|
* about how to quiesce that are specific to the bus or the device's type.
|
|
|
|
* (For example, network drivers mark the link state.) Other details may
|
|
|
|
* differ according to the message:
|
|
|
|
*
|
|
|
|
* SUSPEND Quiesce, enter a low power device state appropriate for
|
2014-03-18 00:26:10 +04:00
|
|
|
* the upcoming system state (such as PCI_D3hot), and enable
|
|
|
|
* wakeup events as appropriate.
|
2006-08-15 10:11:04 +04:00
|
|
|
*
|
2008-02-23 21:13:25 +03:00
|
|
|
* HIBERNATE Enter a low power device state appropriate for the hibernation
|
2014-03-18 00:26:10 +04:00
|
|
|
* state (eg. ACPI S4) and enable wakeup events as appropriate.
|
2008-02-23 21:13:25 +03:00
|
|
|
*
|
2006-08-15 10:11:04 +04:00
|
|
|
* FREEZE Quiesce operations so that a consistent image can be saved;
|
2014-03-18 00:26:10 +04:00
|
|
|
* but do NOT otherwise enter a low power device state, and do
|
|
|
|
* NOT emit system wakeup events.
|
2006-08-15 10:11:04 +04:00
|
|
|
*
|
|
|
|
* PRETHAW Quiesce as if for FREEZE; additionally, prepare for restoring
|
2014-03-18 00:26:10 +04:00
|
|
|
* the system from a snapshot taken after an earlier FREEZE.
|
|
|
|
* Some drivers will need to reset their hardware state instead
|
|
|
|
* of preserving it, to ensure that it's never mistaken for the
|
|
|
|
* state which that earlier snapshot had set up.
|
2006-08-15 10:11:04 +04:00
|
|
|
*
|
|
|
|
* A minimally power-aware driver treats all messages as SUSPEND, fully
|
|
|
|
* reinitializes its device during resume() -- whether or not it was reset
|
|
|
|
* during the suspend/resume cycle -- and can't issue wakeup events.
|
|
|
|
*
|
|
|
|
* More power-aware drivers may also use low power states at runtime as
|
|
|
|
* well as during system sleep states like PM_SUSPEND_STANDBY. They may
|
|
|
|
* be able to use wakeup events to exit from runtime low-power states,
|
|
|
|
* or from system low-power states such as standby or suspend-to-RAM.
|
2005-04-17 02:20:36 +04:00
|
|
|
*/
|
|
|
|
|
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-21 01:00:01 +04:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
2011-03-24 00:16:41 +03:00
|
|
|
extern void device_pm_lock(void);
|
2012-01-29 23:38:29 +04:00
|
|
|
extern void dpm_resume_start(pm_message_t state);
|
2009-05-25 00:05:42 +04:00
|
|
|
extern void dpm_resume_end(pm_message_t state);
|
2014-09-30 04:21:34 +04:00
|
|
|
extern void dpm_resume_noirq(pm_message_t state);
|
|
|
|
extern void dpm_resume_early(pm_message_t state);
|
2011-05-18 01:26:00 +04:00
|
|
|
extern void dpm_resume(pm_message_t state);
|
|
|
|
extern void dpm_complete(pm_message_t state);
|
2005-04-17 02:20:36 +04:00
|
|
|
|
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-21 01:00:01 +04:00
|
|
|
extern void device_pm_unlock(void);
|
2012-01-29 23:38:29 +04:00
|
|
|
extern int dpm_suspend_end(pm_message_t state);
|
2009-05-25 00:05:42 +04:00
|
|
|
extern int dpm_suspend_start(pm_message_t state);
|
2014-09-30 04:21:34 +04:00
|
|
|
extern int dpm_suspend_noirq(pm_message_t state);
|
|
|
|
extern int dpm_suspend_late(pm_message_t state);
|
2011-05-18 01:26:00 +04:00
|
|
|
extern int dpm_suspend(pm_message_t state);
|
|
|
|
extern int dpm_prepare(pm_message_t state);
|
2005-09-13 06:39:34 +04:00
|
|
|
|
2006-03-23 12:38:34 +03:00
|
|
|
extern void __suspend_report_result(const char *function, void *fn, int ret);
|
|
|
|
|
|
|
|
#define suspend_report_result(fn, ret) \
|
|
|
|
do { \
|
2008-10-16 09:01:24 +04:00
|
|
|
__suspend_report_result(__func__, fn, ret); \
|
2006-03-23 12:38:34 +03:00
|
|
|
} while (0)
|
2005-10-24 10:02:20 +04:00
|
|
|
|
2010-09-23 00:10:57 +04:00
|
|
|
extern int device_pm_wait_for_dev(struct device *sub, struct device *dev);
|
2012-08-17 18:06:59 +04:00
|
|
|
extern void dpm_for_each_dev(void *data, void (*fn)(struct device *, void *));
|
2011-05-18 01:26:21 +04:00
|
|
|
|
|
|
|
extern int pm_generic_prepare(struct device *dev);
|
2012-01-29 23:38:41 +04:00
|
|
|
extern int pm_generic_suspend_late(struct device *dev);
|
2011-07-02 00:12:59 +04:00
|
|
|
extern int pm_generic_suspend_noirq(struct device *dev);
|
2011-05-18 01:26:21 +04:00
|
|
|
extern int pm_generic_suspend(struct device *dev);
|
2012-01-29 23:38:41 +04:00
|
|
|
extern int pm_generic_resume_early(struct device *dev);
|
2011-07-02 00:12:59 +04:00
|
|
|
extern int pm_generic_resume_noirq(struct device *dev);
|
2011-05-18 01:26:21 +04:00
|
|
|
extern int pm_generic_resume(struct device *dev);
|
2011-07-02 00:12:59 +04:00
|
|
|
extern int pm_generic_freeze_noirq(struct device *dev);
|
2012-01-29 23:38:41 +04:00
|
|
|
extern int pm_generic_freeze_late(struct device *dev);
|
2011-05-18 01:26:21 +04:00
|
|
|
extern int pm_generic_freeze(struct device *dev);
|
2011-07-02 00:12:59 +04:00
|
|
|
extern int pm_generic_thaw_noirq(struct device *dev);
|
2012-01-29 23:38:41 +04:00
|
|
|
extern int pm_generic_thaw_early(struct device *dev);
|
2011-05-18 01:26:21 +04:00
|
|
|
extern int pm_generic_thaw(struct device *dev);
|
2011-07-02 00:12:59 +04:00
|
|
|
extern int pm_generic_restore_noirq(struct device *dev);
|
2012-01-29 23:38:41 +04:00
|
|
|
extern int pm_generic_restore_early(struct device *dev);
|
2011-05-18 01:26:21 +04:00
|
|
|
extern int pm_generic_restore(struct device *dev);
|
2011-07-02 00:12:59 +04:00
|
|
|
extern int pm_generic_poweroff_noirq(struct device *dev);
|
2012-01-29 23:38:41 +04:00
|
|
|
extern int pm_generic_poweroff_late(struct device *dev);
|
2011-05-18 01:26:21 +04:00
|
|
|
extern int pm_generic_poweroff(struct device *dev);
|
|
|
|
extern void pm_generic_complete(struct device *dev);
|
|
|
|
|
2017-11-18 17:31:49 +03:00
|
|
|
extern bool dev_pm_may_skip_resume(struct device *dev);
|
PCI / PM: Take SMART_SUSPEND driver flag into account
Make the PCI bus type take DPM_FLAG_SMART_SUSPEND into account in its
system-wide PM callbacks and make sure that all code that should not
run in parallel with pci_pm_runtime_resume() is executed in the "late"
phases of system suspend, freeze and poweroff transitions.
[Note that the pm_runtime_suspended() check in pci_dev_keep_suspended()
is an optimization, because if is not passed, all of the subsequent
checks may be skipped and some of them are much more overhead in
general.]
Also use the observation that if the device is in runtime suspend
at the beginning of the "late" phase of a system-wide suspend-like
transition, its state cannot change going forward (runtime PM is
disabled for it at that time) until the transition is over and the
subsequent system-wide PM callbacks should be skipped for it (as
they generally assume the device to not be suspended), so add checks
for that in pci_pm_suspend_late/noirq(), pci_pm_freeze_late/noirq()
and pci_pm_poweroff_late/noirq().
Moreover, if pci_pm_resume_noirq() or pci_pm_restore_noirq() is
called during the subsequent system-wide resume transition and if
the device was left in runtime suspend previously, its runtime PM
status needs to be changed to "active" as it is going to be put
into the full-power state, so add checks for that too to these
functions.
In turn, if pci_pm_thaw_noirq() runs after the device has been
left in runtime suspend, the subsequent "thaw" callbacks need
to be skipped for it (as they may not work correctly with a
suspended device), so set the power.direct_complete flag for the
device then to make the PM core skip those callbacks.
In addition to the above add a core helper for checking if
DPM_FLAG_SMART_SUSPEND is set and the device runtime PM status is
"suspended" at the same time, which is done quite often in the new
code (and will be done elsewhere going forward too).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
2017-10-26 13:12:22 +03:00
|
|
|
extern bool dev_pm_smart_suspend_and_suspended(struct device *dev);
|
|
|
|
|
2008-03-20 00:37:42 +03:00
|
|
|
#else /* !CONFIG_PM_SLEEP */
|
|
|
|
|
2009-03-04 14:44:00 +03:00
|
|
|
#define device_pm_lock() do {} while (0)
|
|
|
|
#define device_pm_unlock() do {} while (0)
|
|
|
|
|
2009-05-25 00:05:42 +04:00
|
|
|
static inline int dpm_suspend_start(pm_message_t state)
|
2008-03-20 00:37:42 +03:00
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2008-03-20 00:39:13 +03:00
|
|
|
#define suspend_report_result(fn, ret) do {} while (0)
|
2008-03-20 00:37:42 +03:00
|
|
|
|
2010-09-23 00:10:57 +04:00
|
|
|
static inline int device_pm_wait_for_dev(struct device *a, struct device *b)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
2011-05-18 01:26:21 +04:00
|
|
|
|
2012-08-17 18:06:59 +04:00
|
|
|
static inline void dpm_for_each_dev(void *data, void (*fn)(struct device *, void *))
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
2014-02-19 16:09:21 +04:00
|
|
|
#define pm_generic_prepare NULL
|
|
|
|
#define pm_generic_suspend_late NULL
|
|
|
|
#define pm_generic_suspend_noirq NULL
|
|
|
|
#define pm_generic_suspend NULL
|
|
|
|
#define pm_generic_resume_early NULL
|
|
|
|
#define pm_generic_resume_noirq NULL
|
|
|
|
#define pm_generic_resume NULL
|
|
|
|
#define pm_generic_freeze_noirq NULL
|
|
|
|
#define pm_generic_freeze_late NULL
|
|
|
|
#define pm_generic_freeze NULL
|
|
|
|
#define pm_generic_thaw_noirq NULL
|
|
|
|
#define pm_generic_thaw_early NULL
|
|
|
|
#define pm_generic_thaw NULL
|
|
|
|
#define pm_generic_restore_noirq NULL
|
|
|
|
#define pm_generic_restore_early NULL
|
|
|
|
#define pm_generic_restore NULL
|
|
|
|
#define pm_generic_poweroff_noirq NULL
|
|
|
|
#define pm_generic_poweroff_late NULL
|
|
|
|
#define pm_generic_poweroff NULL
|
|
|
|
#define pm_generic_complete NULL
|
2008-03-20 00:37:42 +03:00
|
|
|
#endif /* !CONFIG_PM_SLEEP */
|
|
|
|
|
2009-03-04 14:44:00 +03:00
|
|
|
/* How to reorder dpm_list after device_move() */
|
|
|
|
enum dpm_order {
|
|
|
|
DPM_ORDER_NONE,
|
|
|
|
DPM_ORDER_DEV_AFTER_PARENT,
|
|
|
|
DPM_ORDER_PARENT_BEFORE_DEV,
|
|
|
|
DPM_ORDER_DEV_LAST,
|
|
|
|
};
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
#endif /* _LINUX_PM_H */
|