On Mon, 16 Feb 2009 21:43:52 -0500 (EST) Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, 16 Feb 2009, Arjan van de Ven wrote: > > > > Set the automatic PM parameters (idle timeout, state to go to, > > > etc.). And disabling automatic PM altogether (effectively the > > > same as setting the idle timeout to infinity). > > > > > > > shouldn't idle timeout etc be internal to the driver? > > Yes policy preferences / constraints makes sense to communicate, > > actual settings do not. For one they keep changing fast all the time > > anyway. > > Sorry, I don't agree. A single driver may control many different > kinds of device -- it may not even be aware of the distinction! > Consider the SCSI disk driver: It has to handle both traditional > rotating media and solid-state disks. Clearly they should have > different runtime PM parameters. But the driver isn't in a good > position to know what those parameters should be. ... and userspace is ? Sorry I don't buy that. Kernel is supposed to abstract the hardware... That's its fundamental task. Now if the driver doesn't know it can get help from the subsystem, that's perfectly fine. (and quiet often the kernel gets updated more often as the userspace) -- 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
