From: Andrew Lunn <andrew@lunn.ch>
To: Tristram.Ha@microchip.com
Cc: maxime.chevallier@bootlin.com, olteanv@gmail.com,
Woojung.Huh@microchip.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: microchip: Add SGMII port support to KSZ9477 switch
Date: Fri, 17 Jan 2025 14:36:13 +0100 [thread overview]
Message-ID: <91b52099-20de-4b6e-8b05-661e598a3ef3@lunn.ch> (raw)
In-Reply-To: <DM3PR11MB87361CADB3A3A26772B11EEEEC1B2@DM3PR11MB8736.namprd11.prod.outlook.com>
> The KSZ9477 SGMII module does use DesignWare IP, but its implementation
> is probably too old as some registers do not match.
Is there a revision value somewhere in the registers? Maybe the lower
nibble of ID registers 2 and 3?
> When using XPCS
> driver link detection works but the SGMII port does not pass traffic for
> some SFPs. It is probably doable to update the XPCS driver to work in
> KSZ9477, but there is no way to submit that patch as that may affect
> other hardware implementation.
We have PHY drivers which change their behaviour based on the
revision. So it is possible. And XPCS is used quite a bit, so i don't
think it will be an issue finding somebody to do some regression
testing.
Using a PCS driver is the correct way to go here. So either you need
to copy/paste/edit the XPCS driver to create a version specific for
you hardware, or you need to extend the XPCS driver so it supports
your hardware.
Andrew
next prev parent reply other threads:[~2025-01-17 13:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 2:47 Tristram.Ha
2025-01-14 16:09 ` Vladimir Oltean
2025-01-14 16:53 ` Vladimir Oltean
2025-01-15 10:10 ` Maxime Chevallier
2025-01-17 0:56 ` Tristram.Ha
2025-01-17 13:36 ` Andrew Lunn [this message]
2025-01-18 0:59 ` Tristram.Ha
2025-01-18 1:26 ` Vladimir Oltean
2025-01-18 4:07 ` Tristram.Ha
2025-01-18 20:00 ` Andrew Lunn
2025-01-21 0:28 ` Tristram.Ha
2025-01-21 3:08 ` Tristram.Ha
2025-01-17 16:18 ` Vladimir Oltean
2025-01-17 0:51 ` Tristram.Ha
2025-05-07 0:09 Tristram.Ha
2025-05-07 7:44 ` Maxime Chevallier
2025-05-07 8:31 ` Russell King (Oracle)
2025-05-07 8:54 ` Maxime Chevallier
2025-05-08 1:41 ` Tristram.Ha
2025-05-10 0:41 ` Jakub Kicinski
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=91b52099-20de-4b6e-8b05-661e598a3ef3@lunn.ch \
--to=andrew@lunn.ch \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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®