From: sashiko-bot@kernel.org
To: "Johannes Wüller" <johanneswueller@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RESEND PATCH v2 2/2] drm/amd: fix HDMI signal type for EDID overrides
Date: Sat, 03 Oct 2026 17:56:19 +0000 [thread overview]
Message-ID: <20261003175619.722451F0089E@smtp.kernel.org> (raw)
In-Reply-To: <20261003161525.23600-3-johanneswueller@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] amdgpu: missing EDID override check in rgb_output_is_limited_range()
--
commit 8529835fe6f32deeb33be0fa62706033cd8f1243
Author: Johannes Wüller <johanneswueller@gmail.com>
drm/amd: fix HDMI signal type for EDID overrides
This commit updates AMD display code to trust the physical connector type
over the EDID for HDMI capabilities when an EDID override is active. This
fixes cases where the overriding EDID does not advertise HDMI capabilities.
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_connector.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_connector.c
> index ad3383169d83f..2bce57b060374 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_connector.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_connector.c
> @@ -2134,7 +2134,14 @@ VISIBLE_IF_KUNIT void create_eml_sink(struct amdgpu_dm_connector *aconnector)
> return;
> }
>
> - if (connector->display_info.is_hdmi)
> + /*
> + * If an EDID override is active, it may not advertise HDMI capability
> + * even though the physical connector is HDMI. Trust the connector type.
> + */
> + if (connector->display_info.is_hdmi ||
> + (connector->edid_overridden &&
> + (connector->connector_type == DRM_MODE_CONNECTOR_HDMIA ||
> + connector->connector_type == DRM_MODE_CONNECTOR_HDMIB)))
[Severity: Medium]
Does this same logic need to be applied to rgb_output_is_limited_range()
in the same file?
Looking at rgb_output_is_limited_range(), it relies directly on
display_info.is_hdmi to determine the default RGB range:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_connector.c:rgb_output_is_limited_range()
{
switch (connector_state->hdmi.broadcast_rgb) {
...
default:
return connector_state->connector->display_info.is_hdmi &&
dc_crtc_timing->vic > 1;
}
If a user supplies an EDID override without HDMI capabilities for a physical
HDMI connector, display_info.is_hdmi evaluates to false here. This causes
the function to incorrectly default to Full Range RGB instead of Limited
Range RGB for standard TV formats (VIC > 1). This results in incorrect
color range output (crushed blacks and clipped whites).
Could this override check also be added to rgb_output_is_limited_range()
so TV formats correctly output limited range RGB?
> init_params.sink_signal = SIGNAL_TYPE_HDMI_TYPE_A;
>
> aconnector->drm_edid = drm_edid;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261003161525.23600-1-johanneswueller@gmail.com?part=2
next prev parent reply other threads:[~2026-10-03 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 16:15 [RESEND PATCH v2 0/2] drm/amd: fix HDMI output with non-HDMI EDID overrides Johannes Wüller
2026-10-03 16:15 ` [RESEND PATCH v2 1/2] drm: add edid_overridden flag to drm_connector Johannes Wüller
2026-10-03 17:56 ` sashiko-bot
2026-10-04 8:49 ` Johannes Wüller
2026-10-03 16:15 ` [RESEND PATCH v2 2/2] drm/amd: fix HDMI signal type for EDID overrides Johannes Wüller
2026-10-03 17:56 ` sashiko-bot [this message]
2026-10-04 8:49 ` Johannes Wüller
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=20261003175619.722451F0089E@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=johanneswueller@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.