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: Update on USB PM state (2.6.15 queue)
Date: Wed, 28 Sep 2005 09:57:06 -0700	[thread overview]
Message-ID: <200509280957.06073.david-b@pacbell.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]

I just thought I'd provide a quick update on the state of USB PM,
at least according to my testing(*)  after the patches that are now
in Greg's 2.6.15 queue(**) ... I just forwarded the patch overviews
to this list, the details are on linux-usb-devel.

  - Suspend/resume of the PCI devices through sysfs behaves again ...
    it seems to have broken badly sometime after 2.6.10 or 2.6.11

  - Likewise it behaves through swsusp "shutdown/reboot", both with
    and without devices attached.

  - I have one system on which S1 suspend/resume works, at
    least if I use PS/2 keyboard to trigger wakeup.

  - On some other systems, both S1 and S3 suspend fail; the
    system dies in ACPI during wakeup processing.

As for remote wakeup, using a USB keyboard, that still looks OK
(no regressions needed fixing) except when ACPI kicks in:

  - For "runtime PM" scenarios where individual devices and
    hubs (including root hubs) are suspended, the relevant
    parts of the device tree wake up just fine.

  - For "system PM" scenarios, and with /proc/acpi/wakeup
    tweaked to enable all wakeup events, mixed results:

        * The system where S1 works seems to run into some
          ACPI bugs; the last messages relate to overflow,
          evidently the wakeup signal is never acknowledged.

        * Those other systems don't have any better luck
          when the S1/S3 resume signal is a USB wakeup than
          any other kind of wakeup.

Compared to the last time I tested this, it's good to at least
see the USB remote wakeup signals waking the system up; those
seem to be ACPI improvements.  But it still looks like the
cases I most want to see working (S1, S3) are failing on PCs.

There are a few small USB PM updates on the way from me (call
it all cleanups), and Alan's planning some updates too.

- Dave

(*)  EHCI and OHCI only; no UHCI boxes.

(**) http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2005-09-28 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 16:57 David Brownell [this message]
2005-10-04 13:03 ` Update on USB PM state (2.6.15 queue) Pavel Machek
2005-10-05 14:57   ` David Brownell
2005-10-06  6:38     ` Pavel Machek

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=200509280957.06073.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