linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Udo van den Heuvel <udovdh@xs4all.nl>,
	USB list <linux-usb@vger.kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: 3.15.6 USB issue with pwc cam
Date: Tue, 12 Aug 2014 18:21:38 +0200	[thread overview]
Message-ID: <6676742.btapbsDqkp@avalon> (raw)
In-Reply-To: <53EA350F.2040403@xs4all.nl>

Hi Hans,

On Tuesday 12 August 2014 17:38:55 Hans Verkuil wrote:
> On 08/12/2014 05:07 PM, Hans de Goede wrote:
> > On 08/07/2014 04:49 PM, Udo van den Heuvel wrote:
> >> On 2014-08-04 11:17, Laurent Pinchart wrote:
> >>> (CC'ing Hans de Goede, the pwc maintainer, and the linux-media mailing
> >>> list)
> >
> > Thanks for the bug report. I've been looking into this, and there
> > seem to be 2 problems:
> > 
> > 1: xhci_hcd 0000:02:00.0: ERROR: unexpected command completion code 0x11.
> > 
> > This seems to be what is causing things to not work with a usb-3 port
> > for you. Might be fixed by this commit:
> > https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/drivers
> > /usb/host?h=usb-next&id=3213b151387df0b95f4eada104f68eb1c1409cb3
> > 
> > Can you please do "lspci -nn", and then copy and paste the output here,
> > so that we can see what sort of xhci controller you've (and try to
> > reproduce the problem).
> > 
> > 2: The triggering of a WARN_ON in __vb2_queue_cancel() when called on
> > streamoff. I've been looking at the code and I cannot figure out why this
> > is triggering I'm afraid.
> 
> You can ignore this one.
> 
> The uvc driver is doing messy things with vb2 which causes this warning.
> That said, it will not break things for you. It is just a warning that the
> driver needs to be improved.

I can certainly take the blame when my code needs to be improved, but in this 
case the webcam is supported by the pwc driver, not the uvc driver :-)

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-08-12 16:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53DCE329.4030106@xs4all.nl>
2014-08-04  9:17 ` 3.15.6 USB issue with pwc cam Laurent Pinchart
2014-08-07 14:49   ` Udo van den Heuvel
2014-08-12 15:07     ` Hans de Goede
2014-08-12 15:29       ` Udo van den Heuvel
2014-08-14 10:10         ` Hans de Goede
2014-08-12 15:38       ` Hans Verkuil
2014-08-12 16:21         ` Laurent Pinchart [this message]
2014-08-12 16:27           ` Hans Verkuil
2014-08-12 16:31             ` Udo van den Heuvel
2014-08-14 13:23               ` Mathias Nyman
2014-09-11 10:55                 ` Udo van den Heuvel
2014-08-12 16:35             ` Laurent Pinchart
2014-08-12 16:46               ` Kimmo Taskinen
2014-08-12 17:23       ` Udo van den Heuvel
2014-08-08  3:42   ` 3.15.8 USB issue with uvc cam Udo van den Heuvel
2014-08-08 11:24     ` Udo van den Heuvel

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=6676742.btapbsDqkp@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /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;
as well as URLs for NNTP newsgroup(s).