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
crabbedhaloablut has joined #linux-ti
crabbedhaloablut has quit [Read error: Connection reset by peer]
loki_val has joined #linux-ti
rob_w has joined #linux-ti
florian has joined #linux-ti
florian_kc has joined #linux-ti
loki_val has quit []
crabbedhaloablut has joined #linux-ti
crabbedhaloablut has quit [Client Quit]
crabbedhaloablut has joined #linux-ti
<pivi> following up from yesterday, it really seems that we get non-existing interrupts, we'll see if we can come-up with some self-contained example (just a simple driver, 2 gpios loopback together, one output, one input as interrupt and counting the actual interrupts received)
Kubu_work has joined #linux-ti
<NishanthMenon> pivi: what i saw on beagleboard hdmi hpd was signal noise - possibly parasitic on the pcb. debounce solved the problem.
minash has quit [Remote host closed the connection]
minash has joined #linux-ti
rob_w has quit [Remote host closed the connection]
ikarso has joined #linux-ti
rsalveti has joined #linux-ti
<javierm> the am625 SoC in the BeaglePlay is GP (General Purpose?) not HS-SE or HS-FS, am I correct ?
<bryanb> javierm: yep. it's a am625 GP SoC
<javierm> bryanb: cool, thanks for the confirmation
<pivi> NishanthMenon: ok, so this is something else. Let's see if we can provide some more details, ideally something you can reproduce on the SK or beagleplay
<pivi> One more, AM62 issues with 6.6 RC kernel, I2C and Ethernet. https://paste.debian.net/1292359/. I did not have time to look into that more carefully yet, this is just coming out straight from our CI and it looks like a regression.
<pivi> the audio code error is because of the I2C, to be ignored
florian has quit [Quit: Ex-Chat]
florian_kc has quit [Ping timeout: 246 seconds]
Kubu_work has quit [Quit: Leaving.]
florian_kc has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
<pivi> NishanthMenon: mumble, we do test also 100MBit/s ourself, and we have a different clock compared to those 2 boards. We'll have to look into that and provide mode details obviously. Thanks for the quick feedback
<NishanthMenon> np
<pivi> For what is worth, it happens after a while, not just after boot, and we do run quite some test. So it's also possible that the issue just not reproduce in your tests
<pivi> I will try to find a little time to do some more test ...
florian_kc has quit [Ping timeout: 255 seconds]
<NishanthMenon> pivi: understood. thanks
crabbedhaloablut has quit []
florian_kc has joined #linux-ti
florian_kc is now known as florian
minash has quit [Ping timeout: 240 seconds]
minash has joined #linux-ti
florian has quit [Ping timeout: 240 seconds]