> > > I think we need to make /sys/power/state handle S1.
> > >
> > > There are two cases
> > >
> > > 1. Platform supports S1, but does not support S3.
> > >
> > > This is more common. You see this a lot on server-class machines.
> > >
> > > We could make "mem" simply mean S1 here b/c it is effectively
> > > the closest thing to S3.
Today, this system would list "standby" in /sys/power/state,
but not "mem". I have a system like that here ...
> > > 2. Platform supports both S1 and S3.
> > >
> > > This is pretty rare -- at least on the systems I've got.
> > > I'd like the generic interface be able to describe and handle this case.
Today, this system would list both "standby" and "mem"
in /sys/power/state. I have a system like that here ...
3. (ACPI) platform supports S3 but not S1
Today, this system would list "mem" in /sys/power/state,
but not "standby". I have a system like that here ...
> > > I'm open to suggestions on what to call S1 if it isn't called "mem".
> >
> > 'standby'? That's what occurs to me from previous M$ usage.
>
> Yes, something like that, I think..
Good news ... it already works that way!!! :)
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
