From: Xilin Wu <sophon@radxa.com>
To: Graham O'Connor <graham.oconnor@gmail.com>,
linux-arm-msm@vger.kernel.org
Cc: andersson@kernel.org, konradybcio@kernel.org,
robin.clark@oss.qualcomm.com, lumag@kernel.org,
abhinav.kumar@linux.dev, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
neil.armstrong@linaro.org
Subject: Re: [PATCH 0/6] arm64: qcom: Enable additional hardware on Radxa Dragon Q6A
Date: Sun, 24 May 2026 09:58:23 +0800 [thread overview]
Message-ID: <15015D7EB84640D6+cc21a9f7-ae1b-4a22-bb38-34d6fafe1bcb@radxa.com> (raw)
In-Reply-To: <20260522101323.31911-1-graham.oconnor@gmail.com>
On 5/22/2026 6:13 PM, Graham O'Connor wrote:
> Thank you to Konrad, Neil, and others for the very prompt and helpful reviews.
>
> Based on the feedback received, I think it best to withdraw this series to
> address the issues raised, most notobly:
>
> 1. The DP_TRAIN_LEVEL_MAX change (patch 3) is too broad - it affects all
> devices using the Qualcomm MSM DP driver rather than being specific to
> the RA620 bridge. A proper fix should be implemented at the bridge
> level. This is going to take more investigation.
>
> 2. The display DT nodes (patch 5) should use the radxa,ra620 compatible
> string per the existing Radxa upstream series from Xilin Wu, and the
> lane ordering needs correcting.
>
> 3. The rpmh-rsc early return (patch 1) needs further review regarding
> the implications of returning before full driver initialization.
>
> 4. DTS patch label dependency issue (sorry)
>
> I'll integrate with the Radxa upstream effort, re-evaluate the other areas
> and resubmit corrected patches addressing these concerns at a later date.
>
> Thanks for the feedback.
>
> Cheers
>
> Graham
Hi Graham,
Thanks for working on the additional hardware bring-up for Q6A upstream
support. I'm really glad to see someone pushing this forward.
I actually posted a patch series [1] last month, and it is generally in
good shape. Unfortunately, I got busy with other work and haven't had a
chance to send v2 yet.
If it helps, please feel free to take over that series and fold your
additional patches into it. I think that would be a good way to move
things forward.
Also, I believe patches 10-12 in my series are no longer needed and can
be dropped.
Thank you again for the work you have done.
[1]
https://patchwork.kernel.org/project/linux-arm-msm/list/?series=1078242&state=%2A&archive=both
--
Best regards,
Xilin Wu <sophon@radxa.com>
next prev parent reply other threads:[~2026-05-24 2:07 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 [this message]
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=15015D7EB84640D6+cc21a9f7-ae1b-4a22-bb38-34d6fafe1bcb@radxa.com \
--to=sophon@radxa.com \
--cc=abhinav.kumar@linux.dev \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=graham.oconnor@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=robin.clark@oss.qualcomm.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