Related to https://e2e.ti.com/support/interface/f/138/t/923688
Our device with tps65982 is configured as a dp-alt-mode source (DFP_D) on a dual role port (usually acting as a power sink to get charged). When plugging an of the shelf USB-C to HDMI adapter into our device the tps65982 in our device negotiates DP alt mode successfully (verified by data status register 0x5f) and DP sid status (0x58) however DPStatusRX in 0x58 never changes the HPD state (Bit 7) also GPIO4 is never asserted. I have no PD analyzer at hand so here's what i figured out by looking at registers when I2C_IRQ1 triggers (i've enabled all bits in that register):
0.) I'm seeing data status and status changes
1.) I'm seeing DRSwapComplete
2.) I'm seeing DiscoverModesComplete and VDMReceived with 2 VDOs: (0xff018043, 0x00000c05)
3.) I'm seeing VDMReceived with 1 VDO: 0xff018151
If I read that correctly step 2.) is the responders ack of the our DFP_D's discover modes. It offers one possible mode with usable pin assignment C and D. and step 3.) is the ack of the configure selecting that mode.
This matches Step 12 of the `USB PD and VESA DP Alternate Mode Flow` in your `PD Alternate Mode: DisplayPort` document. However it seems `Step 13` (self-initiated Attention message) never happens.
Can you please help with these two points:
1.) Would the UFP_D's attention message also trigger an IRQ with VDMReceived?
2.) Can you point to possible error sources why UFP_D would not send the attention message (and hence our DFP_D would not start sending DP data)?
Happy to provide configuration and schematics if that helps. Let me know where to send them.