SPMU380 July   2026 TPS25730A

 

  1.   1
  2. 1Read This First
    1. 1.1 About This Manual
    2. 1.2 Notational Conventions
    3. 1.3 Glossary
    4. 1.4 Related Documents
    5. 1.5 Support Resources
    6. 1.6 Trademarks
  3. 2Introduction
    1. 2.1 Purpose and Scope
    2. 2.2 PD Controller Host Interface Description
      1. 2.2.1 Overview
    3. 2.3 Unique Address Interface
      1. 2.3.1 Unique Address Interface Protocol
  4. 3PD Controller Policy Modes
    1. 3.1 Overview
    2. 3.2 Sink Policy Mode
  5. 4Register Overview
    1. 4.1 TPS25730A Registers
  6. 54CC Task Detailed Descriptions
    1. 5.1 Overview
    2. 5.2 PD Message Tasks
      1. 5.2.1 'GSrC' - PD Get Source Capabilities
      2. 5.2.2 'GPPI' - PD Get Port Partner Information
      3. 5.2.3 'MBRd' - Message Buffer Read
    3. 5.3 System Tasks
      1. 5.3.1 'ANeg' - Auto Negotiate Sink Update
      2. 5.3.2 'DBfg' - Clear Dead Battery Flag
  7. 6User Reference
    1. 6.1 AUTO_NEGOTIATE_SINK Register
      1. 6.1.1 AUTO_NEGOTIATE_SINK Usage Example 1
      2. 6.1.2 AUTO_NEGOTIATE_SINK Usage Example 2
      3. 6.1.3 AUTO_NEGOTIATE_SINK Usage Example 3
      4. 6.1.4 AUTO_NEGOTIATE_SINK Usage Example 4
  8. 7Revision History

TPS25730A Registers

Table 4-1 lists the memory-mapped registers for the TPS25730A registers. All register offset addresses not listed in Table 4-1 should be considered as reserved locations and the register contents should not be modified.

Table 4-1 TPS25730A Registers
OffsetAcronymRegister NameSection
8hCommand Register (CMD1) for I2CtCommand Register (CMD1) for I2CtSection 4.1.1
9hData Register (DATA1) for CMD1Data Register (DATA1) for CMD1Section 4.1.2
1AhStatusStatusSection 4.1.3
26hPower Path StatusPower Path StatusSection 4.1.4
30hReceived Source CapabilitiesReceived Source CapabilitiesSection 4.1.5
33hTransmit Sink CapabilitiesTransmit Sink CapabilitiesSection 4.1.6
34hActive PDO ContractActive PDO ContractSection 4.1.7
35hActive RDO ContractActive RDO ContractSection 4.1.8
37hAutonegotiate SinkAutonegotiate SinkSection 4.1.9
40hPD StatusPD StatusSection 4.1.10

Complex bit access types are encoded to fit into small table cells. Table 4-2 shows the codes that are used for access types in this section.

Table 4-2 TPS25730A Access Type Codes
Access TypeCodeDescription
Read Type
RRRead
Write Type
WWWrite
Reset or Default Value
-nValue after reset or the default value

4.1.1 Command Register (CMD1) for I2Ct (Offset = 8h) [Reset = 00000000h]

Command Register (CMD1) for I2Ct is shown in Table 4-3.

Return to the Summary Table.

Command register. The PD Controller clears it on initialization and after completing a command.

Table 4-3 Command Register (CMD1) for I2Ct Field Descriptions
BitFieldTypeResetDescription
31-0CommandR/W0h Command register for the command interface. The PD Controller clears this register to 0x0 on initialization and after completing any recognized commands. Unrecognized commands are overwritten with !CMD.

4.1.2 Data Register (DATA1) for CMD1 (Offset = 9h) [Reset = 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000h]

Data Register (DATA1) for CMD1 is shown in Table 4-4.

Return to the Summary Table.

Data register (DATA1) for the command interface (CMD1).

