From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: arm64: qcom: Enable additional hardware on Radxa Dragon Q6A
Date: Mon, 25 May 2026 19:16:36 +1000 [thread overview]
Message-ID: <review-overall-20260522060645.4399-1-graham.oconnor@gmail.com> (raw)
In-Reply-To: <20260522060645.4399-1-graham.oconnor@gmail.com>
Overall Series Review
Subject: arm64: qcom: Enable additional hardware on Radxa Dragon Q6A
Author: Graham O'Connor <graham.oconnor@gmail.com>
Patches: 14
Reviewed: 2026-05-25T19:16:36.146330
---
This is a 6-patch series enabling additional hardware on the Radxa Dragon Q6A (QCS6490) when booting via UEFI. The series covers RSC firmware coexistence, EFI variable access, DP link training, and DTS additions for GPU/display/USB3.
The DTS patches (4-6) are generally well-structured and demonstrate real hardware testing. However, there are two significant issues:
1. **Patch 3 (DP_TRAIN_LEVEL_MAX)** changes a global constant affecting *all* MSM DP connections, not just the RA620 bridge. This will regress other platforms that require voltage swing level 3. This needs to be reworked as a per-bridge or per-platform quirk.
2. **Patch 1 (rpmh-rsc)** early-returns from probe, skipping critical initialization including `devm_of_platform_populate()`, IRQ setup, and client cache initialization. Child devices won't probe, and the `rsc_drv` structure left in driver data is only partially initialized, risking use of uninitialized fields if any code later references it.
The DTS display pipeline modeling in patch 5 uses `dp-connector` to represent what is described as a bridge, which is semantically questionable and misuses port@1 of the binding.
---
---
Generated by Claude Code Patch Reviewer
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 review: " Claude Code Review Bot
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 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-20260522060645.4399-1-graham.oconnor@gmail.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