On Mon, 2026-01-19 at 15:23 +0200, Jani Nikula wrote: > On Mon, 19 Jan 2026, Tomasz Pakuła <[email protected]> wrote: > > [Why] > > The function would continue to try to parse EDID even if DisplayID > > extension block wasn't found. Sometimes it got lucky and found AMD vsdb > > in CEA extension block which made debugging harder. > > > > [How] > > Add a return if DisplayID extension block wasn't found > > Maybe don't use homegrown EDID parsing, but use drm_edid.c instead? > > BR, > Jani. >
I would be all for it but I didn't want to make even more changes. I cannot refactor the whole amdgpu on my own :) Plus, the generic drm code doesn't yet parse AMD vsdb. I could certainly add such functionality, especially since it's already in projects like edid-decode but amdgpu seems to be doing a lot of home-grown edid parsing and I'm not really sure why, even sending stuff to firmware. Especially confusing is the part where AMD vsdb is parsed differently if it's in CTA extensiton block or DisplayID. They honestly are identical. At least, here in, setting the freesync caps, getting info from generic drm should be ok. I'll think about it and probably intoroduce AMD vsdb parsing to drm in a separate series. > Tomasz
