summaryrefslogtreecommitdiff
path: root/drivers/ddr/microchip
diff options
context:
space:
mode:
authorRufus Segar <rhs@riseup.net>2024-12-04 13:34:30 +0000
committerTom Rini <trini@konsulko.com>2025-01-01 14:35:54 -0600
commitc5cda4ae4aeec7b5e23e4f48ccbe8e4e95bc326c (patch)
tree2bfc737fe3622a1e831b38fd99901095a997626f /drivers/ddr/microchip
parent395ee74991aaeac3c0ba0aa505f108571a107da7 (diff)
Revert "net: phy: marvell 88e151x: Fix handling of bare RGMII interface type"
This reverts commit 431be621c6cbc72efd1d45fa36686a682cbb470a. Section 3.3 of Reduced Gigabit Media Independent Interface (RGMII) Version 2.0 (4/1/2002) details that a PHYs using a ~2ns internal delay are referred to as RGMII-ID. This internal delay is optional. Page 147-148 of the Marvell Doc. No. MV-S107146-U0 Rev. F details timings of the RX/TX delays. We see that with the TX/RX_CLK delay enabled, our RX/TX_CTL signal is shifted w.r.t CLK to reflect the delay added. In 431be62 there is no timing difference between RGMII and RGMII-ID, and so programmers wanting to explicitly set their PHY to RGMII will find that delay added anyway. This could throw off timing if that internal delay is undesired. We should be handling all 4 possible RGMII cases of PHY_INTERFACE_MODE: RGMII, RGMII_ID, RGMII_TXID, and RGMII_RXID. Reverting 431be62 implements this. See also m88e1111_config_init_rgmii_delays in the equivalent driver in Linux (drivers/net/phy/marvell.c), which does not set these delays in RGMII mode. 68e6eca was tested out on an 88E1512 PHY in RGMII-ID mode. This reversion has been tested by myself on an 88E1518 in RGMII-ID mode. This patch affects boards using this driver in "rgmii" mode, as the internal delay will no longer be enabled. Namely kikwood-nsa310s. Signed-off-by: Rufus Segar <rhs@riseup.net>
Diffstat (limited to 'drivers/ddr/microchip')
0 files changed, 0 insertions, 0 deletions