From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] media: uvc: simplify uvc_enpoint_max_bpi
Date: Mon, 25 Apr 2022 01:18:13 +0300 [thread overview]
Message-ID: <YmXMpQOb3bb4l6IF@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220401172437.625645-1-ribalda@chromium.org>
Hi Ricardo,
Thank you for the patch.
I think you meant uvc_endpoint_max_bpi() in the subject line.
On Fri, Apr 01, 2022 at 07:24:36PM +0200, Ricardo Ribalda wrote:
> The case USB_SPEED_WIRELESS and the default one were doing the same.
>
> Also, make always use of usb_endpoint_maxp_mult, as it should have a
> sane value, even for LOW speed and WIRELESS.
I always fear regressions with this kind of patch, but I have no reason
to think there's a specific issue, so
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> ---
> drivers/media/usb/uvc/uvc_video.c | 9 +--------
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git a/drivers/media/usb/uvc/uvc_video.c b/drivers/media/usb/uvc/uvc_video.c
> index 1b4cc934109e..a2dcfeaaac1b 100644
> --- a/drivers/media/usb/uvc/uvc_video.c
> +++ b/drivers/media/usb/uvc/uvc_video.c
> @@ -1760,21 +1760,14 @@ static unsigned int uvc_endpoint_max_bpi(struct usb_device *dev,
> struct usb_host_endpoint *ep)
> {
> u16 psize;
> - u16 mult;
>
> switch (dev->speed) {
> case USB_SPEED_SUPER:
> case USB_SPEED_SUPER_PLUS:
> return le16_to_cpu(ep->ss_ep_comp.wBytesPerInterval);
> - case USB_SPEED_HIGH:
> - psize = usb_endpoint_maxp(&ep->desc);
> - mult = usb_endpoint_maxp_mult(&ep->desc);
> - return psize * mult;
> - case USB_SPEED_WIRELESS:
> - psize = usb_endpoint_maxp(&ep->desc);
> - return psize;
> default:
> psize = usb_endpoint_maxp(&ep->desc);
> + psize *= usb_endpoint_maxp_mult(&ep->desc);
> return psize;
> }
> }
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2022-04-24 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 17:24 [PATCH 1/2] media: uvc: simplify uvc_enpoint_max_bpi Ricardo Ribalda
2022-04-01 17:24 ` [PATCH 2/2] media: uvc: Undup use uvv-endpoint_max_bpi code Ricardo Ribalda
2022-04-24 22:31 ` Laurent Pinchart
2022-04-24 22:18 ` Laurent Pinchart [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=YmXMpQOb3bb4l6IF@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.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