From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/msm/dp: Skip push_idle in atomic_disable if display is not powered on
Date: Sat, 16 May 2026 15:42:51 +1000 [thread overview]
Message-ID: <review-overall-20260511-edp_suspend-v1-1-128555968d7c@oss.qualcomm.com> (raw)
In-Reply-To: <20260511-edp_suspend-v1-1-128555968d7c@oss.qualcomm.com>
Overall Series Review
Subject: drm/msm/dp: Skip push_idle in atomic_disable if display is not powered on
Author: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Patches: 2
Reviewed: 2026-05-16T15:42:51.497192
---
This is a single-patch fix for a real crash scenario on Qualcomm eDP interfaces. When an eDP connector has no panel attached, the probe-time DPCD read fails, leaving `hpd_state` at `ST_DISCONNECTED`. Consequently `msm_dp_bridge_atomic_enable()` exits early, `power_on` stays `false`, and link clocks are never enabled. During system suspend, `drm_atomic_helper_suspend()` still calls `atomic_disable()` on all registered bridges, and `msm_dp_ctrl_push_idle()` writes to `REG_DP_STATE_CTRL` on an unpowered controller — triggering a NoC slave error and a fatal crash.
The fix is straightforward and correct in principle: guard `msm_dp_ctrl_push_idle()` with a `power_on` check. This is consistent with how `msm_dp_display_disable()` (called from the subsequent `atomic_post_disable`) already guards itself with `if (!msm_dp_display->power_on) return 0;`.
**Verdict: The patch looks correct and the approach is reasonable.** One minor concern below.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-05-16 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 8:36 [PATCH] drm/msm/dp: Skip push_idle in atomic_disable if display is not powered on Yongxing Mou
2026-05-13 13:28 ` Dmitry Baryshkov
2026-05-16 5:42 ` Claude review: " Claude Code Review Bot
2026-05-16 5:42 ` Claude Code Review Bot [this message]
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-20260511-edp_suspend-v1-1-128555968d7c@oss.qualcomm.com \
--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