ShenZhen Legendary. USB Developer Days USB Power Delivery. Developer Days 2016 Hong Kong October 19-20, 2016

Transcription

1 USB Power Delivery Developer Days 2016 Hong Kong October 19-20, 2016 October 19 USB Implementers Forum

2 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

3 Introduction How PD is used today Key Characteristics Target Requirements Revision 3.0 October 19 USB Implementers Forum

4 How PD is used today Dedicated Charging based on Standards (IEC) Support different charging algorithms (high voltage, direct charge) Power banks, UPSes Charging plus data Charging docks Charge through adapters Cable capabilities (current, speed, length, active/passive ) Alternate Mode Adapters DP Alt mode MHL Alt mode Thunderbolt Alt mode October 19 USB Implementers Forum

5 Key Characteristics Voltage and current values negotiated Higher voltage and current allows power up to ~100W Limits to match cable capabilities (3A/5A) Upper limit bound by international safety requirements Coexists with USB Battery Charging 1.2 Swapping of power direction, data direction and source of VCONN Communication with USB Type-C Electronically Marked Cables Support for Alternate Modes of operation (DP, MHL) October 19 USB Implementers Forum

6 Revision 3.0 Improved Collision avoidance scheme Use Rp/Rd to indicate Source/Sink transmission Deprecated BFSK Revision 2.0 support will still be permitted Extended messages Up to 260 bytes Chunking into existing packet sizes enabled for compatibility Additional alerts, capabilities and status Support for IEC power supply standards Battery capabilities/status Support for Direct Charge Programmable Power Supplies October 19 USB Implementers Forum

7 Revision 3.0 continued Fast Role Swap for adapters Solves issues when adapter changes from wall powered to bus powered Occurs due to surprise removal of wall power Keeps the hub and attached devices alive Keep alive time needs to be short to minimize caps PDUSB Hub definition moved to new USB-C Bridging Specification Encapsulates UCSI and Security related requests over USB Device USB operation and Battery status will be retained Power Rules Based about communicating Watts to the user Adds voltages/currents incrementally Bigger means better to the user Multi-port charger October 19 USB Implementers Forum

8 Architectural Overview Terminology Topology Walk through the Layers PD and USB Device States Battery Status October 19 USB Implementers Forum

9 Terminology DFP/UFP Defines the Port s position in the USB topology DFP is equivalent to A-Port/Host, UFP is equivalent to B-Port/Device Does not require USB Communication Capability Source/Sink Defines the power role the port is currently operating in Dual-role Power Port can operate as either a Source or a Sink Dual-role Data Port can operate as either a DFP or a UFP USB Communications Capable Port can send/receive USB traffic may be asymmetric for DFP/UFP SOP* Start of packet (SOP/SOP /SOP ) October 19 USB Implementers Forum

10 Source Sink Overview Device Policy Manager Device Policy Manager Source Port Sink Port Policy Engine Policy Engine Protocol Power Source(s) Power Sink Protocol USB-C Control Physical Layer Physical Layer USB-C Control BMC BMC USB Port USB Port CC VBUS VBUS CC V BUS USB-C Port Control USB Type-C state operation (attach/detach) Physical Layer (Chapter 5) Port to Port over CC wire Collision Avoidance Protocol Layer (Chapter 6) Handles retries, message construction and chunking CC Power Source/Sink (Chapter 7) Controls power transitions Device Policy (Chapter 8) Policy Engine Drives the Atomic Message Sequences Device Policy Manager Handles PD across multiple ports Makes decisions on how to allocate power Talks to Power Source/Sink and Cable Detection October 19 USB Implementers Forum

11 USB-C Control / Cable Discovery Source/Sink USB Port USB-C Control Device Policy Manager Source Port Policy Engine Protocol Physical Layer BMC Power Source(s)/ Sink USB-C Control USB Type-C mechanisms indicate attach/detach Cables support 3A by default Cable Discovery USB Type-C full featured cables are electronically marked USB PD uses SOP to read cable capabilities Identify Cables supporting more than 3A Active cables Alternate Modes CC VBUS October 19 USB Implementers Forum

12 Physical Layer Source/Sink USB Port USB-C Control Device Policy Manager Source Port Policy Engine Protocol Physical Layer BMC CC Power Source(s)/ Sink VBUS Uses USB Type-C CC wire no dependence on (D+/- or Tx/Rx) Biphase Mark Coding (BMC) Signaling >10e-6 BER 300kbps Half duplex with collision avoidance Tx appends CRC-32 to message / Rx validates CRC-32 Built in self-test modes October 19 USB Implementers Forum

