30 Nov
2019
30 Nov
'19
1:58 a.m.
On Thu, Aug 15, 2019 at 5:09 PM nhed+uboot@starry.com wrote:
From: Stefan Chulski stefanc@marvell.com
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
Acked-by: Joe Hershberger joe.hershberger@ni.com