Add flow control support flags to gianfar's capabilities
The phy device supports 802.3x flow control, but the specific flags are not set in the phy initialisation code. Flow control flags need to be added to the supported capabilities of the phydev by the driver. This is needed in order for ethtool to work ('ethtool -A' code checks for these flags) Signed-off-by: Pavaluca Matei <matei.pavaluca@freescale.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
2c6c49ded7
commit
cf987afc7e
|
@ -1687,6 +1687,9 @@ static int init_phy(struct net_device *dev)
|
|||
priv->phydev->supported &= (GFAR_SUPPORTED | gigabit_support);
|
||||
priv->phydev->advertising = priv->phydev->supported;
|
||||
|
||||
/* Add support for flow control, but don't advertise it by default */
|
||||
priv->phydev->supported |= (SUPPORTED_Pause | SUPPORTED_Asym_Pause);
|
||||
|
||||
return 0;
|
||||
}
|
||||
|
||||
|
|
|
@ -145,9 +145,7 @@ extern const char gfar_driver_version[];
|
|||
| SUPPORTED_Autoneg \
|
||||
| SUPPORTED_MII)
|
||||
|
||||
#define GFAR_SUPPORTED_GBIT (SUPPORTED_1000baseT_Full \
|
||||
| SUPPORTED_Pause \
|
||||
| SUPPORTED_Asym_Pause)
|
||||
#define GFAR_SUPPORTED_GBIT SUPPORTED_1000baseT_Full
|
||||
|
||||
/* TBI register addresses */
|
||||
#define MII_TBICON 0x11
|
||||
|
|
Loading…
Reference in New Issue