13 Protocol Layer Source/Sink USB Port USB-C Control Device Policy Manager Source Port Policy Engine Protocol Physical Layer BMC Power Source(s)/ Sink Directed by policy engine Constructs messages which it passes to the PHY Receives messages from the PHY Deconstructs messages and passes back to policy engine Ensures reliable communications Timeouts, retries and GoodCRC messages CC VBUS October 19 USB Implementers Forum

14 USB Type-C Port Controller (TCPC) Source/Sink Device Policy Manager Source Port Policy Engine Protocol TCPC USB-C Control Physical Layer Power Source(s)/ Sink Covers the following: Physical Layer Protocol Layer state operation GoodCRC generation Optionally USB-C Control I2C interface to upper Protocol Layer USB Port BMC CC VBUS October 19 USB Implementers Forum

15 Power Source/Sink Source/Sink USB Port Cable Detection Device Policy Manager Source Port Policy Engine Protocol Physical Layer BMC Power Source(s)/ Sink Behavioral aspects of sources and sinks Defines transitions Increasing/decreasing voltage Increasing/decreasing current Swapping roles Detailed diagrams showing the relationship between the messaging and transitions CC VBUS October 19 USB Implementers Forum

16 Device Policy Source/Sink USB Port Cable Detection Device Policy Manager Source Port Policy Engine Protocol Physical Layer BMC CC Power Source(s)/ Sink VBUS Device Policy Manager Manages shared resources Notion of reserved power Notion of reclaimed power Interacts with the policy engine, power supply, cable detect, and system policy manager Policy Engine Enacts policy for a port Interacts with the protocol layer and device policy manager October 19 USB Implementers Forum

17 System Policy USB Host PD USB Device System Policy Manager USB hub tree (optional) USB Interface (optional) Device Policy Manager Policy Engine Protocol Provides OS visibility into Power Delivery System can overlay a coordinated policy on device policy Communication is done over USB Devices report capabilities Hubs report and allow control of their downstream ports Rev 3.0 moves this functionality to the bridging specification Physical Layer CC October 19 USB Implementers Forum

18 PD and USB Device States Device moves from USB Attached to USB Powered: No Negotiate enough Power? Yes Device is a Sink, sees VBUS and has enough power to operate from PD USB Attached VBUS Present Yes No Can enumerate? Yes USB Powered Device is a Source seeing that a Sink is attached (after PR_Swap) No Device in Sink Mode Device in Source Mode (5V) Source? Yes Attached? Yes No No October 19 USB Implementers Forum

19 PD and USB Device States Hard reset Hard Reset and Can Operate Hard Reset and Can t Operate Any USB State VBUS Present No Swapping Power Roles? No USB Attached Yes Yes Hard Reset and Bus Powered Hard Reset refers to PD Hard Reset It is recommended that implementers of USB Devices and Hosts to stay in the same USB State on reception of PD Hard Reset October 19 USB Implementers Forum

20 Battery Status Battery status structure returns information about the battery Battery Attributes: no battery, charging, discharging, neither Battery SOC: State of charge in % Battery Status: Various battery error conditions Battery Remove Wake Events: present error, charging flow, error Remaining Operating Time Remaining Charging Time October 19 USB Implementers Forum

21 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

22 Physical Layer Signaling BMC Characteristics Symbol Coding Collision Avoidance Packet Formats Multi-Drop October 19 USB Implementers Forum

23 Signaling Half duplex system Bit rate is 300kbps Uses Bi-mark phase Coding (BMC) A form of Manchester Coding Signal is DC coupled on USB Type-C CC Low impedance - nominally V BER < 10 6 at SNR of 25dB Typical operating SNR would be higher CRC-32 used to detect data corruption Same CRC-32 as USB 3.1 October 19 USB Implementers Forum

24 BMC Characteristics 2 transitions for one and 1 transition for zero Defined by transmit and receive masks October 19 USB Implementers Forum

25 Symbol Coding 4b5b coding scheme Allows use of K-Codes Use both single K-Codes and Ordered sets of 4 K-Codes Start of Packet (SOP*) Ordered set Used to address Ports or Cable Plugs (multi-drop) SOP Communications between the DFP and UFP SOP Communications with the Cable Plug attached to the DFP SOP Communications with the Cable Plug attached to the UFP End of Packet (EOP) Reset Ordered Sets Hard Reset Resets both Ports and any Cable Plugs Cable Reset Resets only Cable Plugs October 19 USB Implementers Forum

26 Collision Avoidance Rp used by the Source to control when Sink can initiate an Atomic Message Sequence (AMS) Source Rp Sink operation Source operation 1.5A Sink cannot initiate an AMS, but may continue ongoing AMS. Source can initiate an AMS after at least 16ms (tsinktx) of setting Rp to this value. 3A Sink can initiate an AMS. Source cannot initiate an AMS while it has this value set. October 19 USB Implementers Forum

