diff mbox

[1/3,v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR

Message ID VI1PR04MB16645A2F24DB515D86136BE2E8C00@VI1PR04MB1664.eurprd04.prod.outlook.com (mailing list archive)
State Not Applicable
Headers show

Commit Message

shaohui xie Jan. 18, 2016, 7:23 a.m. UTC 
> > If you look at the list of possible values for "phy-mode" you'd see

> > that none of it describes a PHY-to-PHY connection but all are for

> > MAC-to-PHY connections. Also, names above suggest it already: MII is

> > short for media _independent_ interface.

> >

> > I copy Andrew's concerns and think that neither 10000base-kx nor

> > 10gbase-kr belong in the list of phy-mode properties.

> 

> I concur with that as well, if the phy connection does not really matter here,

> or does not seem like a good fit, maybe we should have a different property, or

> just define the hardware interface a little differently?

Right, 'phy-mode' is not a good fit for backplanes, how about a new property like
'backplane-mode' or something, like below:


Thank you!

Shaohui
diff mbox

Patch

--- a/Documentation/devicetree/bindings/net/phy.txt
+++ b/Documentation/devicetree/bindings/net/phy.txt
@@ -33,6 +33,9 @@  Optional Properties:
 - broken-turn-around: If set, indicates the PHY device does not correctly
   release the turn around line low at the end of a MDIO transaction.
 
+- backplane-mode: string, operation mode of the backplane PHY;
+  must be "1000base-kx" for 1000BASE-KX, or "10gbase-kr" for 10GBASE-KR.
+
 Example:
 
 ethernet-phy@0 {