kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #lima
Net147 has joined #lima
megi has quit [Ping timeout: 258 seconds]
buzzmarshall has quit [Remote host closed the connection]
Barada has joined #lima
psydread has left #lima [#lima]
psydread has joined #lima
yuq825 has quit [Remote host closed the connection]
dddddd has quit [Remote host closed the connection]
mixfix41 has joined #lima
mixfix41 has left #lima [#lima]
machinehum has quit [Ping timeout: 246 seconds]
yuq825 has joined #lima
machinehum has joined #lima
machinehum has quit [Ping timeout: 260 seconds]
Elpaulo has quit [Quit: Elpaulo]
megi has joined #lima
machinehum has joined #lima
machinehum has quit [Ping timeout: 246 seconds]
yuq825 has quit [Remote host closed the connection]
yuq825 has joined #lima
yuq825 has quit [Remote host closed the connection]
yuq825 has joined #lima
Elpaulo has joined #lima
dddddd has joined #lima
warpme_ has joined #lima
machinehum has joined #lima
machinehum has quit [Ping timeout: 246 seconds]
megi has quit [Quit: WeeChat 2.8]
Barada has quit [Quit: Barada]
megi has joined #lima
yuq825 has quit [Quit: Leaving.]
machinehum has joined #lima
machinehum has quit [Ping timeout: 265 seconds]
buzzmarshall has joined #lima
megi has quit [Quit: WeeChat 2.8]
megi has joined #lima
machinehum has joined #lima
machinehum has quit [Ping timeout: 272 seconds]
machinehum has joined #lima
dddddd has quit [Ping timeout: 240 seconds]
Putti has joined #lima
ornxka has joined #lima
<Putti>
Hi, I get on samsung s3 (i9305) graphics glitches in lineageos setup wizard but not after that. When the graphics totally hang I see error messages like: lima 13000000.gpu: mmu command 2 timeout
<Putti>
and [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:34:plane-1] flip_done timed out
<Putti>
I have disabled PM_DEVFREQ but that didn't help
<Putti>
could this still be something related to bus clocks?
<Putti>
the kernel I'm using is 5.7rc1
<Putti>
and latest mesa3d master
<anarsoul>
hi
<anarsoul>
yeah, likely something's up with hardware
<anarsoul>
try lowering gpu clock
<Putti>
hmm, not quite sure how to do that, but will try to find out
<anarsoul>
assigned-clock-rates in dts is the easiest way
<Putti>
exynos4.dtsi contains clocks
<anarsoul>
oh, it also has voltage regulator for gpu
<anarsoul>
devfreq patches are not in 5.7-rc1 yet and moreover you don't have operation points
<anarsoul>
so make sure your gpu runs at lowest frequency
<Putti>
anarsoul, hmm, this has the bus and core clocks
<Putti>
bus at highest, core at lowest?
<anarsoul>
Putti: lima in 5.7-rc1 doesn't configure clock rate, so it uses default
<anarsoul>
also you have a voltage regulator for GPU
<anarsoul>
so you may be undervolting GPU if default voltage is too low for default clock rate
<anarsoul>
as temporary workaround you can set clock rate in dts
<anarsoul>
grep for assigned-clock-rates for examples
<anarsoul>
I'm not sure if you can configure voltage in the same way
<Putti>
anarsoul, so core clock? (I'm asking since there is also bus clock here)
<anarsoul>
Putti: yes
<Putti>
anarsoul, thanks a lot, I will try now :)
<xdarklight>
anarsoul: Putti: lima devfreq missed the v5.7 cycle so it will only be part of v5.8-rc1
<anarsoul>
xdarklight: exynos still would need opp :)
<Putti>
the exynos display controller doesn't work (at least in 5.3 kernel) correctly with devfreq so I don't know if devfreq can only be enabled for lima
<xdarklight>
anarsoul: OK. just wanted to let you know so you don't waste time debugging devfreq issues on 5.7 while you could spend your time better (like pushing out more lima improvements) :)
<anarsoul>
xdarklight: thanks, I'm following kernel driver development as well :P
<Putti>
xdarklight, yeah, thanks for letting me know, today is the first day I tried lima on this device :)
<Putti>
and so much better than SW rendering
<Putti>
so thanks a lot to you all lima developer!
<anarsoul>
Putti: you're welcome, please keep us up to date on lima integration into lineageos
<Putti>
anarsoul, so I lowered the clock rate all the way down to 40mhz but kernel says "lima 13000000.gpu: mod rate = 50000000" so I guess it doesn't want to go below 50Mhz. This still didn't fix the glitches so now I will have to figure out how else I can configure the voltage regulator
<anarsoul>
50mhz is probably too low
<anarsoul>
but it shouldn't cause glitches
<anarsoul>
so yeah, check voltage regulator
<Putti>
I don't know what to check on the voltage regulator
<Putti>
not sure I understand the PMU driver but I only see low power setting for the G3D power supply being used
<Putti>
so that could be it, will have to figure out how to get the normal power option enabled