From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: non-working UVC device 058f:5608
Date: Mon, 09 Jun 2014 11:25:01 +0200 [thread overview]
Message-ID: <17531102.o7hyOUhSH7@avalon> (raw)
In-Reply-To: <1402299186.4148.3.camel@jlt4.sipsolutions.net>
Hi Johannes,
On Monday 09 June 2014 09:33:06 Johannes Berg wrote:
> Hi Laurent,
>
> Thanks for the quick reply!
You're welcome.
> > > and then the kernel message repeats forever, while I can't even exit
> > > uvccapture unless I kill it hard, at which point I get
> > >
> > > xhci_hcd 0000:00:14.0: Signal while waiting for configure endpoint
> > > command
> > > usb 1-3.4.4.3: Not enough bandwidth for altsetting 0
> > >
> > > from the kernel.
> >
> > This looks like low-level USB issues, CC'ing the linux-usb mailing list.
>
> Ok.
>
> > > Any thoughts? Just to rule out hardware defects I connected it to my
> > > windows 7 work machine and it works fine without even installing a
> > > driver.
> >
> > Could you try connecting it to an EHCI controller instead of XHCI on a
> > Linux machine ?
>
> Indeed, that works! Interestingly, it works neither on a USB3 port
> directly, nor on a USB2 hub behind the USB3 port.
I would thus be tempted to classify this as an XHCI controller issue. linux-
usb should be the right list to get help. I've CC'ed Mathias Nyman, the XHCI
maintainer.
Johannes, could you enable USB debugging in the linus/master kernel and
provide a kernel log ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-06-09 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 21:51 non-working UVC device 058f:5608 Johannes Berg
2014-06-08 22:29 ` Laurent Pinchart
2014-06-09 7:33 ` Johannes Berg
2014-06-09 9:25 ` Laurent Pinchart [this message]
2014-06-09 9:59 ` Johannes Berg
2014-06-09 10:27 ` Johannes Berg
2014-06-09 10:29 ` Johannes Berg
2014-07-21 16:34 ` Laurent Pinchart
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=17531102.o7hyOUhSH7@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=johannes@sipsolutions.net \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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