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

Notational Conventions

This document uses the following conventions.

  • Hexadecimal numbers may be shown with the suffix h or the prefix 0x. For example, the following number is 40 hexadecimal (decimal 64): 40h or 0x40.
  • Registers in this document are shown in figures and described in tables.
    • Byte convention for N bytes is 0 through (N-1) bytes.
    • Bit convention for N bits is 0 through (N-1) bits.
    • Each register figure shows a rectangle divided into fields that represent the fields of the register. Each field is labeled with its bit name, its beginning and ending bit numbers above, and its read/write properties with default reset value below. A legend explains the notation used for the properties.
    • Reserved bits in a register figure can have one of multiple meanings:
      • Not implemented on the device
      • Reserved for future device expansion
      • Reserved for TI testing
      • Reserved configurations of the device that are not supported
    • Writing nondefault values to the Reserved bits could cause unexpected behavior and should be avoided.