From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sarah Sharp <sarah.a.sharp@intel.com>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org, "Ryan,
Mark D" <mark.d.ryan@intel.com>
Subject: Re: Dell XPS 12 USB camera bulk mode issues
Date: Wed, 26 Feb 2014 15:36:22 +0100 [thread overview]
Message-ID: <2437951.gNx7vUrxFR@avalon> (raw)
In-Reply-To: <20140225214956.GC4035@xanatos>
Hi Sarah,
On Tuesday 25 February 2014 13:49:56 Sarah Sharp wrote:
> Hi Laurent and Mauro,
>
> Mark has running into issues with the Realtek integrated webcam on a Dell
> XPS 12 system that uses bulk endpoints. The webcam shows visible glitches
> with certain resolutions (stripes of frame missing, distorted images, purple
> and green colors, blank image, or missing the bottom half of the image).
How frequent are those issues, do they occur every frame (or nearly every
frame), or are they transient ?
> The webcam works fine in Windows. The webcam works fine in Linux if we
> upgrade the firmware to make the camera use isochronous endpoints rather
> than bulk endpoints. This makes us suspect an issue with bulk mode.
>
> How is the Linux support for bulk mode cameras? If it's supposed to work,
> could we be dealing with a camera that doesn't conform to the bulk mode USB
> video class spec?
It's supposed to work, I'm running a test with a bulk device right now using
the latest linuxtv/master branch (or, to be accurate, the V4L subsystem from
that branch compiled for a 3.10 kernel).
We might be dealing with a device that doesn't conform to the spec, with a bug
in the uvcvideo driver that happened to remain unnoticed until now, or just
with a gray area in the spec that has been understood differently by the
device manufacturer, Microsoft and me.
> Details:
> --------
>
> I tested using Ubuntu with a 3.14-rc4 kernel with guvcview.
>
> Resolutions that work:
>
> YUYV, resolutions:
> 640x480
> 160x120
> 352x288
> 848x480
> 960x540
> MJPG, resolutions:
> 160x120
> 320x240
> 352x288
>
> Resolutions that fail:
>
> YUYV, resolutions:
> 320x180
> 320x240
> 424x240
> 640x360
> MJPG, resolutions:
> 640x480
> 320x180
> 424x240
> 640x360
> 848x480
> 960x540
> RGB3, any resolution. (In fact, this seems to hang guvcview with
> messages like "VIDIOC_DQBUF - Unable to dequeue buffer")
>
> Didn't thoroughly test BGR3, YU12, YV12. Those capture modes also
> sometimes hang guvcview.
>
> Attached is the lsusb output for the device, along with two usbmon
> captures. One shows the device working as MJPG at a 320x240 resolution,
> and the other shows the device failing as MJPG at a 320x180 resolution.
I'm looking at that, I'll reply to Mark's e-mail.
> Please let me know if anything jumps out at you. For further debugging,
> please work with Mark.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-02-26 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 21:49 Dell XPS 12 USB camera bulk mode issues Sarah Sharp
2014-02-26 10:20 ` Ryan, Mark D
2014-02-26 15:40 ` Laurent Pinchart
2014-02-26 20:52 ` Mark Ryan
2014-02-28 9:34 ` Mark Ryan
2014-03-04 11:11 ` Laurent Pinchart
2014-03-04 16:16 ` Mark Ryan
2014-02-26 14:36 ` Laurent Pinchart [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=2437951.gNx7vUrxFR@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mark.d.ryan@intel.com \
--cc=sarah.a.sharp@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