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:26:22 +0900	[thread overview]
Message-ID: <20110711112619.GH5092@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110711111424.GV5783@atomide.com>

On Mon, Jul 11, 2011 at 04:14:24AM -0700, Tony Lindgren wrote:
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [110711 03:59]:

> > 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.

> All PMIC devices should be shut down when not in use, so I don't know
> what else you would configure in the PMIC. Maybe you have something else
> there to configure? Just curious what kind of mess you have to deal with
> compared to the mess I need to deal with :)

The interesting bits are things like being able to kill lots of the SoC
core supplies when the RAM is in retention mode - the CPU needs to go
through its shutdown procedures.

> Also, hitting deeper sleep states from idle is not same as suspend to ram.
> With suspend to ram the system timer is killed while timers behave in a
> normal way when hitting deeper sleep states from idle.

Actually, it just occurred to me that if we're waiting for a system
timer and can hand that off to a suitable timer in the PMIC then we can
do a suspend to RAM for the deep idle state from the hardware point of
view.

  reply	other threads:[~2011-07-11 11:26 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
2011-07-11 11:14                         ` Tony Lindgren
2011-07-11 11:26                           ` Mark Brown [this message]
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=20110711112619.GH5092@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