public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Stoppa <igor.stoppa@nokia.com>
To: "ext V, Sankara Narayanan" <sankara.narayanan.v@intel.com>
Cc: johannes@sipsolutions.net, linux-pm@lists.linux-foundation.org
Subject: RE: Power event notification patch
Date: Thu, 05 Jul 2007 16:46:35 +0300	[thread overview]
Message-ID: <1183643195.3619.21.camel@localhost.localdomain> (raw)
In-Reply-To: <67670A5CEA5C374B8E7B16D7DC55F9530124746A@bgsmsx413.gar.corp.intel.com>

Hi,
On Thu, 2007-07-05 at 19:09 +0530, ext V, Sankara Narayanan wrote:
> I really can't stop the kernel from going to suspend using my master app
> (well, my app is not really a master app). It is just to inform the apps
> in the user space "Hey, I'm going to suspend, in the time available
> before I go to sleep, do whatever you can do!" whenever kernel goes to
> sleep. And I'm really can't stop the kernel from going to sleep (from a
> theoretical point I can do that as well, but at least I have not
> implemented that).

Yes, i've understood that.

What i'm saying is that your approach:

"Hey, I'm going to suspend, in the time available before I go to sleep,
do whatever you can do!"

is faulty, imo.


What we are doing in Maemo is:

App1 changes states -> App1 saves its state using library
App2 changes states -> App2 saves its state using library
App3 changes states -> App3 saves its state using library
App4 changes states -> App4 saves its state using library
....

Suspend event -> Apps do nothing 


Very simple and deterministic. Note also that you can track is Apps are
saving their state by refcounting and therefore delaying the actual
suspend command.

I hope that it's clear now.

cheers, igor

-- 
Cheers, Igor

Igor Stoppa <igor.stoppa@nokia.com>
(Nokia Multimedia - CP - OSSO / Helsinki, Finland)

  reply	other threads:[~2007-07-05 13:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 12:01 Power event notification patch V, Sankara Narayanan
2007-07-05 12:08 ` Oliver Neukum
2007-07-05 12:17   ` V, Sankara Narayanan
2007-07-05 12:34     ` Oliver Neukum
2007-07-05 12:44       ` V, Sankara Narayanan
2007-07-05 12:51         ` Oliver Neukum
2007-07-05 12:54         ` Igor Stoppa
2007-07-05 13:09           ` V, Sankara Narayanan
2007-07-05 13:12             ` Johannes Berg
2007-07-05 13:17               ` V, Sankara Narayanan
2007-07-05 13:28                 ` Johannes Berg
2007-07-05 13:33                   ` V, Sankara Narayanan
2007-07-06 10:46                     ` Johannes Berg
2007-07-05 13:56                   ` Scott Preece
2007-07-05 13:22               ` Johannes Berg
2007-07-05 13:20             ` Igor Stoppa
2007-07-05 13:39               ` V, Sankara Narayanan
2007-07-05 13:46                 ` Igor Stoppa [this message]
2007-07-05 12:48       ` Johannes Berg
2007-07-06 18:41 ` Greg KH
2007-07-09  4:34   ` V, Sankara Narayanan
2007-07-09 16:34     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2007-07-05 12:02 V, Sankara Narayanan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1183643195.3619.21.camel@localhost.localdomain \
    --to=igor.stoppa@nokia.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=sankara.narayanan.v@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox