diff options
| author | Ioana Ciornei <ioana.ciornei@nxp.com> | 2020-12-09 13:31:58 +0200 |
|---|---|---|
| committer | Priyanka Jain <priyanka.jain@nxp.com> | 2021-02-08 14:01:14 +0530 |
| commit | 64a0fb4cc35ced6ac83e4177889501782b51891d (patch) | |
| tree | b4e4207b9f2b7373a35a8b52ba88f748620b54ff /include/cpsw.h | |
| parent | 46fdf763b8b316d1eec25977e6e7b8051e89e3fd (diff) | |
| download | u-boot-64a0fb4cc35ced6ac83e4177889501782b51891d.tar.gz u-boot-64a0fb4cc35ced6ac83e4177889501782b51891d.tar.xz u-boot-64a0fb4cc35ced6ac83e4177889501782b51891d.zip | |
net: memac_phy: add a timeout to MDIO operations
We have encountered circumstances when a board design does not include
pull-up resistors on the external MDIO buses which are not used. This
leads to the MDIO data line not being pulled-up, thus the MDIO controller
will always see the line as busy.
Without a timeout in the MDIO bus driver, the execution is stuck in an
infinite loop when any access is initiated on that external bus.
Add a timeout in the driver so that we are protected in this
circumstance. This is similar to what is being done in the Linux
xgmac_mdio driver.
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Reviewed-by: Madalin Bucur <madalin.bucur@oss.nxp.com>
[Rebased]
Signed-off-by: Priyanka Jain <priyanka.jain@nxp.com>
Diffstat (limited to 'include/cpsw.h')
0 files changed, 0 insertions, 0 deletions