Re: [PATCH v7 00/10] drm/amd/display: Use drm_edid for more code

On 9/27/24 14:45, Melissa Wen wrote: Hi Alex, Thanks for the intensive testing. I'll need some time to reproduce and debug these regressions. So, we can divide this series into four steps: 1-2 are the basis for drm_edid migration 3-4 are code cleanups 5-9 are drm_edid_product_id migration 1

Re: [PATCH v7 00/10] drm/amd/display: Use drm_edid for more code

Hi Alex, Thanks for the intensive testing. I'll need some time to reproduce and debug these regressions. So, we can divide this series into four steps: 1-2 are the basis for drm_edid migration 3-4 are code cleanups 5-9 are drm_edid_product_id migration 10 is for ACPI EDID feature. Bearing this

Re: [PATCH v7 00/10] drm/amd/display: Use drm_edid for more code

Hi Mario and Melissa, There are three regressions identified during the test, and improvement is required before the patches can be merged. Please see details below. 1. null pointer when hot-plugging a dsc hub (+ three 4k60 monitors). This may point to "drm/amd/display: use drm_edid_product_i

[PATCH v7 00/10] drm/amd/display: Use drm_edid for more code

This is the successor of Melissa's v5 series that was posted [1] as well as my series that was posted [2]. Melissa's patches are mostly unmodified from v5, but the series has been rebase on the new 6.10 based amd-staging-drm-next. As were both touching similar code for fetching the EDID, I've mer