All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Johannes Wüller" <johanneswueller@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RESEND PATCH v2 1/2] drm: add edid_overridden flag to drm_connector
Date: Sat, 03 Oct 2026 17:56:19 +0000	[thread overview]
Message-ID: <20261003175620.245AE1F0089B@smtp.kernel.org> (raw)
In-Reply-To: <20261003161525.23600-2-johanneswueller@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm: edid_overridden flag not set in fallback override path
--

commit e2139c9168877ee02f537cbf19084a0d24c136be
Author: Johannes Wüller <johanneswueller@gmail.com>

drm: add edid_overridden flag to drm_connector

When an EDID override is in effect, the physical connector may not
match reported capabilities. Adds a drm_connector flag that allows
drivers to detect such mismatches.

> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index 42f4e41c459fd..9ea6f5f19131f 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -2424,6 +2424,7 @@ static struct edid *_drm_do_get_edid(struct drm_connector *connector,
>  	struct edid *edid, *new;
>  	size_t alloc_size = EDID_LENGTH;
>  
> +	connector->edid_overridden = false;
>  	override = drm_edid_override_get(connector);
>  	if (override) {
>  		alloc_size = override->size;
> @@ -2431,6 +2432,7 @@ static struct edid *_drm_do_get_edid(struct drm_connector *connector,
>  		drm_edid_free(override);
>  		if (!edid)
>  			return NULL;
> +		connector->edid_overridden = true;

[Severity: Medium]
Does this new flag also need to be set when falling back to an override EDID
after a failed DDC probe?

If an EDID override is provided but the physical DDC probe fails (e.g. due to
broken DDC lines), drm_helper_probe_get_modes() skips reading the EDID and
falls back to drm_edid_override_connector_update(). This fallback applies the
override but appears to miss setting this new flag:

drivers/gpu/drm/drm_edid.c:drm_edid_override_connector_update() {
	const struct drm_edid *override;
	int num_modes = 0;

	override = drm_edid_override_get(connector);
	if (override) {
		if (drm_edid_connector_update(connector, override) == 0)
			num_modes = drm_edid_connector_add_modes(connector);

		drm_edid_free(override);
	...
}

If a driver relies on this flag to apply HDMI signal type workarounds, could
this cause it to read a false value and fail to apply the necessary quirks?

>  		goto ok;
>  	}
>  

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261003161525.23600-1-johanneswueller@gmail.com?part=1

  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 [this message]
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
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=20261003175620.245AE1F0089B@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.