Table 4-4 Data Register (DATA1) for CMD1 Field Descriptions
BitFieldTypeResetDescription
511-0DataR/W0h Data register (DATA1) for the command interface (CMD1). The first byte of this register will contain the return code if applicable, and the remaining bytes will contain the command's output

4.1.3 Status Register (Offset = 1Ah) [Reset = 0000000000h]

Status is shown in Table 4-5.

Return to the Summary Table.

Status bit field for events.

Table 4-5 Status Register Field Descriptions
BitFieldTypeResetDescription
39-26RESERVEDR0h
25-24Acting as LegacyR0h Indicates when PD Controller has gone into a mode where it is acting like a legacy (non PD) device. It can take approximately 10 seconds for the PD controller to determine that it is attached to a legacy source or sink.
  • 0h = PD Controller is not in a legacy (non PD) mode
  • 1h = PD Controller is acting like a legacy sink
  • 3h = Acting as legacy sink due to dead-battery.
23-22RESERVEDR0h
21-20VBUS StatusR0h Indicates the present state of VBUS.
  • 0h = At vSafe0V (less than 0.8V)
  • 1h = At vSafe5V (4.75V to 5.5V)
  • 2h = Within expected limits
  • 3h = Not within any of the other specified ranges
19-7RESERVEDR0h
6Data RoleR0h PD controller data role. This is only valid once there is a connection.
  • 0h = Upward-facing port (UFP)
5Port RoleR0h Current state of PD Controller CCx terminations. This also indicates the PD Controller Power Role, once connected. This bit does not toggle during Unattached state transitions.
  • 0h = PD Controller is in the Sink role
4Plug OrientationR0h Plug orientation indicator. Indicates port orientation when known (requires connection).
  • 0h = Upside-up orientation (plug CC on CC1)
  • 1h = Upside-down orientation (plug CC on CC2)
3-1Connection StateR0h Details of a connected plug.
  • 0h = No connection
  • 1h = Port is disabled
  • 2h = Corrosion Mitigaion (Ra/Ra)
  • 3h = Debug connection (Rd/Rd)
  • 4h = No connection Ra detected (Ra but no Rd)
  • 5h = Debug connection (Rp/Rp)
  • 6h = Connection present no Ra detected
  • 7h = Connection present Ra detected
0Plug PresentR0h Status of the plug
  • 0h = No plug is connected
  • 1h = A plug is connected

4.1.4 Power Path Status Register (Offset = 26h) [Reset = 0000000000h]

Power Path Status is shown in Table 4-6.

Return to the Summary Table.

Power Path Status. This is a hardware dependent register.

Table 4-6 Power Path Status Register Field Descriptions
BitFieldTypeResetDescription
39-38Power SourceR0h Indicates current PD Controller power source. NOTE: Since the Dead Battery flag forces PD Controller to be powered from VBUS, only 10b is valid when this flag is set. Any other setting indicates that the Dead Battery flag is not set.
  • 0h = Reserved
  • 1h = PD Controller is powered from VIN_3V3
  • 2h = PD Controller is powered from VBUS
  • 3h = Reserved
37-21RESERVEDR0h
20-18RESERVEDR0h
17-15RESERVEDR0h
14-12PP3 SwitchR0h Indicates current state of PP3 (PP_EXT).
  • 0h = PP3 switch disabled
  • 1h = PP3 switch currently disabled due to fault
  • 3h = PP3 switch enabled (system input)
11-0RESERVEDR0h

4.1.5 Received Source Capabilities Register (Offset = 30h) [Reset = 0000000000000000000000000000000000000000000000000000000000h]

Received Source Capabilities is shown in Table 4-7.

Return to the Summary Table.

Received Source Capabilties. This register stores latest Source Capabilities message received over BMC.

