ChanServ changed the topic of #linux-msm to:
niej_ has joined #linux-msm
<krzk> lumag: hey, logs with 0x16: https://pastebin.com/H2Stdwrr thanks for looking into this!
hexdump01 has joined #linux-msm
hexdump02 has quit [Ping timeout: 480 seconds]
<lumag> krzk: I think you have two options: either lower the mode->clock, lowering the refresh rate (it's 120 now). Or enable DSC if your panel supports DSC
<lumag> hmm, is it a bonded DSI panel?
<lumag> if so this might help too: <20250923-modeclk-fix-v2-1-01fcd0b2465a@oss.qualcomm.com
<krzk> lumag: panel has already DSC enabled. I had impression that maybe these claculations from your commit do not include DSC.
<krzk> Without DSC it could not find matching pixel clock at all.
<krzk> lumag: what is bonded panel? Like two? I don't know, honestly.
<krzk> I'll try that patch
<krzk> that patch works
<lumag> bonded panel = two DSI hosts used to drive one panel
<krzk> ah, then no, it's not the case
valpackett has joined #linux-msm
krzk has quit [Remote host closed the connection]
krzk has joined #linux-msm
<Tooniis[m]> anyone getting detected fb_set_par error, error code: -16 spammed in their kernel log?
niej_ has quit [Ping timeout: 480 seconds]
mripard has quit [Quit: WeeChat 4.7.1]