All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.osdl.org
Subject: Re: RFC -- updated Documentation/power/devices.txt
Date: Mon, 24 Jul 2006 08:15:04 -0700	[thread overview]
Message-ID: <200607240815.05332.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0607241040400.6638-100000@iolanthe.rowland.org>

On Monday 24 July 2006 7:51 am, Alan Stern wrote:
> On Mon, 24 Jul 2006, Rafael J. Wysocki wrote:

> > So, it looks like the core will only need to tell the driver to "resume"
> > with the implicit "go directly to the saved state" meaning and the
> > driver will actually decide what to do.
> 
> And this implies that the meanings of the suspend() and resume() method
> calls are different from what people might normally think.

No ...

> suspend()   
> doesn't really mean "Put your device into a low-power state"; it means
> "The system is going into a suspend, so remember the device's current
> power state and take whatever actions are appropriate".

Which is exactly what it means today.


> For example, if 
> the device is already in a low-power state then it might be appropriate to
> do nothing at all.

Ditto.


> Likewise, resume() doesn't mean "Change your device to fully ON"; it means
> "The system is waking up from a suspend, so put your device back into
> whatever power state it was in before the suspend occurred".

It means "put it back in a fully operational state".

And whether that state is "full on", or one of the "runtime suspend" states,
or whether it goes into "full on" and then automagically into a "runtime suspend",
doesn't matter externally.  And can't even be noticed without test setups
measuring differential power usage between different configurations...


> These meanings may not be entirely consistent with the way the PM core
> works now,

I don't believe any semantic change is being discussed here.


> but to me they make more sense.  To make the core consistent 
> with this approach wouldn't require much of a change.  Basically we just
> have to rip out all the stuff referring to dev->power.power_state, which
> needs to be done anyway.

Considering how few drivers use dev->power.power_state, it's easier to
say the problem is in the ones that use it  ... rather than the ones that
ignore it and act as I've described above! :)

- Dave



> Alan Stern
> 

  reply	other threads:[~2006-07-24 15:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 22:25 RFC -- updated Documentation/power/devices.txt David Brownell
2006-07-11  5:56 ` Andrew Morton
2006-07-11 16:38   ` David Brownell
2006-07-11 21:57   ` David Brownell
2006-07-12 12:25     ` Pavel Machek
2006-07-12 14:04     ` Alan Stern
2006-07-12 15:45       ` David Brownell
2006-07-12 16:03         ` Alan Stern
2006-07-23  1:37           ` David Brownell
2006-07-23  3:59             ` Alan Stern
2006-07-23 10:50               ` Rafael J. Wysocki
2006-07-23 13:03                 ` Alan Stern
2006-07-23 22:45                   ` Rafael J. Wysocki
2006-07-24  3:22                     ` David Brownell
2006-07-24  9:46                       ` Rafael J. Wysocki
2006-07-24 14:51                         ` Alan Stern
2006-07-24 15:15                           ` David Brownell [this message]
2006-07-24 15:42                             ` Alan Stern
2006-07-24 17:11                               ` David Brownell
2006-07-24 20:44                                 ` Alan Stern
2006-07-24 21:19                                   ` David Brownell
2006-07-25 15:42                                     ` Alan Stern
2006-08-10 23:38                                     ` [patch 2.6.18-rc] " David Brownell
2006-07-23 16:22               ` RFC -- " David Brownell
2006-07-11 14:40 ` Pavel Machek
2006-07-11 21:28 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-07-11  7:56 Woodruff, Richard
2006-07-11 16:51 ` David Brownell

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=200607240815.05332.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.