<lumag>
konradybcio, look for msm_mpm_timer_write(). I think on rb1 we are hitting the same story as we had on RPMh devices: all the cores are down and are not woken up properly.
<konradybcio>
Alright I'll look into it after classes
<Marijn[m]>
<Adrian[m]> "> <@marijns95:matrix.org> In..." <- Doublecheck the init sequence, pinctrl, and power, and set the brightness in prepare as I suggested before? Not getting anything on the screen, but also not getting timeouts is not something that is going to be fixed by implementing 10-bpc. I'd expect colorful corruption (or a working panel if it reads the bit depth from PPS) if bpc is wrong at least, it might be something else that got
<Marijn[m]>
broken
<lumag>
konradybcio, there is no pressure, I worked around it by disabling cluster sleep
<konradybcio>
lumag functional cpuidle would be nice though!
<Fekz115>
And ofcourse corrupted image when I set bpc to 8
andrey-konovalov has quit [Quit: ZNC - http://znc.in]
Fekz115 has quit [Quit: Konversation terminated!]
mripard_ has joined #linux-msm
mripard has quit [Ping timeout: 480 seconds]
mripard_ has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Quit: WeeChat 4.1.2]
mripard has joined #linux-msm
animist has quit [Ping timeout: 480 seconds]
andrey-konovalov has joined #linux-msm
<Adrian[m]>
worthing noting that the spacewar panel has `qcom,mdss-dsi-bpp = <24>;` while cupid has 30, which downstream translates to `MIPI_DSI_FMT_RGB888` and `MIPI_DSI_FMT_RGB101010` in downstream as far as I remember. I think the panels aren't as similar as it seems
<Adrian[m]>
s/in downstream//
animist has joined #linux-msm
<Adrian[m]>
s/worthing/worth/, s/in downstream//
mripard has quit [Remote host closed the connection]