From: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>
To: alexander.deucher@amd.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, harry.wentland@amd.com, sunpeng.li@amd.com,
siqueira@igalia.com
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] amdgpu: Enable Adaptive Sync over PCON with HDMI VRR
Date: Sun, 18 Jan 2026 12:41:14 +0100 [thread overview]
Message-ID: <f7eb4d8540e1453fa7612e76ad7b78e5f4c165a4.camel@gmail.com> (raw)
In-Reply-To: <20260113214104.146856-1-tomasz.pakula.oficjalny@gmail.com>
On Tue, 2026-01-13 at 22:41 +0100, Tomasz Pakuła wrote:
> Adaptive Sync over PCON is only available as FreeSync over HDMI. TVs which do
> not support FreeSync, do not have working VRR with DP -> HDMI 2.1 adapters even
> though adapters will take care of HDMI VRR info packets.
>
> Since HDMI VRR relies on FRL modes, this will only be enabled for PCONs in the
> VRR whitelist. HDMI VRR for native HDMI connector will still not be
> possible/attempted.
>
> I myself validated these changes with my Samsung S95B + Bernhard validated on
> LG C4 + FreeSync-less Sony Bravia 8. I used Alienware AW3423DWF that only
> has HDMI 2.0 to check that FreeSync still triggers properly for "older" hardware
>
> For missing VRRmax or VRRmax == 0, the upper boundary is the currently selected
> video mode refresh rate. I wasn't sure how best to implement it but 10000
> works since the driver already limits VRR range to the currently selected
> video mode and 10000 Hz should be good enough for years to come.
>
> Changes in v2:
> - More info parsed from HDMI Forum vsdb
> - EDID parsing squashed into one commit
> - Support for VRRmax == 0
>
> Tomasz Pakuła (3):
> drm/edid: parse more info from HDMI Forum vsdb
> drm/amd/display: rename PCON adaptive sync types
> drm/amd/display: enable HDMI VRR over PCON
>
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 27 +++++++++--
> .../amd/display/amdgpu_dm/amdgpu_dm_helpers.c | 2 +-
> .../amd/display/modules/inc/mod_info_packet.h | 4 +-
> .../display/modules/info_packet/info_packet.c | 4 +-
> drivers/gpu/drm/drm_edid.c | 41 +++++++++++++++-
> include/drm/drm_connector.h | 47 +++++++++++++++++++
> 6 files changed, 114 insertions(+), 11 deletions(-)
I'd like to inform you that this patch series will be superseded by
another, bigger patch series which compiles my recent work as all the
separate series/patches di conflict with each other.
Thank you.
Tomasz
prev parent reply other threads:[~2026-01-18 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 21:41 [PATCH v2 0/3] amdgpu: Enable Adaptive Sync over PCON with HDMI VRR Tomasz Pakuła
2026-01-13 21:41 ` [PATCH v2 1/3] drm/edid: parse more info from HDMI Forum vsdb Tomasz Pakuła
2026-01-13 21:41 ` [PATCH v2 2/3] drm/amd/display: rename PCON adaptive sync types Tomasz Pakuła
2026-01-13 21:41 ` [PATCH v2 3/3] drm/amd/display: enable HDMI VRR over PCON Tomasz Pakuła
2026-01-18 11:41 ` Tomasz Pakuła [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=f7eb4d8540e1453fa7612e76ad7b78e5f4c165a4.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=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--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