USB Type-C and You
summary
Spec says Type‑C is detailed — ~450 pages — and PD another ~750, and you need PD if you want more than 15 watts or alternate modes; power ranges span 5 V 100 mA up to ~245 W and VCON requirements run ~100 mV to 1.5 W. Zephyr supplies concrete tooling: create a device tree connector node, implement three policy callbacks and register a DPM. Walkthrough shows exact PD message flow (SET_SOURCE_CAP, RDO, PS_READY) and two working Zephyr samples for BG747E and STM32G081B.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:58Port Role Recap
- 3:25Accessing the Specifications
- 4:39Roles: Which of these USB Type-C states apply to me?
- 8:44Roles: Do I have to source Vconn?
- 11:21Do I need Power Delivery support?
- 12:14Which PD messages do I have to support?
- 14:30Three Steps to create a USB Type-C Device
- 15:00Zephyr's USB Type-C Port perspective
- 15:15Devicetree USB Type-C Sink Port description
- 15:49Type-C Port Controller (TCPC) Driver
- 16:15VBUS Driver
- 17:38Minimum Sink Policy Callbacks
- 17:59Power Delivery Negotiation (Step 1)
- 18:55Power Delivery Negotiation (Step 2)
- 19:44Power Delivery Negotiation (Step 3)
- 20:28Power Delivery Negotiation (Step 4)
- 21:50Power Role Swap to Source
- 22:58Register the Application's data structure
- 23:22Start the Zephyr USB Type-C stack
- 23:46Zephyr USB Type-C Boards
related talks
45mUSB Support in Zephyr OS
36mUSB Support in Zephyr OS
43mDebugging USB Type-C Power Delivery: Beauty and the Beast
13mKeynote: Towards an Industry-Standard EC
41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con
30mZXDH DPU Adapter and It's Application
46mDevice Power Management: Journey to 5uA
46mDevice Tree in Zephyr Project