fix broken/dubious driver suspend() methods

From: Mauro Carvalho Chehab <mchehab@infradead.org>

Applied the rellevant v4l-dvb part of this patch from 
David Brownell <dbrownell@users.sourceforge.net>

kernel-sync:

Original description:

Small driver suspend() fixes in preparation for the PRETHAW events:

 - Only compare message events for equality against PM_EVENT_* codes;
   not against integers, or using greater/less-than comparisons.
   (PM_EVENT_* should really become a __bitwise thing.)

 - Explicitly test for SUSPEND events (rather than not-something-else)
   before suspending devices.

 - Removes more of the confusion between a pm_message_t (wraps event code)
   and a "state" ... suspend() originally took a target system state.

These updates are correct and appropriate even without new PM_EVENT codes.

benh: "I think in the Mesh case, we should handle the freeze case as well or
we might get wild DMA."

Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>

0 files changed, 0 insertions, 0 deletions