Hi! > >...but adding new /sys/power/state might be okay. We should not have > >introduced "standby" in the first place [but I guess it is not worth > >removing now]. If something has more than 2 states (does user really > >want to enter different states in different usage?), I guess we can > >add something like "deepmem" or whatever. Is there something with > >more > >than 3 states? > > In most of the cases I'm thinking of, it wouldn't be a user > requesting a state but rather software (say, a cell phone > progressively entering lower power states due to inactivity). I > haven't noticed a platform with more than 3 low-power modes so far, Are not your power states more like cpu power states? These are expected to be system states, and sleeping system does not take calls, etc... (Unless you have second cpu that wakes you on incoming call, that is). > but I'm sure it'll happen soon. If the time isn't right for > incompatible changes to these interfaces then I guess mapping standby > and mem to platform-specific things will work for now, maybe with > some tweak to allow a choice of actual state entered. At some more > opportune time in the future I'll suggest an attribute that allows a > choice of platform-specific method of suspend-to-mem, somewhat like > the "disk" attribute for suspend-to-disk. Or just resurrect your original patch when one more state is needed. -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
