Commit 05ca1b32 authored by Russell King's avatar Russell King Committed by David S. Miller

net: phy: marvell10g: update header comments

Update header comments to indicate the newly found behaviour with XAUI
interfaces.
Signed-off-by: default avatarRussell King <rmk+kernel@armlinux.org.uk>
Reviewed-by: default avatarAndrew Lunn <andrew@lunn.ch>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 3abbcccc
...@@ -6,12 +6,18 @@ ...@@ -6,12 +6,18 @@
* *
* There appears to be several different data paths through the PHY which * There appears to be several different data paths through the PHY which
* are automatically managed by the PHY. The following has been determined * are automatically managed by the PHY. The following has been determined
* via observation and experimentation: * via observation and experimentation for a setup using single-lane Serdes:
* *
* SGMII PHYXS -- BASE-T PCS -- 10G PMA -- AN -- Copper (for <= 1G) * SGMII PHYXS -- BASE-T PCS -- 10G PMA -- AN -- Copper (for <= 1G)
* 10GBASE-KR PHYXS -- BASE-T PCS -- 10G PMA -- AN -- Copper (for 10G) * 10GBASE-KR PHYXS -- BASE-T PCS -- 10G PMA -- AN -- Copper (for 10G)
* 10GBASE-KR PHYXS -- BASE-R PCS -- Fiber * 10GBASE-KR PHYXS -- BASE-R PCS -- Fiber
* *
* With XAUI, observation shows:
*
* XAUI PHYXS -- <appropriate PCS as above>
*
* and no switching of the host interface mode occurs.
*
* If both the fiber and copper ports are connected, the first to gain * If both the fiber and copper ports are connected, the first to gain
* link takes priority and the other port is completely locked out. * link takes priority and the other port is completely locked out.
*/ */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment