unixabg has quit [Remote host closed the connection]
unixabg has joined #linux-cros-arm
amstan has joined #linux-cros-arm
jenneron[m] has joined #linux-cros-arm
hexdump0815 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #linux-cros-arm
<hexdump0815>
jenneron[m]: after looking through the v6.1.52 patch and not finding anything which might cause the usb3 breakage at all i decided to retest again
<hexdump0815>
it looks like i did something wrong during my last v6.1.51 with new pmos patches testing - retesting showed that it also does not see the usb3 device
<hexdump0815>
so looks like its something introduced with newer pmos patches - diffing old and new patched tree now - lets see what comes out of this
<hexdump0815>
nothing which will be very important, but i guess that oe is for free ...
<hexdump0815>
will check that too
<hexdump0815>
oh - looks like that brightness change is already in :)
<hexdump0815>
i'm out of ideas: reverting that usb2 phy patch did not fix the problem, neither did reverting the hsotg node patch, the clk naming patch or the spi flash adding patch
<hexdump0815>
besides those there is nothing left among the pmos patches of the last less 10 months (when i did my last pmos kernel changes sync) which might even remotely have an influence on usb3
<hexdump0815>
the difference between working and non-working usb3 for a v6.1.51 kernel is the small diff i linked in the pastebin above
<hexdump0815>
that is just 715 lines of diff, most of which is obviously not related to usb - in there must be the problem somehow
<hexdump0815>
ok - i think i understand what part of the problem is: for testing a cold boot is required - if i boot my usb3 working kernel after having booted a non usb3 kernel, it will not work anymore as well
<hexdump0815>
looks like broken code somewhere which seems to evaluate this node even if it is disabled
<hexdump0815>
enough for today ...
<hexdump0815>
i "fixed" it by adding a /delete-node/ for it in the snow-common.dtsi - might be a useable workaround to to still keep it working for that tablet which seems to use/need it