Re: [ANNv4] Media Summit on May 26th in Nice, France

Hans Verkuil
2026-04-14T06:49:31Z

On 13/04/2026 11:57, Michael Riesch wrote:
> Hi Hans,
>
> On 4/12/26 12:25, Hans Verkuil wrote:
>> [...]
>> 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.
>
> If there is still a bit of time left, maybe we can reserve some 15-30
> minutes for the following:

I added this to the agenda. Thanks!

Regards,

Hans

>
> -------%<---snip--------------------------------------------------------
>
> The Butterfly Effect or How Support for Complex Hardware may affect the uAPI
>
> Video capture and camera hardware in recent SoCs is exceedingly complex
> and the assumption that there is one central V4L2 driver that registers
> the media device does not necessarily hold anymore. IMHO we need a
> central media device to rule them all and adaptations to the
> v4l2_{async,device}_register_subdev code. The discussion [0, 1] quickly
> escalated:
> - Dynamic (de)registration of media entities is desired
> - This requires considerations about the uAPI
> - There is significant overlap with the notion of fault-tolerant V4L2
> - There is also a ton of cleanup work, but the resulting patches must
> not break anything existing
> - So we need to talk about possible migration strategies in order to
> achieve reasonable progress without interfering too much with
> existing and working parts
>
> TL;DR: This short talk outlines the effects of upstreaming Rockchip
> RK3588 video capture and camera support on the V4L2/MC uAPI and on the
> (linux-media) universe as we know it today.
>
> [0]
> https://linuxtv.org/irc/oftc/irclogger_log/linux-media?date=2026-02-17,Tue&sel=72#l68
> [1]
> https://linuxtv.org/irc/oftc/irclogger_log/linux-media?date=2026-02-18,Wed&sel=14#l10
>
> -------%<---snip--------------------------------------------------------
>
> If desired, I'll try to find the time to describe the issue in more
> detail on the list *before* everyone travels to Nice. Then, we can use
> the time on site more effectively to discuss it.
>
> Best regards,
> Michael