From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH 3/6] drm/msm/dp: Limit voltage swing level to 2 for RA620 bridge
Date: Mon, 25 May 2026 19:16:36 +1000 [thread overview]
Message-ID: <review-patch3-7e435e8c-ba0e-453a-b95c-450446dfc0ff@oss.qualcomm.com> (raw)
In-Reply-To: <7e435e8c-ba0e-453a-b95c-450446dfc0ff@oss.qualcomm.com>
Patch Review
**This patch has a serious problem: it changes a global constant.**
```c
-#define DP_TRAIN_LEVEL_MAX 3
+#define DP_TRAIN_LEVEL_MAX 2
```
`DP_TRAIN_LEVEL_MAX` is used throughout the MSM DP driver for *all* DP connections:
- `dp_ctrl.c`: Determines when `DP_TRAIN_MAX_SWING_REACHED` is signaled to the sink
- `dp_link.c`: Clamps voltage swing and pre-emphasis levels; calculates `max_p_level = DP_TRAIN_LEVEL_MAX - v_level`
The DP specification defines voltage swing levels 0-3. Level 3 (1200 mV) is a valid, in-spec operating point. Some monitors and bridges legitimately require level 3 to establish a link. Capping the global maximum at 2 will break those configurations on all Qualcomm DP platforms — not just the Radxa Dragon Q6A.
**Recommendation**: This needs to be a per-bridge or per-platform quirk, not a global constant change. Options include:
1. A device tree property on the DP node specifying the max voltage swing level
2. A quirk based on the connected bridge's identity (though the RA620 is passive and has no identity)
3. A platform-specific override in the board DTS that the DP driver reads
The commit message correctly identifies the problem (RA620 doesn't complete link training at level 3) but the fix has too broad a blast radius.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 9:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 6:06 [PATCH 0/6] arm64: qcom: Enable additional hardware on Radxa Dragon Q6A Graham O'Connor
2026-05-22 6:06 ` [PATCH 1/6] soc: qcom: rpmh-rsc: Skip TCS init when RSC is managed by firmware Graham O'Connor
2026-05-25 9:16 ` Claude review: " Claude Code Review Bot
2026-05-22 6:06 ` [PATCH 2/6] firmware: qcom: scm: Allow EFI variable access on Radxa Dragon Q6A Graham O'Connor
2026-05-24 16:33 ` Dmitry Baryshkov
2026-05-25 9:16 ` Claude review: " Claude Code Review Bot
2026-05-22 6:06 ` [PATCH 3/6] drm/msm/dp: Limit voltage swing level to 2 for RA620 bridge Graham O'Connor
2026-05-22 9:28 ` Konrad Dybcio
2026-05-25 9:16 ` Claude Code Review Bot [this message]
2026-05-22 6:06 ` [PATCH 4/6] arm64: dts: qcom: qcs6490-radxa-dragon-q6a: Add regulator supplies and disable EUD Graham O'Connor
2026-05-24 16:38 ` Dmitry Baryshkov
2026-05-25 9:16 ` Claude review: " Claude Code Review Bot
2026-05-22 6:06 ` [PATCH 5/6] arm64: dts: qcom: qcs6490-radxa-dragon-q6a: Enable GPU and display pipeline Graham O'Connor
2026-05-22 6:44 ` Neil Armstrong
2026-05-25 9:16 ` Claude review: " Claude Code Review Bot
2026-05-22 6:06 ` [PATCH 6/6] arm64: dts: qcom: qcs6490-radxa-dragon-q6a: Enable USB3 SuperSpeed Graham O'Connor
2026-05-22 6:44 ` Neil Armstrong
2026-05-25 9:16 ` Claude review: " Claude Code Review Bot
2026-05-22 10:13 ` [PATCH 0/6] arm64: qcom: Enable additional hardware on Radxa Dragon Q6A Graham O'Connor
2026-05-24 1:58 ` Xilin Wu
2026-05-25 9:16 ` 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-patch3-7e435e8c-ba0e-453a-b95c-450446dfc0ff@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