The fact that we confuse the driver methods for putting the hardware in a low power state
(suspending) and the driver methods for quiescing a device and being prepared for it to
disappear results in unfixable infrasturcture bugs and unclear semantics.
So the current set of suspend/resume and hibernate operations must be
reexamined if we are to have something that is sane, and generally implentable.
Just a few more drivers is a nice idea. But the driver authors can't do that if we don't have
clear expectations of what the functions they are supposed to implement should do.
In fact except for some goofy corner cases. We should be able to get away with no operations
for hibernation. The fact that the last propsal has more driver methods for hibernation shows
that the design while it may be sane from the infrastructure point of view. Still has a ways
to go before it makes sense from a driver and mainteance point of view.