27 Packet Format Control Messages Preamble SOP* (Start Of Packet) Message Header (16 bit) CRC EOP (End Of Packet) Legend: PHY Layer Protocol Layer 1. Packet starts with a preamble for receiver training 2. One of the SOP* start of packet K-codes (SOP/SOP /SOP ) 3. Header of the message being sent (start of payload) bit CRC 5. End of Packet K-code Preamble is encoded with 4b/5b Start of packet, CRC and End of Packet are 4b/5b encoded Payload is not 4b/5b encoded but is just sent as data October 19 USB Implementers Forum

28 Packet Format Data Messages Preamble SOP* (Start Of Packet) Message Header (16 bit) 0..7 Data Object(s) CRC EOP (End Of Packet) Legend: PHY Layer Protocol Layer 1. Packet starts with a preamble for receiver training 2. One of the SOP* start of packet K-codes (SOP/SOP /SOP ) 3. Header of the message being sent (start of payload) data objects (end of payload) bit CRC 6. End of Packet K-code Preamble is encoded with 4b/5b Start of packet, CRC and End of Packet are 4b/5b encoded Payload is not 4b/5b encoded but is just sent as data October 19 USB Implementers Forum

29 Packet Format Extended Message Preamble SOP* (Start Of Packet) Message Header (16 bit) Extended Message Header (16 bit) Data ( bytes) CRC EOP (End Of Packet) Legend: PHY Layer Protocol Layer 1. Packet starts with a preamble for receiver training 2. One of the SOP* start of packet K-codes (SOP/SOP /SOP ) 3. Header of the message being sent (start of payload) 4. Extended Message Header bytes of data (end of payload) bit CRC 7. End of Packet K-code Preamble is encoded with 4b/5b Start of packet, CRC and End of Packet are 4b/5b encoded Payload is not 4b/5b encoded but is just sent as data October 19 USB Implementers Forum

30 Packet Format - Extended Message - Chunked Chunk 0 Preamble SOP* (Start Of Packet) Message Header (16 bit) Extended Message Header (16 bit) Data (26 bytes) CRC EOP (End Of Packet) Chunk 1 Preamble SOP* (Start Of Packet) Message Header (16 bit) Extended Message Header (16 bit) Data (26 bytes) CRC EOP (End Of Packet) Chunk n Preamble SOP* (Start Of Packet) Message Header (16 bit) Extended Message Header (16 bit) Data (remaining bytes + padding) CRC EOP (End Of Packet) Legend: PHY Layer Protocol Layer Header fields Chunked bit = 1 -> chunking used since one or both Port Partners doesn t do 260 byte Messages Chunk number field > Chunk number sent/requested Request Chunk bit set for a Chunk request (no Data), reset for the returned Chunk Number of Chunks = Data Size/26 i.e. 26 byte Chunks Matches legacy Message data payload of 28 bytes 2 byte Extended Message Header + 26 bytes of Data for first chunks (NDO = 7) Last Chunk remaining data padded to the next Data Object boundary with 0x00 October 19 USB Implementers Forum

31 Multi-drop DFP VCONN Cable Plug (SOP ) Electronically Marked Cable Cable Plug (SOP ) UFP SOP signaling SOP signaling SOP signaling Multi-drop Packet structure unchanged Start of packet is message address (SOP /SOP ) Limited access to the new addresses Electronically marked cables respond to SOP Only the VCONN Source can reliably talk to the cable Source of VCONN swapped with VCONN_Swap Single initiator of multi-drop message sequences Cable Plug not allowed to initiate messages Source can initiate communication SOP prior to an explicit contract DFP can initiate communication SOP /SOP within an explicit contract October 19 USB Implementers Forum

32 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

33 Protocol Messages Data Objects Errors Attach/Detach Detection Structured VDMs Alternate Modes October 19 USB Implementers Forum

34 Sending a Message October 19 USB Implementers Forum

35 Sending a Message (Retry) October 19 USB Implementers Forum

36 Host Power Brick Extended Messages Security_Request Chunk Security_Request (Number of Data Objects = 3, Chunked = 1, Chunk Number = 0, Request Chunk = 0, Data Size = 7) Host Power Brick GoodCRC Security_Request (Data Size = 7, Chunked = 0) GoodCRC Security_Response (Data Size = 30, Chunked = 0) GoodCRC Extended messages of up to 260 bytes can be transmitted The example above is a Security_Request and Security_Response To maintain compatibility with existing HW Extended Messages can also be Chunked Example to the right is the same sequence, but chunked Security_Response Security_Response (Number of Data Objects = 7, Chunked = 1, Chunk Number = 0, Request Chunk = 0, Data Size = 30) GoodCRC Security_Response Chunk request (Number of Data Objects = 1, Chunked = 1, Chunk Number = 1, Request Chunk = 1, Data Size = 0) GoodCRC Security_Response (Number of Data Objects = 2, Chunked = 1, Chunk Number = 1, Request Chunk = 0, Data Size = 30) GoodCRC October 19 USB Implementers Forum

