Other Parts Discussed in Thread: TUSB1146
I have an issue with the TPS65987D setting up the TUSB1146 before it has power.
I have a custom system that uses the TUSB1146 in conjunction with TPS65987D. There are two power supplies, USB-C via the TPS65987D, and a wall supply. TPS65987D I2C communication with TUSB1146 works great except for one detail... the TUSB1146 is powered by downstream power supplies (that are turned on via a mechanical switch) while the TPS65987D is powered by its own 3V3 LDO. Basically, TUSB1146 gets set up properly when plugging USB C device if I'm using wall power and the system is already on. But if I'm powering with USB C, then the TPS65987D issues the I2C commands as soon as the TPS65987D detects the cable insertion. But the TUSB1146 isn't on yet as it is still waiting for the downstream 3V3 rail to come up.
I'm trying to find a way to input the downstream 3V3 to a GPIO input to trigger I2C events again. Something like using a GPIO to perform a power on reset but there isn't that input for GPIO. There doesn't quite seem to be the right combination between the GPIO mapped events and I2C trigger events. But maybe I'm not thinking creatively enough. FYI I'm not using any alt modes and currently use the "Cable Attach CC_x PD" trigger events to send I2C commands.
Any suggestions?