zephyr/drivers/ethernet/phy
Declan Snyder 495a374a0d drivers: ethernet: ksz8081: RMII override RNB part
I for the life of me do not know what is going on here with the RNB chip
but it seems this override must be set in order for the chip to work,
regardless of strap-in configuration, and if not set explicitly, the
value after a reset for these two bits will be seemingly random and
inconsistent. And it was working before by luck before removing a second
redundant reset in a recent commit, because apparently the register
was getting the opposite of the reset value according to the datasheet
which makes it work. The result of these bits after reset seem to vary
depending on host mcu, board, debugger, number of times reset, type of
reset, and with a pinch of random chance after keeping all variables
seemingly the same, so let's just set it to the value that works
explicitly, even if it doesn't make sense. The bit here doesn't have
clear documentation but it seems it's for using RMII regardless of the
strap in option, which is what we want to do anyways if we know the
interface type from DT, so I think it's fine, considering it is making
this driver work again.

Signed-off-by: Declan Snyder <declan.snyder@nxp.com>
2024-11-01 13:54:00 -05:00
..
CMakeLists.txt drivers: ethernet: Add DP83825 phy driver 2024-10-15 04:10:06 -04:00
Kconfig drivers: ethernet: Add DP83825 phy driver 2024-10-15 04:10:06 -04:00
Kconfig.tja1103
phy_adin2111.c zephyr: bulk update to DT_NODE_HAS_STATUS_OKAY 2024-10-03 17:06:52 +01:00
phy_adin2111_priv.h
phy_microchip_ksz8081.c drivers: ethernet: ksz8081: RMII override RNB part 2024-11-01 13:54:00 -05:00
phy_mii.c drivers: ethernet: phy: phy_mii: log remove excess newlines 2024-10-25 12:50:38 -05:00
phy_qualcomm_ar8031.c
phy_realtek_rtl8211f.c
phy_ti_dp83825.c drivers: ethernet: Add DP83825 phy driver 2024-10-15 04:10:06 -04:00
phy_tja1103.c