37 Messages Source/Sink Capabilities (Source_Capabilities, Sink_Capabilities, Source_Capabilities_Extended) Used to advertise a Source s outputs or Sink s required inputs Type of source (charger, battery) Voltage/current combinations available/required Requests Request capabilities (Get_Source_Cap, Get_Sink_Cap, Get Source_Cap_Extended) Request status (Get_Status, Status) Request voltage and/or current (Request) Request power role change (PR_Swap, FR_Swap) Request data role change (DR_Swap) Request Vconn source change (VCONN_Swap) Accept/Reject/Wait Possible responses to a request Alert Notification after OVP/OCP/OTP Miscellaneous GoodCRC Soft Reset Power Supply (PS_RDY) Not_Supported Ping BIST VDMs October 19 USB Implementers Forum

38 Error Detection Various conditions can lead to errors: Protocol Layer Missing GoodCRC Retry MessageID mismatch Lost messages Policy Engine Wrong/not received messages during message sequence Timeout on expected message e.g. lack of PS_RDY No response after Hard Reset Rp or Rd not asserted during PR_Swap October 19 USB Implementers Forum

39 Error Recovery Soft Reset Reset only the protocol layer Specific to a particular SOP* Hard Reset Resets all SOP* and the power supply Doesn t impact USB Type-C power role (Rp/Rd unchanged) USB Type-C VCONN source returned to Source (Rp asserted) Cable Reset Resets the cable (SOP /SOP ) but not the Port Partners (SOP) USB Type-C Error Recovery Performs disconnect and reconnect Errors unresolved by PD Hard Reset October 19 USB Implementers Forum

40 Attach/Detach Detection Source (Rp asserted) Presence of Rd indicates port to port attach Immediately sends Source Capabilities Absence of Rd indicates detached state Sink (Rd asserted) Presence of VBUS is attached to a Source Responds with GoodCRC to Source Capabilities or Times out and sends Hard Reset When VBUS is removed During PR_Swap connection is retained During Hard Reset if self-powered and can operate connection is retained At other times this means detached October 19 USB Implementers Forum

41 Vendor Defined Messages Identify the device or cable Discover Identity of attached cable or Port Partner Support of USB Type-C Alternate Modes Discover SVIDS, Discover Modes Enter, Exit and manage USB Type-C Alternate Modes of attached device or cable Attention for the device to get the host s attention October 19 USB Implementers Forum

42 DFP Electronically Marked Cable UFP Electronically Marked Cable VBUS CC VBUS CC VCONN (Sourced) Iso ( ) Iso ( ) VCONN (Not sourced) Ra SOP Ra GND GND Discover Identity used to get cable information HW/FW Version Connectors Latency Passive/Active VCONN required RX/TX Directionality VBUS current capability VBUS end-to-end SOP controller USB Signalling (2.0, Gen1, Gen 2) October 19 USB Implementers Forum

43 Alternate Modes A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 GND RX2+ RX2 VBUS SBU1 D D+ CC VBUS TX1 TX1+ GND GND TX2+ TX2 VBUS VCONN SBU2 VBUS RX1 RX1+ GND B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 Alternate modes reconfigure the connector Repurpose pins to support another bus Change the mode of operation of a bus Enable sideband signals Note: Accessory Mode is not the same October 19 USB Implementers Forum

44 Alternate Mode Process Discover SVIDS Device returns the SVIDS for which is has modes Discover Mode Device returns the modes is has for each SVID Host evaluates the intersection of the modes it and the device supports USB Safe State Prevent any signaling that appears on data wires from damaging USB PHY May be simple isolation (mux/switch) May be very robust PHY inputs Enter mode SVID + mode Stay in USB mode Initiator (DFP) N Establish PD Contract Discover SVIDs List of SVIDs For every DFP supported SVID Discover Modes (SVID) Modes Supported? Y USB Safe State Modes for SVID Enter Mode Responder (UFP or Cable Plug) ACK (Responder switched to Mode) Initiator and Responder operate using Mode Exit Mode or PD Hard Reset or cable unplugged or power removed? Y Return to USB mode N October 19 USB Implementers Forum

