<jluthra>
pivi: which explains why applying that fix from ti-linux fixed this issue on your board as well
<jluthra>
pivi: i am tempted to think that the overlay is a red-herring, and if you run your arecord script multiple-times without reboot even with the overlay applied you will hit the issue again
<jluthra>
at least we reliably hit the issue with multiple arecords on SK-AM62 without that fix
mripard has quit [Remote host closed the connection]
rob_w has joined #linux-ti
mripard has joined #linux-ti
mripard has quit [Remote host closed the connection]
ikarso has joined #linux-ti
Kubu_work has joined #linux-ti
mripard has joined #linux-ti
minash has quit [Remote host closed the connection]
minash has joined #linux-ti
rsalveti has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
florian_kc has joined #linux-ti
<pivi>
jluthra: you are right, multiple arecord there.
ikarso has joined #linux-ti
<pivi>
jluthra: I agree on your comment on the overlay, however this is what I experienced in my half a hour testing.
<pivi>
in general it would be nice to have some visibility on these issues you are tracking internally
manchaw has quit [Quit: Connection closed for inactivity]
tlwoerner has quit [Ping timeout: 256 seconds]
tlwoerner has joined #linux-ti
darkapex has quit [Remote host closed the connection]
darkapex has joined #linux-ti
florian_kc has quit [Quit: Ex-Chat]
florian has joined #linux-ti
rob_w has quit [Read error: Connection reset by peer]
crabbedhaloablut has quit []
ikarso has quit [Quit: Connection closed for inactivity]