Hi Maxime, On Mon, Jul 06, 2026 at 10:52:32AM +0200, Maxime Ripard wrote: > On Mon, Jul 06, 2026 at 12:35:39AM +0300, Laurent Pinchart wrote: > > Since DDC version 2, introduced in 1996, VGA monitors have exposed EDID > > data over an I2C bus. The bus is also used to detect the presence of a > > connected monitor by trying to read the EDID data. > > > > Some devices where the VGA display is integrated in the device and > > always connected do not connect the DDC pins. Some development boards, > > such as the Renesas M3N Salvator-XS, also do not connect the DDC pins. > > > > To support those, add the ability to provide hardcoded EDID data in the > > device tree. This is mutually exclusive with specifying a DDC bus, and > > can only be done when the VGA display is guaranteed to be always > > connected. > > > > Signed-off-by: Laurent Pinchart <[email protected]> > > This feels redundant with the EDID firmware loading mechanism we have in > KMS already. It should at least be mentioned why we would need to set it > in the device tree at all.
Very good question. I assume you're talking about CONFIG_DRM_LOAD_EDID_FIRMWARE, as the debugfs override_edid feature isn't meant for production. If there are other relevant mechanisms I'm not aware of, please let me know. In the use case at hand, the VGA display is an integral part of the device, the same way an LVDS or DSI panel would be. Using CONFIG_DRM_LOAD_EDID_FIRMWARE, the manufacturer would need to set the drm.edid_firmware command line parameter, and provide EDID as a file in /lib/firmware/ (possibly in an initramfs). Beside the complexity, and the fact it won't be very friendly to people who run a different userspace on the device, I think EDID counts in this case as system description, the same way we support specifying panel timings in device tree. Does this make sense ? If so, I'll update the commit message accordingly in v2. -- Regards, Laurent Pinchart
