<chewitt>
I've asked the guy who's been poking things (Pavel) to grab some stats and report it
<krzk>
chewitt: cool!
jma has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
<krzk>
chewitt: that exynos power domain is unlikely to cause performance degradation - I don't see there any code which could do it... more likely is that for old driver some domains for example do not work at all, therefore maybe PM runtime is disabled?
<krzk>
chewitt: different topic - it's quite surprising how many patches you like to carry over instead of upstreaming them. Like with everything - not having things upstream is a costly choice, bringing troubles in debugging and reporting bugs (for any reporting buh answer will be: test it on mainline).
<chewitt>
@krzk I loathe patches
<chewitt>
the Amlogic patchset that I carry is mostly WIP device-tree hacking .. nothing too serious
<chewitt>
the Exynos patchset is somewhat derived from the Hardkernel images
<chewitt>
I'm not convinced half of the patches are required
<chewitt>
my personal problem is that i'm not a coding developer, so figuring out what's essential vs. random garbage is hard
<chewitt>
most of the Exynos patches have subject lines and zero description, so if you can't read the code it's not simple
<chewitt>
my personal mission will be to have a minimal patchset that supports Kodi with hardware decode working