ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
fevv8[m] has joined #aarch64-laptops
shawnguo4 is now known as shawnguo
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
kholk[m] has joined #aarch64-laptops
Dylanger has joined #aarch64-laptops
strongtz[m] has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
sporos11[m] has joined #aarch64-laptops
EmersonCardoso[m] has joined #aarch64-laptops
qzed[m] has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov__ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov_ has quit [Ping timeout: 480 seconds]
jonasbits has quit [Ping timeout: 480 seconds]
jonasbits has joined #aarch64-laptops
Lucanis1 has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
hightower2 has joined #aarch64-laptops
ajhalaney[m] has joined #aarch64-laptops
waifro has quit []
<robclark> macc24: haven't had a chance to try it yet, but https://lkml.org/lkml/2022/2/9/997 should fix display on lazor on v5.17-rc
<robclark> bamse: ^^^ thought crossed my mind that the gdsc issue could also be related to a630 issues with frequent freq changes?
<macc24> robclark: i'll finish up what i'm doing now and test that patch
<macc24> thanks!
<robclark> hmm, is `DEFAULT_TRANSITION_DELAY` getting set anywhere? I wonder if that patch is complete?
<robclark> anyways, the issue was traced down to gdsc setting shorter than default transition delay
<macc24> damn that must've took long
<robclark> it took a while to figure out why the hw was getting grumpy
* robclark realizes that is a two patch series
<robclark> you need both
<maz> robclark: could this explain the GPU hanging? it just happened to me twice in a row with -rc2 on a c630.
<robclark> that is what I was suspecting.. but the series doesn't set that new flag on any gpu related ioctls..
<maz> well, it looked to me as a GPU hang, but nothing was moving anymore -- managed to switch to a vt, and then it was dead.
<robclark> but you are hitting that on v5.17-rc2? I thought we nerf'd that freq clamping (which seemed to be the thing that triggered frequently)
<robclark> dmesg?
<maz> let me see if it has been salvaged...
<robclark> (I wish we had console-ramoops on c630)
<maz> looks like the display going wonky.
<robclark> ok, could be same issue we were hitting on sc7180.. worth trying that series
<maz> right. I'll give it a shot. thanks.
<robclark> np, thx
iivanov__ has quit [Ping timeout: 480 seconds]
<bamse> robclark: so that's the delay as we power the gdsc on?
<bamse> robclark: but reading that patch, isn't it only changing the transition delay back to default for the mdss gdsc? that makes it seem unrelated to me
derzahl has quit [Remote host closed the connection]
<steev> maz: we've seen that frame enc timeout before on the c630
<steev> back when the "blue screen" was often happening
<steev> also patch 2 has an extra space after the | in the sc7180
<robclark> bamse: patch 2/2 in that series is dispcc part
<robclark> bamse: I'm not *entirely* sure if the delay only applies to on/off transitions or also freq transitions that change the power requirements
hightower2 has quit [Ping timeout: 480 seconds]
iivanov_ has joined #aarch64-laptops
<steev> srinik: any luck tracking down the COMP pops? with 5.17 rc3, there seems to be a lot more popping
<steev> https://paste.debian.net/1230164/ - it seems like it's opening/closing the port more often? it used to be that there would only be 4 of those
xnox has joined #aarch64-laptops
<bamse> robclark: ahh, now i see...ther'es a regmap_read() added in the !DEFAULT_TRANDITION_DELAY as well...so that would retain whatever other bits was in the gdscr register
<robclark> right
minecrell has joined #aarch64-laptops
<bamse> robclark: still would like a slightly better comment from Taniya, but that patch looks really promising then
<steev> bamse: assuming it gets accepted, https://github.com/steev/linux/commit/5086359c3112ef461df6c5324b33baf07598db82 seem right for the c630? i'd probably change the commit message though since it becomes identical to the others
<steev> taniya's patchset gets accepted, i mean
<bamse> robclark: we have the wrong EN_FEW_WAIT (8, downstream seems to leave it at 2) value for gpu_cx_gdsc upstream...we can align that by setting the DEFAULT_TRANSITION_DELAY after Taniya's patch...
<bamse> robclark: but CLK_DIS_WAIT_VAL should be 8 per the downstream dts...and we set it to 2 upstream, and hw default is 2...so Taniya's change won't help us there
<robclark> hmm, setting to long a delay seems less likely to cause problems than the other way around..
<bamse> so the question is what CLK_DIS_WAIT actually is, because we have it at 2 and it should be at 8...
<bamse> and the gpu cx gdsc seems to be the only one specifying qcom,clk-dis-wait-val downstream...so it is likely there for some particular reason
<robclark> does downstream have git history that is slightly more useful than "copy xyz from commit abc"?
<bamse> just found it
<bamse> "Change clock-disable-wait value based on HW recommendation."
Lucanis has joined #aarch64-laptops
<robclark> ahh, the good 'ol "based on HW recommendation"
<robclark> well, I guess in worst case maybe reply to Taniya about the gpu_cx_gdsc difference from downstream and see if they can follow-up?
Lucanis1 has quit [Ping timeout: 480 seconds]
<CosmicPenguin> To be fair to the software team, that's usually all they get from the HW team as an explanation
<steev> hm, actually i notice one huge issue with the c630 and 5.17
<steev> usb seems broken
<steev> nope, just had usb cable go bad, it seems
suihkulokki has quit [Server closed connection]
suihkulokki has joined #aarch64-laptops
SallyAhaj has quit [Remote host closed the connection]
pg12 has quit [Server closed connection]
pg12 has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov_ has quit [Ping timeout: 480 seconds]
SallyAhaj has joined #aarch64-laptops
<amstan> has anyone seen a loop= kernel command line option?
<amstan> a device i'm using has it, can't find docs for it anywhere
<bamse> robclark: iirc it was reported that we can trigger the gpu issue downstream as well...and it would have the settings correctly
<robclark> oh.. hmm
<robclark> that is unfortunate
<amstan> steev: you found it! perfect, yeah, that's what i was expecting
iivanov has quit [Remote host closed the connection]
jonasbits has quit [Ping timeout: 480 seconds]