jacobk has joined #linux-msm
jacobk has quit [Ping timeout: 480 seconds]
jacobk has joined #linux-msm
gnuiyl_ has joined #linux-msm
gnuiyl has quit [Ping timeout: 480 seconds]
gnuiyl__ has joined #linux-msm
gnuiyl_ has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
zstas has joined #linux-msm
funderscore is now known as f_
jacobk_ has joined #linux-msm
jacobk is now known as Guest3454
jacobk_ is now known as jacobk
Guest3454 has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
gnuiyl__ has quit [Remote host closed the connection]
mripard has joined #linux-msm
pespin has joined #linux-msm
srinik has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
srinik has joined #linux-msm
<
zstas>
has anybody experienced issues with gpi_dma + geni_i2c on qcom? after some time after the startup it starts to reset itself all the time
<
zstas>
I wonder if it can be caused by buggy driver or unstable i2c device or there's something to do with gpi_dma itself
<
mani_s>
zstas, I think it is a known issue with fw
<
mani_s>
maybe lumag or vkoul know more
<
vkoul>
zstas does it happen always or sometimes..?
<
zstas>
always after some time: might be 30 seconds, might be 5-6 minutes
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
zstas has quit [Ping timeout: 480 seconds]
zstas has joined #linux-msm
animist has quit [Remote host closed the connection]
animist has joined #linux-msm
srinik has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
zstas has quit [Ping timeout: 480 seconds]