ChanServ changed the topic of #linux-msm to:
rmsilva- has joined #linux-msm
rmsilva has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
zstas_ has joined #linux-msm
mripard has joined #linux-msm
loki6660 has joined #linux-msm
loki666 has quit [Ping timeout: 480 seconds]
pespin has joined #linux-msm
ungeskriptet has quit [Read error: Permission denied]
ungeskriptet has joined #linux-msm
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet has joined #linux-msm
<loki6660> Hi, I'm trying to get an unknown panel working on a sm8550. I'm pretty sure I have the timings, init seq correct and various regulator correct, but it still doesn't display anything... I can see some dsi_err_worker: status=5 and dsi_err_worker: status=4 in the logs
<loki6660> looking at the Android DTS this panel seems to require some panel register read for ESD checking... could that be the reason why it's not working ?
<loki6660> also: the panel seems to flash for a split second during probe
loki6660 has quit []
loki666 has joined #linux-msm
<krzk> loki666: reset gpios? or their polarity? any errors from MDSS DRM (with drm.debug)?
<krzk> and which kernel...
<loki666> I think my reset-gpios are aslo correct, and I tried to swap the polarity and the reset sequence... doesn't change... I'm on 6.15.2, but tried 6.16-rc4 also
<loki666> which flag for drm.debug ?
<loki666> 0x3 ?
<loki666> the only difference I see from other working panels is the qcom,esd-check-enabled; and qcom,mdss-dsi-panel-status-check-mode = "reg_read";
Daanct12 has quit [Quit: WeeChat 4.6.3]
<sgerhold> loki666: have you used the panel driver generator?
<loki666> sgerhold: yes
<loki666> some gpio should be exposed as regulators... but that's for when it will be working
<sgerhold> I've seen plenty of panels with ESD stuff in downstream, but not a single one needed that to be working on mainline
<sgerhold> So I doubt that's it
<loki666> so there is still hopes...
<sgerhold> There is some funkyness with display handover from the bootloader sometimes, you might need to experiment a bit with making DRM MSM a module and/or builtin and/or clk_ignore_unused
<sgerhold> I've seen all of these cause dsi errors in some situations
<loki666> I'll try that
<loki666> drm.debug=0x3 is flooding my dmesg... I can't get the top
<sgerhold> log_buf_len=?
<loki666> sgerhold: ok, what am I looking for ?
<sgerhold> I don't know, you wanted to run with drm.debug 😅
<loki666> arf... krzk asked me... here is the log https://gist.github.com/loki666/4dc2f22083dc6f0974fcd7cc27cef583
krzk has quit [Ping timeout: 480 seconds]
zstas_ has quit [Ping timeout: 480 seconds]
<loki666> sgerhold: with/without clk_ignore built-in or module doesn't change anything
krzk has joined #linux-msm
zstas_ has joined #linux-msm
danylo has quit [Quit: Ping timeout (120 seconds)]
danylo has joined #linux-msm
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
pespin has quit [Remote host closed the connection]
zstas_ has quit [Ping timeout: 480 seconds]
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #linux-msm
jhovold has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Ping timeout: 480 seconds]
<loki666> sgerhold: got it! the vfp was too small bumped from 8 to 18. and voila !