diff options
author | Sergey Ryazanov <ryazanov.s.a@gmail.com> | 2017-10-16 02:31:18 +0300 |
---|---|---|
committer | John Crispin <john@phrozen.org> | 2017-11-06 16:39:41 +0100 |
commit | 204f3f5987bacf725394dbdd6497b4972db5056e (patch) | |
tree | 3fdc29cb13dcf0c1f2bcfeb7892ae8613d08fa84 /toolchain | |
parent | 6d2f3b1b1974d742576b0902e9c4777c9ac1ba67 (diff) | |
download | upstream-204f3f5987bacf725394dbdd6497b4972db5056e.tar.gz upstream-204f3f5987bacf725394dbdd6497b4972db5056e.tar.bz2 upstream-204f3f5987bacf725394dbdd6497b4972db5056e.zip |
ixp4xx: fix non-standard phy support
The patch, which adds multiphy support, adds new path for non-standard
PHYs (e.g. MV88E6060 switch IC) to avoid using kernel phy framework. All
work well except the link status traking (Duplex and Speed), which is
reseted as soon as PHY connection procedure is done. This leads to lost
of the link status of non-standard PHY, which is configured exactly in
the ixp4xx_phy_connect() function.
Move the generic reset of a link state to the ixp4xx_phy_connect()
function to the code path, which is intended for handling of a normal
PHY.
Reported-by: Nerijus Baliunas <nerijus@users.sourceforge.net>
Tested-by: Nerijus Baliunas <nerijus@users.sourceforge.net>
Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Diffstat (limited to 'toolchain')
0 files changed, 0 insertions, 0 deletions