mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yongzhao Chen <yongzhao.derek@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
	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: Fri,  2 Oct 2026 22:35:22 +0200	[thread overview]
Message-ID: <20261002203522.1219-1-yongzhao.derek@gmail.com> (raw)
In-Reply-To: <7eed302b-d455-447f-9ce9-f15468b9792b@lunn.ch>

Hi Andrew,

> The traffic failure was however because of the error with setting the
> DACs?

No, sorry, my last mail was not clear about this. The failure was on
a QCA8337 user port connected to a NAS, not on the IPQ5018 CPU link
from the DAC investigation. With the same OpenWrt 6.18.52 diagnostic
image and unchanged DAC settings, switching only that user PHY's
read_status changed the MAC speed from an incorrect 1000 Mb/s to the
actual 100 Mb/s and restored ping in both directions.

> Reporting the correct downshift has nothing to do with that, as far as
> i understand. Correctly reporting downshift i would put to net-next.

If net-next is still your preference with that in mind, I will send
v2 there.

Thanks,
Yongzhao Chen

      reply	other threads:[~2026-10-02 20:35 UTC|newest]

Thread overview: 7+ 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
2026-10-01 18:16       ` Yongzhao Chen
2026-10-01 18:46         ` Andrew Lunn
2026-10-02 20:35           ` Yongzhao Chen [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=20261002203522.1219-1-yongzhao.derek@gmail.com \
    --to=yongzhao.derek@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --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 \
    /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®