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

5.1 Overview

This section describes the 4CC Tasks defined by the PD Controller Host Interface. The Tasks are categorized into various sub-groups in this section. All Tasks that return data using the DATAx registers will always ensure the proper output data is loaded into those registers before setting the CMDx register to 0 to indicate Task completion. DATAx is never modified by PD Controller after CMDx has been changed to 0, to ensure the Host can retrieve data from the previously-executed Task, and to ensure the Host can load these registers for a future Task without risk of overwriting. Note that other registers can continue to be updated after a Task completes, as Tasks can have additional side effects.

Many of the Tasks return a status code in the first byte of the DATAx register. The standard Task response byte is defined in Table 5-1. The remaining DATAx bytes can be used at each Task's discretion.

Table 5-1 Standard Task Response
DescriptionTasks are a special form of Tasks that return a status code in the first byte of the DATAX register.
Output DATAXBitNameDescription
Byte 1: Task Return Code
7:4ReservedReserved for standard Tasks. May be used by certain Tasks for Task-specific return codes. Successful return codes can use this byte provided TaskResult is 0x0.
3:0TaskResultStandard Task return codes.
0x0Task completed successfully.
0x1Task timed-out.
0x2Reserved.
0x3Task rejected.
0x4Task rejected because the Rx Buffer was locked. This is for Tasks that can require the PD controller to use the Rx Buffer.
0x5-0xFReserved for standard Tasks. May be used by certain Tasks for Task-specific error codes. Treated as an error when encountered.