From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Scally <dan.scally@ideasonboard.com>
Cc: linux-usb@vger.kernel.org, laurent.pinchart@ideasonboard.com,
kieran@linuxembedded.co.uk, balbi@kernel.org, mgr@pengutronix.de
Subject: Re: [PATCH] uvc: gadget: uvc: Defer uvcg_complete_buffer() until .complete()
Date: Wed, 9 Nov 2022 11:39:04 +0100 [thread overview]
Message-ID: <Y2uDSLCXlM922EwB@kroah.com> (raw)
In-Reply-To: <20221003101627.144026-1-dan.scally@ideasonboard.com>
On Mon, Oct 03, 2022 at 11:16:27AM +0100, Daniel Scally wrote:
> Calling uvcg_complete_buffer() from uvc_video_encode_isoc() sometimes
> causes the final isoc packet for a video frame to be delayed long
> enough to cause the USB controller to drop it. The first isoc packet
> of the next video frame is then received by the host, which interprets
> the toggled FID bit correctly such that the stream continues without
> interruption, but the first frame will be missing the last isoc
> packet's worth of bytes.
>
> To fix the issue delay the call to uvcg_complete_buffer() until the
> usb_request's .complete() callback, as already happens when the data
> is encoded via uvc_video_encode_isoc_sg().
>
> Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
> ---
> drivers/usb/gadget/function/uvc_video.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
What commit id does this fix? Should it go to stable kernels?
thanks,
greg k-h
prev parent reply other threads:[~2022-11-09 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 10:16 [PATCH] uvc: gadget: uvc: Defer uvcg_complete_buffer() until .complete() Daniel Scally
2022-10-03 11:47 ` Michael Grzeschik
2022-10-03 15:26 ` Dan Vacura
2022-10-03 22:23 ` Dan Scally
2022-11-09 10:39 ` Greg KH [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=Y2uDSLCXlM922EwB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=kieran@linuxembedded.co.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-usb@vger.kernel.org \
--cc=mgr@pengutronix.de \
/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).