mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Parmjot Singh <parmjotsinghrobot@gmail.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, hansg@kernel.org,
	mchehab@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] media: uvcvideo: skip GET_DEF(PROBE) for HP True Vision 5MP
Date: Sun, 22 Nov 2026 19:03:08 +1300	[thread overview]
Message-ID: <20261122060309.105714-2-parmjotsinghrobot@gmail.com> (raw)
In-Reply-To: <20261122060309.105714-1-parmjotsinghrobot@gmail.com>

The HP True Vision 5MP Camera (04f2:b767, revision 0.05) was observed
returning zero format and frame indices in GET_DEF(PROBE). The driver
can send those indices back in SET_CUR(PROBE) during initialization.

Use the existing UVC_QUIRK_PROBE_DEF workaround so initialization
reads the current probe settings without replaying the default. Match
the UVC 1.5 VideoControl interfaces used by the color and IR streams.

OpenAI Codex (GPT-6.2 Sol) helped turn the reported USB trace into a device
table entry and checked the reported protocol on both interfaces.

Signed-off-by: Parmjot Singh <parmjotsinghrobot@gmail.com>

---
 drivers/media/usb/uvc/uvc_driver.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
index cbc145697..99c28991b 100644
--- a/drivers/media/usb/uvc/uvc_driver.c
+++ b/drivers/media/usb/uvc/uvc_driver.c
@@ -2754,6 +2754,15 @@ static const struct usb_device_id uvc_ids[] = {
 	  .bInterfaceSubClass	= 1,
 	  .bInterfaceProtocol	= 0,
 	  .driver_info		= UVC_INFO_QUIRK(UVC_QUIRK_RESTRICT_FRAME_RATE) },
+	/* HP True Vision 5MP Camera */
+	{ .match_flags		= USB_DEVICE_ID_MATCH_DEVICE
+				| USB_DEVICE_ID_MATCH_INT_INFO,
+	  .idVendor		= 0x04f2,
+	  .idProduct		= 0xb767,
+	  .bInterfaceClass	= USB_CLASS_VIDEO,
+	  .bInterfaceSubClass	= 1,
+	  .bInterfaceProtocol	= UVC_PC_PROTOCOL_15,
+	  .driver_info		= (kernel_ulong_t)&uvc_quirk_probe_def },
 	/* Alcor Micro AU3820 (Future Boy PC USB Webcam) */
 	{ .match_flags		= USB_DEVICE_ID_MATCH_DEVICE
 				| USB_DEVICE_ID_MATCH_INT_INFO,
-- 
2.56.0


  reply	other threads:[~2026-11-22  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-22  6:03 [PATCH 0/2] media: uvcvideo: fix HP True Vision 5MP color streaming Parmjot Singh
2026-11-22  6:03 ` Parmjot Singh [this message]
2026-11-22  6:03 ` [PATCH 2/2] media: uvcvideo: delay HP True Vision 5MP isochronous start Parmjot Singh

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=20261122060309.105714-2-parmjotsinghrobot@gmail.com \
    --to=parmjotsinghrobot@gmail.com \
    --cc=hansg@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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®