Hi, On Tue, Aug 19, 2025 at 09:57:30PM +0300, Dmitry Baryshkov wrote: > Currently DRM framework expects that the HDMI connector driver supports > all infoframe types: it generates the data as required and calls into > the driver to program all of them, letting the driver to soft-fail if > the infoframe is unsupported. This has a major drawback on userspace > API: the framework also registers debugfs files for all Infoframe types, > possibly surprising the users when infoframe is visible in the debugfs > file, but it is not visible on the wire. > > Let drivers declare that they support only a subset of infoframes, > creating a more consistent interface. > > Signed-off-by: Dmitry Baryshkov <dmitry.barysh...@oss.qualcomm.com>
I'm not really convinced. Infoframes aren't really something you should ignore, AVI is effectively mandatory, HDMI kind of is too, AUDIO is if audio support is enabled, DRM is mandatory if HDR is used. SPD is indeed optional though. So, it's really dynamic in essence, and not really something we should expect drivers to ignore. I do acknowledge that a lot of drivers just silently ignore the infoframes they don't support at the moment, which isn't great either. Maybe we should standardize and document what drivers should do when they don't support a given infoframe type? Something like return EOPNOTSUPP if you don't support it, and we warn in the core if we get one for a mandatory infoframe? Maxime
signature.asc
Description: PGP signature
