From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: torvalds@osdl.org, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [BK PATCH] USB fixes for 2.6.0-test7
Date: Fri, 10 Oct 2003 17:43:38 -0700 [thread overview]
Message-ID: <3F87523A.1030100@pacbell.net> (raw)
In-Reply-To: <20031010231820.GA18566@kroah.com>
Greg KH wrote:
> ... Oh, and suspend now works for USB devices, thanks to Paul :)
And on some systems, the resume path even works ... :)
The D3cold resume path -- which should behave very much
like resuming from software suspend -- can be made to
self-deadlock in some cases: dpm_sem is held while the
resume callbacks are made, so they deadlock when calls to
device_del (for getting rid of the old device tree) try
to grab the same lock.
So don't get your hopes up too far yet -- but yes,
that usbcore patch does help some configs a bunch.
- Dave
prev parent reply other threads:[~2003-10-11 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 23:18 [BK PATCH] USB fixes for 2.6.0-test7 Greg KH
2003-10-11 0:43 ` 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=3F87523A.1030100@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=torvalds@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