From: "Timo Prömer" <timo.proemer04@gmail.com>
To: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>
Cc: "Rodrigo Siqueira" <siqueira@igalia.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Timo Prömer" <timo.proemer04@gmail.com>
Subject: [PATCH v2 0/2] drm/amd/display: Fix missing HF-EEODB blocks in EDID copies
Date: Mon, 13 Jul 2026 21:32:35 +0200 [thread overview]
Message-ID: <20260713193237.2639-1-timo.proemer04@gmail.com> (raw)
Fix an issue in amd/display where devices with HF-EEODB blocks would
be missing these additional blocks during EDID reads.
The driver previously used `edid->extensions + 1` to calculate the
number of blocks to copy, but the base extension flag does not include
HF-EEODB blocks.
Use drm_edid_block_count() directly to get the true number of blocks,
ensuring that HF-EEODB blocks are properly copied.
Changes in v2:
- Fixed a bug in patch 2 where the bounds check still used the old
extension count.
- Patch 1 remains unchanged.
Timo Prömer (2):
drm/edid: Export drm_edid_block_count()
drm/amd/display: Use drm_edid_block_count() instead of raw extensions
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c | 11 ++++++++---
drivers/gpu/drm/drm_edid.c | 3 ++-
include/drm/drm_edid.h | 1 +
3 files changed, 11 insertions(+), 4 deletions(-)
--
2.55.0
next reply other threads:[~2026-07-13 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 19:32 Timo Prömer [this message]
2026-07-13 19:32 ` [PATCH v2 1/2] drm/edid: Export drm_edid_block_count() Timo Prömer
2026-07-13 19:32 ` [PATCH v2 2/2] drm/amd/display: Use drm_edid_block_count() instead of raw extensions Timo Prömer
2026-07-13 19:49 ` sashiko-bot
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=20260713193237.2639-1-timo.proemer04@gmail.com \
--to=timo.proemer04@gmail.com \
--cc=airlied@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.