public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Null suspend/resume functions
Date: Mon, 23 Nov 2009 11:02:36 +0000	[thread overview]
Message-ID: <20091123110236.GB24326@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20091121234509.GC1411@ucw.cz>

On Sun, Nov 22, 2009 at 12:45:10AM +0100, Pavel Machek wrote:

> So you place a comment there; it should be there anyway. Having nop
> during suspend/resume *is* unusual, and it should raise red flags.

This isn't a good assumption here.  Remember that this is for runtime PM
so if we're getting as far as these calls then the driver has already
told the core that it is idle, which probably means that the hardware is
already quieseced.  For a lot of hardware that will mean that the only
thing left to do in order to suspend is to (possibly) remove power and
in many cases (as with SH) that's going to be done by the bus rather
than the device.  It's a bit more likely that some activity will be
needed on resume but in many cases the device gets fully reprogrammed on
when it becomes active anyway.

Looking at it another way a key goal of runtime PM is to get the bus
involved in the process - if we can do things at device level to reduce
power consumption then there's no need to go through runtime PM to do
them.

> Plus, if we allowed NULLs there, we'd not know if the driver does not
> implement it because it is not neccessary, or because they don't care.

Again, in order to use runtime PM the driver must already be doing
explicit calls so it should be fairly clear that the driver is trying to
support suspend.

  reply	other threads:[~2009-11-23 11:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ud43sjtaf.wl%morimoto.kuninori@renesas.com>
     [not found] ` <20091109105858.GB1245@sirena.org.uk>
2009-11-09 13:31   ` [alsa-devel] [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support Mark Brown
     [not found]   ` <20091109133136.GC1245@sirena.org.uk>
2009-11-16 15:30     ` Null suspend/resume functions Mark Brown
     [not found]     ` <20091116153000.GB29479@sirena.org.uk>
2009-11-16 19:07       ` Rafael J. Wysocki
2009-11-17 11:52       ` Pavel Machek
     [not found]       ` <20091117115236.GB1376@ucw.cz>
2009-11-17 12:41         ` Mark Brown
     [not found]         ` <20091117124125.GD823@rakim.wolfsonmicro.main>
2009-11-18 16:09           ` Pavel Machek
     [not found]           ` <20091118160908.GD20887@elf.ucw.cz>
2009-11-19 11:21             ` Mark Brown
     [not found]             ` <20091119112102.GF9763@rakim.wolfsonmicro.main>
2009-11-21 23:45               ` [linux-pm] " Pavel Machek
2009-11-23 11:02                 ` Mark Brown [this message]
2009-11-24 11:57                   ` Pavel Machek
2009-11-17 12:46       ` Magnus Damm
     [not found]       ` <aec7e5c30911170446n71031671i48aca11f5276405d@mail.gmail.com>
2009-11-17 12:59         ` Mark Brown
     [not found]         ` <20091117125901.GF823@rakim.wolfsonmicro.main>
2009-11-17 22:14           ` Rafael J. Wysocki
2009-11-18 10:09           ` Magnus Damm
     [not found]           ` <aec7e5c30911180209x1981978es80db2dadf7dd8ef4@mail.gmail.com>
2009-11-18 12:05             ` Mark Brown
     [not found]           ` <200911172314.04396.rjw@sisk.pl>
2009-11-18 13:41             ` Mark Brown

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=20091123110236.GB24326@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    /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