netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Bhaskar Upadhaya <Bhaskar.Upadhaya@nxp.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] phy: Add 2.5G SGMII interface mode
Date: Thu, 30 Nov 2017 17:33:50 +0000	[thread overview]
Message-ID: <20171130173350.GE10595@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20171130155050.GD7483@lunn.ch>

On Thu, Nov 30, 2017 at 04:50:50PM +0100, Andrew Lunn wrote:
> On Thu, Nov 30, 2017 at 10:00:35AM +0530, Bhaskar Upadhaya wrote:
> > Add 2.5G SGMII interface mode(PHY_INTERFACE_MODE_2500SGMII)
> > in existing phy_interface list.As auto-negotiation is not
> > supported for 2.5G SGMII
> 
> Hi Bhaskar
> 
> I've been thinking about this some more...
> 
> Is auto negotiation not supported in 2.5G SGMII in general, or just in
> the system you are using? Is it the PHY or the MAC which does not
> support it. Are we going to get into trouble if we find an 2.5G SGMII
> link which does negotiate?

I've been doing some research on this 2.5G SGMII "thing", and what
I've found so far (from Xilinx, I haven't been able to look through
anything else yet) is that at least Xilinx do the same thing.

There's a Xilinx document (pg047-gig-eth-pcs-pma.pdf) which says
throughout that the speed bits are not applicable for 2.5G SGMII.

Speeds > 1G appear to be defined only for full duplex (since the
latency through the PHY is too great for CDMA half-duplex to work.)
So, the duplex bits in SGMII would be meaningless for >1G.  Many
MACs, incidentally, do not support half-duplex at 1G speeds either.

That just leaves pause mode in the SGMII word.

> My understanding is that one of the main differences between SGMII and
> 1000BASE-X is the negotiation.

True.  1000BASE-X is an 802.3 standard, with the configuration word
defined by IEEE.  SGMII is derived from that by Cisco, but with the
configuration word replaced by a system whereby the PHY can inform
the MAC about the results of negotiation.

SGMII has a handshake so the PHY knows that the MAC has configured
itself, and some PHYs will not pass data until that handshake has
completed.

I suspect for 2.5G SGMII, I would expect that the handshake also has
to complete, so the PHY knows that the pause modes have been properly
received by the MAC.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

      parent reply	other threads:[~2017-11-30 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  4:30 [PATCH 1/1] phy: Add 2.5G SGMII interface mode Bhaskar Upadhaya
2017-11-30 15:50 ` Andrew Lunn
2017-11-30 17:16   ` Bhaskar Upadhaya
2017-11-30 17:34     ` David Miller
2017-11-30 17:41     ` Andrew Lunn
2017-11-30 18:15       ` Russell King - ARM Linux
2017-11-30 18:26         ` Andrew Lunn
2017-11-30 18:53           ` Russell King - ARM Linux
2017-12-01 18:40             ` Bhaskar Upadhaya
2017-12-01 18:44               ` Florian Fainelli
2017-12-01 19:12               ` Andrew Lunn
2017-11-30 17:33   ` Russell King - ARM Linux [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=20171130173350.GE10595@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=Bhaskar.Upadhaya@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).