Hi!
> > So how about this instead? We have a policy-oriented list of power
> > settings, pretty much the same as it is now. Things like Full-Power,
> > Standby, Suspend-to-RAM, Suspend-to-Disk, Power-Off, and
> > Selective-Suspend. The values are descriptive only; they don't indicate
> > anything about the actual power available to or power used by a device.
> > They only indicate the reason for making a power-level change. And they
> > are not stored in the dev_pm_info structure.
>
> Pavel says this is <linux/kernel.h> system_state, but I don't
> see the mapping. Used by "ide-disk.c", and little else.
> SYSTEM_BOOTING isn't a power level...
Unless you want to do powermanagment during boot
(and I think boot is complex
enough already), that should
not matter.
> I'd be interested in seeing system power policies be pluggable
> objects like cpufreq governors, i/o schedulers, and so forth.
???
> A sysadmin would choose from a list of policies. Some would
> take command like "suspend to disk" (on systems with disks),
> some architectures would add their own commands. If you
> suspend from a "max power savings" policy, you'd normally
> resume into that same policy, not go to full power.
Suspend to disk is not a policy and no, we do not want it to be pluggable.
swsusp already has perfectly working user interface.
Actually, it has 3 of them. We do not want 4th.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
