From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F06AF1E515 for ; Tue, 14 Apr 2026 06:47:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776149269; cv=none; b=VFLki85cvl7z80I1e0mVnSYoNgauHqGD+csk28CfrSKbclSD1OQhYhEsDXsPS2DfBO1QPcB+octZWlID+jH7zaZd/hCuXDOl7MzUZzYWH8xnY2j128/dJVfa5yp4gis5Uk3OScVTwZcEU/cYO+IHUBXc136zjXndHbPPsb+qugg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776149269; c=relaxed/simple; bh=GfdMwXIxFLgeH6dRd3zkWYt7Jm6WS9weggX+bFFW7Q4=; h=Message-ID:Date:MIME-Version:From:Subject:To:Cc:References: In-Reply-To:Content-Type; b=VexwV/NgzDYBErJeSMSWHh01781+tRx8xVNveR+6EXGk6a9yGo4gLFx4s106Uqc7+0jk1Jk3QK5hzq+1gwpVg13sh92iMfs+CcpKFXVpNup/E0fsS++UT+GcSUGyzQuEJ/scVlailub++91QssLSzBd/rXuSk/TCg3/QpQhZOg0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=bh940Dnb; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="bh940Dnb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5C3D5C19425; Tue, 14 Apr 2026 06:47:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776149268; bh=GfdMwXIxFLgeH6dRd3zkWYt7Jm6WS9weggX+bFFW7Q4=; h=Date:From:Subject:To:Cc:References:In-Reply-To:From; b=bh940DnbkbHJRU11ZgAhUNTeW3eJem+Y6lwSz+qsRl62Vf2di34u9ql9iSTTAY+Vy tYvgHuTNZT/zF/bQnf6XR/mp8y9LMK21JmW8+Myzy+nG7jKgjUYvuKlqZqHsgwR5V/ 3E+itH2wBk47fVhOuCXDvuMsYGtAWwJx55kQgKwyh3Br4WNXb66bi2nU09fuyE0NAx /OCwZTJjl4gP0hU6y2pT3Ha9s6yFWKCFc26iCy+LB5Ye3iNYv2+h1QzvJTwgPaXcd9 UpkurKoqYU7WOeaJTkx1tEFxxHm4WGHpoOwSEdulqHbBDVAQZLSEmYgUP7h4oKKvrh tDD1ZbiC5QOQA== Message-ID: Date: Tue, 14 Apr 2026 08:47:39 +0200 Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Hans Verkuil Subject: Re: [ANNv4] Media Summit on May 26th in Nice, France To: Laurent Pinchart , Nicolas Dufresne Cc: Loic Poulain , Linux Media Mailing List , Mauro Carvalho Chehab , Sean Young , Sakari Ailus , Ricardo Ribalda , Jacopo Mondi , =?UTF-8?Q?Niklas_S=C3=B6derlund?= , Tomi Valkeinen , Alain Volmat , Bryan O'Donoghue , Dave Stevenson , Daniel Almeida , Michael Tretter , Tomasz Figa , Steve Cho , Kieran Bingham , Kevin Hilman , Paul Kocialkowski , Benjamin Mugnier , Hans de Goede , Maxime Ripard , Brandon Brnich , Marco Felsch , =?UTF-8?Q?Sven_P=C3=BCschel?= , Michael Riesch , Devarsh Thakkar , Yemike Abhilash Chandra , Jackson Lee , Jai Luthra , Mehdi Djait , "Padhi, Beleswar" , "Donadkar, Rishikesh" , Rouven Czerwinski References: <0f95419b-93c1-4c4f-873b-43bd2a9853f7@kernel.org> <20260413201907.GD4034@killaraus.ideasonboard.com> <20260413211602.GE4034@killaraus.ideasonboard.com> Content-Language: en-US, nl In-Reply-To: <20260413211602.GE4034@killaraus.ideasonboard.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. >>> >>> 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. The agenda for the media summit is getting quite full, and I agree with Laurent that 20 minutes is likely not enough. If we can so a session on Monday instead, then that would be a good solution. I have never been very enthusiastic about the m2m framework: it's fine for e.g. simple scalers, but it's awkward to use for codecs let alone ISPs. I always felt that we really need variants of the m2m framework that are customized to specific use-cases: i.e. a codec m2m framework, and (perhaps) an ISP m2m framework. The big problem with that is of course who will do the work. Making new frameworks is difficult and takes a long time. Regards, Hans > >>>> On Sun, Apr 12, 2026 at 12:25 PM Hans Verkuil wrote: >>>>> >>>>> (Please pass this on to anyone you think might be interested in this!) >>>>> >>>>> Hi all, >>>>> >>>>> This is the fourth version of this announcement, updating the list of >>>>> attendees >>>>> and the tentative agenda at the end: please let me know if you see >>>>> mistakes. >>>>> Note that there is still time for one or two other topics. Also please >>>>> check >>>>> the agenda if you need more (or perhaps less) time for your topic. >>>>> >>>>> This year's Media Summit will be held on Tuesday May 26th the day before >>>>> the >>>>> Embedded Recipes Conference in Nice, France: >>>>> >>>>> https://embedded-recipes.org/2026/ >>>>> >>>>> The Media Summit will be held at Hotel Campanile and in the same meeting >>>>> room >>>>> as last year (Nikaia): >>>>> >>>>> https://nice-aeroport.campanile.com/en-us/ >>>>> >>>>> It is close to the Airport and to the Embedded Recipes venue. >>>>> >>>>> The meeting room can hold up to 30 people and I will provide video >>>>> conferencing support, >>>>> just like last year. The location and the meeting room was quite nice last >>>>> year, so >>>>> I saw no need to change it. >>>>> >>>>> That said, in-person participation is very much preferred. This yearly >>>>> summit is meant >>>>> for active media developers to meet face-to-face and to discuss media >>>>> subsystem issues. >>>>> >>>>> And it is also a good opportunity to talk to each other during the >>>>> Embedded Recipes >>>>> conference to discuss topics in a smaller group. But if you are an active >>>>> media developer >>>>> and are really not able to attend in person, then remote participation is >>>>> an option. >>>>> >>>>> If you want to attend the meeting (either in person or remote), then send >>>>> an email to me >>>>> directly. The deadline for in-person attendance is May 14 as the hotel >>>>> needs to know the >>>>> final number of attendees by then. >>>>> >>>>> There is no registration fee, the meeting room is sponsored by Cisco and >>>>> Collabora, and >>>>> the lunch is sponsored by Ideas on Board! Many thanks to our sponsors, >>>>> it's very much >>>>> appreciated. >>>>> >>>>> If you have a topic that you want to discuss, just 'Reply All' to this >>>>> announcement >>>>> and give the topic title, a short description and a guesstimate of the >>>>> time you need >>>>> for your topic. >>>>> >>>>> See last year's Media Summit Report as an example of what to expect: >>>>> >>>>> https://lore.kernel.org/linux-media/21769183-ca57-4f8f-818a-6a1ad089298d@jjverkuil.nl/ >>>>> >>>>> Regards, >>>>> >>>>>         Hans >>>>> >>>>> PS: Be aware that May 24 and 25 are public holidays in France. So many >>>>> shops may be >>>>> closed those days. >>>>> >>>>> In-person attendees: >>>>> Sakari Ailus >>>>> Kieran Bingham >>>>> Brandon Brnich >>>>> Rouven Czerwinski >>>>> Mehdi Djait >>>>> Bryan O'Donoghue >>>>> Nicolas Dufresne >>>>> Marco Felsch >>>>> Paul Kocialkowski >>>>> Jai Luthra >>>>> Jacopo Mondi >>>>> Benjamin Mugnier >>>>> Beleswar Padhi >>>>> Laurent Pinchart >>>>> Loic Poulain >>>>> Sven Püschel >>>>> Ricardo Ribalda >>>>> Michael Riesch >>>>> Devarsh Thakkar >>>>> Michael Tretter >>>>> Hans Verkuil >>>>> >>>>> Remote attendees: >>>>> Yemike Abhilash Chandra >>>>> Rishikesh Donadkar >>>>> Jackson Lee >>>>> Dave Stevenson (tentative) >>>>> >>>>> >>>>> Agenda (tentative): >>>>> >>>>> 8:45-9:20: Arrive, settle in >>>>> >>>>> 9:20-9:30: Short intro (Hans Verkuil) >>>>> >>>>> 9:30-9:45: Status of ISP support in V4L2 >>>>>         Presenter: Laurent Pinchart >>>>>         Description: Summary of ISP-related development in V4L2 since the >>>>> last >>>>>         Linux Media Summit. This includes a brief overview of technical >>>>>         developments, and a summary of the efforts to engage with vendors. >>>>> >>>>> 9:45-10:45: V4L2 Stateless Video Encoding uAPI Progress Update >>>>>         Presenter: Paul Kocialkowski >>>>>         Description: An update on the ongonig work to support stateless >>>>> codecs in V4L2. >>>>>         Some of the remaining open topics will be presented and discussed. >>>>> >>>>> 10:45-11:00: break >>>>> >>>>> 11:00-11:30: Vulkan Video Codecs >>>>>         Presenter: Nicolas Dufresne >>>>>         Description: Vulkan video codecs: what are the viable options for >>>>> Linux Media >>>>>         and what is in preparation outside of our subsystem. The second >>>>> aspect is >>>>>         informative as these discussions don't seem to lean toward our >>>>> subsystem as the >>>>>         foundation. But I think it's rather useful for everyone to >>>>> understand why and >>>>>         what is included. >>>>> >>>>> 11:30-12:00: Protected Video playback on i.MX8MQ >>>>>         Presenter: Rouven Czerwinski >>>>>         Description: Introduction to protected video playback >>>>>         on i.MX8MQ and missing bits for linux-media & protected heap >>>>> interoperability. >>>>> >>>>> 12:00-13:30: Lunch >>>>> >>>>> 13:30-14:00: HDCP support for HDMI receivers >>>>>         Presenter: Hans Verkuil >>>>>         Description: I have been working on adding HDCP support for HDMI >>>>> receivers. >>>>>         Specifically the HDCP negotiation between sources and sinks. >>>>> >>>>> 14:00-14:30: AI patches >>>>>         Presenter: Sakari Ailus >>>>>         Description: What is our policy w.r.t. AI generated patches? >>>>> >>>>> 14:30-15:00 Overview of Media CI: where do pipelines run? >>>>>         Presenter: Ricardo Ribalda >>>>>         Description: How are jobs in pipelines assigned? How does the >>>>> infrastructure >>>>>         for Media CI work? Are there things that can be tweaked to make it >>>>> more >>>>>         reliable? >>>>> >>>>> 15:00-15:15: Break >>>>> >>>>> 15:15-16:15: Discussion of the media subsystem development process >>>>>         Presenter: Hans Verkuil >>>>>         Description: Review of the multi-committer model: current status >>>>> and next steps. >>>>>         Are there any bottlenecks, any ideas for improvements, w.r.t. the >>>>> development process? >>>>> >>>>> As you can see, there is still some available time for other topics. >