diff options
| author | sean.wang@mediatek.com <sean.wang@mediatek.com> | 2016-08-16 08:55:14 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-08-16 09:02:44 +0300 |
| commit | b2025c7cc92d5bfc8c5ce756c8d8a6f57c776fbd (patch) | |
| tree | fa2ddcc2c23a1f674882cd8a39b261d318ad5c15 /drivers/net/ethernet/natsemi | |
| parent | 8ca7f4fe0733342c862b8585dd6eb6521b9bf533 (diff) | |
| download | linux-b2025c7cc92d5bfc8c5ce756c8d8a6f57c776fbd.tar.xz | |
net: ethernet: mediatek: fix flow control settings on GMAC0 is not being enabled properly
Commit 08ef55c6f257acf3bdc6940813f80e8f0f5d90ec
("net-next: mediatek: fix gigabit and flow control advertisement")
had supported proper flow control settings for GMAC1. But for GMAC0,
1.GMAC0 shares the common logic with GMAC1 inside mtk_phy_link_adjust()
to adapt various settings for the target phy.
2.GMAC0 uses fixed-phy to connect to a builtin gigabit switch with
fixed link speed as commit 0c72c50f6f93b0c3daa9ea35d89ab3a933c7b5a0
("net-next: mediatek: add fixed-phy support") describes.
3.However, fixed-phy doesn't enable SUPPORTED_Pause & SUPPORTED_Asym_Pause
supported flag on default that would cause mtk_phy_link_adjust() not to
enable flow control setting on GMAC0 properly and cause packet dropped
when high traffic.
Due to these reasons, the patch adds SUPPORTED_Pause & SUPPORTED_Asym_Pause
supported flags on fixed-phy used by the driver to have proper handling on
the both GMAC with the shared common logic.
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/natsemi')
0 files changed, 0 insertions, 0 deletions