From: "Michał Pecio" <michal.pecio@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans de Goede <hdegoede@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] media: uvcvideo: Support large SuperSpeedPlus isochronous endpoints
Date: Mon, 21 Apr 2025 11:49:43 +0200 [thread overview]
Message-ID: <20250421114943.085160c6@foxbook> (raw)
In-Reply-To: <2025042101-coyness-vitality-e636@gregkh>
On Mon, 21 Apr 2025 10:51:38 +0200, Greg KH wrote:
> On Mon, Apr 21, 2025 at 09:59:51AM +0200, Michal Pecio wrote:
> > USB 3.1 increased maximum isochronous bandwidth to 96KB per
> > interval, too much for 16 bits and the SuperSpeed Endpoint
> > Companion descriptor. A new SuperSpeedPlus Isochronous Endpoint
> > Companion descriptor was introduced to encode such bandwidths, see
> > spec sections 9.6.7, 9.6.8.
> >
> > Support the descriptor with code based on
> > xhci_get_max_esit_payload() and widen all 'psize' variables to 32
> > bits. Subsequent calculations are 32 bit already and not expected
> > to overflow, so this change ought to suffice for proper alt setting
> > selection on USB 3.x Gen 2 devices.
> >
> > Signed-off-by: Michal Pecio <michal.pecio@gmail.com>
> > ---
> >
> > This change appears to be a strict necessity for supporting USB3
> > Gen2 isochronous devices meaningfully. Whether it's sufficient I
> > don't know, I don't have such HW. No regression seen on High Speed
> > and SuperSpeed.
>
> If you don't have the hardware, why make this change?
Because it's an obvious and easily removed limitation, and may be the
only thing missing in uvcvideo to support such hardware. I saw it when
investigating a related SuperSpeed problem earlier.
If media believes that more is needed, or if there is objection to such
changes based on spec alone then fine, at least the patch is out there
for anyone wondering why things aren't working.
> > drivers/media/usb/uvc/uvc_
>
> This line looks odd, because:
>
> > drivers/media/usb/uvc/uvc_driver.c | 2 +-
> > drivers/media/usb/uvc/uvc_video.c | 13 +++++++++----
> > drivers/media/usb/uvc/uvcvideo.h | 4 ++--
> > 3 files changed, 12 insertions(+), 7 deletions(-)
>
> Only 3 files were changed. What went wrong?
Sorry, some editing mistake.
prev parent reply other threads:[~2025-04-21 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 7:59 [PATCH] media: uvcvideo: Support large SuperSpeedPlus isochronous endpoints Michal Pecio
2025-04-21 8:51 ` Greg KH
2025-04-21 9:49 ` Michał Pecio [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=20250421114943.085160c6@foxbook \
--to=michal.pecio@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@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