PM / sleep: Mention async suspend in PM_TRACE documentation
Document pm_tracing actually affecting suspend in non-trivial way. Signed-off-by: Pavel Machek <pavel@ucw.cz> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
parent
d78cb3680c
commit
a03ff6f20c
1 changed files with 4 additions and 0 deletions
|
@ -69,6 +69,10 @@ Reason for this is that the RTC is the only reliably available piece of
|
|||
hardware during resume operations where a value can be set that will
|
||||
survive a reboot.
|
||||
|
||||
pm_trace is not compatible with asynchronous suspend, so it turns
|
||||
asynchronous suspend off (which may work around timing or
|
||||
ordering-sensitive bugs).
|
||||
|
||||
Consequence is that after a resume (even if it is successful) your system
|
||||
clock will have a value corresponding to the magic number instead of the
|
||||
correct date/time! It is therefore advisable to use a program like ntp-date
|
||||
|
|
Loading…
Reference in a new issue