public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>, Arve Hj?nnev?g <arve@android.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Kevin Hilman <khilman@ti.com>
Subject: Re: [linux-pm] Runtime PM discussion notes
Date: Mon, 11 Jul 2011 20:04:38 +0900	[thread overview]
Message-ID: <20110711110435.GF5092@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110711095812.GT5783@atomide.com>

On Mon, Jul 11, 2011 at 02:58:12AM -0700, Tony Lindgren wrote:
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [110708 21:01]:

> > At least the Nexus S doesn't implmeent any of the deep idle
> > infrastructure.  However, I'd expect that you can achieve some power
> > saving from entering system suspend as if *everything* is off then the
> > PMIC can be suspended which can enable additional power savings.  Unless
> > I'm missing something that'd be hard to hit with cpuidle only stuff.

> You should be able to hit the same states from idle no problem. At that
> point the only things on are memory in retention and some wake-up timer.
> Even the timer could be off if you have hardware wake-up events, but then
> system timer won't work the noral way naturally.

Right, but it can be interesting to tell the PMIC that we went into this
mode.  Possibly cpuidle will end up doing this as a result of signals
generated as the CPU core goes down, but at that point it's just s2ram
by another name.

> The only way power down everything in suspend to disk :) Most PMICs have
> some functionality always on so they can charge the battery when it's
> empty.

With some PMICs the truly always on functionality is *very* minimal and
doesn't include chargers, it can be pretty much limited to wake sources
(including power status changes which might start charging if power
appears).

  reply	other threads:[~2011-07-11 11:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTim=aunvBDLincgXX5yYNhvDTk+fhQ@mail.gmail.com>
     [not found] ` <201106102015.47146.rjw@sisk.pl>
     [not found]   ` <BANLkTimgiJGKASGx80=hTBPBQ52ttmp+Kw@mail.gmail.com>
     [not found]     ` <201106150048.43187.rjw@sisk.pl>
2011-06-23 14:51       ` Runtime PM discussion notes Paul Walmsley
2011-06-23 15:23         ` [linux-pm] " Alan Stern
2011-06-23 20:34           ` Rafael J. Wysocki
2011-06-24 19:53             ` Paul Walmsley
2011-06-24 22:27               ` Arve Hjønnevåg
2011-06-25  5:33                 ` Magnus Damm
2011-06-28 19:47                 ` Paul Walmsley
2011-07-09  4:06                   ` Mark Brown
2011-07-11  9:58                     ` Tony Lindgren
2011-07-11 11:04                       ` Mark Brown [this message]
2011-07-11 11:14                         ` Tony Lindgren
2011-07-11 11:26                           ` Mark Brown
2011-07-11 11:32                             ` Tony Lindgren
2011-07-13  7:17                             ` Paul Walmsley
2011-07-13  9:04                               ` Rafael J. Wysocki
2011-07-29 13:41                                 ` Pavel Machek
2011-07-29 19:52                                   ` Rafael J. Wysocki
2011-07-30 20:37                                     ` Pavel Machek
2011-07-30 21:05                                       ` Rafael J. Wysocki
2011-07-30 21:09                                         ` Rafael J. Wysocki
2011-07-30 21:25                                           ` [linux-pm] " Pavel Machek
2011-07-30 21:36                                             ` Rafael J. Wysocki
2011-07-30 22:09                                         ` Pavel Machek
2011-07-30 22:41                                           ` Rafael J. Wysocki
2011-06-25 13:51               ` [linux-pm] " Rafael J. Wysocki
2011-06-24 18:36           ` Paul Walmsley
2011-06-25 18:59             ` Alan Stern

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=20110711110435.GF5092@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=arve@android.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=magnus.damm@gmail.com \
    --cc=paul@pwsan.com \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=tony@atomide.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