public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thomas Pugliese <thomas.pugliese@gmail.com>
Cc: linux-media@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] uvc: update uvc_endpoint_max_bpi to handle USB_SPEED_WIRELESS devices
Date: Thu, 17 Apr 2014 23:59:22 +0200	[thread overview]
Message-ID: <13572613.UXhodzMO7U@avalon> (raw)
In-Reply-To: <alpine.DEB.2.10.1404170949070.8990@mint32-virtualbox>

Hi Thomas,

On Thursday 17 April 2014 09:53:32 Thomas Pugliese wrote:
> On Thu, 17 Apr 2014, Laurent Pinchart wrote:
> > On Wednesday 16 April 2014 12:29:22 Thomas Pugliese wrote:

[snip]

> > > As you had mentioned previously, it should be possible to support both
> > > formats by ignoring the endpoint descriptor and looking at the
> > > bMaxBurst, bOverTheAirInterval and wOverTheAirPacketSize fields in the
> > > WUSB endpoint companion descriptor.  That is a more involved change to
> > > the UVC driver and also would require changes to USB core to store the
> > > WUSB endpoint companion descriptor in struct usb_host_endpoint similar
> > > to what is done for super speed devices.
> > 
> > It's more complex indeed, but I believe it would be worth it. Any
> > volunteer ? ;-) In the meantime I'm fine with a patch that reverts to the
> > previous behaviour. Please include the explanation of the problem in the
> > commit message.
> 
> I may make an attempt at the more complete fix once I finish some of the
> other items in my queue.
> 
> For clarification, would you like a patch that reverts to the pre-super
> speed behavior where windows-compatible devices work not but spec
> compliant devices will not (i.e. treat USB_SPEED_HIGH and
> USB_SPEED_WIRELESS the same)?

I'll trust your judgment on that, if you believe it would be better from a 
user point of view, please send a patch. Otherwise we can wait until you find 
time to work on a proper fix.

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2014-04-17 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 21:17 [PATCH] uvc: update uvc_endpoint_max_bpi to handle USB_SPEED_WIRELESS devices Thomas Pugliese
2014-01-26 23:12 ` Laurent Pinchart
2014-01-27 15:54   ` Thomas Pugliese
2014-01-27 21:49     ` Laurent Pinchart
2014-04-15  2:07       ` Thomas Pugliese
2014-04-15 15:16         ` Laurent Pinchart
2014-04-15 21:45           ` Thomas Pugliese
2014-04-16 11:06             ` Laurent Pinchart
2014-04-16 17:29               ` Thomas Pugliese
2014-04-17 14:34                 ` Laurent Pinchart
2014-04-17 14:53                   ` Thomas Pugliese
2014-04-17 21:59                     ` 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=13572613.UXhodzMO7U@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=thomas.pugliese@gmail.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