From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/msm/dp: add missing drm_edid_connector_update() before add_modes on cached EDID
Date: Thu, 04 Jun 2026 12:21:12 +1000 [thread overview]
Message-ID: <review-overall-20260602-drm_plug_flaky_edid-v2-1-1269fb942299@oldschoolsolutions.biz> (raw)
In-Reply-To: <20260602-drm_plug_flaky_edid-v2-1-1269fb942299@oldschoolsolutions.biz>
Overall Series Review
Subject: drm/msm/dp: add missing drm_edid_connector_update() before add_modes on cached EDID
Author: Jens Glathe via B4 Relay
<devnull+jens.glathe.oldschoolsolutions.biz@kernel.org>
Patches: 1
Reviewed: 2026-06-04T12:21:12.498053
---
This is a single-patch fix for a real regression introduced by commit 5bea90ad9743 ("drm/msm/dp: switch to struct drm_edid"). The analysis is correct: the `struct drm_edid` API requires `drm_edid_connector_update()` to be called before `drm_edid_connector_add_modes()`, as explicitly documented in the kernel (`drm_edid.c:7152`: "Must be called before calling drm_edid_connector_add_modes()"). The initial EDID read path (`msm_dp_panel_read_sink_caps` at line 281) already calls `drm_edid_connector_update()`, but when `msm_dp_panel_get_modes()` is called with a cached EDID (i.e., the EDID was read on an earlier call), the connector's internal state may not have the EDID associated — for instance, after a connector reset or if `get_modes` is called on a different connector lifecycle. The fix is minimal, correct, and well-motivated by the v2 cover letter analysis.
**Verdict: Looks good. Recommend merge.**
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 18:18 [PATCH v2] drm/msm/dp: add missing drm_edid_connector_update() before add_modes on cached EDID Jens Glathe via B4 Relay
2026-06-04 2:21 ` Claude Code Review Bot [this message]
2026-06-04 2:21 ` Claude review: " 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=review-overall-20260602-drm_plug_flaky_edid-v2-1-1269fb942299@oldschoolsolutions.biz \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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