From: Chenyu Chen <chen-yu.chen@amd.com>
To: <dri-devel@lists.freedesktop.org>, <amd-gfx@lists.freedesktop.org>
Cc: Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Limonciello Mario <Mario.Limonciello@amd.com>,
Chenyu Chen <chen-yu.chen@amd.com>
Subject: [PATCH 0/2] drm: Move AMD VSDB parsing into DRM EDID core
Date: Fri, 27 Mar 2026 16:21:57 +0800 [thread overview]
Message-ID: <20260327082342.1286878-1-chen-yu.chen@amd.com> (raw)
The AMD Vendor-Specific Data Block (VSDB) v3 parsing currently lives
in amdgpu_dm, using raw byte-walking over EDID extension blocks. This
series moves the parsing into the DRM EDID core so the data is
available through drm_display_info for any driver.
Patch 1 adds the parser in drm_edid.c and the new drm_amd_vsdb_info
struct in drm_connector.h.
Patch 2 updates amdgpu_dm to consume the parsed data from
display_info instead of doing its own parsing, and factors out
panel type determination into a dedicated function.
Chenyu Chen (2):
drm/edid: Parse AMD Vendor-Specific Data Block
drm/amd/display: Use drm_display_info for AMD VSDB data
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 120 ++++++++++--------
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 14 --
drivers/gpu/drm/drm_edid.c | 72 +++++++++++
include/drm/drm_connector.h | 38 ++++++
4 files changed, 178 insertions(+), 66 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-27 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 8:21 Chenyu Chen [this message]
2026-03-27 8:21 ` [PATCH 1/2] drm/edid: Parse AMD Vendor-Specific Data Block Chenyu Chen
2026-03-27 8:21 ` [PATCH 2/2] drm/amd/display: Use drm_display_info for AMD VSDB data Chenyu Chen
2026-03-27 13:04 ` [PATCH 0/2] drm: Move AMD VSDB parsing into DRM EDID core Mario Limonciello
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=20260327082342.1286878-1-chen-yu.chen@amd.com \
--to=chen-yu.chen@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=sunpeng.li@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