On ?t 05-01-06 16:37:52, Alan Stern wrote:
> > > And it's not all that complex. Certainly no more complex than forcing
> > > userspace tools to use {"on", "D1, "D2", "suspend"} instead of the
> > > much-more-logical {"D0", "D1", "D2", "D3"}.
> >
> > It is not much more logical. First, noone really needs D1 and
> > D2. Plus, people want to turn their devices on and off, and don't want
> > and should not have to care about details like D1.
>
> Who are you to say what people really need? What about people who want to
> test their PCI device and see if it behaves properly in D1 or D2? How are
> they going to do that if you don't let them put it in that state?
> What about people with platform-specific non-PCI devices that have a whole
> bunch of different internal power states? Why force them to use only two
> of those states?
Its okay with me to add more states _when they are needed_. Just now,
many drivers do not even handle system suspend/resume correctly.
> The kernel isn't supposed to prevent people from doing perfectly legal
> things. The kernel should provide mechanisms to help people do what they
> want.
We are not adding random crap to kernel just because "someone may need
it". And yes, having aliases counts as "random crap". Perfectly legal
but totally useless things count as a random crap, too.
Bring example hardware that needs more than two states, implement
driver support for that, and then we can talk about adding more than
two states into core code.
Pavel
--
Thanks, Sharp!