Table 4-7 Received Source Capabilities Register Field Descriptions
BitFieldTypeResetDescription
231-200Source PDO 7R0h Seventh Source Capabilities PDO received
199-168Source PDO 6R0h Sixth Source Capabilities PDO received
167-136Source PDO 5R0h Fifth Source Capabilities PDO received
135-104Source PDO 4R0h Fourth Source Capabilities PDO received
103-72Source PDO 3R0h Third Source Capabilities PDO received
71-40Source PDO 2R0h Second Source Capabilities PDO received
39-8Source PDO 1R0h First Source Capabilities PDO received
7-3RESERVEDR0h
2-0Number Valid PDOsR0h Number of valid SPR PDOs in this register. Each PDO is 4 bytes. (max of 7)

4.1.6 Transmit Sink Capabilities Register (Offset = 33h) [Reset = 0000000000000000000000000000000000000000000000000000000002h]

Transmit Sink Capabilities is shown in Table 4-8.

Return to the Summary Table.

Sink Capabilities for sending. This register stores PDOs for outgoing Sink Capabilities USB PD messages. The PD controller transmits the contents of this register as a Sink_Capabilities message after receiving a Get_Sink_Cap message unless its configuration or USB PD rules require a different response in the context. Each PDO in this TX_SINK_CAPS register follows the definition from the USB PD specification. For more details on the meaning of each field refer to the USB PD specification.

Table 4-8 Transmit Sink Capabilities Register Field Descriptions
BitFieldTypeResetDescription
231-200TX Sink PDO 7R/W0h SPR Seventh Sink Capabilities PDO contents.
199-168TX Sink PDO 6R/W0h SPR Sixth Sink Capabilities PDO contents.
167-136TX Sink PDO 5R/W0h SPR Fifth Sink Capabilities PDO contents.
135-104TX Sink PDO 4R/W0h SPR Fourth Sink Capabilities PDO contents.
103-72TX Sink PDO 3R/W0h SPR Third Sink Capabilities PDO contents.
71-40TX Sink PDO 2R/W0h SPR Second Sink Capabilities PDO contents.
39-8TX Sink PDO 1R/W0h SPR First Sink Capabilities PDO contents.
7-3RESERVEDR0h
2-0Number Valid PDOsR/W2h Number of valid PDOs in this register. Each PDO is 4 bytes. (max of 7)

4.1.7 Active PDO Contract Register (Offset = 34h) [Reset = 000000000000h]

Active PDO Contract is shown in Table 4-9.

Return to the Summary Table.

Power data object for active contract. This register stores PDO data for the current explicit USB PD contract, or all zeroes if no contract.

Table 4-9 Active PDO Contract Register Field Descriptions
BitFieldTypeResetDescription
47-42RESERVEDR0h
41-32First PDO Control BitsR0h Contains PDO specific information of the first PDO. It does not matter which PDO was selected, this field is always drawn from the first PDO.
31-0Active PDOR0h Power data object. This field contains the contents of the PDO requested by PD controller as sink and accepted by source, once it is accepted by source.

4.1.8 Active RDO Contract Register (Offset = 35h) [Reset = 00000000h]

Active RDO Contract is shown in Table 4-10.

Return to the Summary Table.

Power data object for the active contract. This register stores the RDO of the current explicit USB PD contract, or all zeroes if no contract.

Table 4-10 Active RDO Contract Register Field Descriptions
BitFieldTypeResetDescription
31-28Object PositionR0h Corresponding PDO location in the Source_Capabilities Message.
27Give Back FlagR0h When set, the device will respond to a GotoMin message by reducing its load to minimum operating current
26Capabality MissmatchR0h Set when Source cannot satisfy the Sink's power or voltage requirements per Souce Capabilities
25USB Communication CapableR0h When set, the device has USB data lines and is capable of communicating using USB2, USB3 or USB4 protocols
24No USB SuspendR0h This flag is used to indicate what actions are taken in USB Suspend.
23Unchunked SupportedR0h When set, the port supports chunked and unchucked messagse.
22-20RESERVEDR0h
19-10Operating CurrentR0h Operating current (10mA per LSB)
9-0Max Min Operation CurrentR0h Shall be assigned same as Operating Current field

