[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <175916291050.2234821.14335723233391402773@freya>
Date: Mon, 29 Sep 2025 21:51:50 +0530
From: Jai Luthra <jai.luthra@...asonboard.com>
To: Hans Verkuil <hverkuil+cisco@...nel.org>, Hans Verkuil <hverkuil@...nel.org>, Jacopo Mondi <jacopo.mondi@...asonboard.com>, Laurent Pinchart <laurent.pinchart@...asonboard.com>, Mauro Carvalho Chehab <mchehab@...nel.org>, Sakari Ailus <sakari.ailus@...ux.intel.com>, Tomi Valkeinen <tomi.valkeinen@...asonboard.com>, linux-media@...r.kernel.org
Cc: Jai Luthra <jai.luthra@...ux.dev>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 08/10] media: ti: j721e-csi2rx: Use video_device_state
Quoting Hans Verkuil (2025-09-22 13:46:00)
> On 19/09/2025 11:56, Jai Luthra wrote:
> > Use the newly introduced video_device_state to store the active V4L2
> > format for the video device.
> >
> > This change allows using a single function for both .s_fmt and .try_fmt
> > hooks, while leveraging the framework helper for the .g_fmt hook.
>
> Rather than replying to 00/10, since that is CC-ed to a million people, I'll
> reply here.
>
> For core framework changes like this I want to see it applied to the test-drivers
> as well. At minimum the vivid driver and, if we support this for M2M devices as
> well, either vim2m or vicodec.
>
> The test-drivers are used in the media CI regression tests, so it is important
> that this is implemented in at least some of the test drivers.
Sure, will add state support to vivid in the next revision.
I'm not very familiar with M2M though, and depends on what the series looks
like, but I will give that an attempt.
>
> Regards,
>
> Hans
>
Thanks,
Jai
[snip]
Powered by blists - more mailing lists