From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Burke Cates <burke.cates@gmail.com>,
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>,
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: Wed, 28 Oct 2026 13:22:13 +0100 [thread overview]
Message-ID: <80fad9c9-4a90-447e-96cb-b1fb0ed98a36@oss.qualcomm.com> (raw)
In-Reply-To: <830ef909-d0d9-4f4f-8b73-0fc0cb7b46eb@gmail.com>
On 10/28/26 12:55 AM, Burke Cates wrote:
> On 27/10/2026 04:07, Konrad Dybcio wrote:
>> Please check the attached patch.
>
> Thanks, Konrad: your patch fixes C2. With it, the RTL8159 10G NIC
> enumerates at 10000M on C2 in 8 of 8 tries (both cables, both
> orientations, present at boot and hotplugged, including a hotplug
> after a cold boot with C2 empty), with no regressions on C1 or DP.
>
> I tested on the A16 (UX3607OA, SoC ID 662, revision 2.0, BIOS
> UX3607OA.312), on v7.3 plus out-of-tree Glymur platform/board patches.
> Your patch applied as-is, and I removed my local PHY changes so it
> alone programs the USB tables.
>
> - RTL8159 on C2: 10000M (SuperSpeed Plus Gen 2x1) in 8 of 8 tries,
> with both C-C cables from my report, in both orientations, present
> at boot and hotplugged. No -71 or resets during SuperSpeed
> enumeration.
> - Cold boot with C2 empty (my original failure case), then hotplug:
> 10000M in both orientations.
> - A VIA VL822 USB 3.2 Gen2 hub on C2 (a third cable) enumerates at
> 10000M, and the NIC behind it does too.
> - C2 stays at Gen2 across s2idle (no disconnect or reset on resume).
> - C1 is still Gen2 in both orientations.
> - DP alt mode on C2 still trains 4 lanes at HBR (1080p60 monitor).
> - With the NIC present at boot on C2, iperf3 to a 10G host gave
> about 4.6 Gbit/s each way (TX 4.58, RX 4.71; 4.55 + 4.56 Gbit/s
> bidirectional over 60 s). The NIC's link partner is 5GbE.
>
> Under sustained load I see about one burst of "r8152 ... Tx status
> -71" per minute, each followed by an r8152 reset of the device.
> Traffic continues and the link stays at Gen2.
Is this something you've also seen with your local changes?
Konrad
next prev parent reply other threads:[~2026-10-28 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 6:40 Burke Cates
2026-10-27 7:08 ` Burke Cates
2026-10-27 11:07 ` Konrad Dybcio
2026-10-27 23:55 ` Burke Cates
2026-10-28 12:22 ` Konrad Dybcio [this message]
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=80fad9c9-4a90-447e-96cb-b1fb0ed98a36@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=burke.cates@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®