From: Mark Brown <broonie@sirena.org.uk>
To: Igor Stoppa <igor.stoppa@nokia.com>
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: Thu, 9 Apr 2009 15:33:47 +0100 [thread overview]
Message-ID: <20090409143347.GA22508@sirena.org.uk> (raw)
In-Reply-To: <1239220387.6228.233.camel@localhost>
On Wed, Apr 08, 2009 at 10:53:07PM +0300, Igor Stoppa wrote:
> On Wed, 2009-04-08 at 20:23 +0200, ext Mark Brown wrote:
> > Essentially what they are doing is
> > exactly what you suggest, they've identified that suspend is a low power
> > state and make every effort to enter it as often as possible, including
> > when on a call.
> I'm not suggesting that. Suspend is inadequate for _real_ runtime power
> management. Certainly it is not seamless.
> Of course a smarter approach depends on the HW supporting certain
> features, but if the HW is not there, I'd rather consider the suspend
> based approach a workaround, rather than a real solution.
Oh sure, but in principle it's exactly the same idea and you wouldn't
want to use the Android approach without also trying to drive the system
power down as much as possible while active. Either way you're trying
to drive the system to the lowest power state automatically.
I'm not saying that it's the most lovely idea ever but there does seem
to be a use case, more in terms of stopping user space than anything
kernel side.
> > Clearly there are some issues with this approach but
> > the Android guys did feel that entering suspend was worthwhile for them,
> > especially since their users are able to download applications to the
> > phone.
> I don't think this is anyhow different from the Nokia Internet Tablets.
Technically there's no difference. The differences sound like they are
more on the support side and probably reflect the differences in
distribution chain, support model and expected user base for the
products.
> > Besides, no matter how low the power drain from your CPU when fully
> > gated and at the lowest DVFS setting it's still possible to get a lower
> If you have a proper SoC, it can enter clock stop, lower voltage and
...
> Regulators should have the options to be switched off if they are not
> needed to preserve states, or enter a low power mode when only minimal
> (non functional current) is needed.
Right, the issue is that the system also needs to be able to arrange to
power down the supplies to the SoC for maximum power savings. Good on
chip power management is much more common than the ability to do that
without entering suspend. Like I say, the savings from this are going
to be very small anywy so it's probably not worth worrying too much about.
next prev parent reply other threads:[~2009-04-09 14:33 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
2009-04-08 18:23 ` Mark Brown
2009-04-08 19:53 ` Igor Stoppa
2009-04-09 14:33 ` Mark Brown [this message]
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=20090409143347.GA22508@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=igor.stoppa@nokia.com \
--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