-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | On Fri, 18 Apr 2008 08:11:50 +0100 Andy Green <[EMAIL PROTECTED]> babbled: | |> 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. | | yeah - we need both i suspect. we need the pmu to be able to handle touhscreen | and bring up bakclight OR be able to turn that behavior off (it should be
Yes this seems to be a general theme that we are OK with to allow software decision about MPU actions or do it direct. Then we are super flexible. | software controlled in the kenrel). userspace needs to be able to tell the | kenrel: | | * shut down touchscreen and generate no interupts at all | * enable touchscreen (interrupts) (and wake up cpu when they happen) | * disable balckight turn-on on wakeup | * enable backlight turn-on on wakeup OK. | DEFAULT (imho) would be: | * enable touchscreen interrupts | * enable backlight on wakeup OK, but there will be some period ~1s where the user sees white and / or black display from LCM as backlight ramps up but X did not give video back yet. We can see what it looks like and decide. | the rest then is userspace (xserver and then above that wm/desktop and apps) | making all the higher level decisions Yes that is OK if it is understood that "decision" is limited to they are "leaving a will" about what they want to happen when they are in a coma. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkgIUD4ACgkQOjLpvpq7dMoKPQCeLuMxZ8BW5HHPNGSAM0u/Sie1 r7EAoIzC16TA1YyvS7ixG6syD+jt15Fo =yw1V -----END PGP SIGNATURE-----
