summaryrefslogtreecommitdiffstats
path: root/drivers/net/phy/vitesse.c
diff options
context:
space:
mode:
authorDaniel Mack <zonque@gmail.com>2014-06-18 11:01:43 +0200
committerDavid S. Miller <davem@davemloft.net>2014-06-21 15:50:00 -0700
commit13a56b4493259e6b020dbcf6a76b2bef479f3edf (patch)
tree268100006a23483618c21fc14dd2aff0c728488b /drivers/net/phy/vitesse.c
parentbd8ca17f8c74fa36d1dfb1b82de416e310d1b64d (diff)
downloadtalos-op-linux-13a56b4493259e6b020dbcf6a76b2bef479f3edf.tar.gz
talos-op-linux-13a56b4493259e6b020dbcf6a76b2bef479f3edf.zip
net: phy: at803x: Add support for hardware reset
The AT8030 will enter a FIFO error mode if a packet is transmitted while the cable is unplugged. This hardware issue is acknowledged by the vendor, and the only proposed solution is to conduct a hardware reset via the external pin each time the link goes down. There is apparantly no way to fix up the state via the register set. This patch adds support for reading a 'reset-gpios' property from the DT node of the PHY. If present, this gpio is used to apply a hardware reset each time a 'link down' condition is detected. All relevant registers are read out before, and written back after the reset cycle. Doing this every time the link goes down might seem like overkill, but there is unfortunately no way of figuring out whether the PHY is in such a lock-up state. Hence, this is the only way of reliably fixing up things. Signed-off-by: Daniel Mack <zonque@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy/vitesse.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud