backlight device, suspend/resume...
andy at openmoko.com
Wed Jul 9 08:56:33 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
|> Yes a "purposeful suspend" ability, that suspended enough so we are
|> definitely straight with UARTs and so on, did the Cesar things and then
|> came back up again would be an interesting way to guarantee the clock
|> modification did not trash anything.
|> - -Andy
| Is this different from 'disable' as in 'disable bluetooth', 'disable
| WLAN', and 'disable GSM' (aka "airplane mode")? Those things should
| also probably be able to be as 'purposefully suspended' as possible in
| the interest of battery life.
It should be different, the proposal is the enable or disable state is
not disturbed in a sticky way, same as suspend and resume should leave
things up on resume.
The purpose is to hide the fact we could trash communication on several
peripherals when we change clock underneath.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the openmoko-kernel