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)
<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
<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