From: Michal Pecio <michal.pecio@gmail.com>
To: Henry Lin <henryl@nvidia.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/1] media: uvcvideo: reset interface on bulk stream stop
Date: Tue, 26 May 2026 12:16:05 +0200 [thread overview]
Message-ID: <20260526121605.332525c6.michal.pecio@gmail.com> (raw)
In-Reply-To: <SAWPR12MB99911841F75A9492A6FA875421AC0B2@SAWPR12MB999118.namprd12.prod.outlook.com>
On Tue, 26 May 2026 09:55:19 +0000, Henry Lin wrote:
> I tested 25e531b422dc ("usb: xhci: Make usb_host_endpoint.hcpriv
> survive endpoint_disable()") on the affected setup, and it fixes the
> issue.
Good.
> With that change applied, repeated stop/start cycles complete
> successfully, and I no longer see the uvcvideo -71 transfer errors.
Were you seeing one such error for each restart, followed by uvcvideo
dropping a few frames and continuing to stream normally, or multiple
transaction errors and complete functional failure?
I was seeing the formrer on several tested HCs, except for those from
ASMedia which never completed the affected URB at all (IMO a HW bug).
I think multiple errors would also be an indication of some bug,
possibly in HW, possibly worth looking into in its own right.
Regards,
Michal
next prev parent reply other threads:[~2026-05-26 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 18:20 Henry Lin
2026-05-25 18:20 ` [RFC PATCH 1/1] " Henry Lin
2026-05-25 19:40 ` [RFC PATCH 0/1] " Alan Stern
2026-05-26 9:57 ` Henry Lin
2026-05-25 23:55 ` Michal Pecio
2026-05-26 9:55 ` Henry Lin
2026-05-26 10:16 ` Michal Pecio [this message]
2026-05-28 8:36 ` Henry Lin
2026-05-28 16:45 ` Michal Pecio
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=20260526121605.332525c6.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=henryl@nvidia.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
Powered by JetHome