From: Dave Jones <davej@redhat.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net,
Matthew Garrett <mjg59@srcf.ucam.org>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by?default on certain device classes
Date: Fri, 3 Aug 2007 10:36:33 -0400 [thread overview]
Message-ID: <20070803143633.GA17138@redhat.com> (raw)
In-Reply-To: <200708031632.07979.oliver@neukum.org>
On Fri, Aug 03, 2007 at 04:32:07PM +0200, Oliver Neukum wrote:
> Am Freitag 03 August 2007 schrieb Dave Jones:
> > On Fri, Aug 03, 2007 at 09:57:45AM +0200, Oliver Neukum wrote:
> >
> > > Kernel developers are a diverser lot than you think ;-)
> > > We don't enable autosuspend in drivers we can't test, except where
> > > the lack of a kernel driver forces us to use a broad swipe. Printers
> > > were tested, too, and most printers seem to work.
> >
> > My experience suggests the opposite. Of the several I've tried so far,
> > none have worked with usb suspend.
>
> vendor:product please.
Here's one that I have handy..
Bus 002 Device 004: ID 04a9:1097 Canon, Inc.
(The others aren't powered on right now, and I'm remote from them ;-)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-08-03 14:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 23:56 [PATCH] USB: Only enable autosuspend by default on certain device classes Matthew Garrett
2007-08-03 1:15 ` Greg KH
2007-08-03 1:47 ` Matthew Garrett
2007-08-03 2:46 ` [linux-usb-devel] " Alan Stern
2007-08-03 6:01 ` David Brownell
2007-08-03 11:28 ` Matthew Garrett
2007-08-03 11:44 ` Oliver Neukum
2007-08-03 12:04 ` Matthew Garrett
2007-08-03 12:26 ` Rogan Dawes
2007-08-03 12:32 ` Matthew Garrett
2007-08-03 14:01 ` David Brownell
2007-08-03 14:09 ` Matthew Garrett
2007-08-03 14:28 ` Alan Stern
2007-08-03 14:33 ` Matthew Garrett
2007-08-03 14:41 ` Alan Stern
2007-08-03 15:10 ` Matthew Garrett
2007-08-03 14:43 ` Jiri Kosina
2007-08-03 14:53 ` [linux-usb-devel] " Dave Jones
2007-08-03 14:58 ` Jiri Kosina
2007-08-03 15:24 ` David Brownell
2007-08-03 15:29 ` Jiri Kosina
2007-08-03 17:47 ` Alan Stern
2007-08-03 15:25 ` Adam Kropelin
2007-08-03 15:31 ` Jiri Kosina
2007-08-03 15:48 ` Dave Jones
2007-08-03 16:49 ` David Brownell
2007-08-03 16:55 ` Adam Kropelin
2007-08-03 15:06 ` Matthew Garrett
2007-08-03 14:37 ` [linux-usb-devel] " David Brownell
2007-08-03 15:03 ` Matthew Garrett
2007-08-03 16:08 ` Oliver Neukum
2007-08-03 17:49 ` Alan Stern
2007-08-03 20:03 ` Dave Jones
2007-08-03 16:29 ` David Brownell
2007-08-03 16:50 ` Matthew Garrett
2007-08-03 17:49 ` Greg KH
2007-08-03 17:44 ` Greg KH
2007-08-03 17:48 ` Matthew Garrett
2007-08-03 19:29 ` Chuck Ebbert
2007-08-03 19:56 ` Pete Zaitcev
2007-08-07 9:14 ` Amit Kucheria
2007-08-03 20:12 ` [linux-usb-devel] " Dave Jones
2007-08-03 21:17 ` Alan Stern
2007-08-03 21:31 ` Dave Jones
2007-08-03 21:33 ` Matthew Garrett
2007-08-03 12:34 ` Felipe Balbi
2007-08-03 6:06 ` David Brownell
2007-08-03 14:22 ` Dave Jones
2007-08-03 14:52 ` David Brownell
2007-08-03 7:57 ` Oliver Neukum
2007-08-03 14:24 ` Dave Jones
2007-08-03 14:32 ` Oliver Neukum
2007-08-03 14:36 ` Dave Jones [this message]
2007-08-03 19:34 ` Pete Zaitcev
2007-08-03 19:45 ` Dave Jones
2007-08-03 20:04 ` Pete Zaitcev
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=20070803143633.GA17138@redhat.com \
--to=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mjg59@srcf.ucam.org \
--cc=oliver@neukum.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 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.