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.
> >
> > This value is already in system_state variable.
>
> That's the value for the current setting, right? Drivers will also need
> to know the value for the proposed new setting.
No, thats "new" value.
> And while I remember, is there any globally-accessible flag available for
> drivers to check during bootup that will tell them whether or not the boot
> is part of a resume-from-disk?
No. (system can not know if it is going to resume during boot).
> > We can not reserve 0 any more, at least not for PCI devices. [0 is
> > actually the only one that is well defined -- full power :-)]
> > Otherwise this looks okay to me.
>
> If we change from using raw integers to using enumeration constants then
> the actual numerical value doesn't matter.
Actually it will still matter, unless you volunteer to audit all
drivers.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
