From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thomas Pugliese <thomas.pugliese@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] uvc: update uvc_endpoint_max_bpi to handle USB_SPEED_WIRELESS devices
Date: Mon, 27 Jan 2014 22:49:46 +0100 [thread overview]
Message-ID: <14957224.mkfABmkaAb@avalon> (raw)
In-Reply-To: <alpine.DEB.2.10.1401270927410.16196@mint32-virtualbox>
Hi Thomas,
On Monday 27 January 2014 09:54:58 Thomas Pugliese wrote:
> On Mon, 27 Jan 2014, Laurent Pinchart wrote:
> > On Friday 24 January 2014 15:17:28 Thomas Pugliese wrote:
> > > Isochronous endpoints on devices with speed == USB_SPEED_WIRELESS can
> > > have a max packet size ranging from 1-3584 bytes. Add a case to
> > > uvc_endpoint_max_bpi to handle USB_SPEED_WIRELESS. Otherwise endpoints
> > > for those devices will fall to the default case which masks off any
> > > values > 2047. This causes uvc_init_video to underestimate the
> > > bandwidth available and fail to find a suitable alt setting for high
> > > bandwidth video streams.
> >
> > I'm not too familiar with wireless USB, but shouldn't the value be
> > multiplied by bMaxBurst from the endpoint companion descriptor ?
> > Superspeed devices provide the multiplied value in their endpoint
> > companion descriptor's wBytesPerInterval field, but there's no such field
> > for wireless devices.
>
> For wireless USB isochronous endpoints, the values in the endpoint
> descriptor are the logical interval and max packet size that the endpoint
> can support. They are provided for backwards compatibility for just this
> type of situation. You are correct that the actual endpoint
> characteristics are the bMaxBurst, wOverTheAirPacketSize, and
> bOverTheAirInterval values from the WUSB endpoint companion descriptor but
> only the host controller really needs to know about those details. In
> fact, the values from the endpoint companion descriptor might actually
> over-estimate the bandwidth available since the device can set bMaxBurst
> to a higher value than necessary to allow for retries.
OK, I'll trust you on that :-)
I've taken the patch in my tree and will send a pull request for v3.15.
> > Out of curiosity, which device have you tested this with ?
>
> The device is a standard wired UVC webcam: Quanta CQEC2B (VID: 0x0408,
> PID: 0x9005). It is connected to an Alereon Wireless USB bridge dev kit
> which allows it to operate as a WUSB device.
>
> Thomas
>
> > > Signed-off-by: Thomas Pugliese <thomas.pugliese@gmail.com>
> > > ---
> > >
> > > drivers/media/usb/uvc/uvc_video.c | 3 +++
> > > 1 file changed, 3 insertions(+)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-01-27 21:48 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 [this message]
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
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=14957224.mkfABmkaAb@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@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