Hi Marek, On Mon, Jul 12, 2021 at 05:40:59PM +0200, Marek Behun wrote: > Vladimir, on what mv88e6xxx devices are you developing this stuff? > Do you use Turris MOX for this? I didn't develop the Marvell stuff nor did I come up with the idea there, Tobias did. I also am not particularly interested in supporting this for Marvell beyond making sure that the patches look simple and okay, and pave the way for other drivers to do the same thing. I did my testing using a different DSA driver and extra patches which I did not post here yet. I just reposted/adapted Tobias' work because mv88e6xxx needs less work to support the TX data plane offload, and this framework does need a first user to get accepted, so why delay it any further if mv88e6xxx needs 2 patches whereas other drivers need 30. I did use the MOX for some minimal testing however, at least as far as I could - there is this COMPHY SERDES bug in the bootloader which makes the board fail to boot, and now the device tree workaround you gave me does not appear to bypass the issue any longer or I didn't reaply it properly. The point is that it isn't as easy as I would have liked to use the MOX for testing. I was able to validate the "net: dsa: track the number of switches in a tree" patch on MOX, though, since DSA probes earlier than xhci, and even though the boot hung, I did put some prints and got the expected results.
