USB-C Power Delivery Overview
summary
Explains concrete implementation details: a Zephyr USB‑C subsystem thread with a type‑C state machine, protocol layer and policy engine; reliance on separate TCPC chips or TCPCI‑compatible drivers to handle the PHY encoding and good CRC within 1 ms timing; PD contract flow (source capabilities → request → ACCEPT → PS_RDY) and support for PD 3.1 features including role swaps and up to 240 W. Reports real test boards (Chromebook ECs, Honeybuns, STM demo), notes some TCPCs require software CRC generation while many handle it in hardware.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:41USB Type-C Terms and Abbreviations
- 1:56USB Type-C Connector Prs Receptacle
- 3:44Starting a USB-C Connection
- 4:54Example CC Voltages
- 5:29Completing the USB-C Connection
- 7:36PD Terms and Abbreviations
- 8:29PD Messaging
- 9:23PD Contract Negotiation
- 11:20What can a PD connection do?
- 12:36Port Roles in PD
- 14:25USB-C Subsystem Terms and Abbreviations
- 15:23USB-C Thread Layers
- 16:50Device Policy Manager
- 17:48Thread Interactions
- 22:20Example - Initial Contract Negotiation as a Sink
related talks
31mOverview of CAN Subsystem in Zephyr
13mMaking PCI devices ready for confidential computing
43mOCPP: Zephyr RTOS as Electric Vehicle Supply Equipment(EVSE)
27mPCI device authentication & encryption
27mCharging a Battery with Zephyr
31mAdding Support for Power Over Ethernet (PoE or IEEE Clause 33) to Linux Network Stack
18mμUSB: Practical and Safe USB Driver Reuse for Arm TrustZone
Harmonic: Hardware-assisted RDMA Performance Isolation for Public Clouds