From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Kean Ren <rh_king@163.com>,
linux-media@vger.kernel.org, Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: uvcvideo: Add quirk for Luxvisions RGB Camera (30c9:0122)
Date: Mon, 28 Sep 2026 16:24:07 +0300 [thread overview]
Message-ID: <20260928132407.GG4406@killaraus.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCsqZzFY+KMKGBg06vm6rGR4FMy63hd0HShiHfb+vpqyqg@mail.gmail.com>
On Fri, Sep 04, 2026 at 11:15:15AM +0200, Ricardo Ribalda wrote:
> On Thu, 3 Sept 2026 at 10:58, Kean Ren <rh_king@163.com> wrote:
> >
> > The device binds cleanly but delivers no image data; USB autosuspend is
> > suspending the streaming endpoint. Disable autosuspend for it.
> >
> > Issue found on Lenovo ThinkPad X13 (codename Zelda, Intel); confirmed
> > working with this quirk.
> >
> Link: https://lore.kernel.org/linux-media/20260904090751.1814783-1-rh_king@163.com/T/#mf5306ef689ce38ed331a3098272cb0ac2588ed79
When linking to the original thread on lore, the patch.msgid.link domain
is preferred (see Documentation/process/maintainer-tip.rst). That would
be
Link: https://patch.msgid.link/linux-media/20260904090751.1814783-1-rh_king@163.com/
Did you mean to specifically link to the descriptors though ? As they're
in the same mail thread, I think the link to the patch itself should be
enough. Do you prefer otherwise ?
> > Tested-by: Kean Ren <rh_king@163.com>
>
> nit: I think we do not usually add the Tested-by: tag for authors. We
> expect that it has been tested :)
Maybe we shouldn't :-) We merge plenty of code that hasn't been tested
by the author, a prime example being API refactoring. Actually, reading
Documentation/, I can't see anything that explicitly approves or forbids
a Tested-by tag from the author.
This being said, for driver patches like these I would certainly expect
the author to have tested the change.
> > Signed-off-by: Kean Ren <rh_king@163.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 e289cc71ba98..32bf353013a1 100644
> > --- a/drivers/media/usb/uvc/uvc_driver.c
> > +++ b/drivers/media/usb/uvc/uvc_driver.c
> > @@ -3216,6 +3216,15 @@ static const struct usb_device_id uvc_ids[] = {
> > .bInterfaceSubClass = 1,
> > .bInterfaceProtocol = 0,
> > .driver_info = UVC_INFO_META(V4L2_META_FMT_D4XX) },
> > + /* Luxvisions Innotech Integrated RGB Camera (Lenovo laptops) */
> > + { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
> > + | USB_DEVICE_ID_MATCH_INT_INFO,
> > + .idVendor = 0x30c9,
> > + .idProduct = 0x0122,
> > + .bInterfaceClass = USB_CLASS_VIDEO,
> > + .bInterfaceSubClass = 1,
> > + .bInterfaceProtocol = 0,
> > + .driver_info = UVC_INFO_QUIRK(UVC_QUIRK_DISABLE_AUTOSUSPEND) },
>
> The quirks are sorted by vid:pid. Sorry I did not notice this before.
I can handle this when applying.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > /* Intel Realsense D435i depth camera */
> > { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
> > | USB_DEVICE_ID_MATCH_INT_INFO,
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-09-28 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 8:11 Kean Ren
2026-09-03 8:59 ` Ricardo Ribalda
2026-09-04 8:37 ` 任海
2026-09-04 8:40 ` Ricardo Ribalda
2026-09-04 9:07 ` rh_king
2026-09-04 9:15 ` Ricardo Ribalda
2026-09-28 13:24 ` Laurent Pinchart [this message]
2026-09-28 13:32 ` Ricardo Ribalda
2026-09-28 18:50 ` 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=20260928132407.GG4406@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rh_king@163.com \
--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®