From: Tapio Reijonen <tapio.reijonen@vaisala.com>
To: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Tristram Ha <tristram.ha@microchip.com>,
Nicolai Buchwitz <nb@tipi-net.de>,
Jerry Ray <Jerry.Ray@microchip.com>
Subject: Re: [PATCH net-next v3] net: dsa: microchip: enable the SGMII port of the KSZ9897S
Date: Tue, 1 Sep 2026 10:27:57 +0300 [thread overview]
Message-ID: <e2feeb88-8e4d-4b00-93db-2305a59b77ce@vaisala.com> (raw)
In-Reply-To: <20260831-ksz9897-sgmii-port-v3-1-2376aa4edf11@vaisala.com>
On 8/31/26 08:10, Tapio Reijonen wrote:
> The variants do differ in the read-only bit 7 of the port 7 XMII control
> 0 register, which reads one on the KSZ9897S and zero on the KSZ9897R.
Microchip support have now confirmed this with their internal team:
register 0x7300 reads 0xF8 on the KSZ9897S and 0x78 on the KSZ9897R.
The two values differ in bit 7 only, which is the bit this patch tests.
That closes the one gap in my testing. I have no KSZ9897R sample, so the
"this does not break the R" half was reasoned from the two data sheets
and the driver code; it is now confirmed by the vendor.
Tapio
next prev parent reply other threads:[~2026-09-01 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:10 Tapio Reijonen
2026-09-01 7:27 ` Tapio Reijonen [this message]
2026-09-02 17:11 ` [net-next,v3] " netdev-bot+sashiko
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=e2feeb88-8e4d-4b00-93db-2305a59b77ce@vaisala.com \
--to=tapio.reijonen@vaisala.com \
--cc=Jerry.Ray@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=tristram.ha@microchip.com \
--cc=woojung.huh@microchip.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®