Harshal Gohel 89322b4d69 rtl93xx: dsa: Handle lag_change properly ... LACP frequently changes active/backup links. driver must also handle dp->lag_tx_enabled. This should only affect egress LAG table, ingress should not be touched. To test, connect a known working 802.3ad compatible switch (Mikrotik). Configure bond with 802.3ad on openwrt as well as mikrotik. Observer active/backup links on openwrt with ``` for iface in <list of bond participants>; do ip -d link show $iface done ``` This should show ACTIVE/BACKUP status which must be synchronized with the partner's ACTIVE/BACKUP status if LACP is working correctly. Backup interface must not be chosen by the distribution algorithm to transmit egress packet At the moment, we have two parties involved in the selection of active LAG TX ports: - the bonding/DSA code which informs about activated/deactivated ports using .port_lag_change - the HW which is deactivating ports based on the link state see RTL93XX_TRK_CTRL_LINK_DOWN_AVOID In our case, the software is supposed to manage everything Co-developed-by: Sven Eckelmann <se@simonwunderlich.de> Signed-off-by: Sven Eckelmann <se@simonwunderlich.de> Signed-off-by: Harshal Gohel <hg@simonwunderlich.de> Link: https://github.com/openwrt/openwrt/pull/21740 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>		2026-03-07 20:33:22 +01:00
..
imagebuilder
linux	rtl93xx: dsa: Handle lag_change properly	2026-03-07 20:33:22 +01:00
llvm-bpf
sdk
toolchain
Config.in	targets: add REGULATOR_SUPPORT auto-feature	2026-03-01 10:59:19 +01:00
Makefile