On Thu, Jul 14, 2022 at 11:04:09AM +0200, Geert Uytterhoeven wrote: > The mode parsing code recognizes named modes only if they are explicitly > listed in the internal whitelist, which is currently limited to "NTSC" > and "PAL". > > Provide a mechanism for drivers to override this list to support custom > mode names. > > Ideally, this list should just come from the driver's actual list of > modes, but connector->probed_modes is not yet populated at the time of > parsing. > > Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> > Reviewed-by: Hans de Goede <hdegoede@xxxxxxxxxx> Like we discussed on IRC, I'm not sure allowing drivers to handle named modes is the right thing to do. Named modes in general were a workaround the fact that we were missing infos in drm_display_mode to describe all the modes. I think we really should focus on addressing that first, and then creating some kind of backward compat layer to create an initial DRM state from a named mode provided on the command line. Maxime
Attachment:
signature.asc
Description: PGP signature
