Files
u-boot/drivers/net
Stefan Chulski 13b725fd24 net: mvpp2x: fix traffic stuck after PHY start error
Issue:
- Network stuck if autonegotion fails.

Issue root cause:

- When autonegotiation fails during port open procedure, the packet
  processor configuration does not finish and open procedure exits
  with error.
- However, this doesn't prevent u-boot network framework from
  calling send and receive procedures.
- Using transmit and receive functions of misconfigured packet
  processor will cause traffic to get stuck.

Fix:

- Continue packet processor configuration even if autonegotiation
  fails.  Only error message is triggered in this case.
- Exit transmit and receive functions if there is no PHY link
  indication.
- U-boot network framework now calls open procedure again during next
  transmit initiation.

Signed-off-by: Stefan Chulski <stefanc@marvell.com>
Reviewed-by: Igal Liberman <igall@marvell.com>
Tested-by: Igal Liberman <igall@marvell.com>
Reviewed-by: Ramon Fried <rfried.dev@gmail.com>
Acked-by: Joe Hershberger <joe.hershberger@ni.com>
2019-12-09 09:47:42 -06:00
..
2019-12-03 08:44:14 -05:00
2016-10-23 18:33:18 -04:00
2019-08-11 16:43:41 -04:00
2018-11-27 21:06:53 +05:30
2019-08-11 16:43:41 -04:00
2019-09-04 11:37:19 -05:00
2019-01-24 11:35:29 -06:00
2018-07-26 14:08:21 -05:00
2019-09-04 11:37:19 -05:00
2019-08-11 19:27:41 -04:00
2013-04-01 16:33:52 -04:00
2019-08-11 16:43:41 -04:00
2019-08-11 16:43:41 -04:00
2019-08-09 23:15:01 +02:00
2019-04-16 16:29:00 +05:30