Re: [PATCH net-next v4 00/12] ax88179_178a: Add support for AX88179A-based chips

Hi Birger,

I tested v4 on an ASIX AX88179B adapter (USB 0b95:1790,
bcdDevice 0x0200, firmware 1.3.0.0). And it worked smoothly.

I applied the series on top of net-next commit
df13c1df8147675470213ffff29dd5762fa321f5 and tested the resulting
7.2.0-rc3 kernel in a KVM Debian guest with the adapter passed through via
an emulated XHCI controller.

The driver automatically selected USB configuration 1 and bound as
ax88179. The MDIO path bound the "Asix Electronics AX88179A" PHY driver
(MDIO device ID 0x003b179a), and phylink reported 1000 Mb/s, full duplex,
autonegotiation enabled, and link detected. Driver information and read-only
EEPROM access also worked.

DHCP and interface-bound pings worked, and bidirectional iperf3 completed.
I also tested EEE disable/enable, pause enable/restore, module unload/reload,
ACPI S3 suspend/resume, and QEMU USB detach/reattach. Each recovery test
restored the PHY binding, carrier, DHCP, 1000/full reporting, and traffic.
I saw no AX88179/PHY/phylink warning, oops, call trace, or traffic timeout.

Tested-by: Jianhui Xu <[email protected]>

Thanks,
Jianhui