public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Subject: Re: Information in PM messages
Date: Tue, 13 Jun 2006 10:25:34 -0700	[thread overview]
Message-ID: <200606131025.35106.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0606091018160.16847-100000@netrider.rowland.org>

On Friday 09 June 2006 7:24 am, Alan Stern wrote:
> On Thu, 8 Jun 2006, David Brownell wrote:
> 
> > > 	A message whose source is USER or DRIVER should not be
> > > 	allowed to resume a device that was suspended by a message
> > > 	whose source was SYSTEM.  In other words, runtime PM and
> > > 	autoresume should not interfere with a system sleep transition.
> > 
> > Why wouldn't that be entirely the driver's responsibility, and
> > something they don't need API changes to achieve?
> 
> Perhaps we don't need to worry about this.
> 
> After all, in most cases it's impossible for a device which is suspended
> as part of a system-sleep transition to get either a runtime-PM resume or
> an autoresume request.  It can only happen in situations where the
> system-sleep did not first freeze all tasks.  In those situations people
> may agree that it is acceptable for the sleep transition to be aborted by
> a user request or an autoresume.
> 
> If that is so then yes, we don't need to alter the PM message structures
> in this way.

I think that's pretty much what I was saying by insisting that the driver's
PM state transitions have to be correct... invalid transtions will always
be invalid, regardless of whether or not the API gets complexified!  :)

- Dave

      reply	other threads:[~2006-06-13 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 21:53 Information in PM messages Alan Stern
2006-06-08 19:57 ` David Brownell
2006-06-09  4:10   ` Alan Stern
2006-06-09 14:24   ` Alan Stern
2006-06-13 17:25     ` David Brownell [this message]

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=200606131025.35106.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    /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