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: 244 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
crabbedhaloablut has joined #linux-ti
<pivi> Hello, currently debugging an issue in which it seems we get non existing interrupts from an I2C device, AM62 running on TI Linux 6.1. The interrupt line is just the usual GPIO with a pull-up. I could add some debouncing on the pin, however from what we can tell so far (to be confirmed) there are no glitches of any kind on the phisical signal. It seems that the SoC is inventing an additional interrupt,
<pivi> just after the real one, on some situation
<pivi> I remember about some issue on the beagleplay with the HDMI hotplug interrupt, I assumed it was a real glitch on the external signal there, and not something "invented" from the SoC. Am I wrong? Is there some known issue on this regard?
florian has joined #linux-ti
ikarso has joined #linux-ti
florian has quit [Ping timeout: 240 seconds]
florian has joined #linux-ti
florian has quit [Ping timeout: 240 seconds]
florian has joined #linux-ti
florian has quit [Ping timeout: 240 seconds]
florian has joined #linux-ti
minash has quit [Remote host closed the connection]
minash has joined #linux-ti
florian has quit [Ping timeout: 240 seconds]
<bryanb> yeah it was backported by Greg in v6.1.28... so that may not be the culprit
<pivi> bryanb: the spurious interrupt is just a gpio interrupt, not the I2C one (it happens to come from an I2C components, however)
<pivi> we'll do some more test tomorrow, maybe we are just overlooking something obvious
florian has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
crabbedhaloablut has quit []
florian has quit [Ping timeout: 240 seconds]