<jenneron[m]>
hexdump0815: that's dumb, why is it affecting in disabled state
<jenneron[m]>
i've asked the author of the patch firstly
<jenneron[m]>
i don't really want to touch my snow, it is very annoying without display
hexdump01 has quit []
hexdump0815 has joined #linux-cros-arm
<hexdump0815>
jenneron[m]: i'm giving up on this for now - i built a fresh v6.1.59 kernel with the new pmos patches and my hack and initially booted my snow into my old v6.1.11 kernel which ad usb2 working and it was not working
<hexdump0815>
then i booted the freshly built .59 kernel and plugged in an usb3 device which did not work, i did shutdown and booted with the usb3 device connected and it was seen
<hexdump0815>
another time it was not there anymore, while testing more xhci died during an lsusb -v -v and during a few tests usb3 sometimes worked and sometimes not
<hexdump0815>
maybe my snow is broken, maybe it is because it has no battery anymore and the power supply cannot deliver enough current for hungry usb2 devices initially - no idea
<hexdump0815>
i would consider usb3 on snow simply unreliable to not working until we have it proven otherwise - as said even the v6.1.11 kernel which worked yesterday die not work today, even with a cold boot
<hexdump0815>
i'm not going to put more time into this for now
<hexdump0815>
i ment usb3 in my first line today
<hexdump0815>
no idea why i sometimes write usb2 instead of 3 - all above issupposed to be usb3 ... while at usb2: that port is working perfectly fine
<jenneron[m]>
hexdump0815: i'm wondering if we can just disable USB 3.0 and have it in 2.0 mode
<hexdump0815>
maybe - not sure - strange thing is that xhci is always probed cleanly and there are usually no errors - connected devices simply do not show up
<hexdump0815>
if we would be able to get it working in usb2 mode that should be fine as well for something as old as snow
<hexdump0815>
it looks like disabling usb3 mode should help - i just connected a usb2 hub to the usb3 port and in that even usb3 devices (in usb2 mode then) seem to work fine and reliable
<hexdump0815>
maybe its really a power issue and it should be checked on a snow with battery
<hexdump0815>
in the dts there is a "phys" line in the usb3 entry listing usb2 and usb3 - maybe just dropping usb3 there solves the problem ... i might give that a try if i find some time later or during the next days
<hexdump0815>
ok - just setting phys = <&usbdrd_phy 0>; and phy-names = "usb2-phy"; for &usbdrd_dwc3 does not seem to help