dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adolfo <adolfotregosa@gmail.com>
To: Fangzhi Zuo <jerry.zuo@amd.com>,
	harry.wentland@amd.com, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH v1 0/3] drm/amd/display: passive VRR
Date: Wed, 2 Sep 2026 17:23:45 +0100	[thread overview]
Message-ID: <1aeed63d-c7ee-426b-977f-af00a309987a@gmail.com> (raw)
In-Reply-To: <20260901191251.2653684-1-jerry.zuo@amd.com>


I tested these patches in conjunction with the HDMI 2.1 VRR ones on 
kernel 7.3-rc1, and VRR still does not engage while on the desktop, only 
in-game.


On 01/09/2026 20:12, Fangzhi Zuo wrote:

> Passive VRR keeps a sink in its variable-refresh state during fixed-refresh
> (desktop) use, avoiding the blanking/brightness flicker that HDMI sinks
> without seamless VRR transitions show on VRR entry/exit. It is opt-out
> (enabled by default where the connector advertises passive_vrr_capable) and
> is not useful for DP/eDP, where seamless VRR transitions are mandated by the
> standard.
>
> Patch 1 adds the DRM core plumbing: the PASSIVE_VRR_DISABLED atomic CRTC
> property and the immutable passive_vrr_capable connector property, with the
> attach/set helpers.
>
> Patch 2 wires these into amdgpu via the existing DC
> stream->freesync_on_desktop path.
>
> Patch 3 fixes the MCCS FreeSync fallback so that HDMI-Forum VRR (HF-VSDB)
> sinks keep freesync_capable; without it passive VRR never engages on the
> very TMDS HF-VSDB sinks it targets.
>
>
> Fangzhi Zuo (1):
>    drm/amd/display: Keep FreeSync for HF-VSDB VRR sinks in MCCS fallback
>
> Tomasz Pakuła (2):
>    drm: Add passive_vrr properties for passive/desktop VRR
>    drm/amd/display: Use passive_vrr properties in amdgpu
>
>   .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h |  1 +
>   .../display/amdgpu_dm/amdgpu_dm_connector.c   | 13 +++-
>   .../display/amdgpu_dm/amdgpu_dm_freesync.c    |  7 ++
>   drivers/gpu/drm/drm_atomic_uapi.c             |  4 +
>   drivers/gpu/drm/drm_connector.c               | 73 +++++++++++++++++++
>   drivers/gpu/drm/drm_crtc.c                    |  2 +
>   drivers/gpu/drm/drm_mode_config.c             |  6 ++
>   include/drm/drm_connector.h                   | 15 ++++
>   include/drm/drm_crtc.h                        |  9 +++
>   include/drm/drm_mode_config.h                 |  6 ++
>   10 files changed, 134 insertions(+), 2 deletions(-)
>
>
> base-commit: 8c77d618886a143de5cd87a35963b4993075802a

      parent reply	other threads:[~2026-09-03  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 19:12 [PATCH v1 0/3] drm/amd/display: passive VRR Fangzhi Zuo
2026-09-01 19:12 ` [PATCH v1 1/3] drm: Add passive_vrr properties for passive/desktop VRR Fangzhi Zuo
2026-09-01 19:24   ` sashiko-bot
2026-09-01 19:28   ` Tomasz Pakuła
2026-09-01 19:12 ` [PATCH v1 2/3] drm/amd/display: Use passive_vrr properties in amdgpu Fangzhi Zuo
2026-09-01 19:29   ` sashiko-bot
2026-09-01 19:12 ` [PATCH v1 3/3] drm/amd/display: Keep FreeSync for HF-VSDB VRR sinks in MCCS fallback Fangzhi Zuo
2026-09-02 16:23 ` Adolfo [this message]

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=1aeed63d-c7ee-426b-977f-af00a309987a@gmail.com \
    --to=adolfotregosa@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=jerry.zuo@amd.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