From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: chenchangcheng <ccc194101@163.com>,
hdegoede@redhat.com, mchehab@kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
chenchangcheng <chenchangcheng@kylinos.cn>
Subject: Re: [PATCH v10] media: uvcvideo: Fix bandwidth issue for Alcor camera.
Date: Thu, 15 May 2025 10:12:02 +0200 [thread overview]
Message-ID: <20250515081202.GA8748@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCsXPgQZVtq9RL_TkXCAW9Bt3kMO3-cR4X8GZaQvmYCQyA@mail.gmail.com>
On Wed, May 14, 2025 at 11:17:06AM +0200, Ricardo Ribalda wrote:
> Hi chenchangcheng
>
> Thanks for your patience fixing the warnings from media-ci :)
>
> Regards
>
> On Sat, 10 May 2025 at 08:18, chenchangcheng <ccc194101@163.com> wrote:
> >
> > From: chenchangcheng <chenchangcheng@kylinos.cn>
> >
> > Some broken device return wrong dwMaxPayloadTransferSize fields
> > as follows:
> > [ 218.632537] [pid:20427,cpu6,guvcview,8]uvcvideo: Device requested 2752512 B/frame bandwidth.
> > [ 218.632598] [pid:20427,cpu6,guvcview,9]uvcvideo: No fast enough alt setting for requested bandwidth.
> >
> > When dwMaxPayloadTransferSize is greater than maxpsize,
> > it will prevent the camera from starting.
> > So use the bandwidth of maxpsize.
> >
> > Signed-off-by: chenchangcheng <chenchangcheng@kylinos.cn>
> Reviewed-by: Ricardo Ribalda <ribalda@chromium.org>
>
> > ---
> > drivers/media/usb/uvc/uvc_video.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/drivers/media/usb/uvc/uvc_video.c b/drivers/media/usb/uvc/uvc_video.c
> > index e3567aeb0007..a74cf89852d1 100644
> > --- a/drivers/media/usb/uvc/uvc_video.c
> > +++ b/drivers/media/usb/uvc/uvc_video.c
> > @@ -262,6 +262,15 @@ static void uvc_fixup_video_ctrl(struct uvc_streaming *stream,
> >
> > ctrl->dwMaxPayloadTransferSize = bandwidth;
> > }
> > +
> > + if (stream->intf->num_altsetting > 1 &&
> > + ctrl->dwMaxPayloadTransferSize > stream->maxpsize) {
> > + dev_warn_ratelimited(&stream->intf->dev,
> > + "the max payload transmission size (%d) exceededs the size of the ep max packet (%d). Using the max size.\n",
> > + ctrl->dwMaxPayloadTransferSize,
>
> Minor nitpick. I am trying to standarize "UVC non compliance" header
> in the logs for this kind of things.
>
> "UVC non compliance: the max payload transmission size (%d) exceededs
> the size of the ep max packet (%d). Using the max size.\n"
s/exceededs/exceeds/
I will also replauce %d with %u as both variables are unsigned.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > + stream->maxpsize);
> > + ctrl->dwMaxPayloadTransferSize = stream->maxpsize;
> > + }
> > }
> >
> > static size_t uvc_video_ctrl_size(struct uvc_streaming *stream)
> >
> > base-commit: d76bb1ebb5587f66b0f8b8099bfbb44722bc08b3
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-05-15 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 6:18 chenchangcheng
2025-05-14 9:17 ` Ricardo Ribalda
2025-05-15 8:12 ` Laurent Pinchart [this message]
2025-05-15 10:59 ` 自己
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=20250515081202.GA8748@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=ccc194101@163.com \
--cc=chenchangcheng@kylinos.cn \
--cc=hdegoede@redhat.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
all inboxes | Powered by JetHome®