macb: Keep driver's speed/duplex in sync with actual NCFGR
When underlying phy driver restores its state very fast after being brought down and up so that macb driver function macb_handle_link_change() was never called with link state "down", driver's internal representation of phy speed and duplex (bp->speed and bp->duplex) didn't change. So, macb driver sees no reason to perform actual write to the NCFGR register, although the speed and duplex settings in that register were reset when interface was brought down and up. In that case actual phy speed and duplex differ from NCFGR settings. The patch fixes that by keeping internal driver representation of speed and duplex in sync with actual content of NCFGR. Signed-off-by: Vitalii Demianets <vitas@nppfactor.kiev.ua> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
7f2cd328d4
commit
26cdfb4915
|
@ -1031,6 +1031,8 @@ static void macb_init_hw(struct macb *bp)
|
|||
config |= MACB_BIT(NBC); /* No BroadCast */
|
||||
config |= macb_dbw(bp);
|
||||
macb_writel(bp, NCFGR, config);
|
||||
bp->speed = SPEED_10;
|
||||
bp->duplex = DUPLEX_HALF;
|
||||
|
||||
macb_configure_dma(bp);
|
||||
|
||||
|
|
Loading…
Reference in a new issue