NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/| paste logs in https://pastebin.ubuntu.com/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
florian has quit [Ping timeout: 276 seconds]
vigneshr has joined #linux-ti
crabbedhaloablut has joined #linux-ti
ikarso has joined #linux-ti
Kubu_work has joined #linux-ti
minash has quit [Remote host closed the connection]
minash has joined #linux-ti
florian has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
<NishanthMenon> aradhya7: it was rahul ravikumar and me
<NishanthMenon> aradhya7: https://github.com/nmenon/linux-2.6-playground/commits/beagle-ai64-dsi-rebase wip branch i could find.. older history is there somewhere.. but it was a mess
<pivi> wow, I have a super weird behavior. not sure if you remember me reporting issue with audio/i2c with mainline linux
<pivi> [ 494.675445] omap_i2c 20010000.i2c: controller timed out
<pivi> [ 494.680764] wm8904 1-001a: ASoC: error at snd_soc_component_update_bits on wm8904.1-001a for register: [0x00000004] -
<pivi> stuff like that
<pivi> today is mainline friday and I am looking how v6.7-rc2 looks like
<pivi> and it seems that this issue appear/disappear depending on me applying or not a specific DT overlay
florian_kc has quit [Quit: Ex-Chat]
<pivi> this specific overlay is doing a few things, that seems all unrelated. no change on bus speed or anything else, the only relevant thing it does is to add another device on that specific i2c bus
<pivi> mumble, could it be that this freaking i2c device, when not initialized is messing up with the I2C bus ?!
florian has quit [Ping timeout: 260 seconds]
<pivi> nope, removing the physical device does not solve the situation
<aradhya7> NishanthMenon: thanks! got what I was looking for from your tree!
<pivi> ok, TI 6.1 downstream kernel is not affected by this issue. I would exclude the HW therefore. anyway, ....
Kubu_work has quit [Quit: Leaving.]
florian has joined #linux-ti
florian has quit [Ping timeout: 256 seconds]
<jluthra> pivi: hmm i2c has been cursed in the past for some camera sensors for me
<jluthra> but given that you are seeing this with audio tests, and not seeing on ti 6.1, I wonder if this is due to the known bug with recording causing lockups
<jluthra> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.1.y-cicd&id=f53378ff892b70c24ee6a0364ae94b690b70d11d this is a hack workaround in ti 6.1, have not been able to upstream it yet as need hw team to debug/root cause
florian has joined #linux-ti
<NishanthMenon> i have also noticed https://gist.github.com/nmenon/e2a2eeac938efc1d65dd4a33213fb082#file-am62-sk-L935 -> but only appears around the i2c mux thingy that TI SKs have..
<NishanthMenon> and is very intermittent
ikarso has joined #linux-ti
mripard has quit [Quit: mripard]
Kubu_work has joined #linux-ti
crabbedhaloablut has quit []
Kubu_work has quit [Quit: Leaving.]