[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8ad501e1-a56c-48d5-bafb-125bc1099b7b@lunn.ch>
Date: Sat, 18 Jan 2025 21:00:46 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Tristram.Ha@...rochip.com
Cc: olteanv@...il.com, maxime.chevallier@...tlin.com,
Woojung.Huh@...rochip.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, UNGLinuxDriver@...rochip.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: microchip: Add SGMII port support
to KSZ9477 switch
> 0x1f8001 needs to be written 0x18 in 1000BaseX mode, but the XPCS driver
> does not do anything, and bit 4 is not defined in the driver.
Does the Synopsis data book describe this bit, for the version of the
IP you have? Is it described in later version?
> The driver enables interrupt in 1000BaseX mode when poll is not set, but
> it does not do that in SGMII Mode. In KSZ9477 SGMII mode can trigger
> both link up and link down interrupt, but 1000BaseX mode can only trigger
> link up interrupt. It requires polling to detect link down.
I don't know this driver, but a quick look suggest TXGBE requires
polling. It should be easy to piggy back on that and have KSZ9477
always poll. Just because the hardware can do interrupts does not mean
you actually need to use it. My experience is you are more interested
in fast link down notification, so you can trigger routing protocols
to find an alternative route. You are less interested in fast link up.
Andrew
Powered by blists - more mailing lists