45 Failure to find an Alternate Mode Alternate mode device does not receive an Enter Alternate Mode command Host does not support PD so does not look for alternate mode devices Host finds alternate mode devices, but does not support this particular device Alternate mode device presents either an equivalent USB function and/or USB Billboard Device interface to the USB stack BB device provides the OS with information about the alternate mode device that it can use to inform the user that the host does not support the alternate mode October 19 USB Implementers Forum

46 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

47 Device Policy Device Policy Manager Managing Power Needs Power Reserve Capability Mismatch Policy Engine Power Negotiation Power Role Swap Fast Role Swap October 19 USB Implementers Forum

48 Device Policy Manager PD USB Device USB-C Control USB Host Device Policy Manager Source Port System Policy Manager USB hub tree (optional) USB Interface (optional) Policy Engine Protocol Physical Layer Power Source(s)/ Sink One instance per device Acts across one or more ports Manages bus traffic Manages power resources in the device Monitors and controls the power supply Interacts with the cable detection module Causes Policy Engine to enact policy for a given port Optional USB interface to System Policy October 19 USB Implementers Forum

49 Managing Power Needs Finite power resources on a Provider Sinks responsible for requesting optimal power Device Policy Manager balances power needs to ensure smooth system operation Also interacts with System Policy, which can use its system wide view to allocate resources or inform the user of issues October 19 USB Implementers Forum

50 Capability Mismatch Sink may require more than a Source can supply in order to enumerate on USB: e.g. needs 2A@20V and can only get 2A@5V Sink will indicate a Capability Mismatch to end user and also via PD messaging Indication can be handled on the Source and also in System Policy October 19 USB Implementers Forum

51 Policy Engine Source/Sink USB Port USB-C Control Device Policy Manager Source Port Policy Engine Protocol Physical Layer BMC CC Power Source(s)/ Sink VBUS One instance per port, per SOP* supported Interacts with Device Policy Manager to determine and request: Power resources for the port Power source or sink transitions Attached cabling Handles power negotiation, swapping, etc. Uses Protocol Layer to form messages Handles message timers, errors and resets October 19 USB Implementers Forum

52 Power Negotiation Sequence Source Cable Plug Sink Cable Capabilities (Required for >3A) VDMResponseTimer Discover Identity (Request, SOP ) Discover Identity (ACK, SOP ) SenderResponseTimer Source Capabilities Request SenderResponseTimer Accept PSTransitionTimer PS_RDY October 19 USB Implementers Forum

53 Fast Role Swap Initial Sink Rd asserted Initial Source Rp asserted Hub SenderResponseTimer Initial Source (Hub) has power removed Maintains power to downstream peripherals Stops sourcing power upstream Needs new power source urgently! Signals Fast Swap on CC line Initial Sink (Laptop) has 5V Source ready to be applied quickly Detects Fast Swap Waits for VBUS to drop to vsafe5v Starts Sourcing 5V In parallel Port Partners start the role swap process Ensures that Source and Sink roles are aligned HDD PS SourceOffTimer Stop Sinking New Source is applying vsafe5v and asserts Rp New Source Fast Swap Signal (CC driven to GND) FR_Swap Accept PS_RDY PS_RDY Stop Sourcing -> Sink Vbus vsafe5v Initial Source asserts Rd New Sink PSSourceOnTimer October 19 USB Implementers Forum

54 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

55 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

56 Power Supply Architecture Overview Source & Sink Behaviors Transitioning Voltage and Current Robust Port Considerations Swapping Power PPS Preview October 19 USB Implementers Forum

57 Example Source & Sink Configurations Source External Power Sources Dual-Role Power External Power System Power System Power PD Source Port Legacy Power Source Battery Dual-Role Power Port Legacy Power Source Battery * must be self powered VBUS VBUS VBUS VBUS VBUS VBUS VBUS VBUS Sink External Power Sinks Dual-Role Power External Power System Power System Power PD Sink Port Battery Dual-Role Power Port Battery VBUS VBUS * must be self powered October 19 USB Implementers Forum

58 VBUS System SOURCE CABLE SINK Power Supply BMC Tx/Rx V BUS cc... Refer to USBType-C1.0 V BUS cc... BMC Tx/Rx Load GND GND SHIELD SHIELD Dedicated communications path using CC conductor Isolation impedance is not required The transceiver CC conductor is DC coupled October 19 USB Implementers Forum

59 Source Behavior Backward compatible with legacy VBUS ports. Supplies default USB 2.0, USB 3.1, USB Type-C Current or BC 1.2 voltage and current to VBUS When USB cable attached prior to an Explicit Contract When Hard Reset signaling is received Returns to vsafe0v for some time then returns to vsafe5v PD bounds VBUS voltage transitions by undershoot, overshoot and transition time requirements October 19 USB Implementers Forum

