GrimKriegor_ has quit [Read error: Connection reset by peer]
GrimKriegor has joined #linux-exynos
GrimKriegor has quit [Changing host]
GrimKriegor has joined #linux-exynos
<mszyprow> memeka: please check with disabled exynos5422-dmc driver
<mszyprow> memeka: 933MHz is fake
<mszyprow> memeka: the memory chips supports only 800MHz
<memeka> mszyprow: I added the patches for DMC, ASV
<memeka> latest ones
<mszyprow> memeka: uboots configures bus at 933MHz, but leaves memory chips in self-refresesh mode
<memeka> set all governors to performance
<mszyprow> memeka: which is still slower than the real (synchronous) 800MHz
<mszyprow> memeka: I would start disabling devfreq at all
<mszyprow> memeka: there are too many issues with it
<memeka> on wayland, I still get limited to 20fps refresh, and offline glmark2 can go up to 50fps (i remember much higher values ~80fps with individual tests in the hundreds on 5.0 kernel
<memeka> mszyprow: mali is set to run on devfreq :D
<mszyprow> then disable exynos-bus and exynos5422-dmc drivers
<memeka> mszyprow: the issue was present before adding all the DMC/ASV patches anyway
<memeka> and it's weird to have a nice cutoff on-screen for 20fps
<memeka> is it possible there is an issue with the DRM?
<mszyprow> this way you will be sure that hw runs at be performance
<memeka> i didn't see any big exynos drm change (maybe DRMPRIME getting out)
<mszyprow> frankly I have no idea, afair nothing has changed in drm since v5.0...
<mszyprow> memeka: if you have a good test environment, you can bisect that issue ;P
<memeka> mszyprow: I don’t have a good test env :)
<memeka> also, i am not really sure where the issue is or how to debug it :P
<memeka> clocks? drm? gpu? bus? .... ?!
<memeka> heck even CPU has an influence - running egl on big or little cores behave VERY differently
<memeka> in terms of speed
<memeka> mszyprow: can even be some other software (e.g. i am running ubuntu 17.10, maybe too old e.g. libdrm or other lib....)
<memeka> (although it is running faster with older kernel, so maybe not that)
<memeka> mszyprow: but i do like this: https://pastebin.com/jKPrut7U
<mszyprow> memeka: if it is related to scheduling, then try 'taskset' based test
<mszyprow> memeka: please disable devfreq
<memeka> mszyprow: i did try taskset of course, still slow :P
<memeka> ok i will try with that next
<mszyprow> memeka: there have been a few changes to exynos-bus
<memeka> hmm maybe that?
<mszyprow> memeka: we are trying to make it more reliable, but there is a lot of things to be fixed first
<memeka> mszyprow: I will try porting some more of what I had from 5.0 first, then try check performance with devfreq disabled
<memeka> but again, being limited to 20fps seems fishy (and related to DRM...)
<mszyprow> memeka: that really sounds strange, I don't suspect any exynos related patch for that, maybe something in the drm core?
<memeka> mszyprow: yes when i said DRM i didn't mean exynos drm, i meant drm core :(
<memeka> maybe next RCs will fix that .....
adjtm has quit [Ping timeout: 265 seconds]
adjtm has joined #linux-exynos
adjtm has quit [Quit: Leaving]
_whitelogger has joined #linux-exynos
adjtm has joined #linux-exynos
ahajda has quit [Quit: Leaving.]
ahajda has joined #linux-exynos
ahajda has quit [Remote host closed the connection]
ahajda has joined #linux-exynos
ahajda has quit [Client Quit]
ahajda has joined #linux-exynos
ahajda has quit [Quit: Leaving.]
ahajda has joined #linux-exynos
ahajda has quit [Remote host closed the connection]
ahajda has joined #linux-exynos
mszyprow has quit [Ping timeout: 245 seconds]
paulk-leonov has quit [Ping timeout: 240 seconds]
paulk-leonov has joined #linux-exynos
adjtm has quit [Ping timeout: 240 seconds]
paulk-leonov has quit [Ping timeout: 250 seconds]
paulk-leonov has joined #linux-exynos
adjtm has joined #linux-exynos
paulk-leonov has quit [Ping timeout: 245 seconds]
paulk-leonov has joined #linux-exynos
paulk-leonov has quit [Excess Flood]
paulk-leonov has joined #linux-exynos
putti_ has joined #linux-exynos
putti_ has quit [Changing host]
putti_ has joined #linux-exynos
Putti has quit [Ping timeout: 240 seconds]
putti_ is now known as Putti