From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: imx219: Report streams using frame descriptors
Date: Thu, 11 Jun 2026 16:06:38 +0300 [thread overview]
Message-ID: <b39bc319-8ae0-4715-8e3f-b822cdb535dc@ideasonboard.com> (raw)
In-Reply-To: <aip-xwYlKT1d3N0S@kekkonen.localdomain>
Hi,
On 11/06/2026 12:24, Sakari Ailus wrote:
> Moi,
>
> On Thu, Jun 11, 2026 at 12:13:02PM +0300, Tomi Valkeinen wrote:
>> From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>
>> Implement the .get_frame_desc() subdev operation to report information
>> about streams to the connected CSI-2 receiver. This is required to let
>> the CSI-2 receiver driver know about virtual channels and data types for
>> each stream.
>>
>> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>> Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
>> [tomi.valkeinen: picked from "Generic line based metadata support, internal pads" series]
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>> ---
>> This patch that adds .get_frame_desc() support to imx219 driver has been
>> circulating for a few years, and is currently posted in "[PATCH v12
>> 00/86] Generic line based metadata support, internal pads" series.
>>
>> However, as some bridge drivers require modern drivers that support
>> .get_frame_desc, specifically ds90ub960.c, let's pick the patch and
>> queue it separately from the huge metadata series.
>
> I've been recently working on
> <URL:https://lore.kernel.org/linux-media/20260518164318.3367888-1-sakari.ailus@linux.intel.com/>.
> In other words, drivers that have a single stream don't need this. We could
Thanks, I had missed that. I like the idea of a helper that does the
fallback mechanism. But I wonder about the need for dynamic alloc, which
complicates the series. In any case, we can drop this series and
continue the discussion on your series.
Tomi
next prev parent reply other threads:[~2026-06-11 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 9:13 Tomi Valkeinen
2026-06-11 9:24 ` Sakari Ailus
2026-06-11 13:06 ` Tomi Valkeinen [this message]
2026-06-11 13:10 ` Laurent Pinchart
2026-06-11 18:49 ` Sakari Ailus
2026-08-14 7:43 ` Mattijs Korpershoek
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=b39bc319-8ae0-4715-8e3f-b822cdb535dc@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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®