Team, a customer experienced an issue with rapid connect/disconnect causing a TPS65986 chip RESET/re-boot, during which time it asserted I2C_IRQZ. Due to a SW Driver complication they think they've now overcome (the driver keeps repeatedly reading/processing IntEventX and writing to IntClearX register expecting I2C_IRQZ to de-assert), they initially saw a lock-up in this condition with I2C_IRQZ asserted, and could not recover without disconnecting again to cycle.
Just wondering if this is expected that rapid connect/disconnect could/should cause RESET condition, and I2C_IRQZ to assert.... and what might be the underlying root-cause to ensure their fix will handle appropriately to avoid the unwanted lock-up initially experienced. Thank you.
