From: Fangzhi Zuo <jerry.zuo@amd.com>
To: Harry Wentland <harry.wentland@amd.com>
Cc: <amd-gfx@lists.freedesktop.org>, Fangzhi Zuo <Jerry.Zuo@amd.com>,
"Pei-Hsin Yang" <peihsiny@valvesoftware.com>
Subject: [PATCH] drm/amd/display: Emit VTEM for HF-VSDB VRR on TMDS links
Date: Fri, 28 Aug 2026 10:32:27 -0400 [thread overview]
Message-ID: <20260828143227.2280936-1-jerry.zuo@amd.com> (raw)
From: Fangzhi Zuo <Jerry.Zuo@amd.com>
HDMI-Forum VRR metadata is carried in the Video Timing Extended Metadata
Packet (VTEM). amdgpu_dm_update_freesync_state_on_stream() only built the
VTEM for SIGNAL_TYPE_HDMI_FRL, so on a TMDS link a sink that advertises
HDMI-Forum VRR via the HF-VSDB (but not AMD FreeSync via the AMD-VSDB)
never received a VTEM and VRR could not engage.
Per HDMI 2.1 a VTEM is a video-blanking data-island packet valid in both
TMDS and FRL modes; only the compressed-video CVTEM is tied to FRL. Build
the VTEM on a TMDS link as well when the sink reports HF-VSDB VRR. Sinks
without HF-VSDB VRR keep the existing AMD FreeSync SPD infopacket path, so
AMD FreeSync behavior is unchanged.
Signed-off-by: Fangzhi Zuo <Jerry.Zuo@amd.com>
Tested-by: Pei-Hsin Yang <peihsiny@valvesoftware.com>
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_freesync.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_freesync.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_freesync.c
index 63d10cb7f5ed..281c6cec9f4b 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_freesync.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_freesync.c
@@ -238,7 +238,10 @@ void amdgpu_dm_update_freesync_state_on_stream(
&vrr_infopacket,
pack_sdp_v1_3);
- if (new_stream->sink->sink_signal == SIGNAL_TYPE_HDMI_FRL)
+ /* Per HDMI 2.1, VTEM is valid on TMDS as well as FRL */
+ if (new_stream->sink->sink_signal == SIGNAL_TYPE_HDMI_FRL ||
+ (new_stream->sink->sink_signal == SIGNAL_TYPE_HDMI_TYPE_A &&
+ aconn && aconn->base.display_info.hdmi.vrr_cap.supported))
mod_build_infopacket_vtem(new_stream, &vrr_params, 0, &vrr_infopacket);
new_crtc_state->freesync_vrr_info_changed |=
base-commit: eb3ff61912825e72633f70b6f7197973be83c8db
--
2.53.0
next reply other threads:[~2026-08-28 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 14:32 Fangzhi Zuo [this message]
2026-08-28 14:35 ` [PATCH] drm/amd/display: Emit VTEM for HF-VSDB VRR on TMDS links Harry Wentland
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=20260828143227.2280936-1-jerry.zuo@amd.com \
--to=jerry.zuo@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=peihsiny@valvesoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.