From: Mario Limonciello <superm1@kernel.org>
To: Alex Huang <Alex.Huang2@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,
alexander.deucher@amd.com, christian.koenig@amd.com,
alex.hung@amd.com
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] drm/edid: Parse AMD VSDB FreeSync range in common code
Date: Fri, 24 Jul 2026 11:31:11 -0500 [thread overview]
Message-ID: <a9d8e66f-bf4b-4299-9b2e-cdbbcac22b09@kernel.org> (raw)
In-Reply-To: <20260724161713.119382-1-Alex.Huang2@amd.com>
On 7/24/26 11:17, Alex Huang wrote:
> This patch series implements parsing for AMD VSDB block's FreeSync
> related data directly in the EDID common parser.
>
> Some monitor manufacturers advertise their VRR capability exclusively
> using the AMD VSDB block's FreeSync data fields, many other
> manufacturers (notably pre EDID 1.4 monitors and some post 1.4 monitors)
> also do not include the relevant continuous frequency feature flag in
> the EDID. This makes it difficult to differentiate true VRR capability
> from supporting a few refresh rates between the range specified in EDID
> refresh rate range field in a spec compliant manner.
>
> Incidentally also resolves a recent regression where amdgpu failed to
> detect some DP monitors as VRR capable after EDID parser was moved to
> DRM common.
>
> v2:
> - Use a ladder style parser as suggested by Mario.
> - Validate payload lengths before parsing.
> - Removed an extra amd_vsdb_version reassignment.
>
> Alex Huang (4):
> drm/edid: Parse AMD VSDB for FreeSync refresh range
> drm/amd/display: Use HDMI FreeSync range from common EDID parser
> drm/amd/display: Clean up FreeSync capability detection
> drm/amd/display: Remove unused DMCU/DMUB EDID CEA parser
>
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 252 +++---------------
> drivers/gpu/drm/amd/display/dc/Makefile | 1 -
> .../gpu/drm/amd/display/dc/dc_edid_parser.c | 80 ------
> .../gpu/drm/amd/display/dc/dc_edid_parser.h | 44 ---
> drivers/gpu/drm/amd/display/dc/dce/dce_dmcu.c | 121 ---------
> drivers/gpu/drm/amd/display/dc/inc/hw/dmcu.h | 10 -
> .../gpu/drm/amd/display/dmub/inc/dmub_cmd.h | 71 -----
> drivers/gpu/drm/drm_edid.c | 141 ++++++++--
> include/drm/drm_connector.h | 22 +-
> 9 files changed, 175 insertions(+), 567 deletions(-)
> delete mode 100644 drivers/gpu/drm/amd/display/dc/dc_edid_parser.c
> delete mode 100644 drivers/gpu/drm/amd/display/dc/dc_edid_parser.h
>
> --
> 2.34.1
>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
prev parent reply other threads:[~2026-07-24 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 16:17 Alex Huang
2026-07-24 16:17 ` [PATCH v2 1/4] drm/edid: Parse AMD VSDB for FreeSync refresh range Alex Huang
2026-07-24 16:30 ` Mario Limonciello
2026-07-24 16:17 ` [PATCH v2 2/4] drm/amd/display: Use HDMI FreeSync range from common EDID parser Alex Huang
2026-07-24 16:17 ` [PATCH v2 3/4] drm/amd/display: Clean up FreeSync capability detection Alex Huang
2026-07-24 16:17 ` [PATCH v2 4/4] drm/amd/display: Remove unused DMCU/DMUB EDID CEA parser Alex Huang
2026-07-24 16:31 ` Mario Limonciello [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=a9d8e66f-bf4b-4299-9b2e-cdbbcac22b09@kernel.org \
--to=superm1@kernel.org \
--cc=Alex.Huang2@amd.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--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
all inboxes | Powered by JetHome®