> On Thu, 5 Jan 2006, Pavel Machek wrote: > > > Its okay with me to add more states _when they are needed_. Just now, > > many drivers do not even handle system suspend/resume correctly. > > > 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. > > Embedded devices are a great example. Consider putting Linux on a > portable phone. The individual components can have many different power > states, depending on which clock and power lines are enabled. "on" and > "suspend" won't be sufficient to handle the vendor's needs. Consider putting Linux on a portable phone. It could contain 13-bit bytes. Does that mean we should support 13-bit bytes in linux? No. People are running Linux on cellphones today, and they are running for weeks in standby, too. And runtime suspend support is still terminally broken, so they somehow get around that. Do you have example of device that has multiple "sleep states" and it makes sense to use them? There are examples of devices that have multiple "on states". IIRC graphics cards can already control their clock tick rates. I hope we are not trying to solve that one here. Pavel -- Thanks, Sharp!
