From: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>,
alexander.deucher@amd.com, harry.wentland@amd.com,
sunpeng.li@amd.com
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
siqueira@igalia.com, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
bernhard.berger@gmail.com, daniel@fooishbar.org
Subject: Re: [PATCH v4 23/27] drm: Add passive_vrr_disabled property to crtc
Date: Tue, 17 Feb 2026 17:41:00 +0100 [thread overview]
Message-ID: <8006baea7c35850de3a39f155b7aa004c4896495.camel@gmail.com> (raw)
In-Reply-To: <c6a852ae-4edf-4336-9f2a-448c296cc045@mailbox.org>
On Tue, 2026-02-17 at 09:21 +0100, Michel Dänzer wrote:
> On 2/16/26 17:45, Tomasz Pakuła wrote:
> > Many TVs and other HDMI sinks suffer from blanking and possibly other
> > glitches when VRR is toggled. With VRR present on such sinks and
> > vrr_on_desktop enabled, they behave like the signal is always variable,
> > even in fixed refresh rate situations. DisplayPort and eDP enforce
> > seamless VRR transitions but HDMI unfortunately doesn't.
> >
> > Keep VRR toggled if it's supported and not explicitly disabled. It can
> > be used for any VRR sinks, but this is mainly targeted for HDMI.
> >
> > Functionally, for an end user, this is the same as normal, fixed refresh
> > rate mode. The only difference is that sink is kept in VRR state which
> > enables seamless transitions into/out of variable refresh rate.
> >
> > Basically, the driver shouldn't change it's behavior around VRR_ENABLED
> > set to false, jut keep sending info packets/frames with VRR/FreeSync/
> > G-Sync/HDMI VRR active.
> >
> > Enabled by default for sinks that claim it's support
>
> Having a negation term like "disabled" in the property name can be confusing (as it involves double negation when the property value is 0) and is better avoided.
>
I understand that and felt a little cheaty by doing this but I couldn't
for the life of my figure out how to make it so a driver could override
this by default, before the compositor will set this. Would a "set"
function work, just like for "capable" properties?
I 100% believe this "Passive VRR" for HDMI should be the default and
helps massively but I'm not even that convinced if this must be user
configurable. Alex asked to make it a property, but In the end, it's not
something thsdat can be controlled on other OSes. I still believe that
users should be able to change this somehow, but if amdgpu module
setting wasn't a good fit, I don't know what is.
In the end, I can just yeet all this completely and hardcode
freesync_on_desktop = true for HDMI like it's done in the windows
driver.
next prev parent reply other threads:[~2026-02-18 8:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:44 [PATCH v4 00/27] drm/amd: VRR fixes, HDMI Gaming Features Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 01/27] drm/amd/display: Return if DisplayID not found in parse_amd_vsdb() Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 02/27] drm/amd/display: Refactor amdgpu_dm_update_freesync_caps() Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 03/27] drm/amd/display: Remove redundant edid checks Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 04/27] drm/amd/display: Move DisplayID vrr parsing Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 05/27] drm/amd/display: Always try to parse AMD vsdb Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 06/27] drm/amd/display: Check for VRR range in CEA " Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 07/27] drm/amd/display: Use bigger VRR range if found in " Tomasz Pakuła
2026-02-26 12:36 ` Jani Nikula
2026-02-26 13:42 ` Tomasz Pakuła
2026-03-17 10:03 ` Tomasz Pakuła
2026-03-20 14:48 ` Leo Li
2026-02-16 16:44 ` [PATCH v4 08/27] drm/amd/display: Separate DP/eDP and PCON paths completely Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 09/27] drm/amd/display: Refactor PCON VRR compatibility check Tomasz Pakuła
2026-02-16 16:44 ` [PATCH v4 10/27] drm/amd/display: Add PCON VRR ID check override Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 11/27] drm/amd/display: Add CH7218 PCON ID Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 12/27] drm/edid: Parse more info from HDMI Forum vsdb Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 13/27] drm/amd/display: Rename PCON adaptive sync types Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 14/27] drm/amd/display: Enable HDMI VRR over PCON Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 15/27] drm/amd/display: Support HDMI VRRmax=0 Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 16/27] drm/amd/display: Build HDMI vsif in correct slot Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 17/27] drm/amd/display: Save HDMI gaming info to edid caps Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 18/27] drm/amd/display: Restore ALLM support in HDMI vsif Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 19/27] drm/amd/display: Trigger ALLM if it's available Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 20/27] drm/amd/display: Reintroduce VTEM info frame Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 21/27] drm/amd/display: Enable HDMI VRR Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 22/27] drm/amd/display: freesync_on_desktop support for " Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 23/27] drm: Add passive_vrr_disabled property to crtc Tomasz Pakuła
2026-02-17 8:21 ` Michel Dänzer
2026-02-17 16:41 ` Tomasz Pakuła [this message]
2026-02-16 16:45 ` [PATCH v4 24/27] drm: Add passive_vrr_capable property to connector Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 25/27] drm: Add ALLM properties " Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 26/27] drm/amd/display: Use passive_vrr properties in amdgpu Tomasz Pakuła
2026-02-16 16:45 ` [PATCH v4 27/27] drm/amd/display: Use ALLM " Tomasz Pakuła
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=8006baea7c35850de3a39f155b7aa004c4896495.camel@gmail.com \
--to=tomasz.pakula.oficjalny@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bernhard.berger@gmail.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michel.daenzer@mailbox.org \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
/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