From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: "Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
"Hans Verkuil" <hverkuil+cisco@kernel.org>,
"Jacopo Mondi" <jacopo.mondi@ideasonboard.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Michael Riesch" <michael.riesch@collabora.com>,
"Ricardo Ribalda" <ribalda@chromium.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Sean Young" <sean@mess.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Alain Volmat" <alain.volmat@foss.st.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Michael Tretter" <m.tretter@pengutronix.de>,
"Tomasz Figa" <tfiga@chromium.org>,
"Steve Cho" <stevecho@chromium.org>,
"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Paul Kocialkowski" <paulk@sys-base.io>,
"Benjamin Mugnier" <benjamin.mugnier@foss.st.com>,
"Hans de Goede" <hansg@kernel.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Brandon Brnich" <b-brnich@ti.com>,
"Marco Felsch" <m.felsch@pengutronix.de>,
"Sven Püschel" <s.pueschel@pengutronix.de>,
"Devarsh Thakkar" <devarsht@ti.com>,
"Yemike Abhilash Chandra" <y-abhilashchandra@ti.com>,
"Jackson Lee" <jackson.lee@chipsnmedia.com>,
"Jai Luthra" <jai.luthra@ideasonboard.com>,
"Mehdi Djait" <mehdi.djait@linux.intel.com>,
"Padhi, Beleswar" <b-padhi@ti.com>,
"Donadkar, Rishikesh" <r-donadkar@ti.com>,
"Rouven Czerwinski" <rouven.czerwinski@linaro.org>,
"Nayden Kanchev" <Nayden.Kanchev@arm.com>,
"Konstantin Babin" <Konstantin.Babin@arm.com>,
"Anthony McGivern" <Anthony.McGivern@arm.com>
Subject: Re: [ANNv4] Media Summit on May 26th in Nice, France
Date: Fri, 22 May 2026 22:10:03 +0200 [thread overview]
Message-ID: <ahC1Ec_CA0tq3PtX@zed> (raw)
In-Reply-To: <CAFEp6-1pA6v7P-ZrOD+iEGfq5Dv0CZ_CLiZ5u35tutQ6zAPqWA@mail.gmail.com>
Hi Loic
On Fri, May 22, 2026 at 09:49:34PM +0200, Loic Poulain wrote:
> Hi Folks,
>
> On Tue, Apr 28, 2026 at 7:55 PM Nicolas Dufresne
> <nicolas.dufresne@collabora.com> wrote:
> >
> > Le mardi 28 avril 2026 à 15:00 +0200, Hans Verkuil a écrit :
> > > On 4/28/26 14:30, Jacopo Mondi wrote:
> > > > Hello
> > > >
> > > > On Tue, Apr 14, 2026 at 11:42:59AM +0300, Laurent Pinchart wrote:
> > > > > On Tue, Apr 14, 2026 at 10:34:13AM +0200, Loic Poulain wrote:
> > > > > > On Tue, Apr 14, 2026 at 9:42 AM Laurent Pinchart wrote:
> > > > > > > On Tue, Apr 14, 2026 at 09:20:56AM +0200, Michael Riesch wrote:
> > > > > > > > On 4/14/26 08:55, Ricardo Ribalda wrote:
> > > > > > > > > On Tue, 14 Apr 2026 at 08:47, Hans Verkuil <hverkuil+cisco@kernel.org> wrote:
> > > > > > > > > > On 13/04/2026 23:16, Laurent Pinchart wrote:
> > > > > > > > > > > On Mon, Apr 13, 2026 at 04:25:54PM -0400, Nicolas Dufresne wrote:
> > > > > > > > > > > > Le lundi 13 avril 2026 à 23:19 +0300, Laurent Pinchart a écrit :
> > > > > > > > > > > > > On Mon, Apr 13, 2026 at 10:03:52PM +0200, Loic Poulain wrote:
> > > > > > > > > > > > > > Hi Hans,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I would be happy to discuss this if a slot is available:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Title: Generic V4L2 ISP M2M framework
> > > > > > > > > > > > > > Presenter: Loic Poulain
> > > > > > > > > > > > > > Time estimate: ~20min
> > > > > > > > > > > > > > Description: During early development of a Qualcomm Offline Image
> > > > > > > > > > > > > > Processing Engine (OPE), we relied on the V4L2 memory‑to‑memory
> > > > > > > > > > > > > > (v4l2‑m2m) framework, which is widely used and provides solid support
> > > > > > > > > > > > > > for buffer management and scheduling. However, applying it to an ISP
> > > > > > > > > > > > > > use case exposes limitations: ISP engines often require a richer media
> > > > > > > > > > > > > > graph, with multiple pads and metadata flows, similar to inline ISP
> > > > > > > > > > > > > > pipelines (params, stats, outputs). This talk proposes discussing the
> > > > > > > > > > > > > > need for and design of a common V4L2 ISP M2M framework to factor out
> > > > > > > > > > > > > > shared functionality across drivers, particularly around buffer/queue
> > > > > > > > > > > > > > management and job scheduling.
> > > > > > > >
> > > > > > > > It seems that we share some pain points.. :-) :-/
> > > > > > > >
> > > > > > > > Over the last year, some ideas have been brewing in my mind. Not
> > > > > > > > necessarily *my* ideas, mind you, rather ideas that have been around in
> > > > > > > > linux-media for quite a while, actually. What I would like to prepare
> > > > > > > > for the Media Summit goes along the same lines.
> > > > > > > >
> > > > > > > > > > > > > That's well aligned with the v4l2-isp framework that Jacopo started, and
> > > > > > > > > > > > > to the multi-context and media-jobs APIs that we have proposed. I
> > > > > > > > > > > > > wonder, however, if a short session at the media summit will be enough,
> > > > > > > > > > > > > or if we should try to organize a half day brainstorming workshop at
> > > > > > > > > > > > > some point. Depending on when the people interested in this topic plan
> > > > > > > > > > > > > to arrive, Monday could be an option.
> > > > > > > > > > > >
> > > > > > > > > > > > I'm also/still interested in the multi-context for m2m decoders that have inline
> > > > > > > > > > > > post-processing capabilities (current model forces us to waste a lot of RAM). We
> > > > > > > > > > > > just restarted some design discussion with the team, with an increased
> > > > > > > > > > > > confidence that multi-context is the way. The scheduler could come handy in the
> > > > > > > > > > > > future if we get to deal with more multi-stage codecs in the future. I'll be in
> > > > > > > > > > > > Nice all day Monday.
> > > > > > > > > > >
> > > > > > > > > > > I will unfortunately be available only until 15:00 on Monday, but Jacopo
> > > > > > > > > > > should be available through the day. Let's see who would be interested
> > > > > > > > > > > and available, and try to organize something.
> > > > > > > > > >
> > > > > > > > > > I'm available on Monday as well. I think this is a topic that is well suited
> > > > > > > > > > to a brainstorm session.
> > > > > > > > >
> > > > > > > > > I am also available on Monday and would like to attend the session.
> > > > > > > >
> > > > > > > > I'd be interested too. Right now the plan is to arrive on Monday
> > > > > > > > afternoon. Depending on what time you agree on it may work out anyway.
> > > > > > > > It would be great to know the exact time this session will start (as I
> > > > > > > > might need to adjust my travel arrangements).
> > > > > >
> > > > > > I can arrive on Monday, with a preference for the afternoon.
> > > > > >
> > > > > > > We need a volunteer to organize this, as in finding and booking a
> > > > > > > meeting space. Note that Monday is a public holiday in France (Monday
> > > > > > > the 25th of May in particular, not all Mondays).
> > > > > > >
> > > > > > > If the number of attendees was small I was thinking of hosting the event
> > > > > > > in the place where the Ideas on Board team will be staying, but it looks
> > > > > > > like we're already reaching a fair number of people.
> > > > > > >
> > > >
> > > > Are we still considering this BoF session ?
> > > >
> > > > We would someone to volunteer organizing this, at @IoB we're quite
> > > > full for the week and we might have an hard time organizing this one
> > > > on top of the libcamera workshop.
> > > >
> > > > As Laurent said, that Monday is a public holiday in France, and
> > > > getting a room somewhere might be complicated.
> > > >
> > > > We can host some people in the location where we're having the yearly IoB
> > > > get-together, but you should arrange your travel there (35 minutes
> > > > from Nice by car).
> > > >
> > > > If we get a volunteer we can should maybe a dedicated mail thread as this one
> > > > was about the Media Summit ?
> > >
> > > If the number of people can be kept low (say <= 6), then it shouldn't be a
> > > problem to just find a hotel restaurant or similar, close to the place of
> > > the media summit, and just sit together.
> > >
> > > Who would be the key people for this? And who are 'nice to have'? :-)
> > > I think I probably fit more in the latter category than the first.
> >
> > I was hoping a small number of people and a simple café/lobby too. The mass of
> > people interested in the reply arrive much later, but I'm there all day, and
> > would be more then happy to be able to brainstorm the subject a bit, which is
> > easier in small group.
>
> Is this BoF side session still planned? If there’s still interest,
> perhaps the easiest option would simply be to meet at the hotel lobby
> on Monday morning.
>
I'm around Nice like many others on Monday, but I'm not sure how this
would feel for people that didn't arrange their travels accordingly
because this event was never officially announced.
> Regards,
> Loic
>
next prev parent reply other threads:[~2026-05-22 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 10:25 [ANNv4] Media Summit on May 26th in Nice, France Hans Verkuil
2026-04-12 13:56 ` Sakari Ailus
2026-04-13 6:08 ` Hans Verkuil
2026-04-13 9:57 ` Michael Riesch
2026-04-14 6:49 ` Hans Verkuil
2026-04-13 20:03 ` Loic Poulain
2026-04-13 20:19 ` Laurent Pinchart
2026-04-13 20:25 ` Nicolas Dufresne
2026-04-13 21:16 ` Laurent Pinchart
2026-04-14 6:47 ` Hans Verkuil
2026-04-14 6:55 ` Ricardo Ribalda
2026-04-14 7:20 ` Michael Riesch
2026-04-14 7:42 ` Laurent Pinchart
2026-04-14 8:34 ` Loic Poulain
2026-04-14 8:42 ` Laurent Pinchart
2026-04-14 17:55 ` Nicolas Dufresne
2026-04-14 18:09 ` Laurent Pinchart
2026-04-14 19:25 ` Loic Poulain
2026-04-28 12:30 ` Jacopo Mondi
2026-04-28 13:00 ` Hans Verkuil
2026-04-28 17:54 ` Nicolas Dufresne
2026-05-22 19:49 ` Loic Poulain
2026-05-22 20:10 ` Jacopo Mondi [this message]
2026-05-24 14:09 ` Loic Poulain
2026-05-23 21:46 ` Nicolas Dufresne
2026-04-14 7:04 ` Jacopo Mondi
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=ahC1Ec_CA0tq3PtX@zed \
--to=jacopo.mondi@ideasonboard.com \
--cc=Anthony.McGivern@arm.com \
--cc=Konstantin.Babin@arm.com \
--cc=Nayden.Kanchev@arm.com \
--cc=alain.volmat@foss.st.com \
--cc=b-brnich@ti.com \
--cc=b-padhi@ti.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=bryan.odonoghue@linaro.org \
--cc=daniel.almeida@collabora.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=devarsht@ti.com \
--cc=hansg@kernel.org \
--cc=hverkuil+cisco@kernel.org \
--cc=jackson.lee@chipsnmedia.com \
--cc=jai.luthra@ideasonboard.com \
--cc=khilman@baylibre.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=m.felsch@pengutronix.de \
--cc=m.tretter@pengutronix.de \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=michael.riesch@collabora.com \
--cc=mripard@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=paulk@sys-base.io \
--cc=r-donadkar@ti.com \
--cc=ribalda@chromium.org \
--cc=rouven.czerwinski@linaro.org \
--cc=s.pueschel@pengutronix.de \
--cc=sakari.ailus@linux.intel.com \
--cc=sean@mess.org \
--cc=stevecho@chromium.org \
--cc=tfiga@chromium.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=y-abhilashchandra@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.