Ming Lei [off-list ref] writes:
In ioctl path on net_device, the physical deivce is often
touched, but the physical device may have been put into runtime
suspend state already, so cause some utilitis(ifconfig, ethtool,
...) to return failure in this situation.
I have to as the stupid questions again, sorry...
Just wondering, isn't that really a driver problem? The driver will
know whether or not hardware access is required, and should wake up the
device if necessary. Unless I misunderstand something here, this seems
like papering over driver bugs?
Bjørn