From: Hans de Goede <hansg@kernel.org>
To: Michael Jordan <jordan.mymail@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] media: uvcvideo: fix up missing AUTO_UPDATE on the OBSBOT Tiny 2
Date: Mon, 28 Sep 2026 16:55:16 +0200 [thread overview]
Message-ID: <330448ae-3496-4489-a8fa-332fab02adde@kernel.org> (raw)
In-Reply-To: <20260928143448.757683-1-jordan.mymail@gmail.com>
Hi,
On 28-Sep-26 16:34, Michael Jordan wrote:
> Hi Laurent,
>
> On Mon, 28 Sep 2026 14:57:13 +0300, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
>> The device implements an interrupt endpoint. Does it report control
>> change events for those controls ?
>
> No. I checked today on both the Tiny 2 and the Tail 2, with the uvcvideo
> status trace enabled (trace=0x200) and a stream running so the status
> URB was submitted. Neither camera sent a single status packet during
> commanded pan and zoom moves, or while its subject tracking changed
> pan/tilt and zoom on its own. GET_CUR reported the live values
> throughout.
>
>>> The vendor has been asked to fix the firmware (support ticket #8220,
>>
>> Any public link ?
>
> No, sorry. It is a private ticket filed through OBSBOT's support
> channel, which is the only way I have found to contact them. I have the
> confirmation email showing it was received and is awaiting a reply, and
> can forward it if that is useful, but there has been no response since
> 2026-08-04.
>
>> This belongs to the commit message.
>
> Agreed, I will move it there.
>
> With the Assisted-by tags and the shorter 2/3 message, that makes a v3.
> Hans, let me know whether you would like me to send one, or would
> rather fix these up when applying.
Laurent is also merging some patches atm, not sure what his plans
are for this series. With that said:
I plan to pick this up tomorrow morning, if you can send a full v3,
with the second cameras quirks also added as a patch 4/4 on top
of the updated original 3 patches that will make things easier for me
tomorrow morning.
Thanks & Regards,
Hans
next prev parent reply other threads:[~2026-09-28 14:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 0:25 [PATCH v2 0/3] media: uvcvideo: live pan/tilt/zoom readback " Michael Jordan
2026-09-02 0:25 ` [PATCH v2 1/3] media: uvcvideo: report AUTO_UPDATE controls as volatile Michael Jordan
2026-09-02 0:25 ` [PATCH v2 2/3] media: uvcvideo: generalise the XU flags fixup to all controls Michael Jordan
2026-09-02 6:38 ` Ricardo Ribalda
2026-09-28 11:44 ` Laurent Pinchart
2026-09-28 14:34 ` Michael Jordan
2026-09-02 0:25 ` [PATCH v2 3/3] media: uvcvideo: fix up missing AUTO_UPDATE on the OBSBOT Tiny 2 Michael Jordan
2026-09-02 6:34 ` Ricardo Ribalda
2026-09-27 22:06 ` Michael Jordan
2026-09-28 6:57 ` Ricardo Ribalda
2026-09-28 11:18 ` Ricardo Ribalda
2026-09-28 14:34 ` Michael Jordan
2026-09-28 11:57 ` Laurent Pinchart
2026-09-28 14:34 ` Michael Jordan
2026-09-28 14:55 ` Hans de Goede [this message]
2026-09-28 18:53 ` Laurent Pinchart
2026-09-28 11:01 ` [PATCH v2 0/3] media: uvcvideo: live pan/tilt/zoom readback " Hans de Goede
2026-09-28 11:12 ` Ricardo Ribalda
2026-09-28 11:14 ` Hans de Goede
2026-09-28 11:49 ` 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=330448ae-3496-4489-a8fa-332fab02adde@kernel.org \
--to=hansg@kernel.org \
--cc=hverkuil+cisco@kernel.org \
--cc=jordan.mymail@gmail.com \
--cc=laurent.pinchart@ideasonboard.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®