All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naoki Matsumoto <naoki.matt.matsumoto@sony.com>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	regressions@lists.linux.dev,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	chenchangcheng <chenchangcheng@kylinos.cn>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Sasha Levin <sashal@kernel.org>
Subject: [REGRESSION] 5.15.y, 5.10.y: media: uvcvideo: please backport 5b9c75c794ce
Date: Tue, 17 Nov 2026 21:36:10 +0900	[thread overview]
Message-ID: <avxKOmxCBLF+7qdT@jpc00229873> (raw)

Hi

I use a UVC device of USB3 at v5.15.y. I found the frame rate down with
the below message after updating stable version.

    uvcvideo 2-3:1.3: UVC non compliance: the max payload
    transmission size (1729) exceeds the size of the ep max packet (1024).
    Using the max size.

This message is from by eb6059474e70 ("media: uvcvideo: Fix bandwidth issue for Alcor camera").

    5.15.190: eb6059474e70
    5.10.241: 3eaf16ff8165

kernel-5.15 supports usb3 of course. This problem is stream->maxpsize is
not support usb3. Since this function parses it directly, USB 3 support seems 
to have been overlooked. I found the patch at v5.19

Please apply 5b9c75c794ce ("media: uvcvideo: Undup use
uvc_endpoint_max_bpi() code") to 5.15.y and 5.10.y.

I confirmed that it cherry-picks cleanly and fixes the problem on 5.15.

#regzbot introduced: eb6059474e70

Thank you,
Naoki Matsumoto

             reply	other threads:[~2026-11-17 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 12:36 Naoki Matsumoto [this message]
2026-11-17 12:42 ` [REGRESSION] 5.15.y, 5.10.y: media: uvcvideo: please backport 5b9c75c794ce Ricardo Ribalda
2026-11-17 12:59   ` Naoki Matsumoto

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=avxKOmxCBLF+7qdT@jpc00229873 \
    --to=naoki.matt.matsumoto@sony.com \
    --cc=chenchangcheng@kylinos.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.