From: Andrew Lunn <andrew@lunn.ch>
To: Yongzhao Chen <yongzhao.derek@gmail.com>
Cc: netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: qca83xx: read resolved QCA8337 link status
Date: Wed, 30 Sep 2026 23:33:25 +0200 [thread overview]
Message-ID: <2ea832eb-33f4-4bf3-bdba-5d983038d012@lunn.ch> (raw)
In-Reply-To: <20260930212348.1919-1-yongzhao.derek@gmail.com>
> Separately, I have not yet reproduced on hardware the case this patch
> targets, a QCA8337-side SmartSpeed downshift where the old code reports
> the wrong speed; so far that difference is only shown by the model test.
> With a two-pair cable, the link partner advertised gigabit and then
> withdrew it, and the link came up at 100 Mb/s without the QCA8337
> downshift status set.
>
> If you know of a link partner or setup that reliably makes the QCA8337
> side downshift, I would be glad to test with it.
Sorry, i've never used this hardware.
One thing you can try is to set the link partner to only advertise 1G,
not the lower speeds. I've no idea what it will do then, but you might
get into the situation you are interested in.
Andrew
next prev parent reply other threads:[~2026-09-30 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 22:07 Yongzhao Chen
2026-09-29 0:40 ` Andrew Lunn
2026-09-30 21:23 ` Yongzhao Chen
2026-09-30 21:33 ` Andrew Lunn [this message]
2026-10-01 18:16 ` Yongzhao Chen
2026-10-01 18:46 ` Andrew Lunn
2026-10-02 20:35 ` Yongzhao Chen
2026-10-03 14:38 ` Andrew Lunn
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=2ea832eb-33f4-4bf3-bdba-5d983038d012@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yongzhao.derek@gmail.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®