LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Oliver Neukum <oliver@neukum.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Nigel Cunningham <ncunningham@crca.org.au>,
	pm list <linux-pm@lists.linux-foundation.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Len Brown <lenb@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alexey Starikovskiy <astarikovskiy@suse.de>,
	David Brownell <david-b@pacbell.net>, Pavel Machek <pavel@ucw.cz>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [RFC][PATCH] PM: Introduce new top level suspend and hibernation callbacks (rev. 6)
Date: Wed, 2 Apr 2008 12:42:15 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0804021238190.5042-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <200804021728.45823.oliver@neukum.org>

On Wed, 2 Apr 2008, Oliver Neukum wrote:

> Am Mittwoch, 2. April 2008 17:13:11 schrieb Alan Stern:
> > Basically yes.  Subsystems and drivers are allowed to keep devices
> > suspended if they were suspended before the system went to sleep.  
> > Remember, the purpose of the resume method is to let drivers know that
> > the system is now awake, not to force them to put their devices into a
> > high-power state.
> 
> Well, sometimes it is exactly that what we desire, eg. as a side effect
> of lsusb. Should the callbacks have different semantics depending on
> the reason you call them? And how should that information be transferred?

Which callbacks are you referring to?  When lsusb opens a device and
does an autoresume, it does not call the same routine as the PM core
does when resuming from a system sleep.  lsusb ends up calling
usb_autoresume_device() whereas the PM core ends up calling
usb_resume(), which is the function you quoted earlier.

Alan Stern


  reply	other threads:[~2008-04-02 16:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 22:17 [RFC][PATCH 0/3] PM: Rework suspend and hibernation code for devices (rev. 3) Rafael J. Wysocki
2008-03-29 22:20 ` [RFC][PATCH 1/3] PM: Introduce new top level suspend and hibernation callbacks (rev. 5) Rafael J. Wysocki
2008-03-30  2:54   ` Rafael J. Wysocki
2008-03-31 21:29     ` [RFC][PATCH] PM: Introduce new top level suspend and hibernation callbacks (rev. 6) Rafael J. Wysocki
2008-04-01  8:15       ` Nigel Cunningham
2008-04-01  8:27         ` Benjamin Herrenschmidt
2008-04-01 14:31           ` Alan Stern
2008-04-01 19:34             ` Nigel Cunningham
2008-04-01 20:16           ` Rafael J. Wysocki
2008-04-01 20:12         ` Rafael J. Wysocki
2008-04-01 20:56           ` Alan Stern
2008-04-01 21:38             ` Nigel Cunningham
2008-04-01 21:59               ` Rafael J. Wysocki
2008-04-01 21:50             ` Rafael J. Wysocki
2008-04-02 14:11               ` Alan Stern
2008-04-02 14:22                 ` Oliver Neukum
2008-04-02 15:13                   ` Alan Stern
2008-04-02 15:28                     ` Oliver Neukum
2008-04-02 16:42                       ` Alan Stern [this message]
2008-04-02 20:11                         ` Oliver Neukum
2008-04-02 20:28                           ` Alan Stern
2008-04-01 21:35           ` Nigel Cunningham
2008-04-01 21:57             ` Rafael J. Wysocki
2008-04-01 22:32               ` Nigel Cunningham
2008-04-01 23:00                 ` Rafael J. Wysocki
2008-04-01  8:37       ` Pavel Machek
2008-04-01 20:23         ` Rafael J. Wysocki
2008-03-29 22:22 ` [RFC][PATCH 2/3] PM: New suspend and hibernation callbacks for platform bus type (rev. 3) Rafael J. Wysocki
2008-03-30  2:56   ` Rafael J. Wysocki
2008-03-29 22:23 ` [RFC][PATCH 3/3] PM: New suspend and hibernation callbacks for PCI " Rafael J. Wysocki

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=Pine.LNX.4.44L0.0804021238190.5042-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=astarikovskiy@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=ncunningham@crca.org.au \
    --cc=oliver@neukum.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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;
as well as URLs for NNTP newsgroup(s).