From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: support in-band signalling with external PHY for 1000BaseX/2500BaseX
Date: Sat, 2 Mar 2019 21:45:46 +0100 [thread overview]
Message-ID: <20190302204546.GC10359@lunn.ch> (raw)
In-Reply-To: <dd84d667-ecc6-046d-00e3-9205fa8ec2bd@gmail.com>
> I briefly looked at the SFP connector and there don't seem to be pins for
> out-of-band signalling. So there must be some inband signalling.
Hi Heiner
Optical SFPs have an i2c bus with an 'EEPROM' on it. The EEPROM
contains information about the SFP, including its maximum
bit-rate. The Linux SFP driver will look at this bitrate, and pick the
link mode appropriate to it. It then calls mac_config with that link
mode, and the link speed.
The MAC then needs to configure the SERDES to that mode/speed. After a
while, it will get sync and trigger an interrupt. At is then reported
via phylink_mac_change() at which point the carrier is indicated as
up. If one end is using 1000Base-X and the other 2500Base-X, they will
fail to sync. There is no negotiation down to 1000Base-X.
Optical SFPs are pretty passive devices, they just do electrical to
optical, and not a lot more. All the 'intelligence' is in the SERDES
layers, and they talk to each other end-to-end, unlike copper, where
the MAC SERDES is talking to the PHY SERDES.
Copper SFPs are different. They use SGMII with inband signalling.
There is also a mechanism to encapsulate MDIO over i2c.
Andrew
next prev parent reply other threads:[~2019-03-02 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 15:57 [PATCH net-next] net: dsa: mv88e6xxx: support in-band signalling with external PHY for 1000BaseX/2500BaseX Heiner Kallweit
2019-03-02 20:13 ` Andrew Lunn
2019-03-02 20:34 ` Heiner Kallweit
2019-03-02 20:36 ` Heiner Kallweit
2019-03-02 20:45 ` Andrew Lunn [this message]
2019-03-02 21:03 ` Heiner Kallweit
2019-03-04 18:54 ` David Miller
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=20190302204546.GC10359@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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;
as well as URLs for NNTP newsgroup(s).