[PATCH 3/4] drm/amd: treat max_tmds_clock==0 as unconstrained
From: Johannes Wüller
Date: Sun Mar 15 2026 - 18:35:16 EST
If max_tmds_clock is not specified by the EDID, it should be treated
as unconstrained rather than as a zero MHz limit, since it would cause
adjust_colour_depth_from_display_info() to reject all color depths
unconditionally.
Signed-off-by: Johannes Wüller <johanneswueller@xxxxxxxxx>
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index bc853f7555a9..82c8dc8dd39f 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -6612,7 +6612,8 @@ static bool adjust_colour_depth_from_display_info(
/* The above depths are the only ones valid for HDMI. */
return false;
}
- if (normalized_clk <= info->max_tmds_clock) {
+ if (info->max_tmds_clock == 0 ||
+ normalized_clk <= info->max_tmds_clock) {
timing_out->display_color_depth = depth;
return true;
}
--
2.53.0