usb: gadget: uvc: queue empty isoc requests if no video buffer is available
Subsystems (2)
PATCH 1/1 usb: gadget: uvc: queue empty isoc requests if no video buffer is available
ISOC transfers expect a certain cadence of requests being queued. Not keeping up with the expected rate of requests results in missed ISOC transfers (EXDEV). The application layer may or may not produce video frames to match this expectation, so uvc gadget driver must handle cases where the application is not queuing up buffers fast enough to fulfill ISOC requirements.
Currently, uvc gadget driver waits for new video buffer to become available before queuing up usb requests. With this patch the gadget driver queues up 0 length usb requests whenever there are no video buffers available. The USB controller's complete callback is used as the limiter for how quickly the 0 length packets will be queued. Video buffers are still queued as soon as they become available.
--- drivers/usb/gadget/function/uvc_video.c | 32 ++++++++++++++++++------- 1 file changed, 24 insertions(+), 8 deletions(-)
drivers/usb/gadget/function/uvc_video.c +24 -8
@@ -386,6 +386,9 @@ static void uvcg_video_pump(struct work_struct *work)struct uvc_buffer *buf;unsigned long flags;int ret; +bool buf_int; +/* video->max_payload_size is only set when using bulk transfer */ +bool is_bulk = video->max_payload_size;while (video->ep->enabled) {/*
@@ -408,20 +411,35 @@ static void uvcg_video_pump(struct work_struct *work)*/ spin_lock_irqsave (&queue->irqlock, flags); buf =uvcg_queue_head (queue); -if (buf ==NULL ) { + +if (buf !=NULL ) { + video->encode (req, video, buf); +/* Always interrupt for the last request of a video buffer */ + buf_int = buf->state ==UVC_BUF_STATE_DONE ; + }else if (!(queue->flags &UVC_QUEUE_DISCONNECTED ) && !is_bulk) { +/* +* No video buffer available; the queue is still connected and +* we're traferring over ISOC. Queue a 0 length request to +* prevent missed ISOC transfers. +*/ + req->length =0 ; + buf_int = false; + }else { +/* +* Either queue has been disconnected or no video buffer +* available to bulk transfer. Either way, stop processing +* further. +*/ spin_unlock_irqrestore (&queue->irqlock, flags);break ; } - video->encode (req, video, buf); -/* * With usb3 we have more requests. This will decrease the * interrupt load to a quarter but also catches the corner * cases, which needs to be handled. */ -if (list_empty (&video->req_free) || - buf->state ==UVC_BUF_STATE_DONE || +if (list_empty (&video->req_free) || buf_int || !(video->req_int_count %DIV_ROUND_UP (video->uvc_num_requests,4 ))) { video->req_int_count =0 ;
@@ -441,8 +459,7 @@ static void uvcg_video_pump(struct work_struct *work)/* Endpoint now owns the request */ req =NULL ; -if (buf->state !=UVC_BUF_STATE_DONE ) - video->req_int_count++; + video->req_int_count++; }if (!req)
@@ -527,4 +544,3 @@ int uvcg_video_init(struct uvc_video *video, struct uvc_device *uvc) V4L2_BUF_TYPE_VIDEO_OUTPUT, &video->mutex);return 0 ; } -
Signature · 1 line
2.40.1.521.gf1e218fcd8-goog
Hi Avichal,
Thank you for the patch.
Quoted 6 lines · Avichal Rakesh
ISOC transfers expect a certain cadence of requests being queued. Not keeping up with the expected rate of requests results in missed ISOC transfers (EXDEV). The application layer may or may not produce video frames to match this expectation, so uvc gadget driver must handle cases where the application is not queuing up buffers fast enough to fulfill ISOC requirements.
I think the application *must* not produce video frames to match the expectations. If it did, it would mean that it would either have to use more than the available ISOC bandwidth (which is obviously bad), or use *exactly* the ISOC bandwidth. Unless the application performs rate matching (which would require information about the USB timings that isn't available to userspace as far as I can tell), that's not possible.
Quoted 18 lines
Currently, uvc gadget driver waits for new video buffer to become available before queuing up usb requests. With this patch the gadget driver queues up 0 length usb requests whenever there are no video buffers available. The USB controller's complete callback is used as the limiter for how quickly the 0 length packets will be queued. Video buffers are still queued as soon as they become available.
Link https://lore.kernel.org/CAMHf4WKbi6KBPQztj9FA4kPvESc1fVKrC8G73-cs6tTeQby9=w@mail.gmail.com/ open hereSigned-off-by Avichal Rakesh <[email protected]>--- drivers/usb/gadget/function/uvc_video.c | 32 ++++++++++++++++++------- 1 file changed, 24 insertions(+), 8 deletions(-)drivers/usb/gadget/function/uvc_video.c +0
-0
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 391
Quoted 6 lines
drivers/usb/gadget/function/uvc_video.c +3
-0@@ -386,6 +386,9 @@ static void uvcg_video_pump(struct work_struct *work)struct uvc_buffer *buf;unsigned long flags;int ret; +bool buf_int; +/* video->max_payload_size is only set when using bulk transfer */ +bool is_bulk = video->max_payload_size;
Let's rename buf_int to buf_done, that matches the intent of the code better.
Could you reorder the fields by line length ?
struct uvc_video *video = container_of(work, struct uvc_video, pump); struct uvc_video_queue *queue = &video->queue; /* video->max_payload_size is only set when using bulk transfer */ bool is_bulk = video->max_payload_size; struct usb_request *req = NULL; struct uvc_buffer *buf; unsigned long flags; bool buf_done; int ret;
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 417
Quoted 12 lines
drivers/usb/gadget/function/uvc_video.c +4
-1while (video->ep->enabled) {/* @@ -408,20 +411,35 @@ static void uvcg_video_pump(struct work_struct *work)*/ spin_lock_irqsave (&queue->irqlock, flags); buf =uvcg_queue_head (queue); -if (buf ==NULL ) { + +if (buf !=NULL ) { + video->encode (req, video, buf); +/* Always interrupt for the last request of a video buffer */
I would drop this comment, and ... (see below)
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 422
Quoted 5 lines
drivers/usb/gadget/function/uvc_video.c +5
-0+ buf_int = buf->state ==UVC_BUF_STATE_DONE ; + }else if (!(queue->flags &UVC_QUEUE_DISCONNECTED ) && !is_bulk) { +/* +* No video buffer available; the queue is still connected and +* we're traferring over ISOC. Queue a 0 length request to
s/traferring/transferring/
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 429
Quoted 7 lines
drivers/usb/gadget/function/uvc_video.c +7
-0+* prevent missed ISOC transfers. +*/ + req->length =0 ; + buf_int = false; + }else { +/* +* Either queue has been disconnected or no video buffer
s/Either queue/Either the queue/
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 430
Quoted 1 line
drivers/usb/gadget/function/uvc_video.c +1
-0+* available to bulk transfer. Either way, stop processing
s/to bulk/for bulk/
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 441
Quoted 13 lines
drivers/usb/gadget/function/uvc_video.c +2
-2+* further. +*/ spin_unlock_irqrestore (&queue->irqlock, flags);break ; } - video->encode (req, video, buf); -/* * With usb3 we have more requests. This will decrease the * interrupt load to a quarter but also catches the corner * cases, which needs to be handled. */
... and expand this:
/*
* With USB3 handling more requests at a higher speed, we can't
* afford to generate an interrupt for every request. Decide to
* interrupt:
*
* - When no more requests are available in the free queue, as
* this may be our last chance to refill the endpoint's
* request queue.
*
* - When this is request is the last request for the video
* buffer, as we want to start sending the next video buffer
* ASAP in case it doesn't get started already in the next
* iteration of this loop.
*
* - Four times over the length of the requests queue (as
* indicated by video->uvc_num_requests), as a trade-off
* between latency and interrupt load.
*/
And now that I've written this, I wonder if we could drop the second case. Now that we have a guarantee we will queue 0-length requests after the current buffer if no other buffer is available, I don't think we need to make the last request of a buffer a special case. It even seems to me that we could drop the first case too, and just interrupt 4 times over the length of the requests queue. What do you think ?
Quoted 21 lines
drivers/usb/gadget/function/uvc_video.c +2
-5-if (list_empty (&video->req_free) || - buf->state ==UVC_BUF_STATE_DONE || +if (list_empty (&video->req_free) || buf_int || !(video->req_int_count %DIV_ROUND_UP (video->uvc_num_requests,4 ))) { video->req_int_count =0 ;@@ -441,8 +459,7 @@ static void uvcg_video_pump(struct work_struct *work)/* Endpoint now owns the request */ req =NULL ; -if (buf->state !=UVC_BUF_STATE_DONE ) - video->req_int_count++; + video->req_int_count++; }if (!req)@@ -527,4 +544,3 @@ int uvcg_video_init(struct uvc_video *video, struct uvc_device *uvc) V4L2_BUF_TYPE_VIDEO_OUTPUT, &video->mutex);return 0 ; } -
Signature · 3 lines
Regards, Laurent Pinchart
PATCH v2 1/1 usb: gadget: uvc: queue empty isoc requests if no video buffer is available
ISOC transfers expect a certain cadence of requests being queued. Not keeping up with the expected rate of requests results in missed ISOC transfers (EXDEV). The application layer is not required to produce video frames to match this expectation, so uvc gadget driver must not rely on data from application layer to maintain the ISOC cadence.
Currently, uvc gadget driver waits for new video buffer to become available before queuing up usb requests. With this patch the gadget driver queues up 0 length usb requests whenever there are no video buffers available. The USB controller's complete callback is used as the limiter for how quickly the 0 length packets will be queued. Video buffers are still queued as soon as they become available.
---
Changelog:
v2:
- Updated commit message to make it clear that userspace application is not required to match the ISOC rate.
- Styling and comment revision based on review
drivers/usb/gadget/function/uvc_video.c | 50 +++++++++++++++++++------ 1 file changed, 39 insertions(+), 11 deletions(-)
drivers/usb/gadget/function/uvc_video.c +39 -11
@@ -382,9 +382,12 @@ static void uvcg_video_pump(struct work_struct *work) { struct uvc_video *video = container_of(work, struct uvc_video, pump);struct uvc_video_queue *queue = &video->queue; +/* video->max_payload_size is only set when using bulk transfer */ +bool is_bulk = video->max_payload_size;struct usb_request *req =NULL ;struct uvc_buffer *buf;unsigned long flags; +bool buf_done;int ret;while (video->ep->enabled) {
@@ -408,20 +411,47 @@ static void uvcg_video_pump(struct work_struct *work)*/ spin_lock_irqsave (&queue->irqlock, flags); buf =uvcg_queue_head (queue); -if (buf ==NULL ) { + +if (buf !=NULL ) { + video->encode (req, video, buf); + buf_done = buf->state ==UVC_BUF_STATE_DONE ; + }else if (!(queue->flags &UVC_QUEUE_DISCONNECTED ) && !is_bulk) { +/* +* No video buffer available; the queue is still connected and +* we're transferring over ISOC. Queue a 0 length request to +* prevent missed ISOC transfers. +*/ + req->length =0 ; + buf_done = false; + }else { +/* +* Either the queue has been disconnected or no video buffer +* available for bulk transfer. Either way, stop processing +* further. +*/ spin_unlock_irqrestore (&queue->irqlock, flags);break ; } - video->encode (req, video, buf); -/* -* With usb3 we have more requests. This will decrease the -* interrupt load to a quarter but also catches the corner -* cases, which needs to be handled. +* With USB3 handling more requests at a higher speed, we can't +* afford to generate an interrupt for every request. Decide to +* interrupt: +* +* - When no more requests are available in the free queue, as +* this may be our last chance to refill the endpoint's +* request queue. +* +* - When this is request is the last request for the video +* buffer, as we want to start sending the next video buffer +* ASAP in case it doesn't get started already in the next +* iteration of this loop. +* +* - Four times over the length of the requests queue (as +* indicated by video->uvc_num_requests), as a trade-off +* between latency and interrupt load. */ -if (list_empty (&video->req_free) || - buf->state ==UVC_BUF_STATE_DONE || +if (list_empty (&video->req_free) || buf_done || !(video->req_int_count %DIV_ROUND_UP (video->uvc_num_requests,4 ))) { video->req_int_count =0 ;
@@ -441,8 +471,7 @@ static void uvcg_video_pump(struct work_struct *work)/* Endpoint now owns the request */ req =NULL ; -if (buf->state !=UVC_BUF_STATE_DONE ) - video->req_int_count++; + video->req_int_count++; }if (!req)
@@ -527,4 +556,3 @@ int uvcg_video_init(struct uvc_video *video, struct uvc_device *uvc) V4L2_BUF_TYPE_VIDEO_OUTPUT, &video->mutex);return 0 ; } -
--
2.41.0.rc0.172.g3f132b7071-goog
Hi,
Quoted 13 lines · Avichal Rakesh
ISOC transfers expect a certain cadence of requests being queued. Not keeping up with the expected rate of requests results in missed ISOC transfers (EXDEV). The application layer is not required to produce video frames to match this expectation, so uvc gadget driver must not rely on data from application layer to maintain the ISOC cadence.
Currently, uvc gadget driver waits for new video buffer to become available before queuing up usb requests. With this patch the gadget driver queues up 0 length usb requests whenever there are no video buffers available. The USB controller's complete callback is used as the limiter for how quickly the 0 length packets will be queued. Video buffers are still queued as soon as they become available.
Quoted 9 lines
Signed-off-by Avichal Rakesh <[email protected]>---
Changelog:
v2:
- Updated commit message to make it clear that userspace application is not required to match the ISOC rate.
- Styling and comment revision based on review
BTW, your previous version is already in Greg's usb-next branch. Any new change should be rebased on his usb-next.
Thanks,
Thinh
Quoted 11 lines · Thinh Nguyen
Quoted 7 lines
---
Changelog:
v2:
- Updated commit message to make it clear that userspace application is not required to match the ISOC rate.
- Styling and comment revision based on reviewBTW, your previous version is already in Greg's usb-next branch. Any new change should be rebased on his usb-next.
Oh shoot! I rebased on Linus' master and assumed the patch hadn't been merged because I couldn't find it there. Uploading a new patch with the changes in v2 rebased on greg's usb-next branch. Sorry about that, and thanks for catching it!
- Avi.
PATCH v3 1/1 usb: gadget: uvc: clean up comments and styling in video_pump
In reply to Thinh NguyenThis patch elaborates on some of the edge cases handled by video_pump around setting no_interrupt flag, and brings the code style in line with rest of the file.
---
Changelog:
v2:
- Updated commit message to make it clear that userspace application is not required to match the ISOC rate.
- Styling and comment revision based on review
v3:
- Rebased on to Greg's usb-next where v1 had already merged
- Updated commit message to match the actual changes after rebase.
drivers/usb/gadget/function/uvc_video.c | 38 ++++++++++++++++--------- 1 file changed, 25 insertions(+), 13 deletions(-)
drivers/usb/gadget/function/uvc_video.c +25 -13
@@ -382,13 +382,13 @@ static void uvcg_video_pump(struct work_struct *work) { struct uvc_video *video = container_of(work, struct uvc_video, pump);struct uvc_video_queue *queue = &video->queue; +/* video->max_payload_size is only set when using bulk transfer */ +bool is_bulk = video->max_payload_size;struct usb_request *req =NULL ;struct uvc_buffer *buf;unsigned long flags; +bool buf_done;int ret; -bool buf_int; -/* video->max_payload_size is only set when using bulk transfer */ -bool is_bulk = video->max_payload_size;while (video->ep->enabled) {/*
@@ -414,20 +414,19 @@ static void uvcg_video_pump(struct work_struct *work)if (buf !=NULL ) { video->encode (req, video, buf); -/* Always interrupt for the last request of a video buffer */ - buf_int = buf->state ==UVC_BUF_STATE_DONE ; + buf_done = buf->state ==UVC_BUF_STATE_DONE ; }else if (!(queue->flags &UVC_QUEUE_DISCONNECTED ) && !is_bulk) {/* * No video buffer available; the queue is still connected and -* we're traferring over ISOC. Queue a 0 length request to +* we're transferring over ISOC. Queue a 0 length request to * prevent missed ISOC transfers. */ req->length =0 ; - buf_int = false; + buf_done = false; }else {/* -* Either queue has been disconnected or no video buffer -* available to bulk transfer. Either way, stop processing +* Either the queue has been disconnected or no video buffer +* available for bulk transfer. Either way, stop processing * further. */ spin_unlock_irqrestore (&queue->irqlock, flags);
@@ -435,11 +434,24 @@ static void uvcg_video_pump(struct work_struct *work) }/* -* With usb3 we have more requests. This will decrease the -* interrupt load to a quarter but also catches the corner -* cases, which needs to be handled. +* With USB3 handling more requests at a higher speed, we can't +* afford to generate an interrupt for every request. Decide to +* interrupt: +* +* - When no more requests are available in the free queue, as +* this may be our last chance to refill the endpoint's +* request queue. +* +* - When this is request is the last request for the video +* buffer, as we want to start sending the next video buffer +* ASAP in case it doesn't get started already in the next +* iteration of this loop. +* +* - Four times over the length of the requests queue (as +* indicated by video->uvc_num_requests), as a trade-off +* between latency and interrupt load. */ -if (list_empty (&video->req_free) || buf_int || +if (list_empty (&video->req_free) || buf_done || !(video->req_int_count %DIV_ROUND_UP (video->uvc_num_requests,4 ))) { video->req_int_count =0 ;
--
2.41.0.rc0.172.g3f132b7071-goog
Greg KH
maintainerRe: [PATCH v3] usb: gadget: uvc: clean up comments and styling in video_pump
Quoted 3 lines · Avichal Rakesh
This patch elaborates on some of the edge cases handled by
video_pumparound settingno_interruptflag, and brings the code style in line with rest of the file.
When you say "and" that usually means it should be a separate patch.
But I really don't see what coding style changes you made here, what was it?
I can't see any logical changes made here, am I missing them? Or is this all just a style-cleanup patch?
thanks,
greg k-h
Re: [PATCH v3] usb: gadget: uvc: clean up comments and styling in video_pump
Hi Greg,
Quoted 5 lines · Greg KH
Quoted 3 lines · Avichal Rakesh
This patch elaborates on some of the edge cases handled by
video_pumparound settingno_interruptflag, and brings the code style in line with rest of the file.
Quoted 7 lines
When you say "and" that usually means it should be a separate patch.
But I really don't see what coding style changes you made here, what was it?
I can't see any logical changes made here, am I missing them? Or is this all just a style-cleanup patch?
It's all style cleanup (variable declaration ordering), typo fixes, and naming and documentation improvement, yes. I reviewed Avichal's original patch when coming back from holidays, neither of us realizing that you had merged it already. He sent a v2 and got told to rebase it on top of your tree. That's what v3 is, just handling the review comments.
I generally ask for patches to be split with one change per patch, but given the small changes bundled here, and the fact that all of this just incorporates the review comments, I think it would be a bit overkill.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v3] usb: gadget: uvc: clean up comments and styling in video_pump
Quoted 23 lines · Laurent Pinchart
Hi Greg,
Quoted 5 lines · Greg KH
Quoted 3 lines · Avichal Rakesh
This patch elaborates on some of the edge cases handled by
video_pumparound settingno_interruptflag, and brings the code style in line with rest of the file.Quoted 7 lines
When you say "and" that usually means it should be a separate patch.
But I really don't see what coding style changes you made here, what was it?
I can't see any logical changes made here, am I missing them? Or is this all just a style-cleanup patch?
It's all style cleanup (variable declaration ordering), typo fixes, and naming and documentation improvement, yes. I reviewed Avichal's original patch when coming back from holidays, neither of us realizing that you had merged it already. He sent a v2 and got told to rebase it on top of your tree. That's what v3 is, just handling the review comments.
Quoted 4 lines
I generally ask for patches to be split with one change per patch, but given the small changes bundled here, and the fact that all of this just incorporates the review comments, I think it would be a bit overkill.
Apologies for the goof up. I hadn't realized that Linus' master wasn't the very tip of the Linux tree, and assumed the v1 merge had fallen behind. I am happy to split it up into smaller patches if you want, but as Laurent already mentioned: this is just documentation and styling cleanup from V1 with no logic fixes.
- Avi.
Re: [PATCH v3] usb: gadget: uvc: clean up comments and styling in video_pump
In reply to Avichal RakeshHi Avichal,
Thank you for the patch.
Quoted 6 lines · Avichal Rakesh
This patch elaborates on some of the edge cases handled by
video_pumparound settingno_interruptflag, and brings the code style in line with rest of the file.
Quoted 90 lines
---
Changelog:
v2:
- Updated commit message to make it clear that userspace application is not required to match the ISOC rate.
- Styling and comment revision based on review
v3:
- Rebased on to Greg's usb-next where v1 had already merged
- Updated commit message to match the actual changes after rebase.drivers/usb/gadget/function/uvc_video.c | 38 ++++++++++++++++--------- 1 file changed, 25 insertions(+), 13 deletions(-)drivers/usb/gadget/function/uvc_video.c +25
-13@@ -382,13 +382,13 @@ static void uvcg_video_pump(struct work_struct *work) { struct uvc_video *video = container_of(work, struct uvc_video, pump);struct uvc_video_queue *queue = &video->queue; +/* video->max_payload_size is only set when using bulk transfer */ +bool is_bulk = video->max_payload_size;struct usb_request *req =NULL ;struct uvc_buffer *buf;unsigned long flags; +bool buf_done;int ret; -bool buf_int; -/* video->max_payload_size is only set when using bulk transfer */ -bool is_bulk = video->max_payload_size;while (video->ep->enabled) {/* @@ -414,20 +414,19 @@ static void uvcg_video_pump(struct work_struct *work)if (buf !=NULL ) { video->encode (req, video, buf); -/* Always interrupt for the last request of a video buffer */ - buf_int = buf->state ==UVC_BUF_STATE_DONE ; + buf_done = buf->state ==UVC_BUF_STATE_DONE ; }else if (!(queue->flags &UVC_QUEUE_DISCONNECTED ) && !is_bulk) {/* * No video buffer available; the queue is still connected and -* we're traferring over ISOC. Queue a 0 length request to +* we're transferring over ISOC. Queue a 0 length request to * prevent missed ISOC transfers. */ req->length =0 ; - buf_int = false; + buf_done = false; }else {/* -* Either queue has been disconnected or no video buffer -* available to bulk transfer. Either way, stop processing +* Either the queue has been disconnected or no video buffer +* available for bulk transfer. Either way, stop processing * further. */ spin_unlock_irqrestore (&queue->irqlock, flags);@@ -435,11 +434,24 @@ static void uvcg_video_pump(struct work_struct *work) }/* -* With usb3 we have more requests. This will decrease the -* interrupt load to a quarter but also catches the corner -* cases, which needs to be handled. +* With USB3 handling more requests at a higher speed, we can't +* afford to generate an interrupt for every request. Decide to +* interrupt: +* +* - When no more requests are available in the free queue, as +* this may be our last chance to refill the endpoint's +* request queue. +* +* - When this is request is the last request for the video +* buffer, as we want to start sending the next video buffer +* ASAP in case it doesn't get started already in the next +* iteration of this loop. +* +* - Four times over the length of the requests queue (as +* indicated by video->uvc_num_requests), as a trade-off +* between latency and interrupt load. */ -if (list_empty (&video->req_free) || buf_int || +if (list_empty (&video->req_free) || buf_done || !(video->req_int_count %DIV_ROUND_UP (video->uvc_num_requests,4 ))) { video->req_int_count =0 ;
Signature · 3 lines
Regards, Laurent Pinchart
Quoted 12 lines · Laurent Pinchart
Hi Avichal,
Thank you for the patch.
Quoted 6 lines · Avichal Rakesh
ISOC transfers expect a certain cadence of requests being queued. Not keeping up with the expected rate of requests results in missed ISOC transfers (EXDEV). The application layer may or may not produce video frames to match this expectation, so uvc gadget driver must handle cases where the application is not queuing up buffers fast enough to fulfill ISOC requirements.
Quoted 6 lines
I think the application *must* not produce video frames to match the expectations. If it did, it would mean that it would either have to use more than the available ISOC bandwidth (which is obviously bad), or use *exactly* the ISOC bandwidth. Unless the application performs rate matching (which would require information about the USB timings that isn't available to userspace as far as I can tell), that's not possible.
Ah, that is a good point. This makes it sound like the userspace application is responsible for maintaining the cadence, which is false. Tweaked the language to (hopefully) sound less blame-y.
Quoted 113 lines
Quoted 19 lines
Currently, uvc gadget driver waits for new video buffer to become available before queuing up usb requests. With this patch the gadget driver queues up 0 length usb requests whenever there are no video buffers available. The USB controller's complete callback is used as the limiter for how quickly the 0 length packets will be queued. Video buffers are still queued as soon as they become available.
Link https://lore.kernel.org/CAMHf4WKbi6KBPQztj9FA4kPvESc1fVKrC8G73-cs6tTeQby9=w@mail.gmail.com/ open hereSigned-off-by Avichal Rakesh <[email protected]>--- drivers/usb/gadget/function/uvc_video.c | 32 ++++++++++++++++++------- 1 file changed, 24 insertions(+), 8 deletions(-)drivers/usb/gadget/function/uvc_video.c +0
-0drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 391
Quoted 6 lines
drivers/usb/gadget/function/uvc_video.c +3
-0@@ -386,6 +386,9 @@ static void uvcg_video_pump(struct work_struct *work)struct uvc_buffer *buf;unsigned long flags;int ret; +bool buf_int; +/* video->max_payload_size is only set when using bulk transfer */ +bool is_bulk = video->max_payload_size;Let's rename
buf_inttobuf_done, that matches the intent of the code better.Could you reorder the fields by line length ?
struct uvc_video *video = container_of(work, struct uvc_video, pump); struct uvc_video_queue *queue = &video->queue; /* video->max_payload_size is only set when using bulk transfer */ bool is_bulk = video->max_payload_size; struct usb_request *req = NULL; struct uvc_buffer *buf; unsigned long flags; bool buf_done; int ret;drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 417
Quoted 12 lines
drivers/usb/gadget/function/uvc_video.c +4
-1while (video->ep->enabled) {/* @@ -408,20 +411,35 @@ static void uvcg_video_pump(struct work_struct *work)*/ spin_lock_irqsave (&queue->irqlock, flags); buf =uvcg_queue_head (queue); -if (buf ==NULL ) { + +if (buf !=NULL ) { + video->encode (req, video, buf); +/* Always interrupt for the last request of a video buffer */ I would drop this comment, and ... (see below)
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 422
Quoted 5 lines
drivers/usb/gadget/function/uvc_video.c +5
-0+ buf_int = buf->state ==UVC_BUF_STATE_DONE ; + }else if (!(queue->flags &UVC_QUEUE_DISCONNECTED ) && !is_bulk) { +/* +* No video buffer available; the queue is still connected and +* we're traferring over ISOC. Queue a 0 length request to s/traferring/transferring/
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 429
Quoted 7 lines
drivers/usb/gadget/function/uvc_video.c +7
-0+* prevent missed ISOC transfers. +*/ + req->length =0 ; + buf_int = false; + }else { +/* +* Either queue has been disconnected or no video buffer s/Either queue/Either the queue/
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 430
Quoted 1 line
drivers/usb/gadget/function/uvc_video.c +1
-0+* available to bulk transfer. Either way, stop processing s/to bulk/for bulk/
drivers/usb/gadget/function/uvc_video.c static void uvcg_video_pump(struct work_struct *work) · line 441
Quoted 13 lines
drivers/usb/gadget/function/uvc_video.c +2
-2+* further. +*/ spin_unlock_irqrestore (&queue->irqlock, flags);break ; } - video->encode (req, video, buf); -/* * With usb3 we have more requests. This will decrease the * interrupt load to a quarter but also catches the corner * cases, which needs to be handled. */ ... and expand this:
/*
* With USB3 handling more requests at a higher speed, we can't
* afford to generate an interrupt for every request. Decide to
* interrupt:
*
* - When no more requests are available in the free queue, as
* this may be our last chance to refill the endpoint's
* request queue.
*
* - When this is request is the last request for the video
* buffer, as we want to start sending the next video buffer
* ASAP in case it doesn't get started already in the next
* iteration of this loop.
*
* - Four times over the length of the requests queue (as
* indicated byvideo->uvc_num_requests), as a trade-off
* between latency and interrupt load.
*/
Quoted 6 lines
And now that I've written this, I wonder if we could drop the second case. Now that we have a guarantee we will queue 0-length requests after the current buffer if no other buffer is available, I don't think we need to make the last request of a buffer a special case. It even seems to me that we could drop the first case too, and just interrupt 4 times over the length of the requests queue. What do you think ?
The complete callback of the last request for a buffer is used to return the buffer back to the vb2 framework, which could in the worst case get delayed by 15 requests. This is probably not a functional issue, as we already see system latencies far greater than the 2ms that would occur from those 15 requests, but I think it is a good invariant to have to try and minimize any latency jitters when interacting with the userspace application.
On the other hand, removing it does make the code much simpler, so if you feel strongly about it, I am happy to drop the second case.
Quoted 16 lines
Quoted 16 lines
drivers/usb/gadget/function/uvc_video.c +2
-4-if (list_empty (&video->req_free) || - buf->state ==UVC_BUF_STATE_DONE || +if (list_empty (&video->req_free) || buf_int || !(video->req_int_count %DIV_ROUND_UP (video->uvc_num_requests,4 ))) { video->req_int_count =0 ;@@ -441,8 +459,7 @@ static void uvcg_video_pump(struct work_struct *work)/* Endpoint now owns the request */ req =NULL ; -if (buf->state !=UVC_BUF_STATE_DONE ) - video->req_int_count++; + video->req_int_count++; }
Quoted 7 lines
drivers/usb/gadget/function/uvc_video.c int uvcg_video_init(struct uvc_video *video, struct uvc_device *uvc) · line 530
Quoted 6 lines
drivers/usb/gadget/function/uvc_video.c +0
-1if (!req)@@ -527,4 +544,3 @@ int uvcg_video_init(struct uvc_video *video, struct uvc_device *uvc) V4L2_BUF_TYPE_VIDEO_OUTPUT, &video->mutex);return 0 ; } -
Thank you for the review, sent out a v2 with the comments addressed!
- Avi.