From: Burke Cates <burke.cates@gmail.com>
To: Wesley Cheng <wesley.cheng@oss.qualcomm.com>,
Vinod Koul <vkoul@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Ritesh Kumar <ritesh.kumar@oss.qualcomm.com>,
Nabige Aala <nabige.aala@oss.qualcomm.com>,
Mahadevan P <mahadevan.p@oss.qualcomm.com>,
linux-phy@lists.infradead.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: phy: qcom: qmp-combo: Glymur USB Gen2 fails on one port (chip rev 2.0)
Date: Tue, 27 Oct 2026 00:08:41 -0700 [thread overview]
Message-ID: <4934834b-41ab-4663-b031-d04d736e9fe8@gmail.com> (raw)
In-Reply-To: <5b31ea48-7918-4f0b-b012-6915b384b922@gmail.com>
On 26/10/2026 23:40, Burke Cates wrote:
> These tests used v7.3-rc5 with out-of-tree Glymur platform/board
> patches, including DP PHY support. They were not on an unmodified
> mainline kernel.
The end of my message was cut off when I pasted it. It should have
continued:
AI coding assistants helped with the bring-up and this report. The
logs and test results above are from the recorded hardware tests.
Thanks,
Burke
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-27 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 6:40 phy: qcom: qmp-combo: Glymur USB Gen2 fails on one port (chip rev 2.0) Burke Cates
2026-10-27 7:08 ` Burke Cates [this message]
2026-10-27 11:07 ` Konrad Dybcio
2026-10-27 23:55 ` Burke Cates
2026-10-28 12:22 ` Konrad Dybcio
2026-10-28 15:23 ` Burke Cates
2026-10-28 15:25 ` Konrad Dybcio
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=4934834b-41ab-4663-b031-d04d736e9fe8@gmail.com \
--to=burke.cates@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mahadevan.p@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=nabige.aala@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=ritesh.kumar@oss.qualcomm.com \
--cc=vkoul@kernel.org \
--cc=wesley.cheng@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.