net: enable inband link state negotiation only when explicitly requested
Subsystems (7)
v3 cover net: enable inband link state negotiation only when explicitly requested
Hello.
Currently the link status auto-negotiation is enabled for any SGMII link with fixed-link DT binding.
The regression was reported:
https://lkml.org/lkml/2015/7/8/865
Apparently not all HW that implements SGMII protocol, generates the inband status for the auto-negotiation to work.
More details here:
https://lkml.org/lkml/2015/7/10/206
The following patches reverts to the old behavior by default, which is to not enable the auto-negotiation for fixed-link. The new DT property is added that allows to explicitly request the auto-negotiation.
Those who were affected by the change, please send your Tested-by, Thanks!
PATCH v3 1/3 fixed_phy: handle link-down case
Currently fixed_phy driver recognizes only the link-up state. This simple patch adds an implementation of link-down state. It fixes the status registers when link is down, and also allows to register the fixed-phy with link down without specifying the speed.
--- drivers/net/phy/fixed_phy.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/net/phy/fixed_phy.c +5 -3
@@ -52,6 +52,10 @@ static int fixed_phy_update_regs(struct fixed_phy *fp)u16 lpagb =0 ;u16 lpa =0 ; +if (!fp->status.link) + goto done; + bmsr |=BMSR_LSTATUS |BMSR_ANEGCOMPLETE ; +if (fp->status.duplex) { bmcr |=BMCR_FULLDPLX ;
@@ -96,15 +100,13 @@ static int fixed_phy_update_regs(struct fixed_phy *fp) } } -if (fp->status.link) - bmsr |=BMSR_LSTATUS |BMSR_ANEGCOMPLETE ; -if (fp->status.pause) lpa |=LPA_PAUSE_CAP ;if (fp->status.asym_pause) lpa |=LPA_PAUSE_ASYM ; +done: fp->regs[MII_PHYSID1 ] =0 ; fp->regs[MII_PHYSID2 ] =0 ;
Signature · 1 line
1.9.1
PATCH v3 2/3 of_mdio: add new DT property 'managed' to specify the PHY management type
In reply to Stas SergeevCurrently the PHY management type is selected by the MAC driver arbitrary. The decision is based on the presence of the "fixed-link" node and on a will of the driver's authors.
This caused a regression recently, when mvneta driver suddenly started to use the in-band status for auto-negotiation on fixed links.
It appears the auto-negotiation may not work when expected by the MAC driver. Sebastien Rannou explains:
<< Yes, I confirm that my HW does not generate an in-band status. AFAIK, it's a PHY that aggregates 4xSGMIIs to 1xQSGMII ; the MAC side of the PHY (with inband status) is connected to the switch through QSGMII, and in this context we are on the media side of the PHY. >>
https://lkml.org/lkml/2015/7/10/206
This patch introduces the new string property 'managed' that allows the user to set the management type explicitly.
The supported values are:
"auto" - default. Uses either MDIO or nothing, depending on the presence of the fixed-link node
"mdio" - use MDIO
"in-band-status" - use in-band status
"none" - use fixed-link description
--- Documentation/devicetree/bindings/net/ethernet.txt | 5 ++++ drivers/of/of_mdio.c | 28 ++++++++++++++++++++-- 2 files changed, 31 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/net/ethernet.txt +5 -0
@@ -19,7 +19,12 @@ The following properties are common to the Ethernet controllers: - phy: the same as "phy-handle" property, not recommended for new bindings. - phy-device: the same as "phy-handle" property, not recommended for new bindings. +- managed: string, specifies the PHY management type. Supported values are: + "auto", "mdio", "in-band-status", "none". "auto" is the default, and it + sets the management type to either "mdio" or "none", depending on the + presence of the "fixed-link" child node. Child nodes of the Ethernet controller are typically the individual PHY devices connected via the MDIO bus (sometimes the MDIO bus controller is separate). They are described in the phy.txt file in this same directory. +For non-MDIO PHY management see fixed-link.txt.
drivers/of/of_mdio.c +26 -2
@@ -262,7 +262,16 @@ EXPORT_SYMBOL(of_phy_attach);bool of_phy_is_fixed_link (struct device_node *np) {struct device_node *dn; -int len; +int len, m_err; +const char *managed; + + m_err =of_property_read_string (np,"managed" , &managed); +if (m_err ==0 ) { +if (strcmp (managed,"none" ) ==0 ) +return true; +if (strcmp (managed,"mdio" ) ==0 ) +return false; + }/* New binding */ dn =of_get_child_by_name (np,"fixed-link" );
@@ -271,6 +280,9 @@ bool of_phy_is_fixed_link(struct device_node *np)return true; } +if (m_err ==0 &&strcmp (managed,"auto" ) !=0 ) +return true; +/* Old binding */ if (of_get_property (np,"fixed-link" , &len) && len == (5 *sizeof (__be32)))
@@ -285,8 +297,20 @@ int of_phy_register_fixed_link(struct device_node *np)struct fixed_phy_status status = {};struct device_node *fixed_link_node;const __be32 *fixed_link_prop; -int len; +int len, err;struct phy_device *phy; +const char *managed; + + err =of_property_read_string (np,"managed" , &managed); +if (err ==0 ) { +if (strcmp (managed,"mdio" ) ==0 ) +return -EINVAL ; +if (strcmp (managed,"in-band-status" ) ==0 ) { + status.link =0 ; + phy =fixed_phy_register (PHY_POLL , &status, np); +return IS_ERR (phy) ?PTR_ERR (phy) :0 ; + } + }/* New binding */ fixed_link_node =of_get_child_by_name (np,"fixed-link" );
Signature · 1 line
1.9.1
PATCH v3 3/3 mvneta: use inband status only when explicitly enabled
In reply to Stas SergeevThe commit 898b2970e2c9 ("mvneta: implement SGMII-based in-band link state signaling") implemented the link parameters auto-negotiation unconditionally. Unfortunately it appears that some HW that implements SGMII protocol, doesn't generate the inband status, so it is not possible to auto-negotiate anything with such HW.
This patch enables the auto-negotiation only if explicitly requested with the 'managed' DT property.
This patch fixes the following regression:
https://lkml.org/lkml/2015/7/8/865
and is therefore CCed to stable.
--- drivers/net/ethernet/marvell/mvneta.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/net/ethernet/marvell/mvneta.c +5 -4
@@ -3008,8 +3008,8 @@ static int mvneta_probe(struct platform_device *pdev)const char *dt_mac_addr;char hw_mac_addr[ETH_ALEN ];const char *mac_from; +const char *managed;int phy_mode; -int fixed_phy =0 ;int err;/* Our multiqueue support is not complete, so for now, only
@@ -3043,7 +3043,6 @@ static int mvneta_probe(struct platform_device *pdev)dev_err (&pdev->dev,"cannot register fixed PHY\n" ); goto err_free_irq; } - fixed_phy =1 ;/* In the case of a fixed PHY, the DT node associated * to the PHY is the Ethernet MAC DT node.
@@ -3067,8 +3066,10 @@ static int mvneta_probe(struct platform_device *pdev) pp =netdev_priv (dev); pp->phy_node = phy_node; pp->phy_interface = phy_mode; - pp->use_inband_status = (phy_mode ==PHY_INTERFACE_MODE_SGMII ) && - fixed_phy; + + err =of_property_read_string (dn,"managed" , &managed); + pp->use_inband_status = (err ==0 && +strcmp (managed,"in-band-status" ) ==0 ); pp->clk =devm_clk_get (&pdev->dev,NULL );if (IS_ERR (pp->clk)) {
Signature · 1 line
1.9.1
Re: [PATCH 2/3] of_mdio: add new DT property 'managed' to specify the PHY management type
In reply to Stas SergeevQuoted 14 lines · Stas Sergeev
Currently the PHY management type is selected by the MAC driver arbitrary. The decision is based on the presence of the "fixed-link" node and on a will of the driver's authors.
This caused a regression recently, when mvneta driver suddenly started to use the in-band status for auto-negotiation on fixed links.
It appears the auto-negotiation may not work when expected by the MAC driver. Sebastien Rannou explains:
<< Yes, I confirm that my HW does not generate an in-band status. AFAIK, it's a PHY that aggregates 4xSGMIIs to 1xQSGMII ; the MAC side of the PHY (with inband status) is connected to the switch through QSGMII, and in this context we are on the media side of the PHY. >>
https://lkml.org/lkml/2015/7/10/206
Quoted 8 lines
This patch introduces the new string property 'managed' that allows the user to set the management type explicitly.
The supported values are:
"auto" - default. Uses either MDIO or nothing, depending on the presence of the fixed-link node
"mdio" - use MDIO
"in-band-status" - use in-band status
"none" - use fixed-link description
I thought we agreed in the last thread that "mdio" was implied whenever a proper PHY phandle to a device sitting on MDIO bus is used and that "auto" did not make much sense unless we were also describing how to do this auto-negotiation completely?
The way I see it, the only thing that is needed at this point is an "in-band-status" property which you rightfully placed at the Ethernet MAC DT node level, this is fine, however, I disagree with how the values are enforced, see below:
Quoted 23 lines
Signed-off-by Stas Sergeev <[email protected]>CC Rob Herring <[email protected]>CC Pawel Moll <[email protected]>CC Mark Rutland <[email protected]>CC Ian Campbell <[email protected]>CC Kumar Gala <[email protected]>CC Florian Fainelli <[email protected]>CC Grant Likely <[email protected]>--- Documentation/devicetree/bindings/net/ethernet.txt | 5 ++++ drivers/of/of_mdio.c | 28 ++++++++++++++++++++-- 2 files changed, 31 insertions(+), 2 deletions(-)Documentation/devicetree/bindings/net/ethernet.txt +0
-0
Documentation/devicetree/bindings/net/ethernet.txt The following properties are common to the Ethernet controllers: · line 25
Quoted 7 lines
Documentation/devicetree/bindings/net/ethernet.txt +4
-0@@ -19,7 +19,12 @@ The following properties are common to the Ethernet controllers: - phy: the same as "phy-handle" property, not recommended for new bindings. - phy-device: the same as "phy-handle" property, not recommended for new bindings. +- managed: string, specifies the PHY management type. Supported values are: + "auto", "mdio", "in-band-status", "none". "auto" is the default, and it + sets the management type to either "mdio" or "none", depending on the + presence of the "fixed-link" child node.
As mentioned below, "mdio" is redundant with finding a "phy-handle", and "auto" is not specific enough to be useful to a consumer of this information.
Quoted 14 lines
Documentation/devicetree/bindings/net/ethernet.txt +1
-0Child nodes of the Ethernet controller are typically the individual PHY devices connected via the MDIO bus (sometimes the MDIO bus controller is separate). They are described in the phy.txt file in this same directory. +For non-MDIO PHY management see fixed-link.txt.drivers/of/of_mdio.c +0
-1@@ -262,7 +262,16 @@ EXPORT_SYMBOL(of_phy_attach);bool of_phy_is_fixed_link (struct device_node *np) {struct device_node *dn; -int len;
drivers/of/of_mdio.c EXPORT_SYMBOL(of_phy_attach); · line 274
Quoted 10 lines
drivers/of/of_mdio.c +10
-0+int len, m_err; +const char *managed; + + m_err =of_property_read_string (np,"managed" , &managed); +if (m_err ==0 ) { +if (strcmp (managed,"none" ) ==0 ) +return true; +if (strcmp (managed,"mdio" ) ==0 ) +return false; + }
managed = "mdio" on a fixed link is by definition not something remotely correct, there should be a proper PHY driver for this, and therefore a different representation: a PHY phandle to a PHY node on a MDIO bus. I do not think enforcing this has been incorrect provides much value, since you ought to write correct DT in the first place.
Quoted 21 lines
drivers/of/of_mdio.c +5
-1/* New binding */ dn =of_get_child_by_name (np,"fixed-link" );@@ -271,6 +280,9 @@ bool of_phy_is_fixed_link(struct device_node *np)return true; } +if (m_err ==0 &&strcmp (managed,"auto" ) !=0 ) +return true; +/* Old binding */ if (of_get_property (np,"fixed-link" , &len) && len == (5 *sizeof (__be32)))@@ -285,8 +297,20 @@ int of_phy_register_fixed_link(struct device_node *np)struct fixed_phy_status status = {};struct device_node *fixed_link_node;const __be32 *fixed_link_prop; -int len; +int len, err;struct phy_device *phy; +const char *managed;
drivers/of/of_mdio.c int of_phy_register_fixed_link(struct device_node *np) · line 312
Quoted 10 lines
drivers/of/of_mdio.c +10
-0+ + err =of_property_read_string (np,"managed" , &managed); +if (err ==0 ) { +if (strcmp (managed,"mdio" ) ==0 ) +return -EINVAL ; +if (strcmp (managed,"in-band-status" ) ==0 ) { + status.link =0 ; + phy =fixed_phy_register (PHY_POLL , &status, np); +return IS_ERR (phy) ?PTR_ERR (phy) :0 ; + }
And that is the only hunk of this patch that is really needed and useful to solving the problem here.
Signature · 5 lines
Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/3] fixed_phy: handle link-down case
In reply to Stas SergeevQuoted 7 lines · Stas Sergeev
Currently
fixed_phydriver recognizes only the link-up state. This simple patch adds an implementation of link-down state. It fixes the status registers when link is down, and also allows to register the fixed-phy with link down without specifying the speed.Signed-off-by Stas Sergeev <[email protected]>
This does not quite seem to work for me here on two different setups that use fixed PHYs:
Before patch link up:
# ethtool moca
Settings for moca:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes: 1000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Speed: 1000Mb/s
Duplex: Full
Port: BNC
PHYAD: 2
Transceiver: external
Auto-negotiation: on
Supports Wake-on: gs
Wake-on: d
SecureOn password: 00:00:00:00:00:00
Link detected: yes
#Before patch link down:
# ethtool moca
Settings for moca:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 1000Mb/s
Duplex: Full
Port: BNC
PHYAD: 2
Transceiver: external
Auto-negotiation: off
Supports Wake-on: gs
Wake-on: d
SecureOn password: 00:00:00:00:00:00
Link detected: no
#After patch link up:
# ethtool moca
Settings for moca:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Speed: 10Mb/s <---- this is not quite the speed we want
Duplex: Full
Port: BNC
PHYAD: 2
Transceiver: external
Auto-negotiation: on
Supports Wake-on: gs
Wake-on: d
SecureOn password: 00:00:00:00:00:00
Link detected: yes
#After patch link down:
# ethtool moca
Settings for moca:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: BNC
PHYAD: 2
Transceiver: external
Auto-negotiation: off
Supports Wake-on: gs
Wake-on: d
SecureOn password: 00:00:00:00:00:00
Link detected: no
#Does it behave properly for you?
Quoted 40 lines
--- drivers/net/phy/fixed_phy.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)drivers/net/phy/fixed_phy.c +5
-3@@ -52,6 +52,10 @@ static int fixed_phy_update_regs(struct fixed_phy *fp)u16 lpagb =0 ;u16 lpa =0 ; +if (!fp->status.link) + goto done; + bmsr |=BMSR_LSTATUS |BMSR_ANEGCOMPLETE ; +if (fp->status.duplex) { bmcr |=BMCR_FULLDPLX ;@@ -96,15 +100,13 @@ static int fixed_phy_update_regs(struct fixed_phy *fp) } } -if (fp->status.link) - bmsr |=BMSR_LSTATUS |BMSR_ANEGCOMPLETE ; -if (fp->status.pause) lpa |=LPA_PAUSE_CAP ;if (fp->status.asym_pause) lpa |=LPA_PAUSE_ASYM ; +done: fp->regs[MII_PHYSID1 ] =0 ; fp->regs[MII_PHYSID2 ] =0 ;
Signature · 1 line
Florian
Re: [PATCH 2/3] of_mdio: add new DT property 'managed' to specify the PHY management type
In reply to Florian Fainelli14.07.2015 20:51, Florian Fainelli пишет:
Quoted 22 lines · Stas Sergeev
Quoted 13 lines
Currently the PHY management type is selected by the MAC driver arbitrary. The decision is based on the presence of the "fixed-link" node and on a will of the driver's authors.
This caused a regression recently, when mvneta driver suddenly started to use the in-band status for auto-negotiation on fixed links.
It appears the auto-negotiation may not work when expected by the MAC driver. Sebastien Rannou explains:
<< Yes, I confirm that my HW does not generate an in-band status. AFAIK, it's a PHY that aggregates 4xSGMIIs to 1xQSGMII ; the MAC side of the PHY (with inband status) is connected to the switch through QSGMII, and in this context we are on the media side of the PHY. >>
https://lkml.org/lkml/2015/7/10/206Quoted 8 lines
This patch introduces the new string property 'managed' that allows the user to set the management type explicitly.
The supported values are:
"auto" - default. Uses either MDIO or nothing, depending on the presence of the fixed-link node
"mdio" - use MDIO
"in-band-status" - use in-band status
"none" - use fixed-link description
Quoted 4 lines
I thought we agreed in the last thread that "mdio" was implied whenever a proper PHY phandle to a device sitting on MDIO bus is used and that "auto" did not make much sense unless we were also describing how to do this auto-negotiation completely?
Exactly not:
---
Quoted 3 lines
If we would implement autoneg outside of the fixed-link, then its semantic would likely be
autoneg = "mdio" | "in-band" | "off"
Right, if auto-negotiation was defined outside of fixed-link, that is indeed how I would also specify this.
---
That's why I implemented it the way you see.
But as you changed your mind, I'll remove "mdio".
Quoted 1 line
As mentioned below, "mdio" is redundant with finding a "phy-handle", and "auto" is not specific enough to be useful to a consumer of this information.
I prefer to keep "auto", as otherwise we'll have the default value (when the option is not specified) never achievable when the option _is_ specified, which is probably not very good. But I can remove "none" instead, leaving only "in-band-status" and "auto". Ok?
Of course one can propose to completely ignore that option in presence of MDIO, but I wonder why not to allow for example to opt for in-band status even if you have MDIO? So if we want this option to play nicely with MDIO, as opposed to being entirely overridden, then "auto" still makes sense IMO.
Re: Fwd: Re: [PATCH 1/3] fixed_phy: handle link-down case
In reply to a message not in the archiveFlorian Fainelli <[email protected]> :
Quoted 2 lines
Does it behave properly for you?
Yes, I've just checked and can't reproduce the problem you mentioned. And I can't think of the possible reason:fixed_phy.c keeps the private copy of the status, which should have link speed kept unchanged, and used as long as link is up again.
Could you please help with this?