From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alexander Gran <alex@zodiac.dnsalias.org>, linux-kernel@vger.kernel.org
Subject: Re: fixing usb suspend/resuming
Date: Thu, 29 Jul 2004 07:16:21 -0700 [thread overview]
Message-ID: <200407290716.21238.david-b@pacbell.net> (raw)
In-Reply-To: <20040729083543.GG21889@openzaurus.ucw.cz>
On Thursday 29 July 2004 01:35, Pavel Machek wrote:
> > See http://bugme.osdl.org/show_bug.cgi?id=2886 ... basically
> > it looks like this problem would show up with any of a dozen
> > or so different drivers, few of which are widely used on systems
> > that use suspend/resume much (laptops!).
>
> Ben H. has some ideas how to fix this. Anyway, storing S-state or D-state in
> integer is bad because someone will get it wrong.
Right, there seems to be agreement that passing an ACPI S-state u32 down to
drivers expecting non-ACPI D-state u32 is a bad idea.. Drivers should see
the right bus-specific D-states ... see
http://www.mail-archive.com/linux-usb-devel%40lists.sourceforge.net/msg26528.html
which touches on some of the issues with what he explained to me.
- Dave.
prev parent reply other threads:[~2004-07-29 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405281406.10447@zodiac.zodiac.dnsalias.org>
[not found] ` <40B74FC2.8000708@pacbell.net>
2004-06-01 14:14 ` fixing usb suspend/resuming Alexander Gran
2004-07-17 17:32 ` David Brownell
2004-07-19 7:27 ` Alexander Gran
2004-07-21 5:05 ` David Brownell
2004-07-29 8:35 ` Pavel Machek
2004-07-29 12:17 ` Nigel Cunningham
2004-07-29 12:51 ` Oliver Neukum
2004-07-29 22:15 ` Nigel Cunningham
2004-07-29 14:07 ` David Brownell
2004-07-29 21:02 ` Pavel Machek
2004-07-29 22:26 ` Nigel Cunningham
2004-07-29 22:39 ` Pavel Machek
2004-07-29 22:51 ` Nigel Cunningham
2004-07-29 14:16 ` 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=200407290716.21238.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alex@zodiac.dnsalias.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.