When interrupt (GPI/GPO) capability and I2C are used together they can interfere. Here's how to avoid that
Q: Why does I2C conflict with GPI on GMSL1 devices.
A: Most signals on GMSL1 part, such as: video, audio and I2C; travel from serializer to deserializer. Signals traveling in the direction from deserializer to serializer include I2C and GPI/GPO (often used as an interrupt signal). They use the same transmission path and can conflict (even if the programming of these parts is correct). The way to avoid conflict is to disable GPI while sending I2C data, and not send I2C while you're expecting GPI. To make sure you don't lose a GPI transition, you can read GPI and send it using I2C before re-enabling it.