From: Johannes Wüller <johanneswueller@gmail.com>
To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Johannes Wüller <johanneswueller@gmail.com>
Subject: [PATCH 0/4] drm/amd: fix HDMI output with non-HDMI EDID overrides
Date: Sun, 15 Mar 2026 23:33:02 +0100 [thread overview]
Message-ID: <20260315223307.45807-1-johanneswueller@gmail.com> (raw)
This series fixes several issues that prevent amdgpu from driving an
HDMI display at its native resolution when a non-HDMI EDID is injected
via drm.edid_firmware or debugfs edid_override.
The motivating case is a Dell U3011 (2560x1600) connected via HDMI,
whose native HDMI EDID only advertises CEA modes up to 1920x1080. By
injecting the monitor's DisplayPort EDID (which contains the native
2560x1600 mode), the correct resolution becomes available. However,
amdgpu then fails to drive the output because the injected EDID lacks
an HDMI VSDB, causing the driver to treat the physical HDMI connector
as a passive HDMI-DVI dongle, and rejecting the required pixel clock.
Patch 1 adds an edid_overridden flag to drm_connector, set by the
existing EDID override mechanisms in _drm_do_get_edid(), so that
drivers can detect when an override is in effect and adjust their
behavior accordingly, without duplicating the override mechanism.
Patches 2-4 fix the amdgpu-specific issues:
- incorrect signal type selection when an override is active
- unconditional rejection of all colour depths when max_tmds_clock is
zero
- force_yuv420/422_output flags being silently ignored when the
display doesn't advertise the requested format.
Tested on AMD Ryzen 9 7950X (RDNA3 iGPU, DCN 3.1.5) with a Dell U3011
connected via HDMI at 2560x1600@60Hz RGB 8bpc, and another Dell U3011
connected via DisplayPort in the same mode.
This is my first code contribution to the kernel, so I would appreciate
feedback on whether I've gotten recipients and other procedural details
right! :)
Johannes Wüller (4):
drm: add edid_overridden flag to drm_connector
drm/amd: fix HDMI signal type for EDID overrides
drm/amd: treat max_tmds_clock==0 as unconstrained
drm/amd: fix force_yuv420/422_output being ignored
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 20 +++++++++++--------
.../amd/display/amdgpu_dm/amdgpu_dm_helpers.c | 9 ++++++++-
drivers/gpu/drm/drm_edid.c | 2 ++
include/drm/drm_connector.h | 8 ++++++++
4 files changed, 30 insertions(+), 9 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-15 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 22:33 Johannes Wüller [this message]
2026-03-15 22:33 ` [PATCH 1/4] drm: add edid_overridden flag to drm_connector Johannes Wüller
2026-03-16 1:48 ` Claude review: " Claude Code Review Bot
2026-03-15 22:33 ` [PATCH 2/4] drm/amd: fix HDMI signal type for EDID overrides Johannes Wüller
2026-03-16 1:48 ` Claude review: " Claude Code Review Bot
2026-03-15 22:33 ` [PATCH 3/4] drm/amd: treat max_tmds_clock==0 as unconstrained Johannes Wüller
2026-03-16 1:48 ` Claude review: " Claude Code Review Bot
2026-03-15 22:33 ` [PATCH 4/4] drm/amd: fix force_yuv420/422_output being ignored Johannes Wüller
2026-03-16 1:48 ` Claude review: " Claude Code Review Bot
2026-03-16 1:48 ` Claude review: drm/amd: fix HDMI output with non-HDMI EDID overrides Claude Code Review 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=20260315223307.45807-1-johanneswueller@gmail.com \
--to=johanneswueller@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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