On Mon, 16 Feb 2009 08:06:13 +0100 Oliver Neukum <oliver@xxxxxxxxxx> wrote: > Am Monday 16 February 2009 03:20:12 schrieb Arjan van de Ven: > > >or > > > network or similar where the driver cannot shut the device down > > > without losing the ability to detect activity (ie, switch your PHY > > > off is nice but you lose the ability to monitor the link for > > > example). > > > > what this needs is a separation between "interface down, all off" > > and "interface down enough so that link detection works". > > Some NICs can go all the way down and still do link detection, > > others cannot. This is obviously something the driver will know, > > nothing else in the system should know. > > Why shouldn't user space know the consequences of still requesting > a service and be able to decide on that basis which services to > request? That's not what I said. Userspace should not be the part that goes "oh this is a realtek not an intel nic, so ..." That is the drivers job. Userspace should just be the part that says "I'm interested in link notifications". The driver then just goes to the lowest power state for its device that still gives those notifications. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
