Re: [PATCH 1/8] PM: Add suspend block api.

Tony Lindgren
2010-05-07T22:00:26Z

* Matthew Garrett <mjg@redhat.com> [100507 14:44]:
> On Fri, May 07, 2010 at 02:42:11PM -0700, Tony Lindgren wrote:
> > * Matthew Garrett <mjg@redhat.com> [100507 14:34]:
> > > How do you know to wake the process up in response to the keypress?
> >
> > Does it matter for processes that are not "certified"? Maybe you
> > could assume that you can keep it stopped until the screen is on
> > again, or some other policy.
>
> Yes, it matters. You don't necessarily know whether to turn the screen
> on until the app has had an opportunity to process the event. This is
> exactly the kind of use case that suspend blocks are intended to allow,
> so alternatives that don't permit that kind of use case aren't really
> adequate alternatives.

Hmm, I'm thinking there would not be any need to turn the screen on
for the broken apps until some other event such as a tap on the screen
triggers the need to turn the screen on.

If it's a critical app, then it should be fixed so it's safe to keep
running.

And yeah, I guess you could cgroups to categorize "timer certified"
and "broken" apps.

Regards,

Tony