mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Paul Walmsley <paul@booyaka.com>
Cc: linux-usb-devel@lists.sourceforge.net,
	Chuck Ebbert <cebbert@redhat.com>,
	"Renato S. Yamane" <renatoyamane@mandic.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Error -71 on device descriptor read/all
Date: Tue, 19 Jun 2007 20:56:50 +0200	[thread overview]
Message-ID: <200706192056.50656.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706191134160.12843@utopia.booyaka.com>

Am Dienstag, 19. Juni 2007 schrieb Paul Walmsley:
> On Tue, 19 Jun 2007, Oliver Neukum wrote:
> 
> > Am Dienstag, 19. Juni 2007 schrieb Chuck Ebbert:
> >
> >> Try disabling CONFIG_USB_SUSPEND
> >>
> >> [usb developers: what are the drawbacks of doing this?]
> >
> > Increased power consumption.
> 
> speaking of CONFIG_USB_SUSPEND, I've encountered at least one device -- a 
> Canon EOS 5D camera -- that, after the bus suspends, must be powercycled 
> in order to return the camera's interrupt endpoints to a functional state. 
> How are these types of problems handled, currently?  Is this something for 
> a blacklist?

drivers/usb/core/quirks.c

Please try the reset-resume quirk before you use the no-autosuspend quirk.

	Regards
		Oliver


  reply	other threads:[~2007-06-19 18:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 14:45 Renato S. Yamane
2007-06-19 14:58 ` Jiri Kosina
2007-06-19 15:37   ` Renato S. Yamane
2007-06-19 15:55     ` Jiri Kosina
2007-06-19 18:59       ` [linux-usb-devel] " Alan Stern
2007-06-20 11:07         ` Renato S. Yamane
2007-06-20 14:06           ` Alan Stern
2007-06-20 17:29             ` Chuck Ebbert
2007-06-19 16:17 ` Chuck Ebbert
2007-06-19 17:02   ` [linux-usb-devel] " Oliver Neukum
2007-06-19 17:36     ` Paul Walmsley
2007-06-19 18:56       ` Oliver Neukum [this message]
2007-06-19 19:04       ` 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=200706192056.50656.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=paul@booyaka.com \
    --cc=renatoyamane@mandic.com.br \
    /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
Powered by JetHome