Hi Ivan,
Thanks for reporting this issue and follow-up bisecting.
Can you check if the attached patch resolves the issue?
Thanks in advance,
Melissa Wen
On 20/02/2026 00:35, Ivan Sergeev wrote:
On Fri Feb 20, 2026 at 6:14 AM MSK, Mario Limonciello wrote:
Can you check out at your bad commit and apply just 7f2b5237e313 at the
bad commit? Confirm that fixes it.
Applied 7f2b5237e313 on top of 0159f88a99c9 and the issue persists.
From 5d5c4052fc64a63803f2f0acf7c2760b5b8b5218 Mon Sep 17 00:00:00 2001
From: Melissa Wen <[email protected]>
Date: Fri, 20 Feb 2026 19:38:43 -0300
Subject: [PATCH] drm/drm_edid: ignore continuous freq support for monitor range
Get the min and max refresh rate even if edid doesn't say the display
supports continuous frequencies.
Signed-off-by: Melissa Wen <[email protected]>
---
drivers/gpu/drm/drm_edid.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 26bb7710a462..17c32b33172e 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -6516,9 +6516,6 @@ static void drm_get_monitor_range(struct drm_connector *connector,
if (drm_edid->edid->revision < 4)
return;
- if (!(drm_edid->edid->features & DRM_EDID_FEATURE_CONTINUOUS_FREQ))
- return;
-
drm_for_each_detailed_block(drm_edid, get_monitor_range, &closure);
drm_dbg_kms(connector->dev,
--
2.50.1
