From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Mark Brown <broonie@sirena.org.uk>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
Nigel Cunningham <ncunningham@crca.org.au>
Subject: Re: [RFC Disable suspend on a specific device] This is a little change in linux power scheme
Date: Wed, 08 Apr 2009 19:44:01 +0300 [thread overview]
Message-ID: <1239209041.6228.217.camel@localhost> (raw)
In-Reply-To: <20090408114212.GK20122@sirena.org.uk>
On Wed, 2009-04-08 at 13:42 +0200, ext Mark Brown wrote:
> On Wed, Apr 08, 2009 at 10:34:56AM +0200, Rafael J. Wysocki wrote:
>
> > I think this is a rather fundamental issue and it requires some more thought.
>
> > What platform is your device based on, BTW?
>
> FWIW this is an issue for a very large proportion of modern mobile phone
> platforms - when on a call they can often suspend the bulk of the system
> while leaving the audio path used for the call alive (normally some
> combination of the telephony modem, audio CODEC and bluetooth chipset)
> and wake up if the user presses a button or similar.
That might be the outcome, but it should be simply because those parts
which are not in use are idle and therefore can enter spontaneously into
a low power state.
--
Cheers, Igor
---
Igor Stoppa
Maemo Software - Nokia Devices R&D - Helsinki
next prev parent reply other threads:[~2009-04-08 16:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 10:29 [RFC Disable suspend on a specific device] This is a little change in linux power scheme Michael Trimarchi
2009-04-07 13:45 ` Rafael J. Wysocki
2009-04-07 15:39 ` Michael Trimarchi
2009-04-07 18:55 ` Rafael J. Wysocki
2009-04-07 19:01 ` Michael Trimarchi
2009-04-07 20:40 ` Pavel Machek
2009-04-07 20:57 ` Rafael J. Wysocki
2009-04-07 21:31 ` Alan Stern
2009-04-07 21:38 ` Pavel Machek
2009-04-07 22:25 ` Nigel Cunningham
2009-04-08 5:59 ` Michael Trimarchi
2009-04-08 8:13 ` Rafael J. Wysocki
2009-04-08 8:24 ` Michael Trimarchi
2009-04-08 8:34 ` Rafael J. Wysocki
2009-04-08 8:45 ` Michael Trimarchi
2009-04-07 8:06 ` Pavel Machek
2009-04-20 12:46 ` Mark Brown
2009-04-20 12:55 ` Michael Trimarchi
2009-04-08 11:42 ` Mark Brown
2009-04-08 16:44 ` Igor Stoppa [this message]
2009-04-08 18:23 ` Mark Brown
2009-04-08 19:53 ` Igor Stoppa
2009-04-09 14:33 ` Mark Brown
2009-04-07 21:40 ` Rafael J. Wysocki
2009-04-08 11:53 ` Mark Brown
2009-04-08 16:45 ` Igor Stoppa
2009-04-10 11:17 ` Pavel Machek
2009-04-08 20:37 ` Alan Stern
2009-04-08 21:25 ` Michael Trimarchi
2009-04-08 21:56 ` Rafael J. Wysocki
2009-04-09 18:27 ` Alan Stern
2009-04-09 22:33 ` Rafael J. Wysocki
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=1239209041.6228.217.camel@localhost \
--to=igor.stoppa@nokia.com \
--cc=broonie@sirena.org.uk \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ncunningham@crca.org.au \
/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