linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Dennis Chen <barracks510@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] USB: uvc: add support for the Microsoft Surface Pro 3 Cameras
Date: Mon, 09 Nov 2015 19:33:29 +0200	[thread overview]
Message-ID: <3251528.3ev8VpgUrP@avalon> (raw)
In-Reply-To: <1434053610.2501.5.camel@gmail.com>

Hi Denis,

On Thursday 11 June 2015 13:13:30 Dennis Chen wrote:
> > Could you please send me the output of 'lsusb -v -d 045e:07be' and
> > 'lsusb -v -
> > d 045e:07bf' (running as root if possible) ?
> 
> Bus 001 Device 004: ID 045e:07bf Microsoft Corp.
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               2.00
>   bDeviceClass          239 Miscellaneous Device
>   bDeviceSubClass         2 ?
>   bDeviceProtocol         1 Interface Association
>   bMaxPacketSize0        64
>   idVendor           0x045e Microsoft Corp.
>   idProduct          0x07bf
>   bcdDevice           21.52
>   iManufacturer           1 QCM
>   iProduct                2 Microsoft LifeCam Rear
>   iSerial                 0
>   bNumConfigurations      1

[snip]

>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           1
>       bInterfaceClass        14 Video
>       bInterfaceSubClass      1 Video Control
>       bInterfaceProtocol      1
>       iInterface              2 Microsoft LifeCam Rear

[snip]

I see where the problem comes from now. I had missed it before, but your 
device sets the bInterfaceProtocol value to 1 as it's UVC 1.5 compliant, as 
opposed to value 0 for UVC 1.1.

The uvcvideo driver doesn't support UVC 1.5 yet. It looks like your camera 
supports the UVC 1.1 protocol as well, but that's not true of all UVC devices 
in general. I expect that enabling detection of UVC 1.5 support in the driver 
will result in issues with UVC 1.5 devices, but on the other hand those 
devices are currently not supported at all. I'll thus submit a patch to enable 
UVC 1.5 device detection, and we'll see how that goes. I'll CC you and would 
appreciate if you could test the patch.

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2015-11-09 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 19:53 [PATCH] USB: uvc: add support for the Microsoft Surface Pro 3 Cameras Dennis Chen
2015-06-10  0:55 ` Laurent Pinchart
2015-06-10  1:09   ` Dennis Chen
2015-06-10  1:19     ` Laurent Pinchart
2015-06-10  1:40       ` Dennis Chen
2015-06-11  4:04         ` Laurent Pinchart
2015-06-11 20:13           ` Dennis Chen
2015-11-09 17:33             ` 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=3251528.3ev8VpgUrP@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=barracks510@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.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 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).