From: Jernej Skrabec <jernej.skrabec@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
ville.syrjala@linux.intel.com, lexander.deucher@amd.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: [PATCH] drm/edid: Fix sync polarity of DMT 1920x1080@60Hz
Date: Sat, 14 Nov 2026 19:07:11 +0100 [thread overview]
Message-ID: <20261114180711.207722-1-jernej.skrabec@gmail.com> (raw)
VESA DMT defines 1920x1080@60Hz (DMT ID 0x52) as the CTA-861 1080p
timing (VIC 16), with positive horizontal and vertical sync. The DMT
mode table has both polarities negative instead.
Since drm_match_cea_mode() also compares sync flags, a 1920x1080@60Hz
mode created from an EDID standard timing doesn't match VIC 16 and ends
up as a separate mode next to the one from the CTA Video Data Block. When
userspace picks it, the sink receives the wrong sync polarities, and
because the mode isn't recognized as a CTA format, the AVI InfoFrame
carries no VIC and RGB output uses full instead of limited quantization
range.
Use positive sync polarities, as defined by VESA DMT.
Fixes: bfcd74d2aeda ("drm/edid: Add DMT modes with ID > 0x50")
Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
---
drivers/gpu/drm/drm_edid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index b8f882a17c8f..7adaa428163f 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -607,7 +607,7 @@ static const struct drm_display_mode drm_dmt_modes[] = {
/* 0x52 - 1920x1080@60Hz */
{ DRM_MODE("1920x1080", DRM_MODE_TYPE_DRIVER, 148500, 1920, 2008,
2052, 2200, 0, 1080, 1084, 1089, 1125, 0,
- DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC) },
+ DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
/* 0x44 - 1920x1200@60Hz RB */
{ DRM_MODE("1920x1200", DRM_MODE_TYPE_DRIVER, 154000, 1920, 1968,
2000, 2080, 0, 1200, 1203, 1209, 1235, 0,
--
2.43.0
reply other threads:[~2026-11-14 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261114180711.207722-1-jernej.skrabec@gmail.com \
--to=jernej.skrabec@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lexander.deucher@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®