|Copyright:||© 2016 Intel Corporation|
|Author:||Rafael J. Wysocki <firstname.lastname@example.org>|
There are some operations that subsystems or drivers may want to carry out
before hibernation/suspend or after restore/resume, but they require the system
to be fully functional, so the drivers’ and subsystems’
->resume() or even
->complete() callbacks are not
suitable for this purpose.
For example, device drivers may want to upload firmware to their devices after
resume/restore, but they cannot do it by calling
->complete() callback routines (user land
processes are frozen at these points). The solution may be to load the firmware
into memory before processes are frozen and upload it from there in the
->resume() routine. A suspend/hibernation notifier may be used for that.
Subsystems or drivers having such needs can register suspend notifiers that will be called upon the following events by the PM core:
- The system is going to hibernate, tasks will be frozen immediately. This
is different from
PM_SUSPEND_PREPAREbelow, because in this case additional work is done between the notifiers and the invocation of PM callbacks for the “freeze” transition.
- The system memory state has been restored from a hibernation image or an error occurred during hibernation. Device restore callbacks have been executed and tasks have been thawed.
- The system is going to restore a hibernation image. If all goes well,
the restored image kernel will issue a
- An error occurred during restore from hibernation. Device restore callbacks have been executed and tasks have been thawed.
- The system is preparing for suspend.
- The system has just resumed or an error occurred during suspend. Device resume callbacks have been executed and tasks have been thawed.
It is generally assumed that whatever the notifiers do for
PM_HIBERNATION_PREPARE, should be undone for
Analogously, operations carried out for
PM_SUSPEND_PREPARE should be
Moreover, if one of the notifiers fails for the
PM_SUSPEND_PREPARE event, the notifiers that have already succeeded for that
event will be called for
The hibernation and suspend notifiers are called with
They are defined in the usual way, but their last argument is meaningless (it is
To register and/or unregister a suspend notifier use
respectively (both defined in
include/linux/suspend.h). If you don’t
need to unregister the notifier, you can also use the
macro defined in