From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-usb@vger.kernel.org, tglx@linutronix.de
Subject: [27/27] media: uvcvideo: use usb_fill_int_urb()
Date: Wed, 20 Jun 2018 14:55:23 +0300 [thread overview]
Message-ID: <3925059.Md1u3KRT1n@avalon> (raw)
Hi Sebastian,
Thank you for the patch.
On Wednesday, 20 June 2018 14:01:05 EEST Sebastian Andrzej Siewior wrote:
> Using usb_fill_int_urb() helps to find code which initializes an
> URB. A grep for members of the struct (like ->complete) reveal lots
> of other things, too.
> usb_fill_int_urb() also checks bInterval to be in the 1…16 range on
> HS/SS.
>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> drivers/media/usb/uvc/uvc_video.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/media/usb/uvc/uvc_video.c
> b/drivers/media/usb/uvc/uvc_video.c index a88b2e51a666..79e7a827ed44 100644
> --- a/drivers/media/usb/uvc/uvc_video.c
> +++ b/drivers/media/usb/uvc/uvc_video.c
> @@ -1619,21 +1619,19 @@ static int uvc_init_video_isoc(struct uvc_streaming
> *stream, return -ENOMEM;
> }
>
> - urb->dev = stream->dev->udev;
> - urb->context = stream;
> - urb->pipe = usb_rcvisocpipe(stream->dev->udev,
> - ep->desc.bEndpointAddress);
> + usb_fill_int_urb(urb, stream->dev->udev,
> + usb_rcvisocpipe(stream->dev->udev,
> + ep->desc.bEndpointAddress),
> + stream->urb_buffer[i], size,
> + uvc_video_complete, stream,
> + ep->desc.bInterval);
You're filling an isoc URB with usb_fill_int_urb(), which is explicitly
documented as usable to fill an interrupt URB. Shouldn't we create a
usb_fill_isoc_urb() function ? It could just be an alias for
usb_fill_int_urb() if isoc and interrupt URBs don't need to be treated
differently. Alternatively, I'd be fine using usb_fill_int_urb() if the
function documentation's was updated to mention isoc URBs as well.
> #ifndef CONFIG_DMA_NONCOHERENT
> urb->transfer_flags = URB_ISO_ASAP | URB_NO_TRANSFER_DMA_MAP;
> urb->transfer_dma = stream->urb_dma[i];
> #else
> urb->transfer_flags = URB_ISO_ASAP;
> #endif
> - urb->interval = ep->desc.bInterval;
Unless I'm mistaken this introduces a change in behaviour for HS and SS, and
should thus be documented in the commit message. I suspect that this is the
real reason for this patch. I'd thus update the subject line to describe this
fix, and the body of the message to explain why using usb_fill_int_urb() is
the proper fix.
> - urb->transfer_buffer = stream->urb_buffer[i];
> - urb->complete = uvc_video_complete;
> urb->number_of_packets = npackets;
> - urb->transfer_buffer_length = size;
usb_fill_int_urb() sets urb->start_frame to -1. Does that impact us in any way
?
> for (j = 0; j < npackets; ++j) {
> urb->iso_frame_desc[j].offset = j * psize;
next reply other threads:[~2018-06-20 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 11:55 Laurent Pinchart [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-20 14:14 [27/27] media: uvcvideo: use usb_fill_int_urb() Laurent Pinchart
2018-06-20 13:21 Sebastian Andrzej Siewior
2018-06-20 11:01 Sebastian Andrzej Siewior
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=3925059.Md1u3KRT1n@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=bigeasy@linutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tglx@linutronix.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).