ChanServ changed the topic of #linux-msm to:
irungentoo has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
irungentoo has joined #linux-msm
irungentoo has quit [Remote host closed the connection]
irungentoo has joined #linux-msm
irungentoo has quit [Remote host closed the connection]
irungentoo has joined #linux-msm
irungentoo has quit [Remote host closed the connection]
irungentoo has joined #linux-msm
junari has joined #linux-msm
junari has quit [Ping timeout: 480 seconds]
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
svarbanov__ has quit [Ping timeout: 480 seconds]
junari has joined #linux-msm
jhovold has joined #linux-msm
Caterpillar has joined #linux-msm
Caterpillar has quit [Ping timeout: 480 seconds]
Caterpillar has joined #linux-msm
Caterpillar has quit [Ping timeout: 480 seconds]
svarbanov has joined #linux-msm
<aka_[m]> this breaks wled
<aka_[m]> Unbalanced enable for IRQ 41
<Marijn[m]> That sounds like a driver bug
<aka_[m]> downstream has no ovp irq specified
<aka_[m]> krzk: if i want to adsp on soc dts and it can use msm8996 compatible should i use it straight or document and use fallback(yaml checker complain about too long compat)
<aka_[m]> at some point i believe there was saying we don;t want to grow lists anymore
<z3ntu> <aka_[m]> "Unbalanced enable for IRQ 41" <- I think this happens on most devices but the warning is not harmful really
<z3ntu> does it actually "break" or does just the warning appear?
<aka_[m]> Well there is entire opps or how you call it
<aka_[m]> For enabling ovp irq
<aka_[m]> I still have something wrong in tree because after reverting still it drops to console device
<aka_[m]> Maybe will look tomorrow into it
<aka_[m]> Way to anxious to do anything
<z3ntu> Anybody got a clue how on msm8226 (a3xx) with 6.5 everything works well, with 6.6 when I launch kmscube I just get a blank screen? Nothing unusual in dmesg or kmscube output. When rendering with llvmpipe the output shows up properly, so just freedreno-specific somehow
<z3ntu> I've also tried resetting drivers/gpu/drm/msm tree to basically v6.5 and it still doesn't work so I'm quite confused where the regression could be
<z3ntu> Huh, the only other idea I had now was some clock driver, and indeed restoring drivers/clk/qcom/clk-smd-rpm.c to v6.5 makes it work again. Will check what exact clock this is but there was some changes/cleanups there
<z3ntu> Ah I remember having seen this some months ago, RPM_SMD_OCMEMGX_CLK clock and friends were removed but they're needed. Solved now for my tree I guess but I still need to get konradybcio to tell me what a better solution is than revert that commit
<Danct12> [ 318.247336] gpi 4a00000.dma-controller: cmd: CH STOP completion timeout:0
<Danct12> [ 318.250119] gpi 4a00000.dma-controller: Error with cmd:CH STOP ret:-5
<Danct12> [ 319.271333] geni_i2c 4a88000.i2c: I2C timeout gpi flags:0 addr:0x14
<Danct12> [ 318.253166] Goodix-TS 1-0014: Error writing 1 bytes to 0x814e: -110
<Danct12> [ 319.274124] geni_i2c 4a88000.i2c: GPI transfer failed: -110
<Danct12> does anyone know why this error happens? i was adding goodix touchscreen to the device, the touch screen works but this happened shortly when playing around with it