60 Source Positive Transitions V 105 % 95 % -0.5 V vsrcvalid(max) vsrcnew(max) vsrcnew(typ) vsrcnew(min) vsrcvalid(min) Upper bound of valid Source range Lower bound of valid Source range vsrcslewpos 30 mv/usec Starting voltage t0 tsrcsettle tsrcready 275 msec 285 msec The voltage limits to do not apply to vsafe0v and vsafe5v October 19 USB Implementers Forum

61 Source Negative Transitions Starting voltage vsrcslewneg -30 mv/usec V vsrcvalid(max) Upper bound of valid Source range 105 % vsrcnew(max) vsrcnew(typ) 95 % vsrcnew(min) -0.5 V vsrcvalid(min) Lower bound of valid Source range t0 tsrcsettle tsrcready 275 msec 285 msec The voltage limits to do not apply to vsafe0v and vsafe5v October 19 USB Implementers Forum

62 Application of vsrcnew & vsrcvalid after tsrcready V 105 % vsrcvalid(max) vsrcnew(max) 5 msec tsrctransient windows vsrcnew(typ) 95 % -0.5 V vsrcnew(min) vsrcvalid(min) tsrctransient window 5 msec Sink Load I2 iloadsteprate 150 ma/usec iloadreleaserate -150 ma/usec Sink Load I1 tsrcready 285 msec October 19 USB Implementers Forum

63 Sink Behavior Backwards compatible with legacy VBUS ports Draws default USB 2.0, USB 3.1, USB Type-C Current or BC 1.2 VBUS current at default voltage When the USB cable is attached prior to an Explicit Contract When responding to a Hard Reset Returns to the default USB 2.0, USB 3.1, USB Type-C Current or BC 1.2 VBUS current at default voltage Controls VBUS in-rush current when increasing current consumption October 19 USB Implementers Forum

64 Transition to Increase Voltage Source Port Policy Engine Sink Port Policy Engine 1 Send Accept 2 Evaluate Accept tsrctransition 5 Send PS_RDY PSTransitionTimer (running) 6 Evaluate PS_RDY Port to Port Messaging Source Port Device Policy Mgr Source Port Power Supply Source V OLD 4 Source ñ V t2 Source V NEW Source Port Interaction Sink Port Device Policy Mgr Sink Port Power Supply Sink I OLD 3 Sink to Sink Standby t1 Sink psnkstdby Sink Standby to Sink t3 Sink I OLD Sink Port Interaction Source Port Voltage V OLD V NEW Source V BUS Voltage Sink Port Current I OLD I1 I2 I1 I OLD Sink V BUS Current I1 (psnkstdby/v BUS ) I2 (psnkstdby/v BUS ) + csnkbulkpd(dv BUS /Dt) October 19 USB Implementers Forum

65 Transition to Increase Current Source Port Policy Engine Sink Port Policy Engine 1 Send Accept 2 Evaluate Accept tsrctransition 4 Send PS_RDY PSTransitionTimer (running) 5 Evaluate PS_RDY Port to Port Messaging Source Port Device Policy Mgr Source Port Power Supply Source V OLD 3 Source ñ I t1 Source V OLD Source Port Interaction Sink Port Device Policy Mgr Sink Port Power Supply Sink I OLD Sink ñ I t2 Sink I NEW Sink Port Interaction Source Port Voltage V BUS doesn t change Source V BUS Voltage Sink Port Current I OLD I NEW Sink V BUS Current October 19 USB Implementers Forum

66 Transition to Increase Power Source Port Policy Engine Sink Port Policy Engine 1 Send Accept 2 Evaluate Accept tsrctransition 5 Send PS_RDY PSTransitionTimer (running) 6 Evaluate PS_RDY Port to Port Messaging Source Port Device Policy Mgr Source Port Power Supply Source V OLD 4 Source ñ V ñ I t2 Source V NEW Source Port Interaction Sink Port Device Policy Mgr Sink Port Power Supply Sink I OLD 3 Sink to Sink Standby t1 Sink psnkstdby Sink Standby to Sink t3 Sink I NEW Sink Port Interaction Source Port Voltage V OLD V NEW Source V BUS Voltage Sink Port Current I OLD I1 I2 I1 I NEW Sink V BUS Current I1 (psnkstdby/v BUS ) I2 (psnkstdby/v BUS ) + csnkbulkpd(dv BUS /Dt) October 19 USB Implementers Forum

67 Port Robustness Philosophy Sources protect themselves Sources shall not rely on Sinks for protection Sinks protect themselves Sinks shall not rely on Sources for protection Robust Source and Sink design does not equate to regulatory safety compliance October 19 USB Implementers Forum

