common watchdog interface: handling of suspend/resume



i'm not sure if it is possible to integrate this into the common code
(be great if we could), but we should codify the expected behavior for
the suspend/resume functions. from looking at the 8 that implement
the pm functions, they seem to all do:
suspend(): turn off the watchdog
resume(): turn on the watchdog if it was running

some other issues raised:
- this device should not be able to be selective suspended ... in
other words, you only want to "suspend" the watchdog if the whole
system is going to be suspend
- should the nowayout option be checked at all ?
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • [patch 21/38] pm: vmwatchdog power management callbacks.
    ... operation and suspend cannot work together in a reliable fashion, ... The watchdog can also be active with no open file descriptor. ... static int vmwdt_expect_close; ... return ret; ...
    (Linux-Kernel)
  • Re: Fw: 2.6.9-rc1-mm4: swsusp + AMD64 = LOCKUP on CPU0
    ... Just disable the watchdog. ... disabled interrupts. ... Attempting to suspend to disk. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)