From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: oliver@neukum.org
Cc: linux-media@vger.kernel.org, Oliver Neukum <oneukum@suse.de>
Subject: Re: [PATCH] uvc: more buffers
Date: Fri, 09 Aug 2013 15:58:31 +0200 [thread overview]
Message-ID: <2017146.oxz2IcHa3F@avalon> (raw)
In-Reply-To: <1376053896-8931-1-git-send-email-oliver@neukum.org>
Hi Oliver,
Thank you for the patch.
On Friday 09 August 2013 15:11:36 oliver@neukum.org wrote:
> From: Oliver Neukum <oneukum@suse.de>
>
> This is necessary to let the new generation of cameras from LiteOn used in
> Haswell ULT notebook operate. Otherwise the images will be truncated.
Could you please post the lsusb -v output for the device ?
Why does it need more buffers, is it a superspeed webcam ?
> Signed-off-by: Oliver Neukum <oneukum@suse.de>
> ---
> drivers/media/usb/uvc/uvcvideo.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/usb/uvc/uvcvideo.h
> b/drivers/media/usb/uvc/uvcvideo.h index 9e35982..9f1930b 100644
> --- a/drivers/media/usb/uvc/uvcvideo.h
> +++ b/drivers/media/usb/uvc/uvcvideo.h
> @@ -114,9 +114,9 @@
> /* Number of isochronous URBs. */
> #define UVC_URBS 5
> /* Maximum number of packets per URB. */
> -#define UVC_MAX_PACKETS 32
> +#define UVC_MAX_PACKETS 128
That would mean up to 384KiB per URB. While not unreasonable, I'd like to know
how much data your camera produces to require this.
> /* Maximum number of video buffers. */
> -#define UVC_MAX_VIDEO_BUFFERS 32
> +#define UVC_MAX_VIDEO_BUFFERS 128
I don't think your camera really needs more than 32 V4L2 (full frame) buffers
:-)
> /* Maximum status buffer size in bytes of interrupt URB. */
> #define UVC_MAX_STATUS_SIZE 16
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-08-09 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 13:11 [PATCH] uvc: more buffers oliver
2013-08-09 13:58 ` Laurent Pinchart [this message]
2013-08-12 9:01 ` Oliver Neukum
2013-08-20 17:34 ` Laurent Pinchart
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=2017146.oxz2IcHa3F@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=oneukum@suse.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