ChanServ changed the topic of #linux-msm to:
Danct12 has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
jhovold has joined #linux-msm
Daanct12 has quit [Quit: Leaving]
jhovold has quit [Ping timeout: 480 seconds]
<aka_[m]> Any idea why pil returns -22 on firmware?
<aka_[m]> i just cannot get venus firmware to load
<aka_[m]> when i provide venus.mdt it gives:
<aka_[m]> error -22 initializing firmware venus.mdt
<aka_[m]> for venus-v1.mdt it just crash without saying anything about firmware alocation.
<Marijn[m]> lumag_: Are dispcc/dsi clocks known to not work with `fw_devlink`? On our sm6125 Seine platform I get a `disp_cc_mdss_pclk0_clk_src: rcg didn't update its configuration.` followed by indefinite DPU timeouts if I don't set `fw_devlink=false`.
<Marijn[m]> Perhaps I just missed a clock dependency somewhere
<Mis012[m]> my favorite missed clock dependencies are AHB hangs which TZ helpfully interprets as "guess you wanted a zero context shutdown"
<Mis012[m]> why is the timeout hw there again? so you can RECOVER...
<Mis012[m]> yet again clearly miscommunication between hw and sw departments at qcom...
Danct12 has quit [Quit: Quitting]