WSOD solutions??

Andy Green andy at openmoko.com
Thu Dec 4 01:01:53 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| Further plans: modify driver to take down the complete LCM via LDO6
instead of
| entering deep_suspend. This seems to be the more reasonable approach for
| saving power while LCM disabled anyway, and it might cure WSOD as the
LCM is
| powered up from suspend-mode the same way as on boot. Side-effects still
| under investigation (sneak currents, any persistent data lost during
power
| down, timing issues for LCM coming up)

Any reason none of this is on the Trac report?

The hard reset line we operate into the LCM should make whether the
power to it is up in suspend moot... neither does it explain why the
WSOD comes with the blanking changes that are nothing to do with suspend.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkk3HfEACgkQOjLpvpq7dMqbAgCghkALQA/yCZAFmhvdj8xHt62y
l8kAn1tI0k+8mKkyzOl8dXrZJ92TfPDo
=P6GS
-----END PGP SIGNATURE-----



More information about the support mailing list