-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | On Mon, 14 Apr 2008 19:10:11 +0100 Andy Green <[EMAIL PROTECTED]> babbled: | |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> Somebody in the thread at some point said: |> | Andy Green wrote: |> |> ~ - If we see any user interaction with the phone, ie, touchscreen, |> |> buttons, we always power the LCM backlight and S3C6400 ready to respond |> |> to what it is he wanted to do |> | |> | Hmm, I'd leave the decision whether to power on the backlight or not |> | to the CPU. Before the CPU is up, there's nothing useful to display |> | anyway, and the CPU (application, really) may very well decide not to |> | bring up the LCM. |> |> OK, fair enough. I guess a button might cause the CPU to make a beep |> for feedback or something. | | the problem is x will bring the screen up the moment it gets any touchscreen | interrupts. backlight then must be on and screen will display whatever contents | it has. we need to do some mods to x to have backlight controls in x and then | leave it entirely to the "screensaver" to decide what to do on wakeup (when x | will report the sceensaver/blank has ended).
No worries -- at the time we are talking about the CPU is dead, no power to the core and no PLLs running. We're talking about this MPU taking over the duty of scanning the touchscreen during this time and detecting a touch and coordinating wake from suspend, specifically if the MPU should start ramping up the backlight during the time the CPU is resuming. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkgISbYACgkQOjLpvpq7dMpraACgjuKDKOvpKTzeEw1bnYRC11KL 1vgAniGAO4SYjLLsBpAa00DP27s5GEGk =GLxQ -----END PGP SIGNATURE-----