68 Robust Source Port Considerations Output Over Current Protection Over Temperature Protection vsafe5v to vsafe5v Connection VBUS Discharge at Detach Note: Sources are required to protect themselves from damage. Source protection mechanisms are not expected to protect Sinks. October 19 USB Implementers Forum

69 Robust Sink Port Considerations Input Over Voltage Protection Over Temperature Protection VBUS Discharge at Detach Note: Sinks are required to protect themselves from damage. Sink protection mechanisms are not expected to protect Sources. October 19 USB Implementers Forum

70 VBUS & VCONN Relationship During Hard Reset Old voltage vsafe5v(max), VCONN(max) 5.5 V 5.5 V 0.8 V vsafe0v(max) 150 mv -0.3 V vvconndischarge 0V vsrcneg(max) 250 msec t0 tvconndischarge tvconnon 2 msec 275 msec 650 msec tsafe5v tsafe0v 1 sec tsrcrecover tsrcturnon 275 msec October 19 USB Implementers Forum

71 Swapping Power on VBUS & VCONN Power Role Swap Method to swap Source and Sink VBUS power roles between two ports Fast Role Swap Method to swap VBUS power between two Sources powering a pass-thru device VCONN Swap Method used to source VCONN from different ends of the cable The data roles are not affected by power swaps October 19 USB Implementers Forum

72 Power Role Swap Before the Power Role Swap After the Power Role Swap SOURCE SINK Power Role Swap SINK SOURCE PD ADAPTER DRP Docking LDR6023 DRP Macbook PD ADAPTER REMOVED DRP Docking LDR6023 DRP Macbook *** Data Roles do not change during Power Role swap *** Applies to 1-to-1 power connections between DRPs Initiated using PD messaging by either the Source or the Sink PD messaging is used to manage the power change over VBUS transitions to vsafe0v during the VBUS change over Post power role Swap VBUS voltage is vsafe5v October 19 USB Implementers Forum

73 Power Role Swap Transition Diagram Initial Source Port Policy Engine Initial Sink Port Policy Engine 1 Send Accept 2 Evaluate Accept tsrctransition PSSourceOffTimer (running) 4 Send PS_RDY 5 Evaluate PS_RDY PSSourceOnTimer (running) 7 Send PS_RDY 8 Evaluate PS_RDY Port to Port Messaging Initial Source Port Device Policy Mgr Source Sink Power Supply Initial Source Source V OLD 3 Source to Swap Standby t2 Rp to Rd Swap Standby 9 Swap Standby to Sink t4 New Sink Sink default current Source Port Interaction Initial Sink Port Device Policy Mgr Sink Source Power Supply Initial Sink Sink I OLD 2a Sink to Swap Standby t1 Swap Standby Rd to Rp 6 Swap Standby to Source t3 Source vsafe5v New Source Sink Port Interaction Source Port Voltage Initial Source V OLD not driven vsafe5v New Source Source V BUS Voltage Sink Port Current I OLD Initial Sink I1 I1 isnkswapstdby I2 I2 I1 not driven I2 isnkswapstdby + csnkbulkpd(dv BUS /Dt) psnksusp New Sink Sink V BUS Current October 19 USB Implementers Forum

74 Fast Role Swap (FRS) Before the Fast Role Swap After the Fast Role Swap Sink Fast Role Swap GONE! Source Charger Charge-thru Hub LDR6023 DRP X Charger Charge-thru Hub LDR6023 DRP Power USB Device *** Data Roles do not change during Fast Role Swap *** USB Device Power PD negotiation discovers if the DRP supports FRS The charge-thru hub monitors Charger VBUS to signal FRS to the DRP VBUS can only droop below vsafe5v for 150 usec Why? Needs to be fast for practical Charger hold up capacitance October 19 USB Implementers Forum

75 Fast Role Swap Transition Diagram Source Port Policy Engine Sink Port Policy Engine B 2 Signal Fast Swap C Detect Fast Swap tfrswapinit 1 Send FR_Swap Evaluate FR_Swap 3 Send Accept 4 Evaluate Accept 5 Send PS_RDY 6 Evaluate PS_RDY 7 Send PS_RDY 8 Evaluate PS_RDY Port to Port Signaling & Messaging Source Port Device Policy Mgr Source Port Power Path A Source Stops Source D1 V BUS < vsafe5v Sink F Change Rp to Rd Source Port Interaction Sink Port Device Policy Mgr Sink Port Power Path Sink D2 V BUS < vsafe5v < tsrcfrswap E Source V BUS Ready & Able to Source vsafe5v Source vsafe5v G Change Rd to Rp Sink Port Interaction Source Port Voltage Old Source discharging to vsafe0v New Source = vsafe5v Source V BUS Voltage Sink Port Current Old Sink Represents the increase in current as V BUS voltage discharges New Sink Sink V BUS Current October 19 USB Implementers Forum

