Not true for network cards. Somebody might be running NFS
over it. The problem is that you cannot tell (or rather shouldn't - it's
a layering violation).
Anything that is used for paging needs to be back to life before
you can think about resurrecting user space.
Also you need to bring keyboards back to life early to make
sysreq work.
Secondly, you need a way to get essential devices to work in
all cases. If you implement it, why not use it?
> The device could just mark itself as unusable at suspend time, then at
> resume it schedule_work()s something to reload the firmware and
> complete reinitialization. Shortly after userspace is back in action,
> the device will come back to life.
Is supposed to. You cannot put blind trust into that. You need to use
a pretty arbitrary timeout to deal with this.
I fail to see technical improvements here.
Regards
Oliver
-
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/