@sven@social.treehouse.systems
2026-01-07 17:16 UTC
Replies (5)
-
@sven@social.treehouse.systems 2026-01-08 19:56
And the (likely) real fixes: https://lore.kernel.org/asahi/20260108-atcphy-coldboot-fix-v1-1-01c41c6e84f2@kernel.org/T/#u and https://lore.kernel.org/asahi/20260108-dwc3-apple-usb2phy-fix-v1-1-5dd7bc642040@kernel.org/T/#u macOS briefly bringing up dwc3 and tearing it down again with no device connected was just a red herring, no idea why that happens.
-
@bakkus@bitbang.social 2026-01-07 17:21
@sven @janne whu... why? what's gained by such a sequence? If anything?
-
@valpackett@social.treehouse.systems 2026-01-07 17:42
@sven @janne USB2 is kind of a massive thorn in the side of Type-C handling tbf >_< On Qualcomm SoCs we have a fun issue: the USB2 PHY derives its clock from the USB3 PIPE clock, and the QMPPHY driver currently turns PIPE off when you go into 4-lane alt mode, so using 4-lane DP breaks USB2 on that port until full reboot :D (and just Not Turning it Off only fixes hotplugged devices, I'm gonna try modeling the clk relationship properly) But hey, at least that's literally our only issue and we don't ever have to reset anything :P
-
@gameshack_@infosec.exchange 2026-01-07 18:06
@sven @janne i'd love to ask whoever came up with this... why.
-
@janne@social.treehouse.systems 2026-01-07 18:47
@sven still wondering why it even helps if we might just chasing the “ghost” of initializing the usb controllers in device mode in our m1n1 test setup. that needs of work as well