From: David Brownell <david-b@pacbell.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Zhang Rui <rui.zhang@intel.com>,
Mattia Dongili <malattia@linux.it>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@lists.linux-foundation.org, Len Brown <lenb@kernel.org>,
Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR
Date: Fri, 22 Jun 2007 03:08:26 -0700 [thread overview]
Message-ID: <200706220308.27447.david-b@pacbell.net> (raw)
In-Reply-To: <200706202339.20188.rjw@sisk.pl>
On Wednesday 20 June 2007, Rafael J. Wysocki wrote:
> Well, there's nothing interesting in there, AFAICS:
>
> Device S-state Status Sysfs node
> P0P4 S4 disabled pci:0000:00:1e.0
> BNIC S4 disabled pci:0000:02:05.0
> USB1 S4 disabled pci:0000:00:1d.0
> USB2 S4 disabled pci:0000:00:1d.1
> USB3 S4 disabled pci:0000:00:1d.2
> EUSB S4 disabled pci:0000:00:1d.7
> PS2K S4 disabled pnp:00:0b
> PS2M S4 disabled pnp:00:0c
The interesting thing there is that all those devices are
able to wake from S4 state ... including USB controllers.
That's not very common for USB. EHCI ("EUSB" above) at
least has a spec for how that should work ... it relies on
the PCI Vaux power well to maintain power sessions, though
I don't know that the EHCI code has been tested against
that part of the spec. UHCI likely relies on black magic
to achieve that effect.
- Dave
next prev parent reply other threads:[~2007-06-22 10:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 7:15 [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR Mattia Dongili
2007-05-18 7:22 ` Andrew Morton
2007-05-19 6:48 ` Mattia Dongili
2007-05-19 7:04 ` Andrew Morton
2007-05-19 15:11 ` 2.6.22-rc1 regression: tifm prevents suspending [was: Re: [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR] Mattia Dongili
2007-05-19 16:43 ` Mattia Dongili
2007-05-19 17:17 ` Michal Piotrowski
2007-05-19 18:29 ` Rafael J. Wysocki
2007-05-19 20:50 ` Michal Piotrowski
2007-05-20 6:14 ` [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR Mattia Dongili
2007-05-20 6:47 ` Andrew Morton
2007-05-20 6:59 ` Mattia Dongili
2007-05-20 18:38 ` David Brownell
2007-05-21 0:41 ` Mattia Dongili
2007-05-21 1:22 ` David Brownell
2007-05-21 2:05 ` Mattia Dongili
2007-06-19 8:57 ` Zhang Rui
2007-06-19 9:30 ` Mattia Dongili
2007-06-19 9:55 ` Zhang Rui
2007-06-19 11:26 ` Rafael J. Wysocki
2007-06-20 1:52 ` Zhang Rui
2007-06-20 21:39 ` Rafael J. Wysocki
2007-06-22 10:08 ` David Brownell [this message]
2007-06-22 14:33 ` [linux-pm] " Alan Stern
2007-06-19 10:09 ` Mattia Dongili
2007-06-19 14:20 ` Alan Stern
2007-06-20 14:45 ` [linux-pm] " Mattia Dongili
2007-06-20 16:33 ` Alan Stern
2007-06-21 6:42 ` Mattia Dongili
2007-06-21 7:28 ` Zhang Rui
2007-06-21 9:22 ` Mattia Dongili
2007-06-21 15:45 ` Alan Stern
2007-06-22 9:22 ` Mattia Dongili
2007-06-22 9:43 ` David Brownell
2007-06-22 14:07 ` Alan Stern
2007-06-22 10:02 ` David Brownell
2007-06-22 14:22 ` Alan Stern
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=200706220308.27447.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=malattia@linux.it \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
/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