4.1.9 Autonegotiate Sink Register (Offset = 37h) [Reset = 0000000000000036h]

Autonegotiate Sink is shown in Table 4-11.

Return to the Summary Table.

Configuration for sink power negotiations. This register defines the voltage range between which the system can function properly, allowing the PD Controller to negotiate its own contracts. The register is set by any power up settings and overwritten by customer configurations or MCU.

Table 4-11 Autonegotiate Sink Register Field Descriptions
BitFieldTypeResetDescription
63-62RESERVEDR0h
61-52Auto Neg Capabilities Mismatch PowerR/W0h Capabilities Mismatch Power Threshold. If the selected PDO offers less power than what is specified in this register, then the PD controller will assert the Capability Mismatch bit in its Request message unless NoCapabilityMismatch is set to 1. (250mW per LSB)
51-42Auto Neg Min VoltageR/W0h Minimum voltage to request. During PD power contract negotiation, the PD controller will only select voltages that are greater than or equal to the value specified in this field. Not used unless AutoComputeSinkMinVoltage=0. (50mV per LSB)
41-32Auto Neg Max VoltageR/W0h Maximum voltage to request. During PD power contract negotiation, the PD controller will only select voltages that are less than or equal to the value specified in this field. Not used unless AutoComputeSinkMinVoltage=0. (50mV per LSB) See description in AutoComputeSinkMinPower.
31-22Auto Neg Sink Min Required PowerR/W0h Minimum operating power required by the Sink. The PD Controller will always attempt to receive this power level from the Source. (250mW per LSB)
21-12Auto Neg Max CurrentR/W0h Maximum current to request. The PD controller will not request more current than indicated by this field. The host should ensure that the max current for all PDO's in the TX_SINK_CAPS register do not exceed this value. (10mA per LSB).
11-8RESERVEDR0h
7RESERVEDR0h
6Auto Disable Sink Upon Capability MismatchR/W0h Sink path and capability mismatch settings. If this bit is asserted, then any time the implicit or explicit power contract would cause the Capability Mismatch bit to be set the PD controller will disable the sinking path. This bit should only be asserted if the NoCapabilityMismatch bit is set to 0.
5Auto Compute Sink Max VoltageR/W1h Configuration for maximum voltage. The PD controller can automatically compute ANMaxVoltage, or allow the host to specify it.
  • 0h = Provided by host
  • 1h = Computed by PD controller
4Auto Compute Sink Min VoltageR/W1h Configuration for minimum voltage. The PD controller can automatically compute ANMinVoltage, or allow the host to specify it.
  • 0h = Provided by host
  • 1h = Computed by PD controller
3No Capabality MismatchR/W0h Configuration for capability mismatch in RDO. There is one conditions that will trigger a capability mismatch:
  • If the attached source does not offer a PDO whose power is greater or equal to the ANSinkCapMismatchPower field in this register.
If the condition is true, then the PD controller will assert the capability mismatch bit in its request unless this bit is asserted.
  • 0h = Capabiltiy mismatch enabled
  • 1h = Capability mismatch disabled.
2Auto Compute Sink Min PowerR/W1h Minimum power sink requires. The minimum sink power is the largest power reported in any valid PDO in the TX_SINK_CAPS (0x33). The power for a particular PDO from the TX_SINK_CAPS follows for each supply type:
  • Battery Supply: OperatingPower
  • Variable Supply: MaxVoltage*OperatingCurrent
  • Fixed Supply: Voltage*OperatingCurrent.
However, if the TX_SINK_CAPS register includes Battery supply type PDO(s), then ANSinkMinRequiredPower = maximum OperatingPower in a Battery supply type PDO.
  • 0h = Provided by host
  • 1h = Computed by PD controller
