From: Ricardo Ribalda <ribalda@chromium.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Edwin Gatier <edwin.gatier@protonmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
stable@vger.kernel.org
Subject: [PATCH v4 0/5] media: uvcvideo: Automatically handle invalid uvc_versions
Date: Mon, 28 Sep 2026 14:31:59 +0000 [thread overview]
Message-ID: <20260928-uvc-version-v4-0-da0e983fcb95@chromium.org> (raw)
This series changes the way we handle invalid uvc_versions. Instead of
just failing it will try to continue probing.
Now that we are at it fix the way we handle device warnings.
Thanks!
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
Changes in v4:
- Handle invalid dwMaxVideoFrameSize.
- ctrl_size -> video_ctrl_size
- CTRL_SIZE->VERSION
- Link to v3: https://lore.kernel.org/r/20260911-uvc-version-v3-0-604328d8a0dd@chromium.org
Changes in v3:
- Move uvc_video_ctrl_size to uvc_video_init()
- Fixes for uvc_warn_once
- Remove bmVideoStandardParsing parsing
- Link to v2: https://lore.kernel.org/r/20260911-uvc-version-v2-0-395f27b0444c@chromium.org
Changes in v2:
- Add quirk for Avermedia
- Change the way the compliance error message is printed and cache
ctrl_size
- Link to v1: https://lore.kernel.org/r/20260907-uvc-version-v1-1-34e45dfe04de@chromium.org
---
Ricardo Ribalda (5):
media: uvcvideo: uvc_warn should warn not info
media: uvcvideo: Use uvc_warn_once when it make sense
media: uvcvideo: Automatically handle cameras with invalid uvc_version
media: uvcvideo: Do not parse bmVideoStandards
media: uvcvideo: Force UVC version for Avermedia GC515
drivers/media/usb/uvc/uvc_driver.c | 17 ++++++++----
drivers/media/usb/uvc/uvc_video.c | 56 ++++++++++++++++++++++++--------------
drivers/media/usb/uvc/uvcvideo.h | 6 ++--
3 files changed, 52 insertions(+), 27 deletions(-)
---
base-commit: 58348f64125e9a3e44d3abb275ca7f4e6c9641e5
change-id: 20260907-uvc-version-aedefc4384ce
Best regards,
--
Ricardo Ribalda <ribalda@chromium.org>
next reply other threads:[~2026-09-28 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 14:31 Ricardo Ribalda [this message]
2026-09-28 14:32 ` [PATCH v4 1/5] media: uvcvideo: uvc_warn should warn not info Ricardo Ribalda
2026-09-28 14:32 ` [PATCH v4 2/5] media: uvcvideo: Use uvc_warn_once when it make sense Ricardo Ribalda
2026-09-28 14:32 ` [PATCH v4 3/5] media: uvcvideo: Automatically handle cameras with invalid uvc_version Ricardo Ribalda
2026-09-28 14:32 ` [PATCH v4 4/5] media: uvcvideo: Do not parse bmVideoStandards Ricardo Ribalda
2026-09-28 14:32 ` [PATCH v4 5/5] media: uvcvideo: Force UVC version for Avermedia GC515 Ricardo Ribalda
2026-09-29 15:19 ` [PATCH v4 0/5] media: uvcvideo: Automatically handle invalid uvc_versions Hans de Goede
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=20260928-uvc-version-v4-0-da0e983fcb95@chromium.org \
--to=ribalda@chromium.org \
--cc=edwin.gatier@protonmail.com \
--cc=hansg@kernel.org \
--cc=johannes.goede@oss.qualcomm.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@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 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®