ChanServ changed the topic of #linux-msm to:
hexdump01 has joined #linux-msm
hexdump0815 has quit [Ping timeout: 480 seconds]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Quit: Konversation terminated!]
Caterpillar has joined #linux-msm
jacobk_ has joined #linux-msm
jacobk is now known as Guest15608
jacobk_ is now known as jacobk
Guest15608 has quit [Ping timeout: 480 seconds]
<Tooniis[m]> I ran freqbench on msm8996
<Tooniis[m]> i think something is wrong with cpu clock driver
<Tooniis[m]> for lower freqs pll isnt being divided maybe
<Tooniis[m]> effective freq becomes double of intended
<Tooniis[m]> would that mean for power cluster at 1440MHz we're overclocking to 2880 without realizing it?
<aka_[m]> check debugcc
<aka_[m]> of apcs-mux-c0/c1
zstas has joined #linux-msm
<Tooniis[m]> so its fine?
zstas has quit [Ping timeout: 480 seconds]
svarbanov__ has joined #linux-msm
<Tooniis[m]> idk whether to trust debugcc or coremark results
<Tooniis[m]> lumag: any idea on this?
leo60228 has joined #linux-msm
<leo60228> i have a qualcomm chromebook with an hdr panel (homestar, it's explicitly advertised as hdr-capable in marketing)
<leo60228> unfortunately the mainline drivers as used in chromiumos (and my nixos install).... don't support DP colorspace info
<leo60228> i've thought about trying to build the downstream drm drivers as used in android which do appear to have support for this, is there any chance of getting that to work or is trying to use them on a non-android device a fool's errand?
zstas has joined #linux-msm
zstas has quit [Ping timeout: 480 seconds]
<lumag> Tooniis[m]: on 8996 sometimes there can be an issue with the clock, but I've mostly seen it underclocking, not overclocking
<lumag> I will try to get a timeslot to debug that
Caterpillar has quit [Quit: Konversation terminated!]
Caterpillar has joined #linux-msm