> Instead of taking the device out of suspended mode to perform the required
> action, the driver is moving to a model where 1) said action may be
> scheduled to a later time - or result from past time work - and 2) rpm handler
> must handle a lot of pm unrelated work.
>
> rtl8169_ethtool_ops.{get_wol, get_regs, get_settings} aren't even fixed yet
> (what about the .set_xyz handlers ?).
>
> I can't help thinking that the driver should return to a state where it
> stupidly
> does what it is asked to. No software caching, plain device access, resume
> when needed, suspend as "suspend" instead of suspend as "anticipate
> whatever may happen to avoid waking up".
>
This rpm related patches just the workaround for the issues reported by end
users. As you say, the Linux kernel should handle these events when driver is
in runtime suspend state.
------Please consider the environment before printing this e-mail.
