On 5/22/26 2:02 PM, Dmitry Baryshkov wrote: > On Fri, May 22, 2026 at 01:49:50PM +0200, Konrad Dybcio wrote: >> On 3/14/26 2:09 AM, Dmitry Baryshkov wrote: >>> Currently the driver only updates the EDID when it detects a connected >>> monitor, which results in the connector still listing outdated modes >>> even after the display is unplugged. Set connector's EDID to NULL on >>> unplug to clear the list of modes. >>> >>> Signed-off-by: Dmitry Baryshkov <[email protected]> >>> --- >>> drivers/gpu/drm/msm/dp/dp_display.c | 4 ++++ >>> drivers/gpu/drm/msm/dp/dp_panel.c | 8 ++++++++ >>> drivers/gpu/drm/msm/dp/dp_panel.h | 2 ++ >>> 3 files changed, 14 insertions(+) >>> >>> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c >>> b/drivers/gpu/drm/msm/dp/dp_display.c >>> index 0a38957ea901..5c6a24ec140d 100644 >>> --- a/drivers/gpu/drm/msm/dp/dp_display.c >>> +++ b/drivers/gpu/drm/msm/dp/dp_display.c >>> @@ -447,6 +447,10 @@ static int msm_dp_hpd_unplug_handle(struct >>> msm_dp_display_private *dp) >>> return 0; >>> } >>> >>> + /* Don't forget modes for eDP */ >>> + if (!dp->msm_dp_display.is_edp) >>> + msm_dp_panel_unplugged(dp->panel, dp->msm_dp_display.connector); >> >> Is there a change some ""funny"" panels decide to output a new EDID blob >> after a "proper"/custom reset sequence (e.g. to remove limitations >> presented to the DPTX at the UEFI display init stage?) > > The panels don't know if it is a UEFI init or a normal reset. EDID > changes require a long HPD pulse anyway.
I was wondering about the possibility of the panels effectively having a side-channel for absolutely proprietary configuration. But your last sentence makes me believe even that shouldn't be an issue Konrad