76 VCONN Swap Supported by any port that can operate as VCONN source Either port partner can send the VCONN_Swap Message The recipient responds with either Accept, Reject or Wait Messages An Accept Message response starts a make-before-break change over A Reject Message response indicates a VCONN Swap will not occur A Wait Message response indicates try a VCONN Swap sometime later October 19 USB Implementers Forum

77 Some Words of Caution Only design to official released versions of USB specifications Developer presentations are intended to help familiarize you with the general characteristics of these specifications and provide design guidance These presentations are not technically complete and should not be used as the sole basis for product designs USB technology has evolved into highly complex and challenging designs When possible, make use of certified product suppliers silicon, connectors, etc. Proper materials and manufacturing processes are increasingly more critical to making successful certified products Submit your products for USB certification October 19 USB Implementers Forum

78 Coming Soon Programmable Power Supply (PPS) Provides a continuously adjustable output voltage power source Exhibits a monotonic transfer characteristic across a voltage range Allows for single step or multi-step voltage changes Minimum transition time bound by 30 mv/usec slew rate Maximum transition time in the range of 10 s of msec Current is determined by PD contract Sinks do not transition to Sink Standby during PPS voltage changes October 19 USB Implementers Forum

79 Why define a PPS? Granular VBUS control 10 s of mv resolution, big and small voltage changes are supported Power path optimization It is possible to optimize the efficiency and thermal performance Sink input VBUS control It is possible for the Sink to set its optimal input operating voltage It is possible to adjust for cable loss Sinks do not transition to Sink Standby during PPS voltage changes October 19 USB Implementers Forum

80 PPS Framework V(4) > V(3) Nominal PPS Maximum Voltage V(4) Programmable Power Supply Output Range 0 Volts V(2) > V(1) Nominal PPS Minimum Voltage (3.0V) V(1) Nominal V(2) V(3) > V(2) Nominal V(3) vppsslewpos vppsvalid 300 absolute level vppsslewpos vppsvalid vppsslewpos vppsvalid vppsnew V(2) = 301 absolute level vppsvalid vppsnew V(3) = (301+n) absolute level PPS Maximum Voltage October 19 USB Implementers Forum

81 PPS Charging Application PPS Adapter LDR6022 VBUS CC Local voltage & current regulation Battery Monitoring & Safety Sink PPS based charging must still support 5V charging The PPS is not intended to replace charging control in the Sink The PPS is not taking extra precautions to protect the battery October 19 USB Implementers Forum

82 PPS Charging Application Safe & Pre-Charge (VBAT) Likely Safe & Pre-Charge Scenario PPS adapter voltage may not vary Sink regulation controls battery SOC Battery Current Battery Voltage PPS Adapter LDR6022 VBUS CC Local voltage & current regulation (IBAT) Battery Monitoring & Safety Sink safe pre constant current constant voltage eoc October 19 USB Implementers Forum

83 PPS Charging Application Constant Current Charge (VBAT) Likely Constant Current Scenario Sink actively controls PPS adapter voltage Sink regulation controls battery SOC Battery Current Battery Voltage PPS Adapter LDR6022 VBUS CC Local voltage & current regulation (IBAT) Battery Monitoring & Safety Sink safe pre constant current constant voltage eoc October 19 USB Implementers Forum

84 PPS Charging Application Constant Voltage Charge (VBAT) Likely Constant Voltage Scenario PPS adapter voltage may not vary Sink regulation controls battery SOC Battery Current Battery Voltage PPS Adapter LDR6022 VBUS CC Local voltage & current regulation (IBAT) Battery Monitoring & Safety Sink safe pre constant current constant voltage eoc October 19 USB Implementers Forum

85 Power Delivery is Alive and Growing Fast Role Swap for bus powered pass through applications Other application uses cases may evolve over time Programmable Power Supply for adjustable VBUS applications Paves the way for optimized VBUS power transfer Creates a standardized method to control VBUS voltage Clearly defined Source and Sink robustness philosophy Sources must protect themselves Sinks must protect themselves Neither shall rely on the other for protection October 19 USB Implementers Forum

86 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:45 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum

87 Q & A October 19 USB Implementers Forum

88 Day 2 Power Delivery Agenda 8:30 Introduction and Architectural Overview 8:55 Physical Layer 9:15 Protocol Layer 9:45 Device Policy 10:00 Break 10:30 Power Supply 11:30 System Policy 11:40 Q&A 12:00 Lunch Exhibit Area Open October 19 USB Implementers Forum