Iterating DisplayID is overcomplicated as it is, and it's not getting easier when we eventually add support for DisplayID from DDC 0xA4 instead of EDID extensions. Prepare by abstracting the complexities away from EDID code. Untested, let's see what our CI thinks. ;) Jani Nikula (6): drm/edid: make a number of functions, parameters and variables const drm/displayid: add separate drm_displayid.c drm/displayid: add new displayid section/block iterators drm/edid: use the new displayid iterator for detailed modes drm/edid: use the new displayid iterator for finding CEA extension drm/edid: use the new displayid iterator for tile info drivers/gpu/drm/Makefile | 2 +- drivers/gpu/drm/drm_displayid.c | 133 +++++++++++++++++++++++++ drivers/gpu/drm/drm_edid.c | 171 +++++++------------------------- include/drm/drm_displayid.h | 28 ++++-- include/drm/drm_edid.h | 3 + 5 files changed, 196 insertions(+), 141 deletions(-) create mode 100644 drivers/gpu/drm/drm_displayid.c -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx