TPS65982: Details of the behavior of Status Register(0x5f)

Hi Takashi-san,

DPModeActive and DPConnection bit have very similar function, but slightly different. The DPModeActive bit is set as soon as the DisplayPort alternate mode is entered. The DPConnection bit is set after the configuration message is sent and acknowledged within the alternate mode.

So there is a very brief period in which the DPModeActive bit is set but the DPConnection bit is not yet set, but in most situations these bits will have the same value. (It is also possible that for some reason a device would enter the mode but never send a configuration message, in which case DPModeActive would be set, but DPConnection bit would never be set. This would be unlikely, however.)

As you have said, there is some overlap between the DataStatus register (0x5F) and some other registers, primarily the DPStatus (0x58) and IntelStatus (0x59) registers. This is because the DataStatus register is defined by Intel spec for interface to Intel devices, whereas these other registers are defined by TI.

To complete your question, here are the alternate locations where your queries can be found:
-- DPPinAssignment
--> Available in 0x5F but also available in DPStatus register 0x58 configuration message, bits [72:95]

‐　DPSourceSink (Bug exist, this information is never updated at FW Version 3.10)
--> This can be determined by first reading if the device is UFP_U or DFP_U from the status register 0x1A, and then checking the first two bits of the DPConfig message from DPStatus register [72:73]. Has following translation:
00b = USB only
01b = UFP_U as DFP_D
10b = DFP_U as DFP_D
11b = reserved

‐　USB3Connection
--> I am not aware of another register where this information is presented