1No USB SuspendR/W1h Value used for the NoUSBSusp Flag in the RDO. This is as defined by USB PD.
0Auto Neg RDO PriorityR/W0h Configuration for tie-breaker in PDO selection. The PD controller will find the set of PDOs that fulfill the voltage requirements. From that set of PDOs it will pick the one with higher power. If two acceptable PDOs have the same power, Fixed Supply Type is preferred, and then Variable Supply has second preference. If two PDOs have the same power and the same type, then this bit determines which PDO is selected.
  • 0h = Higher voltage
  • 1h = Lower voltage

4.1.10 PD Status Register (Offset = 40h) [Reset = 00000000h]

PD Status is shown in Table 4-12.

Return to the Summary Table.

Status of PD and Type-C state-machine. This register contains details regarding the status of PD messages and the Type-C state machine.

Table 4-12 PD Status Register Field Descriptions
BitFieldTypeResetDescription
31-28RESERVEDR0h
27-22Error Recovery DetailsR0h Reason for Error Recovery
  • 0h = reset value: no error recovery
  • 3h = System: fault input GPIO was asserted
  • 4h = System: Over-voltage detected on the Px_VBUS pin
  • 8h = System: OVP on CC detected
21-16Hard Reset DetailsR0h Reason for Hard Reset
  • 0h = Reset value no hard reset
  • 1h = Received from Port Partner
  • 2h = Requested by host
  • 3h = DR_Swap Message is a received when there is an active mode between the port-partners
  • 4h = The source output voltage failed to settle at vSrcNew within tSrcSettle during high-low voltage transition. Applicable only when the port role is SRC
  • 6h = The port-partner did not respond to SoftReset message with Accept within tSenderResponse time
  • 7h = The port-partner did not respond to Request message with Accept within tSenderResponse time
  • 8h = The port-partner did not respond to Accept message with PS_RDY within tPSTransition time
  • 9h = The port-partner did not send Source_Capabilities message for a duration of tTypeCSinkWaitCap after presenting VBUS
  • Ah = The port-partner did not respond to SoftReset messsage after nRetryCount attempts
  • 11h = An unexpected message is received during power transitions
15-13RESERVEDR0h
12-8Soft Reset DetailsR0h Reason for Soft Reset
  • 0h = Reset value no soft reset
  • 1h = Soft reset received from Port Partner
  • 2h = Reserved
  • 3h = Reserved
  • 4h = Received source capabilities message was invalid
  • 6h = Received an accept message unexpectedly
  • 7h = Received a control message unexpectedly
  • 8h = Received a GetSinkCap message unexpectedly
  • 9h = Received a GetSourceCap message unexpectedly
  • Ah = Received a GotoMin message unexpectedly
  • Bh = Received a PS_RDY message unexpectedly
  • Ch = Received a Ping message unexpectedly
  • Dh = Received a Reject message unexpectedly
  • Eh = Received a Request message unexpectedly
  • Fh = Received a Sink Capabilities message unexpectedly
  • 10h = Received Source Capabilities message unexpectedly
  • 11h = Received a Swap message unexpectedly
  • 12h = Received a Wait Capabilities message unexpectedly
  • 13h = Received an unknown control message
  • 14h = Received an unknown data message
  • 17h = Received an Extended message unexpectedly
  • 18h = Received an unknown Extended message
  • 19h = Received a data message unexpectedly
  • 1Ah = Received a Not Supported message unexpectedly
  • 1Bh = Received a Get_Status message unexpectedly
7RESERVEDR0h
6Present PD RoleR0h Present PD power role. The PD Controller is acting under this PD power role.
  • 0h = Sink
5-4Port TypeR0h Present Type-C power role. The PD Controller is acting under this Type-C power role.
  • 1h = Sink
3-2CC PullupR0h CC Pull-up value. The pull-up value detected by PD Controller when in CC Pull-down mode.
  • 0h = Not in CC pull-down mode / no CC pull-up detected
  • 1h = USB Default current
  • 2h = 1.5 A (SinkTxNG)
  • 3h = 3.0 A (SinkTxOK)
1-0RESERVEDR0h