public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: USB APM suspend
Date: Thu, 09 Oct 2003 20:19:50 -0700	[thread overview]
Message-ID: <3F862556.5080701@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0309221606230.677-100000@ida.rowland.org>

Alan Stern wrote:

> 
> I tried the experiment of getting rid of the calls to pm_send_all().  
> Surprisingly enough, it worked.  That is, when I typed:
> 
> 	apm --suspend
> 
> everything was suspended, in the correct order; and when I pressed a key 
> everything awoke and seemed to be functioning properly.  

Just for the record:  I tried this on 2.6.0-test7, on a system where
APM has worked reliably forever, and it failed.  (That was without even
involving USB -- there are still non-USB PM problems.)

The device_suspend() logic did seem to call things in the right order,
on one machine I hacked with some printks, but when the moment came to
actually enter the APM suspend mode nothing happened ... except for a
delay of maybe a minute, before the system resumed itself.  (FWIW the
PCI suspend methods involved were for yenta_cardbus and agpgart-intel.
Both of those were called after "hda" spun itself down.)

What should happen of course is the APM BIOS takes over and blanks the
display, and the power indicator changes (in my case to a low-frequency
amber blink, no longer solid green).

- Dave




       reply	other threads:[~2003-10-10  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0309221606230.677-100000@ida.rowland.org>
2003-10-10  3:19 ` David Brownell [this message]
2003-09-19 22:14 USB APM suspend Alan Stern
2003-09-19 22:24 ` Greg KH
2003-09-22  0:58 ` 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=3F862556.5080701@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox