<steev>
calebccff: fwiw, i've tested it here on the c630 and it doesn't spam the hell out of my log. i'll wait for others to reply with nitpicks before sending a t-b
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
anholt_ has joined #linux-msm
anholt has quit [Ping timeout: 480 seconds]
pevik_ has joined #linux-msm
pevik_ has quit []
pevik_ has joined #linux-msm
<minecrell>
calebccff: well stuff exploded because only half of the runtime PM calls were guarded when it was not supposed to be used. Just seems weird to keep some unneeded call again that may explode later (even though I agree it should be a no-op)
<z3ntu>
Also if anybody has an idea how to debug the usb controller failing suspend with "dwc3-qcom a6f8800.usb: HS-PHY not in L2" I'd be grateful :) The phone does seem to suspend correctly but after waking up usb never comes back
pespin has joined #linux-msm
Daanct12 has joined #linux-msm
pevik_ has quit [Quit: Lost terminal]
pevik_ has joined #linux-msm
Daanct12 has quit [Quit: Leaving]
pevik_ has quit [Remote host closed the connection]
svarbanov has quit [Ping timeout: 480 seconds]
<calebccff>
z3ntu: I see the same message on sdm845 but USB continues to work after suspend so that might be a red herring
<z3ntu>
calebccff: oh that's super useful to know, thanks!
<steev>
robclark: will let you know if/when it happens again :) unfortunately, it seems just launching vscode isn't enough. that one happened when i went to close the gnome settings window after changing the audio device from headphones to speakers
<robclark>
steev: that won't really fix the warn splats but at least will prevent things from falling over afterwards.. I've managed to trigger it a couple times, mostly be leaving gnome sitting there and working on something else for a few hrs
<steev>
if i can keep using it, that's good :)
<steev>
my next step is to see how much battery we lose overnight when "suspended"