aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu
diff options
context:
space:
mode:
authorMatthijs Kooijman <matthijs@stdin.nl>2023-08-31 21:10:23 +0200
committerChristian Marangi <ansuelsmth@gmail.com>2023-09-17 16:40:21 +0200
commit92a0dd2447bda9a6d5440f4a94d9b617406e3f76 (patch)
tree9008ac8d12a075987f132b786cc7dee842bedeb5 /target/linux/mvebu
parent3fe2875378d3a0dd2005f6212d4650395dbaab24 (diff)
downloadupstream-92a0dd2447bda9a6d5440f4a94d9b617406e3f76.tar.gz
upstream-92a0dd2447bda9a6d5440f4a94d9b617406e3f76.tar.bz2
upstream-92a0dd2447bda9a6d5440f4a94d9b617406e3f76.zip
ath79: fix packetloss on some WLR-7100
On some WLR-7100 routers, significant packet loss was observed. This is fixed by configuring a delay on the GMAC0 RXD and RXDV lines. The values used in this commit are copied from the values used by the stock firmare (based on register dumping). Out of four test routers, the problem was consistently observed on two. It is unclear what the relevant difference is exactly (the two working routers were v1 001 with AR1022 and v1 002 with AR9342, the two broken routers were both v1 002 with AR1022). All PCB routing also seems identical, so maybe there is some stray capacitance on some of these that adds just enough delay or so... With this change, the packet loss disappears on the broken routers, without introducing new packet loss on the previously working routers. Note that the PHY *also* has delays enabled (through `qca,ar8327-initvals`) on both RX and TX lines, but apparently that is not enough, or it is not effective (registers have been verified to be written). For detailed discussion of this issue and debug history, see https://forum.openwrt.org/t/sitecom-wlr-7100-development-progress/79641 Signed-off-by: Matthijs Kooijman <matthijs@stdin.nl> (cherry picked from commit d2ce3a61aa1cbc53988eb640cbab48e20fbfb1aa)
Diffstat (limited to 'target/linux/mvebu')
0 files changed, 0 insertions, 0 deletions