On Mon, Oct 16, 2023 at 9:20 PM Oleksij Rempel o.rempel@pengutronix.de wrote:
On Mon, Oct 16, 2023 at 11:27:07AM -0700, Maciej Żenczykowski wrote:
On Mon, Oct 16, 2023 at 1:29 AM Oleksij Rempel o.rempel@pengutronix.de wrote:
On Sun, Oct 15, 2023 at 03:13:26PM -0700, Maciej Żenczykowski wrote:
This means even with the option manually enabled, we'd still need to cherrypick dde25846925765a88df8964080098174495c1f10 "net: usb/phy: asix: add support for ax88772A/C PHYs" since apparently this is simply new(ish) hardware with built-in x88772C PHY.
As far as I see, you are not using clean mainline stable kernel. All changes which make your kernel to need an external PHY driver are _not_ in v5.10.198.
No, the dmesg was actually from a (probably clean-ish 6.4-ish) debian kernel on my laptop, where the device enumerates and works in one of the 2 usb-c ports.
As I mentioned the hardware that actually runs 5.10 is having issues even detecting my test device. (and while that 5.10 is far from clean mainline, the usb and network driver portions are more or less untouched)
You will need to cherrypick at least 28 last patches from this stack: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drive...
and some from here too: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drive...
I think this basically means the answer is "if you want this to work upgrade to a newer kernel". Which of course won't make any users happy, but oh well...
It means - what ever problem there is, it is most probably not related to the asix driver. In kernel v5.10, there are no external dependencies to other PHY drivers.
I take this to mean you think that the built-in ax88772C PHY should work out of the box with 5.10, and if it doesn't then this presumably means there's something wrong at the usb controller level. (hopefully I'll get a second unit and be able to confirm this...)