add USB Type-C Spec R2.5
495
USB_TypeC_R2.5/00-front-matter.md
Normal file
|
|
@ -0,0 +1,495 @@
|
|||
<!-- page 1 -->
|
||||
|
||||
**Universal Serial Bus**
|
||||
|
||||
**Type-C Cable and Connector**
|
||||
|
||||
**Specification**
|
||||
|
||||
**Release 2.5**
|
||||
|
||||
**March 2026**
|
||||
|
||||
<!-- page 2 -->
|
||||
|
||||
**Copyright © 2014-2026, USB 3.0 Promoter Group:**
|
||||
|
||||
**Apple Inc., HP Inc., Intel Corporation, Microsoft Corporation,**
|
||||
**Renesas, STMicroelectronics, and Texas Instruments**
|
||||
|
||||
**All rights reserved.**
|
||||
|
||||
NOTE: Adopters may only use the USB Type-C® cable and connector to implement USB or third-party functionality as expressly described in this Specification; all other uses are prohibited.
|
||||
|
||||
LIMITED COPYRIGHT LICENSE: The USB 3.0 Promoters grant a conditional copyright license under the copyrights embodied in the USB Type-C Cable and Connector Specification to use and reproduce the Specification for the sole purpose of, and solely to the extent necessary for, evaluating whether to implement the Specification in products that would comply with the specification. Without limiting the foregoing, use of the Specification for the purpose of filing or modifying any patent application to target the Specification or USB compliant products is not authorized. Except for this express copyright license, no other rights or licenses are granted, including without limitation any patent licenses. In order to obtain any additional intellectual property licenses or licensing commitments associated with the Specification a party must execute the USB 3.0 Adopters Agreement. NOTE: By using the Specification, you accept these license terms on your own behalf and, in the case where you are doing this as an employee, on behalf of your employer.
|
||||
|
||||
INTELLECTUAL PROPERTY DISCLAIMER
|
||||
|
||||
THIS SPECIFICATION IS PROVIDED TO YOU “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE. THE AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY PROPRIETARY RIGHTS, RELATING TO USE OR IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. THE PROVISION OF THIS SPECIFICATION TO YOU DOES NOT PROVIDE YOU WITH ANY LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS.
|
||||
|
||||
All implementation examples and reference designs contained within this Specification are included as part of the limited patent license for those companies that execute the USB 3.0 Adopters Agreement.
|
||||
|
||||
USB Type-C®, USB-C® and USB4® are trademarks of the Universal Serial Bus Implementers Forum (USB-IF). DisplayPort™ is a trademark of VESA. All product names are trademarks, registered trademarks, or service marks of their respective owners.
|
||||
|
||||
Thunderbolt™ is a trademark of Intel Corporation. You may only use the Thunderbolt™ trademark or logo in conjunction with products designed to this specification that complete proper certification and executing a Thunderbolt™ trademark license – see https://www.usb.org/compliance for further information.
|
||||
|
||||
<!-- page 18 -->
|
||||
|
||||
# Specification Editor
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| SpecWerkz | Brad Saunders |
|
||||
|
||||
# Specification Work Group Contributors
|
||||
|
||||
The following is a list of contributor companies and the individuals that were members of the work group roster at the time of this release (October 2024). Note: For historical reasons, the following list also includes individuals that were members of the work group and associated with their company affiliations at the time of each release going back to Release 1.0.
|
||||
|
||||
| | | | |
|
||||
|---|---|---|---|
|
||||
| Acroname Inc. | Grant Fritz | Connor Goss | Matt Krugman |
|
||||
| Advanced-Connectek, Inc. (ACON) | Glen Chandler | Conrad Choy | Alan Tsai |
|
||||
| | Victory Chen | Vicky Chuang | Wayne Wang |
|
||||
| | Bobo Chen | Same Dai | Stephen Yang |
|
||||
| | Dennis Cheung | Jessica Feng | Sunney Yang |
|
||||
| | Jeff Chien | Aven Kao | Kevin Yao |
|
||||
| | Lee (Dick Lee) Ching | Danny Liao | |
|
||||
| Advanced Micro Devices | Steve Capezza | Jason Hawken | Joseph Scanlon |
|
||||
| | Michael Comai | Juan Martinez | Peter Teng |
|
||||
| | Walter Fry | Gerald Merits | Sujan Thomas |
|
||||
| | Will Harris | Tim Perley | |
|
||||
| Allion Labs, Inc. | Howard Chang | Yan Ken | Brian Shih |
|
||||
| | Alex Chuang | Lexus Lee | Chester Tsai |
|
||||
| | Maroco Fan | Stan Lin | Chou Tsungbo |
|
||||
| | Jesse Jiang | Denver Mishima | Liam Wu |
|
||||
| | Terry Kao | Minoru Ohara | |
|
||||
| Amphenol Corporation | Louis Chan | Terry Ke | Shawn Wei |
|
||||
| | Zhinenng Fan | Martin Li | Alan Yang |
|
||||
| | Jesse Jaramillo | Lino Liu | |
|
||||
| Agilent Technologies, Inc. | James Choate | | |
|
||||
| Analogix Semiconductor, Inc. | Mehran Badii | Haijian Sui | Yueke Tang |
|
||||
| | Greg Stewart | | |
|
||||
| Apple Inc. (USB Promoter company) | Colin Abraham | Brian Follis | Nathan Ng |
|
||||
| | Mahmoud Amini | Zheng Gao | James Orr |
|
||||
| | Sree Anantharaman | Derek Iwamoto | Keith Porthouse |
|
||||
| | Brian Baek | Scott Jackson | Breton Saunders |
|
||||
| | Paul Baker | Girault Jones | Reese Schreiber |
|
||||
| | Michael Bonham | Keong Kam | Jay Sha |
|
||||
| | Jonathan Brown | Kevin Keeler | Sascha Tietz |
|
||||
| | Carlos Calderon | Min Kim | Jennifer Tsai |
|
||||
| | Jason Chung | Woopoung Kim | Colin Whitby-Strevens |
|
||||
| | David Conroy | Alan Kobayashi | Jeff Wilcox |
|
||||
| | Bill Cornelius | Alexei Kosut | Eric Wiles |
|
||||
| | Christophe Daniel | Christine Krause | Dan Wilson |
|
||||
| | Raju Desai | Chris Ligtenberg | Dennis Yarak |
|
||||
| | William Ferry | Matthew Mora | |
|
||||
| Aptiv Consumer Connectivity | Andrew Burchett | Moe Elghrawi | |
|
||||
| ASMedia Technology Inc. | Kuo Lung Li | | |
|
||||
| Bizlink Technology, Inc. | Alex Chou | CY Tsai | Giovanni Wang |
|
||||
| | Morphy Hsieh | Kevin Tsai | |
|
||||
|
||||
<!-- page 19 -->
|
||||
|
||||
| | | | |
|
||||
|---|---|---|---|
|
||||
| Cadence Design Systems, Inc. | Marcin Behrendt | Dariusz Kaczmarczyk | Neelabh Singh |
|
||||
| | Huzaifa Dalal | Tomasz Klimek | Michal Staworko |
|
||||
| | Pawel Eichler | Sanjeet Kumar | Fred Stivers |
|
||||
| | Sanjai Gandhi | Jie Min | Mark Summers |
|
||||
| | Sathish Kumar Ganesan | Asila Nahas | Claire Ying |
|
||||
| | | Uyen Nguyen | |
|
||||
| Canova Tech | Piergiorgio Beruto | Michael Marioli | Paola Pilla |
|
||||
| | Andrea Maniero | Antonio Orzelli | Nicola Scantamburlo |
|
||||
| China Telecommunications Technology Labs | Ming Wei | | |
|
||||
| Cirrus Logic Inc. | Sean Davis | Darren Holding | Brad Lambert |
|
||||
| Corning Optical Communication LLC | Wojciech Giziewicz | Ian McKay | Jamie Silva |
|
||||
| Cosemi Technologies Inc. | Samir Desai | Devang Parekh | |
|
||||
| Credo Semiconductor, Inc. | Jim Bartenslager | Yasuo Hidaka | Ping Xiong |
|
||||
| | Yifei Dai | Justin Lee | |
|
||||
| | Kevin Gao | Phil Sun | |
|
||||
| Cypress Semiconductor | Chia Hua Chang | Rushil Kadakia | Jagadeesan Raj |
|
||||
| | Mark Fu | Benjamin Kropf | Sanjay Sancheti |
|
||||
| | Naman Jain | Venkat Mandagulathur | Subu Sankaran |
|
||||
| | Savan Javia | Anup Nayak | Anita Thimma Govarthanarajan |
|
||||
| Dell | Mohammed Hijazi | Ken Nicholas | Siddhartha Reddy |
|
||||
| | Rose Hou | Marcin Nowak | Thomas Voor |
|
||||
| | David Meyers | Ernesto Ramirez | Merle Wood |
|
||||
| | Sean O’Neal | | |
|
||||
| Dialog Semiconductor (UK) Ltd. | Yimin Chen | | |
|
||||
| Diodes Incorporated | Kay Annamalai | Bob Lo | Jin-sheng Wang |
|
||||
| | Justin Lee | Jaya Shukla | Ada Yip |
|
||||
| | Paul Li | Qun Song | |
|
||||
| DisplayLink (UK) Ltd. | Pete Burgers | | |
|
||||
| DJI Technology Co., Ltd. | Steve Huang | | |
|
||||
| eEver Technology, Inc. | Chien-Cheng Kuo | | |
|
||||
| Electronics Testing Center, Taiwan | Sophia Liu | | |
|
||||
| Elka International Ltd. | Roy Ting | | |
|
||||
| Ellisys | Abel Astley | Wenhui Luo | Chuck Trefts |
|
||||
| | Rick Bogart | Mario Pasquali | Tim Wei |
|
||||
| Etron Technology, Inc. | Chien-Cheng Kuo | | |
|
||||
| EverPro Technologies Company, Ltd. | Eva Chen | Hui Jiang | Silane Zhou |
|
||||
| Feature Integration Technologies Inc. | Jacky Chan | KungAn Lin | Paul Yang |
|
||||
| | Chen Kris | Yuchi Tsao | Amanda Ying |
|
||||
| | Yulin Lan | | |
|
||||
|
||||
<!-- page 20 -->
|
||||
|
||||
| | | | |
|
||||
|---|---|---|---|
|
||||
| Foxconn / Hon Hai | Patrick Casher | Fred Fons | Christine Tran |
|
||||
| | Asroc Chen | Chris Goralka | Pei Tsao |
|
||||
| | Brandon Chen | Bob Hall | AJ Yang |
|
||||
| | Joe Chen | Chien-Ping Kao | Yuan Zhang |
|
||||
| | Allen Cheng | Ji Li | Jessica Zheng |
|
||||
| | Jason Chou | Ann Liu | Jie Zheng |
|
||||
| | Edmond Choy | Terry Little | Andy Yao |
|
||||
| | Shruti Deore | Steve Sedio | |
|
||||
| Foxlink/Cheng Uei Precision Industry Co., Ltd. | Robert Chen | Armando Lee | Steve Tsai |
|
||||
| | Sunny Chou | Dennis Lee | Wen Yang |
|
||||
| | Carrie Chuang | Justin Lin | Wiley Yang |
|
||||
| | Wen-Chuan Hsu | Robert Lu | Patrick Yeh |
|
||||
| | Alex Hsue | Tse Wu Ting | Junjie Yu |
|
||||
| Fresco Logic Inc. | Brian Collins | Bob McVay | Christopher Meyers |
|
||||
| Google | Mehdi Abrishamchian | Mark Hayter | Vincent Palatin |
|
||||
| | Naga Viswanadha Udaya Kiran Ammu | Eric Herrmann | Dylan Reid |
|
||||
| | | Nithya Jagannathan | Adam Rodriguez |
|
||||
| | Lucasz Bartosik | Nathan Kolluru | David Schneider |
|
||||
| | Alec Berg | Lawrence Lam | Stephan Schooley |
|
||||
| | Joshua Boilard | Adam Langley | Ketan Shringarpure |
|
||||
| | Alec Berg | Benson Leung | Toshak Singhal |
|
||||
| | Todd Broch | Abraham Levkoy | Bartosz Szpila |
|
||||
| | Charlie Costakis | Ingrid Lin | Jameson Thies |
|
||||
| | Nehemiah Dureus | Prashant Malani | Radu Vele |
|
||||
| | Chao Fei | George-Daniel Matei | Ken Wu |
|
||||
| | Jim Guerin | Richard Palatin | Songping Wu |
|
||||
| | Jeffrey Hayashida | | Diana Zigterman |
|
||||
| Granite River Labs | Yung Han Ang | Mike Engbretson | Kristof Mommen |
|
||||
| | Velmurugan Ayyakkannu | Mark Jiang | Krishna Murthy |
|
||||
| | | Vishal Kakade | Amy Peng |
|
||||
| | Rajesh B | Jesson Li | Johnson Tan |
|
||||
| | Pascal Berten | Caspar Lin | Annie Tao |
|
||||
| | Hariprasad Bhat | Olivia Lu | Vasudev Uttharahalli |
|
||||
| | Sandy Chang | Bala M | Chin Hun Yaep |
|
||||
| | Allen Chen | Prasannakumar Marikunte Nagaraju | Mike Yang |
|
||||
| | Swee Guan Chua | | Yun Yang |
|
||||
| | Alan Chuang | Winson Mok | |
|
||||
| GuangDong OPPO Mobile Telecommunications Corp, Ltd. | Jerry Qin | | |
|
||||
| Honor Device Co., Ltd. | Wang Feng | | |
|
||||
| Hirose Electric Co., Ltd. | Jeremy Buan | Hyejun Lee | Gourgen Oganessyan |
|
||||
| | Kohei Hida | Zhili Liang | Youngbon Park |
|
||||
| | Kazunori Ichikawa | Sang-Muk Lim | Eungsoo Shin |
|
||||
| | Sukkyu Jang | William MacKillop | Sid Tono |
|
||||
| | William Kysiak | | |
|
||||
| Hosiden Corporation | Takahisa Otsuji | Fumitake Tamaki | |
|
||||
|
||||
<!-- page 21 -->
|
||||
|
||||
| | | | |
|
||||
|---|---|---|---|
|
||||
| HP Inc. (USB Promoter company) | Lee Atkinson | Robin Castell | Jim Mann |
|
||||
| | Srinath Balaraman | Steve Chen | Linden McClure |
|
||||
| | Rami Bathaniah | Michael Krause | Mike Pescetto |
|
||||
| | Roger Benson | Rahul Lakdawala | Asjad Shamim |
|
||||
| | Alan Berkema | | |
|
||||
| Huawei Technology Co., Ltd. | Jianhong He | Gang Liang | Ruinan Sun |
|
||||
| | Zhengbing Li | Lauri Soderbacka | Liansheng Zheng |
|
||||
| Hynetek Semiconductor Co., Ltd. | Yingyang Ou | James Xie | |
|
||||
| I-PEX (Dai-ichi Seiko) | Alan Kinningham | Jack Ozeki | Ro Richard |
|
||||
| Indie Semiconductor | Ian Board | Jim Wilshire | |
|
||||
| Infineon Technologies | Godwin Gerald Arulappan | Behzad Jamasbi | Geona Mary Pullankannappally Devasia |
|
||||
| | | Benjamin Kropf | |
|
||||
| | Pradeep Baipai | Venkat Mandagulathur | |
|
||||
| | Dominic Gutierrez | Aniket Shashikant Mathad | Shopitham Ram |
|
||||
| | Anton Gutsul | | Gayathri Vasudevan |
|
||||
| | Naman Jain | | Tue Fatt David Wee |
|
||||
| Insight Test Labs | Caspar Lin | | |
|
||||
| Intel Corporation (USB Promoter company) | Dave Ackelson | Luke Johnson | Rajaram Regupathy |
|
||||
| | Nirmala Bailur | Ziv Kabiry | Oren Salomon |
|
||||
| | Mike Bell | Vijaykumar Kadgi | Brad Saunders |
|
||||
| | Dmitriy Berchanskiy | Jerzy Kolinski | Tomer Savariego |
|
||||
| | Brad Berlin | Venkataramana Kotakonda | Ehud Shoor |
|
||||
| | Pierre Bossart | | Amit Srivastava |
|
||||
| | Huimin Chen | Rolf Kuhnis | Einat Surijan |
|
||||
| | Kuan-Yu Chen | Henrik Leegaard | Eliahu Suued |
|
||||
| | Hengju Cheng | Edmond Lau | Ron Swartz |
|
||||
| | Oded David | Xiang Li | Chuen Ming Tan |
|
||||
| | Sourabh Das | Yun Ling | David Thompson |
|
||||
| | Jhuda Dayan | Guobin Liu | Pranav Tipnis |
|
||||
| | Hem Doshi | Steve McGowan | Karthi Vadivelu |
|
||||
| | Paul Durley | Sankaran Menon | Venkataramani Gopalakrishnan |
|
||||
| | Saranya Gopal | Udaya Natarajan | |
|
||||
| | Venkataramani Gopalakrishnan | Aruni Nelson | Tsion Vidal |
|
||||
| | | Chee Lim Nge | Stephanie Wallick |
|
||||
| | Yaniv Hayat | Asutosh Pathak | Rafal Wielicki |
|
||||
| | Howard Heck | Sagar Pawar | Devon Worrell |
|
||||
| | Hao-Han Hsu | Duane Quiet | Gal Yedidia |
|
||||
| | Seppo Ingalsuo | Amardeep Rai | Li Yuan |
|
||||
| | Abdul (Rahman) Ismail | Kannappan Rajaraman | Reza M. Zamani |
|
||||
| | | Sridharan Ranganathan | Vitaly Zhivov |
|
||||
| | James Jaussi | | |
|
||||
| Japan Aviation Electronics Industry Ltd. (JAE) | Kenji Hagiwara | Tadashi Okubo | Jussi Takaneva |
|
||||
| | Hiroaki Ikeda | Kazuhiro Saito | Junichi Takeuchi |
|
||||
| | Masaki Kimura | Kimiaki Saito | Tomohiko Tamada |
|
||||
| | Toshio Masumoto | Yuichi Saito | Kentaro Toda |
|
||||
| | Kenta Minejima | Mark Saubert | Kouhei Ueda |
|
||||
| | Toshiyuki Moritake | Toshio Shimoyama | Takakazu Usami |
|
||||
| | Joe Motojima | Tatsuya Shioda | Masahide Watanabe |
|
||||
| | Ron Muir | Atsuo Tago | Youhei Yokoyama |
|
||||
| | Norihiko Nakamura | Masaaki Takaku | |
|
||||
|
||||
<!-- page 22 -->
|
||||
|
||||
| | | | |
|
||||
| --- | --- | --- | --- |
|
||||
| JPC/Main Super Inc. | Sam Tseng | Ray Yang | |
|
||||
| Kandou Bus SA | Amanda Dong | Hitaish Sharma | Paul Wilson |
|
||||
| | Majid Foodeei | David Stauffer | |
|
||||
| Keysight Technologies Inc. | Soon Tatt Beh | Jit Lim | Abhijeet Shinde |
|
||||
| | Fang Huey Lim | Pedro Merlo | Xiao Zhang |
|
||||
| Kinetic Technologies, Inc. | Ramesh Dandapani | Jay Slivkoff | Kei Yasuno |
|
||||
| | Akihiro Moto | Sireesha Vemulapalli | |
|
||||
| Leadtrend | Yao-Wei Hsieh | | |
|
||||
| LeCroy Corporation | Mike Engbretson | Tyler Joe | Giuseppe Leccia |
|
||||
| | Daniel H. Jacobs | Chetan Kopalle | |
|
||||
| Lenovo | Rob Bowser | Jianye Li | Howard Locker |
|
||||
| | Tomoki Harada | Wei Liu | Munefumi Nakata |
|
||||
| LG Electronics Inc. | Won-Jong Choi | Jeeyoung Kim | Seung Hyun Yoo |
|
||||
| | Do Kyun Kim | Minji Kim | |
|
||||
| Lintes Technology Co., Ltd. | Tammy Huang | Guobin Liu | JinYi Tu |
|
||||
| | Charles Kaun | Max Lo | Jason Yang |
|
||||
| | RD Lintes | CT Pien | |
|
||||
| Logitech Inc. | Niclas Granqvist | | |
|
||||
| Lotes Co., Ltd. | Ariel Delos Reyes | Charles Kaun | John Lynch |
|
||||
| | Ernest Han | Chi-Chang Lin | Scott Shuey |
|
||||
| | Mark Ho | James Lin | JinYi Tu |
|
||||
| | Regina Liu-Hwang | Max Lo | Jason Yang |
|
||||
| LSI Corporation | Dave Thompson | | |
|
||||
| Luxshare-ICT | Josue Castillo | Peter Jhou | Scott Shuey |
|
||||
| | Daniel Chen | Antony Lin | James Stevens |
|
||||
| | Kenny Chen | Gorden Lin | Carr Wang |
|
||||
| | Lisen Chen | John Lin | Yangli Wang |
|
||||
| | Sally Chiu | Stone Lin | Eric Wen |
|
||||
| | Blue Ho | Alan Liu | Wayne Yeh |
|
||||
| | CY Hsu | Sean O’Neal | Pat Young |
|
||||
| | Alan Kinningham | | |
|
||||
| Maxim Integrated Products | Forrest Christo | Sang Kim | Michael Miskho |
|
||||
| | Ken Helfrich | Jeff Lo | Jacob Scott |
|
||||
| MCCI Corporation | Terry Moore | | |
|
||||
| MediaTek Inc. | Henry Chen | Liang-Yu Hsu | Alex YC Lin |
|
||||
| | Yu-Yi Chu | Jing-Hao Huang | Tung-Sheng Lin |
|
||||
| | Yishu Hsieh | Shih Jyun-Yang | Colin Tsai |
|
||||
| | Jason Hsu | Akan Lin | Chasel Wang |
|
||||
| MegaChips Corporation | Alan Kobayashi | Satoru Kumashiro | |
|
||||
| Mercedes-Benz Research & Development, North America, Inc. | Hans Wickler | | |
|
||||
| Microchip (SMSC) | Josh Averyt | Matthew Kalibat | John Sisto |
|
||||
| | Mark Bohm | Donald Perkins | Anthony Tarascio |
|
||||
| | Shannon Cash | Richard Petrie | Kiet Tran |
|
||||
| | Thomas Farkas | Mohammed Rahman | Christopher Twigg |
|
||||
| | Fernando Gonzalez | Andrew Rogers | Prasanna Vengateshan |
|
||||
|
||||
<!-- page 23 -->
|
||||
|
||||
| | | | |
|
||||
| --- | --- | --- | --- |
|
||||
| Microsoft Corporation (USB Promoter company) | Randy Aull | Kai Inha | Rahul Ramadas |
|
||||
| | Jim Belesiu | Jayson Kastens | Srivatsan Ravindran |
|
||||
| | Michelle Bergeron | Andrea Keating | Kiran Shastry |
|
||||
| | Fred Bhesania | Shoaib Khan | Nathan Sherman |
|
||||
| | Anthony Chen | Patrick Law | Ugan Sivagnanenthirarajah |
|
||||
| | Philip Froese | Eric Lee | Bala Sivakumar |
|
||||
| | Vivek Gupta | Ivan McCracken | Timo Toivola |
|
||||
| | David Hargrove | Arvind Murching | Vahid Vassey |
|
||||
| | Robbie Harris | Gene Obie | David Voth |
|
||||
| | Teemu Helenius | Toby Nixon | Andrew Yang |
|
||||
| | Robert Hollyer | Arjun Padmanabhan | Panu Ylihaavisto |
|
||||
| | Lily Huang | Praveen Kumar Palacharla | |
|
||||
| | Dan Iatco | | |
|
||||
| Molex LLC | Adib Al Abaji | Alan MacDougall | |
|
||||
| Monolithic Power Systems | Junyong Gong | Istvan Nagy | Greg Virnig |
|
||||
| | Di Han | Chris Sporck | Vincent Wu |
|
||||
| | Yuncong Jiang | Ao Sun | |
|
||||
| MQP Electronics Ltd. | Sten Carlsen | Pat Crowe | |
|
||||
| Multilane Inc. | Fadi Daou | Rita Khawaja | Elias Khoury |
|
||||
| NEC Corporation | Kenji Oguma | | |
|
||||
| Newnex Technology Corp. | Sam Liu | Nimrod Peled | |
|
||||
| Nokia Corporation | Daniel Gratiot | Samuli Makinen | Timo Toivola |
|
||||
| | Pekka Leinonen | Pekka Talmola | Panu Ylihaavisto |
|
||||
| Nuvoton Technology Corp. | Nimrod Peled | | |
|
||||
| NVIDIA | Jamie Aitken | Jason Tsai | |
|
||||
| NXP Semiconductors | Mahmoud EL Sabbagh | Nate Johnson | Guru Prasad |
|
||||
| | Dennis Ha | Vijendra Kuroodi | Wouter Sijm |
|
||||
| | Jia Guo | Roger Lo | Krishnan TN |
|
||||
| | Ken Jaramillo | | |
|
||||
| Oculus VR LLC | Amish Babu | Marty Evans | Joaquin Fierro |
|
||||
| ON Semiconductor | Edward Berrios | Alan Finkel | Eric Maier |
|
||||
| | Rod Comer | Oscar Freitas | Rick Pierce |
|
||||
| | Alex Cornwall | Christian Klein | Michael Smith |
|
||||
| | Eduardo De Reza | Amir Lahooti | |
|
||||
| Parade Technologies, Inc. | Tom Burton | Reginald Conley | Paul Xu |
|
||||
| | Jian Chen | Robert McVay | Alan Yuen |
|
||||
| | Brian Collins | Craig Wiley | Jingfan Zhang |
|
||||
| Phison Electronics Corp. | Wilson Wen | | |
|
||||
| Power Integrations | Shruti Anand | Aditya Kulkarni | Amruta Patra |
|
||||
| | Daryll Bonavente | Akshay Nayaknur | Kaushik Raam |
|
||||
| | Rahul Joshi | | |
|
||||
|
||||
<!-- page 24 -->
|
||||
|
||||
| | | | |
|
||||
| --- | --- | --- | --- |
|
||||
| Qualcomm, Inc. | Lior Amarilio | James Goel | Vatsal Patel |
|
||||
| | Vara Prasad Arikatla | Amit Gupta | Jack Pham |
|
||||
| | Aris Balatsos | Philip Hardy | Vamsi Samavedam |
|
||||
| | Nicholas Cadieux | Will Kun | Matthew Sienko |
|
||||
| | David Chang | Jonathan Luty | Dmitrii Vasilchenko |
|
||||
| | Tomer Ben Chen | Adi Menachem | Joshua Warner |
|
||||
| | Richard Burrows | Lalan Mishra | Chris Wiesner |
|
||||
| | Amit Gil | George Paparrizos | |
|
||||
| Realtek Semiconductor Corp. | Marco Chiu | Ray Lee | Chuting Su |
|
||||
| | Tsung-Peng Chuang | Jay Lin | Kyle Tsai |
|
||||
| | Charlie Hsu | Ryan Lin | Jason Wang |
|
||||
| | Fan-Hau Hsu | Terry Lin | Changhung Wu |
|
||||
| | Ty Kingsmore | | |
|
||||
| Renesas Electronics Corp. (USB Promoter company) | Kai Bao | Philip Leung | Yosuke Sasaki |
|
||||
| | Yen-Mo Chen | Mengfei Liu | Toshifumi Yamaoka |
|
||||
| | Yimin Chen | Kiichi Muto | Fengshuan Zhou |
|
||||
| | Nobuo Furuya | Ziba Nami | Yuhuan Zhou |
|
||||
| | Tony Lai | Hajime Nozaki | |
|
||||
| Resillion (Belgium NV) | Bart Grispen | | |
|
||||
| Richtek Technology Corp. | Ben Chiang | Max Huang | Ken Shih |
|
||||
| | Tzuhsien Chuang | Leo Kang | Alex Yang |
|
||||
| | Bryan Huang | Roger Lo | |
|
||||
| Rohde & Schwarz GmbH & Co. KG | Curtis Donahue | Kai Uwe Schmidt | Randy White |
|
||||
| | Patrick McKenzie | Martin Stumpf | |
|
||||
| Rohm Co., Ltd. | Mark Aaldering | Yusuke Kondo | Yoshinori Ohwaki |
|
||||
| | Kris Bahar | Arun Kumar | Takashi Sato |
|
||||
| | Ruben Balbuena | Chris Lin | Hiroshi Yoshimura |
|
||||
| | Nobutaka Itakura | Kazuomi Nagai | |
|
||||
| Samsung Electronics Co., Ltd. | Jaedeok Cha | Sangwoo Kang | Jun Bum Lee |
|
||||
| | KangSeok Cho | Wonseok Kang | Kyunghwan Lee |
|
||||
| | Junhwa Choi | Koyoungwon Kim | Kyungwoo Lee |
|
||||
| | Wooin Choi | Sangju Kim | Jinyoung Oh |
|
||||
| | Yeongbok Choi | Soondo Kim | Chahoon Park |
|
||||
| | Cheolyoon Chung | Woonki Kim | Chulwoo Park |
|
||||
| | Ilhyung Chung | Jagoun Koo | Youngjin Park |
|
||||
| | JaeRyong Han | Termi Kwon | Jung Waneui |
|
||||
| | Jaehyeok Jang | Cheolho Lee | Sunggeun Yoon |
|
||||
| | Sung Geun Joo | Edward Lee | |
|
||||
| SB C&S Corp. | Toshinari Nakamura | Eiji Sakai | Kenji Watanabe |
|
||||
| | Morito Ogikubo | | |
|
||||
| Scosche Industries | Josh Aguilera | Perry DeGuzman | Kevin Trejo |
|
||||
| Seagate | Alvin Cox | Tony Priborsky | Dan Smith |
|
||||
| | Emmanuel Lemay | Tom Skaar | Curtis Stevens |
|
||||
| Shenzhen Deren Electronic Co., Ltd. | Smark (Zhudong) Huo | Yang Lirong | Lucy Zhang |
|
||||
| | Wen Fa Lei | Valerie Yang | |
|
||||
| Silicon Line Gmbh | Ian Jackson | Boleslaw Wojtowicz | Zhiying Zhang |
|
||||
|
||||
<!-- page 25 -->
|
||||
|
||||
| | | | |
|
||||
| --- | --- | --- | --- |
|
||||
| SiliConch Systems Private Limited | Jaswanth Ammineni | Shubham Paliwal | Vishnu Pusuluri |
|
||||
| | Pavitra Balasubramanian | Jinisha Patel | Ranjith S |
|
||||
| | Kaustubh Kumar | Vinay Patel | Abhishek Sardeshpande |
|
||||
| | Aniket Mathad | Rakesh Polasa | Satish Anand Verkila |
|
||||
| Simula Technology Inc. | John Chang | Jung Lin | Richard Liu |
|
||||
| | Voss Cheng | Jyunming Lin | CK Wang |
|
||||
| | Thomas Li | Doris Liu | Alice Yu |
|
||||
| Softnautics LLP | Bhavesh Desai | Dipakkumar Modi | Ujjwal Talati |
|
||||
| | Hetal Jariwala | Ishita Shah | |
|
||||
| Sony Corporation | Shinichi Hirata | Shigenori Tagami | |
|
||||
| Spectra7 Microsystems Corp. | Andrew Kim | James McGrath | John Mitchell |
|
||||
| SpecWerkz | Robert Dunstan | Diane Lenox | Brad Saunders |
|
||||
| | Amanda Hosler | Steve McGowan | |
|
||||
| STMicroelectronics (USB Promoter company) | Jerome Bach | Cedric Force | Federico Musarra |
|
||||
| | Nathalie Ballot | Gregory Gosciniak | Pascal Legrand |
|
||||
| | Filippo Bonaccorso | Chekib Hammami | Richard O’Connor |
|
||||
| | Guenael Cadier | Joel Huloux | Massimo Panzica |
|
||||
| | Dominique Chaillot | Christophe Lorin | Nicolas Perrin |
|
||||
| | Christophe Cochard | Yohann Martiniault | Mathieu Rouviere |
|
||||
| | Nicolas Florenchie | Patrizia Milazzo | |
|
||||
| Sumitomo Electric Ind., Ltd. | Takeshi Inoue | Wataru Sakurai | Masaki Suzuki |
|
||||
| | Yasuhiro Maeda | Sainer Siagian | Mitsuaki Tamura |
|
||||
| Synaptics Inc. | Daniel Bogard | Jeff Lukanc | Prashant Shamarao |
|
||||
| | Dan Ellis | | |
|
||||
| Synopsys, Inc. | Prishkrit Abrol | Morten Christiansen | Satya Patnala |
|
||||
| | Subramaniam Aravindhan | Jaspreet Gambhir | John Stonick |
|
||||
| | | Nivin George | |
|
||||
| Taiwan Testing and Certification Center | Dennis Chang | Sophia Liu | |
|
||||
| Tektronix, Inc. | Sourabh Das | Nitin Jhanwar | Randy White |
|
||||
| | Mark Guenther | Abhijeet Shinde | |
|
||||
| Texas Instruments (USB Promoter company) | Jawaid Ahmad | Michael Koltun IV | Louis Peryea |
|
||||
| | Kasthuri Annamalai | Kevin Kosta | Brian Quach |
|
||||
| | Mike Campbell | Yoon Lee | Sai Karthik Rajaraman |
|
||||
| | Prajith Cheerakkoda | Grant Ley | Wes Ray |
|
||||
| | Greg Collins | Win Maung | Dafydd Roche |
|
||||
| | Gary Cooper | Shafiuddin Mohammed | Anwar Sadat |
|
||||
| | Biju Erayamkot Panayamthatta | Lauren Moore | Cory Stewart |
|
||||
| | Anant Gole | Jacob Ontiveros | Neeta Thawani |
|
||||
| | GP Gopalakrishnan | Brian Parten | Sue Vining |
|
||||
| | Craig Greenberg | Martin Patoka | Bill Waters |
|
||||
| | Richard Hubbard | Jason Peck | Deric Waters |
|
||||
| | Katherine Huckabay | John Perry | Gregory Watkins |
|
||||
| | Nate Johnson | | Roy Wojciechowski |
|
||||
| The Silanna Group Pty. Ltd. | Tod Wolf | | |
|
||||
| Thine Electronica, Inc. | Yuseke Fujita | Shuhei Yamamoto | |
|
||||
| Total Phase | Chris Yokum | | |
|
||||
|
||||
<!-- page 26 -->
|
||||
|
||||
| | | | |
|
||||
| --- | --- | --- | --- |
|
||||
| Trinity Co., Ltd. | Tetsushi Hoshikawa | Kinya Kishita | |
|
||||
| Tyco Electronics Corp. (TE Connectivity Ltd.) | Max Chao | Mike Lockyer | Hiroshi Shirai |
|
||||
| | Robert E. Cid | Jeff Mason | Hidenori Taguchi |
|
||||
| | Calvin Feng | Takeshi Nakashima | Nathan Tracy |
|
||||
| | Kengo Ijiro | Luis A. Navarro | Bernard Vetten |
|
||||
| | Eiji Ikematsu | Masako Saito | Ryan Yu |
|
||||
| | Joan Leu | Yoshiaki Sakuma | Noah Zhang |
|
||||
| | Clark Li | Gavin Shih | Sjoerd Zwartkruis |
|
||||
| UL LLC | Leo Chung | Dylan Su | Eric Wall |
|
||||
| | Michael Hu | Henry Tsou | Lance Yang |
|
||||
| | Terry Kao | Paul Vanderlaan | Chien-Wei Yeh |
|
||||
| Unigraf OY | Steven Chen | Alexander Gushchin | Topi Lampiranta |
|
||||
| | Sergey Grushin | | |
|
||||
| Varjo Technologies | Kai Inha | | |
|
||||
| Ventev Mobile | Brad Cox | Colin Vose | |
|
||||
| VIA Technologies Inc. | Rex Hsu | Terrance Shih | Fong-Jim Wang |
|
||||
| | Einsent Huang | Jay Tseng | |
|
||||
| Vivo Mobile Communications Co. Ltd. | Benny Dong | Junchen Wei | Ziji Zhou |
|
||||
| | Fangding Luo | | |
|
||||
| Weltrend Semiconductor | Hung Chiang | Wayne Lo | Eric Wu |
|
||||
| | Jeng Cheng Liu | Ho Wen Tsai | |
|
||||
| Western Digital | Dave Landsman | Rotem Sela | Prithviraj Sengupta |
|
||||
| | Larry McMillan | | |
|
||||
| Xiaomi Communications Co., Ltd. | Canfeng Chen | Xiaoxing Yang | Qi Zhu |
|
||||
| | Zhe Wang | Juejia Zhou | |
|
||||
| Zhuhai iSmartWare Technology Co., Ltd. | Yuanchao Liang | Liu Qiong | Long Zhang |
|
||||
|
||||
# Pre-Release Draft Industry Reviewing Companies That Provided Feedback
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| Aces | JST Mfg. Co., Ltd. | Pericom |
|
||||
| Fairchild Semiconductor | Korea Electric Terminal | Semtech Corporation |
|
||||
| Fujitsu Ltd. | Marvell Semiconductor | Silicon Image |
|
||||
| Industrial Technology Research Institute (ITRI) | Motorola Mobility LLC | SMK Corporation |
|
||||
| Joinsoon Electronics Mfg. Co. Ltd. | PalCONN/PalNova (Palpilot International Corp.) | Toshiba Corporation |
|
||||
|
||||
<!-- page 27 -->
|
||||
|
||||
# Revision History
|
||||
|
||||
| Release | Date | Description |
|
||||
| --- | --- | --- |
|
||||
| 1.0 | August 11, 2014 | Initial Release |
|
||||
| 1.1 | April 3, 2015 | Reprint release including incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 1.2 | March 25, 2016 | Reprint release including incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 1.3 | July 14, 2017 | Reprint release including incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 1.4 | March 29, 2019 | Reprint release including incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 2.0 | August 2019 | New release primarily for enabling ***USB4*** over USB Type-C connectors and cables. Also includes incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 2.1 | May 2021 | New release primarily for enabling Extended Power Range (EPR) and defining EPR cables aligning with ***USB Power Delivery*** Specification R3.1 V1.0. Also includes incorporation of all approved ECNs as the revision date plus editorial clean-up. |
|
||||
| 2.2 | October 2022 | New release primarily for enabling ***USB4*** Version 2.0 (80 Gbps) over USB Type-C connectors and cables. Also includes incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 2.3 | October 2023 | New release primarily for *deprecating* the ***Audio Adapter Accessory Mode*** and *replacing it with* the ***Liquid Corrosion Mitigation Mode***, and for updating the ***Multi-port Charger Shared Capacity*** definition and behaviors. Also includes incorporation of all other approved ECNs as of the revision date.<br><br>Note: this release was created using a newly developed document template that includes some style adjustments and editorial clean-up. |
|
||||
| 2.4 | October 2024 | Reprint release including incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
| 2.5 | March 2026 | Reprint release including incorporation of all approved ECNs as of the revision date plus editorial clean-up. |
|
||||
BIN
USB_TypeC_R2.5/00-front-matter.pdf
Normal file
232
USB_TypeC_R2.5/01-introduction.md
Normal file
|
|
@ -0,0 +1,232 @@
|
|||
<!-- page 28 -->
|
||||
|
||||
# 1 Introduction
|
||||
|
||||
With the continued success of the USB interface, there exists a need to adapt USB technology to serve newer computing platforms and devices as they trend toward smaller, thinner, and lighter form-factors. Many of these newer platforms and devices are reaching a point where existing USB receptacles and plugs are inhibiting innovation, especially given the relatively large size and internal volume constraints of the Standard-A and Standard-B versions of USB connectors. Additionally, as platform usage models have evolved, usability and robustness requirements have advanced, and the existing set of USB connectors were not originally designed for some of these newer requirements. This specification establishes a new USB connector ecosystem that addresses the evolving needs of platforms and devices while retaining all the functional benefits of USB that form the basis for this most popular computing device interconnect.
|
||||
|
||||
## 1.1 Purpose
|
||||
|
||||
This specification defines the USB Type-C® receptacles, plug and cables.
|
||||
|
||||
The USB Type-C Cable and Connector Specification is guided by the following principles:
|
||||
|
||||
- Enable new and exciting host and device form-factors where size, industrial design and style are important parameters
|
||||
- Work seamlessly with existing USB host and device silicon solutions
|
||||
- Enhance ease of use for connecting USB devices with a focus on minimizing user confusion for plug and cable orientation
|
||||
|
||||
The USB Type-C Cable and Connector Specification defines a receptacle, plug, cable, and detection mechanisms that are compatible with existing USB interface electrical and functional specifications. This specification covers the following aspects that are needed to produce and use this new USB cable/connector solution in newer platforms and devices, and that interoperate with existing platforms and devices:
|
||||
|
||||
- USB Type-C receptacles, including electro-mechanical definition and performance requirements
|
||||
- USB Type-C plugs and cable assemblies, including electro-mechanical definition and performance requirements
|
||||
- USB Type-C to legacy cable assemblies and adapters
|
||||
- USB Type-C-based device detection and interface configuration, including support for legacy connections
|
||||
- ***USB Power Delivery*** optimized for the USB Type-C connector
|
||||
|
||||
The USB Type-C Cable and Connector Specification defines a standardized mechanism that supports ***Alternate Modes***, such as repurposing the connector for docking-specific applications.
|
||||
|
||||
## 1.2 Scope
|
||||
|
||||
This specification is intended as a supplement to the existing ***USB 2.0***, ***USB 3.2***, ***USB4***® and ***USB Power Delivery*** specifications. It addresses only the elements required to implement and support the USB Type-C receptacles, plugs and cables.
|
||||
|
||||
***Normative*** information is provided to allow interoperability of components designed to this specification. ***Informative*** information, when provided, may illustrate possible design implementations.
|
||||
|
||||
## 1.3 Related Documents
|
||||
|
||||
***USB 2.0*** ***Universal Serial Bus Revision 2.0 Specification***
|
||||
This includes the entire document release package.
|
||||
|
||||
<!-- page 29 -->
|
||||
|
||||
***USB 3.2*** ***Universal Serial Bus Revision 3.2 Specification***
|
||||
This includes the entire document release package.
|
||||
USB 3.1 Legacy Cable and Connector Specification, Revision 1.0
|
||||
|
||||
***USB4*** ***USB4 Specification, Version 2.0, June 2023***
|
||||
(including posted errata and ECNs)
|
||||
|
||||
***TBT3*** *Chapter 13 of* ***USB4 Specification, Version 2.0, June 2023***
|
||||
|
||||
***USB PD*** ***USB Power Delivery Specification, Revision 2.0, Version 1.3, January 12, 2017***
|
||||
***USB Power Delivery Specification, Revision 3.2, Version 1.2, January 2026***
|
||||
(including posted errata and ECNs)
|
||||
|
||||
***USB BB*** ***USB Billboard Device Class Specification, Revision 1.2.2, January 29, 2021***
|
||||
|
||||
***USB BC*** ***Battery Charging Specification, Revision 1.2, March 15, 2012***
|
||||
(including posted errata and ECNs)
|
||||
|
||||
***DP AM*** ***DisplayPort™ Alt Mode on USB Type-C Standard, Version 2.1a, August 2024***
|
||||
|
||||
All USB-specific documents are available for download at http://www.usb.org/documents.
|
||||
The ***DisplayPort Alt Mode*** specification is available from VESA (http://www.vesa.org).
|
||||
|
||||
## 1.4 Conventions
|
||||
|
||||
### 1.4.1 Precedence
|
||||
|
||||
If there is a conflict between text, figures, and tables, the precedence ***shall*** be tables, figures, and then text.
|
||||
|
||||
### 1.4.2 Keywords
|
||||
|
||||
The following keywords differentiate between the levels of requirements and options.
|
||||
|
||||
#### 1.4.2.1 Informative
|
||||
|
||||
***Informative*** is a keyword that describes information with this specification that intends to discuss and clarify requirements and features as opposed to mandating them.
|
||||
|
||||
#### 1.4.2.2 May
|
||||
|
||||
***May*** is a keyword that indicates a choice with no implied preference.
|
||||
|
||||
#### 1.4.2.3 May Not
|
||||
|
||||
***May not*** is a keyword that is the inverse of ***May***. Indicates a choice to not implement a given feature with no implied preference.
|
||||
|
||||
#### 1.4.2.4 N/A
|
||||
|
||||
***N/A*** is a keyword that indicates that a field or value is not applicable and has no defined value and ***shall not*** be checked or used by the recipient.
|
||||
|
||||
#### 1.4.2.5 Normative
|
||||
|
||||
***Normative*** is a keyword that describes features that are mandated by this specification.
|
||||
|
||||
<!-- page 30 -->
|
||||
|
||||
#### 1.4.2.6 Optional and Optionally
|
||||
|
||||
***Optional*** and ***Optionally*** are equivalent keywords that describe features not mandated by this specification. However, if an ***optional*** feature is implemented, the feature ***shall*** be implemented as defined by this specification (***optional normative***).
|
||||
|
||||
#### 1.4.2.7 Reserved
|
||||
|
||||
***Reserved*** is a keyword indicating reserved bits, bytes, words, fields, and code values that are set-aside for future standardization. Their use and interpretation may be specified by future extensions to this specification and, unless otherwise stated, ***shall not*** be utilized, or adapted by vendor implementation. A reserved bit, byte, word, or field ***shall*** be set to zero by the sender and ***shall*** be ignored by the receiver. ***Reserved*** field values ***shall not*** be sent by the sender and, if received, ***shall*** be ignored by the receiver.
|
||||
|
||||
#### 1.4.2.8 Shall
|
||||
|
||||
***Shall*** is a keyword indicating a mandatory (***normative***) requirement. Designers are mandated to implement all such requirements to ensure interoperability with other compliant Devices.
|
||||
|
||||
#### 1.4.2.9 Shall Not
|
||||
|
||||
***Shall not*** is a keyword that is the inverse of ***Shall*** indicating non-compliant operation.
|
||||
|
||||
#### 1.4.2.10 Should
|
||||
|
||||
***Should*** is a keyword indicating flexibility of choice with a preferred alternative. Equivalent to the phrase “it is recommended that …”.
|
||||
|
||||
#### 1.4.2.11 Should Not
|
||||
|
||||
***Should not*** is a keyword that is the inverse of ***Should***. Equivalent to the phrase “it is recommended that implementations do not ...”.
|
||||
|
||||
### 1.4.3 Numbering
|
||||
|
||||
Numbers that are immediately followed by a lowercase “b” (e.g., 01b) are binary values. Numbers that are immediately followed by an uppercase “B” are byte values. Numbers that are immediately followed by a lowercase “h” (e.g., 3Ah) are hexadecimal values. Numbers not immediately followed by either a “b”, “B”, or “h” are decimal values.
|
||||
|
||||
## 1.5 Terms and Abbreviations
|
||||
|
||||
| Term | Description |
|
||||
| --- | --- |
|
||||
| Accessory Mode | A reconfiguration of the connector based on the presence of ***Rd***/***Rd*** on CC1/CC2, respectively. |
|
||||
| Active cable | Active cables are USB Full-Featured Type-C Cables that incorporate repeaters in the ***USB 3.2*** data path. All active cables, regardless of length, are expected to comply with this specification, the ***USB 3.2*** Appendix E, and the ***USB 3.2*** active cable CTS. Active cables ***may*** incorporate repeaters in both ends of the cable, one end, or anywhere in the cable. See Chapter 6. |
|
||||
| ***Alternate Mode*** | Operation defined by a vendor or standards organization that is associated with a SVID assigned by the ***USB-IF***. Entry and exit into and from an ***Alternate Mode*** is controlled by the ***USB PD*** Structured VDM Enter Mode and Exit Mode commands. See Appendix E. |
|
||||
| ***Alternate Mode Adapter*** (AMA) | A ***USB PD*** Device which supports ***Alternate Modes*** and acts as a UFP. |
|
||||
|
||||
<!-- page 31 -->
|
||||
|
||||
| Term | Description |
|
||||
| --- | --- |
|
||||
| Assured Capacity Port | A charger port that has a dedicated allocation of power, *i.e.*, the port isn’t part of a Shared Capacity group of ports. |
|
||||
| ***Audio Adapter Accessory Mode*** | The Accessory Mode defined by the presence of ***Ra***/***Ra*** on CC1/CC2, respectively. This mode is ***deprecated*** and replaced by ***Liquid Corrosion Mitigation Mode***. |
|
||||
| BMC | Biphase Mark Coding used for ***USB PD*** communication over the CC wire. |
|
||||
| Cable Port Partner | The USB Type-C DRP, Source, or Sink connected to the cable plug. |
|
||||
| Captive cable | A cable that is terminated on one end with a USB Type-C plug and has a vendor-specific connect means (hardwired or custom detachable) on the opposite end. |
|
||||
| CC | Configuration Channel (CC) used in the discovery, configuration, and management of connections across a USB Type-C cable. See Section 4.5. |
|
||||
| ***Charge-Through VPD*** (***CTVPD***) | A VCONN-Powered USB Device that has the mechanism to pass power and CC communication from one port to the other without any reregulation. See Section 4.10.2. |
|
||||
| Configuration Lane | The ***USB 3.2*** Configuration Lane is used to establish and manage dual-lane SuperSpeed USB operation. The Configuration Lane is specifically the SuperSpeed USB TX1/RX1 differential signal set in the cable/plug. |
|
||||
| ***Debug Accessory Mode*** (DAM) | The Accessory Mode defined by the presence of ***Rd***/***Rd*** or ***Rp***/***Rp*** on CC1/CC2, respectively. See Appendix B. |
|
||||
| ***Debug and Test System*** (DTS) | The combined hardware and software system that provides a system developer debug visibility and control when connected to a ***Target System*** in ***Debug Accessory Mode***. |
|
||||
| Default VBUS | VBUS voltage as defined by the ***USB 2.0*** and ***USB 3.2*** specifications. Note: where used, 5V VBUS connotes the same meaning. |
|
||||
| DFP | Downstream Facing Port, specifically associated with the flow of data in a USB connection. Typically, the ports on a host or the ports on a hub to which devices are connected. In its initial state, the DFP sources VBUS and VCONN, and supports data. A charge-only DFP port only sources VBUS. |
|
||||
| Direct connect device | A device with either a captive cable or just a USB Type-C plug (e.g., thumb drive). |
|
||||
| DRD (Dual-Role-Data) | The acronym used in this specification to refer to a USB port that can operate as either a DFP (Host) or UFP (Device). The role that the port initially takes is determined by the port’s power role at attach. A Source port takes on the data role of a DFP and a Sink port takes on the data role of a UFP. The port’s data role ***may*** be changed dynamically using ***USB PD*** Data Role Swap. |
|
||||
| DRP (Dual-Role-Power) | The acronym used in this specification to refer to a USB port that can operate as either a Source or a Sink. The role that the port offers ***may*** be fixed to either a Source or Sink or ***may*** alternate between the two port states. Initially when operating as a Source, the port will also take on the data role of a DFP and when operating as a Sink, the port will also take on the data role of a UFP. The port’s power role ***may*** be changed dynamically using ***USB PD*** Power Role Swap. |
|
||||
| ***DR_Swap*** | ***USB PD*** Data Role Swap. |
|
||||
| Dual-lane (x2) | Dual-lane operation is defined as simultaneously signaling on both sets of USB transmit and receive differential pairs (TX1/RX1 and TX2/RX2 in the cable/plug). |
|
||||
|
||||
<!-- page 32 -->
|
||||
|
||||
| Term | Description |
|
||||
| --- | --- |
|
||||
| Electronically Marked Cable | A USB Type-C cable that uses ***USB PD*** to provide the cable’s characteristics. See Section 4.9. |
|
||||
| eMarker | The element in an Electronically Marked Cable that returns information about the cable in response to a ***USB PD Discover Identity*** command. |
|
||||
| Guaranteed Capability Port | As defined by the ***USB PD*** specification. |
|
||||
| Hybrid Optical Active Cable | A cable that uses an intermediate optical transmission line for the high-speed signaling path (TX/RX) while retaining a metallic conductor-based solution for the rest of the defined interfaces, e.g., CC, ***USB 2.0***, SBUs, etc. |
|
||||
| Initiator | The port initiating a Vendor Defined Message. It is independent of the port’s PD role (e.g., Provider, Consumer, Provider/Consumer, or Consumer/Provider). In most cases, the Initiator will be a host. |
|
||||
| Internal Temperature | In reference to an active cable, the temperature measured inside a plug. It is not the skin temperature. There is a relationship between the plug’s internal temperature and the skin temperature, but that relationship is design dependent. |
|
||||
| ***Liquid Corrosion Mitigation Mode*** | The mode defined by the presence of ***Ra***/***Ra*** on CC1/CC2, respectively. See Appendix A. |
|
||||
| Local Plug | The cable plug being referred to. |
|
||||
| Managed Capability Port | As defined by the ***USB PD*** specification. |
|
||||
| Optically Isolated Active Cable (OIAC) | A cable that uses an intermediate optical transmission line for all signaling. This cable has no metallic conductors and is electrically isolated between the two plugs. This cable has a USB Type-C Plug on each end with one Cable Plug supporting SOP’ and the other supporting SOP”. |
|
||||
| Passive cable | A cable that does not incorporate any electronics to condition the data path signals. A passive cable ***may*** or ***may not*** be electronically marked. |
|
||||
| Port Partner | Refers to the port (device or host) a port is attached to. |
|
||||
| Power Bank | A device with a battery whose primary function is to charge or otherwise extend the runtime of other USB Type-C devices. |
|
||||
| Power Delivery Mode | A mode where the port partners are in a ***USB PD*** power contract (either Explicit or Implicit). |
|
||||
| Port Maximum PDP | As defined by the ***USB PD*** specification. |
|
||||
| Port Present PDP | As defined by the ***USB PD*** specification. |
|
||||
| Power Sinking Devices (PSD) | Sink which draws power but has no other USB or ***Alternate Mode*** communication function, e.g., a USB-powered light. |
|
||||
| Powered cable | A cable with electronics in the plug that requires VCONN indicated by the presence of ***Ra*** between the VCONN pin and ground. |
|
||||
| ***PR_Swap*** | ***USB PD*** Power Role Swap. |
|
||||
| Re-driver | Re-driver refers to an analog component that operates on the signal without re-timing it. This ***may*** include equalization, amplification, and transmitter. The re- |
|
||||
|
||||
<!-- page 33 -->
|
||||
|
||||
| Term | Description |
|
||||
| --- | --- |
|
||||
| | driver does not include a clock-data recovery (CDR) circuit. Re-drivers are beyond the scope of this document. |
|
||||
| Remaining Shared Capacity | The remaining power available for a Shared Capacity group of ports after power has been allocated to one or more of its ports. |
|
||||
| Remote Plug | A remote cable plug in the context of OIAC plugs is the plug at the other end of the Optically Isolated Active Cable. |
|
||||
| Repeater | Repeater refers to any active component that acts on a signal in order to increase the physical lengths and/or interconnect loss over which the signal can be transmitted successfully. The category of repeaters includes both re-timers and re-drivers. |
|
||||
| Responder | The port responding to the Initiator of a Vendor Defined Message (VDM). It is independent of the port’s ***USB PD*** role (e.g., Provider, Consumer, Provider/Consumer, or Consumer/Provider). In most cases, the Responder will be a device. |
|
||||
| Re-timer | Re-timer refers to a component that contains a clock-data recovery (CDR) circuit that “retimes” the signal. The re-timer latches the signal into a synchronous memory element before re-transmitting it. It is used to extend the physical length of the system without accumulating high frequency jitter by creating separate clock domains on either side of the re-timer. Re-timers are defined in ***USB 3.2*** Appendix E and ***USB4***. |
|
||||
| SBU | Sideband Use. |
|
||||
| Shared Capacity Port | A charger port where its allocation of power may be constrained due to it being part of a group of ports that share a common power source that is less than the sum of the individual port’s power ratings. |
|
||||
| Shared Port Power Available | The power available, up to the port’s PDP, to an unattached port in a Shared Capacity group of ports. This power represents what is available to each port in the group when a Sink is attached after considering power that is already allocated to ports with connected Sinks. This power will be a minimum of 7.5 W, initially offered as USB Type-C Current @ 1.5 A. |
|
||||
| Short Active Cable (SAC) | A cable with a USB Type-C Plug on each end, at least one of which is a Cable Plug supporting SOP’. Cable length up to 5 meters. |
|
||||
| SID | A Standard ID (SID) is a unique 16-bit value assigned by the ***USB-IF*** to identify an industry standard. |
|
||||
| Single-lane (x1) | ***USB 3.2*** single-lane operation is defined as signaling on only one set of SuperSpeed USB transmit and receive differential pairs (TX1/RX1 in the cable/plug). |
|
||||
| Sink | Port asserting ***Rd*** on CC and when attached is consuming power from VBUS; most commonly a Device. |
|
||||
| Skin Temperature | In reference to an active cable, the temperature of a plug’s over-mold. |
|
||||
| Source | Port asserting ***Rp*** on CC and when attached is providing power over VBUS; most commonly a Host or Hub DFP. |
|
||||
| SVID | General reference to either a SID or a VID. Used by ***USB PD*** Structured VDMs when requesting SIDs and VIDs from a device. |
|
||||
| ***Target System*** (TS) | The system being debugged in ***Debug Accessory Mode***. |
|
||||
|
||||
<!-- page 34 -->
|
||||
|
||||
| Term | Description |
|
||||
| --- | --- |
|
||||
| Total Shared Capacity | The total power available for a Shared Capacity group of ports. This is the overall power available when none of the ports in the group are connected to Sinks. |
|
||||
| Type-A | A general reference to all versions of USB “A” plugs and receptacles. |
|
||||
| Type-B | A general reference to all versions of USB “B” plugs and receptacles. |
|
||||
| Type-C Plug | A USB plug conforming to the mechanical and electrical requirements in this specification. |
|
||||
| Type-C Port | The USB port associated to a USB Type-C receptacle. This includes the USB signaling, CC logic, multiplexers, and other associated logic. |
|
||||
| Type-C Receptacle | A USB receptacle conforming to the mechanical and electrical requirements of this specification. |
|
||||
| UFP | Upstream Facing Port, specifically associated with the flow of data in a USB connection. The port on a device or a hub that connects to a host or the DFP of a hub. In its initial state, the UFP sinks VBUS and supports data. |
|
||||
| ***USB 2.0*** Type-C Cable | A USB Type-C to Type-C cable that only supports ***USB 2.0*** data operation. This cable does not include ***USB 3.2*** or SBU wires. |
|
||||
| ***USB 2.0*** Type-C Plug | A USB Type-C plug specifically designed to implement the ***USB 2.0*** Type-C cable. |
|
||||
| USB Full-Featured Type-C Cable | A USB Type-C to Type-C cable that supports ***USB 2.0***, ***USB 3.2*** and ***USB4*** data operation. This cable includes SBU wires and is an Electronically Marked Cable. |
|
||||
| USB Full-Featured Type-C Plug | A USB Type-C plug specifically designed to implement the USB Full-Featured Type-C cable. |
|
||||
| ***USB4*** Hub | A ***USB4*** hub product is used for USB port expansion, includes only USB upstream and downstream ports, and does not include any additional capability that exposes other connector types or functions except as defined in Section 5.2.3 (***Alternate Modes*** Support). |
|
||||
| ***USB4***-based Dock | A ***USB4***-based dock product combines a ***USB4*** hub (including at least one exposed USB Type-C downstream port) with additional capabilities that either exposes other connector types and/or includes other user-visible functions, e.g., storage, networking, etc. Examples of functions that are not considered user-visible include firmware update and device authentication. |
|
||||
| USB Safe State | The USB Safe State as defined by the ***USB PD*** specification. |
|
||||
| ***VCONN-Powered Accessory*** (***VPA***) | An accessory that is powered from VCONN to operate in an ***Alternate Mode***. ***VPA***s cannot implement the charge-through mechanism described for ***VPD***s, and instead must intermediate by negotiating ***USB Power Delivery*** with both the connected host and source in order to enable similar functionality. See Section 4.10.1. |
|
||||
| ***VCONN-Powered USB Device*** (***VPD***) | A USB direct-connect or captive-cable device that can be powered solely from either VCONN or VBUS. ***VPD***s ***may optionally*** support the ***VPD*** charge-through capability. See Section 4.10.2. |
|
||||
| ***VCONN_Swap*** | ***USB PD*** VCONN Swap. |
|
||||
| VDM | Vendor Defined Message as defined by the ***USB PD*** specification. |
|
||||
| VID | A Vendor ID (VID) is a unique 16-bit value assigned by the ***USB-IF*** to identify a vendor. |
|
||||
|
||||
<!-- page 35 -->
|
||||
|
||||
| Term | Description |
|
||||
| --- | --- |
|
||||
| ***vSafe0V*** | VBUS “0 volts” as defined by the ***USB PD*** specification. |
|
||||
| ***vSafe5V*** | VBUS “5 volts” as defined by the ***USB PD*** specification. |
|
||||
| x1 | See Single-lane. |
|
||||
| x2 | See Dual-lane. |
|
||||
BIN
USB_TypeC_R2.5/01-introduction.pdf
Normal file
207
USB_TypeC_R2.5/02-overview.md
Normal file
|
|
@ -0,0 +1,207 @@
|
|||
<!-- page 36 -->
|
||||
|
||||
# 2 Overview
|
||||
|
||||
## 2.1 Introduction
|
||||
|
||||
The USB Type-C® receptacle, plug and cable provide a smaller, thinner, and more robust alternative to legacy USB interconnect (Standard and Micro USB cables and connectors). This solution targets use in very thin platforms, ranging from ultra-thin notebook PCs down to smart phones where existing Standard-A and Micro-AB receptacles are deemed too large, difficult to use, or inadequately robust.
|
||||
|
||||
Some key specific enhancements include:
|
||||
|
||||
- The USB Type-C receptacle may be used in very thin platforms as its total system height for the mounted receptacle is under 3 mm
|
||||
- The USB Type-C plug enhances ease of use by being plug-able in either upside-up or upside-down directions
|
||||
- The USB Type-C cable enhances ease of use by being plug-able in either direction between host and devices
|
||||
|
||||
While the USB Type-C interconnect no longer physically differentiates plugs on a cable by being an A-type or B-type, the USB interface still maintains such a host-to-device logical relationship. Determination of this host-to-device relationship is accomplished through a Configuration Channel (CC) that is connected through the cable. In addition, the Configuration Channel is used to set up and manage power and Alternate/Accessory Modes.
|
||||
|
||||
Using the Configuration Channel, the USB Type-C interconnect defines a simplified 5 volt VBUS-based power delivery and charging solution that supplements what is already defined in the ***USB 3.2*** Specification. More advanced power delivery and battery charging features over the USB Type-C interconnect are based on the ***USB Power Delivery*** specification. As a product implementation improvement, the USB Type-C interconnect shifts the ***USB PD*** communication protocol from being communicated over VBUS to being delivered across the USB Type-C Configuration Channel.
|
||||
|
||||
The USB Type-C receptacle, plug and cable designs are intended to support future USB functional extensions. As such, consideration was given to frequency scaling performance, pin-out arrangement and the configuration mechanisms when developing this solution. The definition of future USB functional extensions is not in the scope of this specification but rather will be provided in future releases of the base USB Specification, i.e., beyond the existing ***USB4*** Specification.
|
||||
|
||||
Figure 2-1 illustrates the comprehensive functional signal plan for the USB Full-Featured Type-C receptacle, not all signals shown are required in all platforms or devices. As shown, the receptacle signal list functionally delivers both ***USB 2.0*** (D+ and D−) and either ***USB 3.2*** or ***USB4*** (TX and RX pairs) data buses, USB power (VBUS) and ground (GND), Configuration Channel signals (CC1 and CC2), and two Sideband Use (SBU) signal pins. Multiple sets of USB data bus signal locations in this layout facilitate being able to functionally map the USB signals independent of plug orientation in the receptacle. For reference, the signal pins are labeled. For the ***USB 2.0*** Type-C receptacle, neither the ***USB 3.2*** nor ***USB4*** signals are implemented.
|
||||
|
||||
**Figure 2-1 USB Type-C Receptacle Interface (Front View)**
|
||||
|
||||

|
||||
|
||||
Figure 2-2 illustrates the comprehensive functional signal plan for the USB Type-C plug. Only one CC pin is connected through the cable to establish signal orientation, and the other CC pin is repurposed as VCONN for
|
||||
|
||||
<!-- page 37 -->
|
||||
|
||||
powering electronics in the USB Type-C plug. Also, only one set of ***USB 2.0*** D+/D− wires are implemented in a USB Type-C cable. For USB Type-C cables that only intend to support ***USB 2.0*** functionality, the TX/RX and SBU signals are not implemented. For the USB Type-C Power-Only plug (intended only for USB Type-C Sink applications), only nine contacts are implemented to support CC, VBUS, and GND.
|
||||
|
||||
**Figure 2-2 USB Full-Featured Type-C Plug Interface (Front View)**
|
||||
|
||||

|
||||
|
||||
## 2.2 USB Type-C Receptacles, Plugs and Cables
|
||||
|
||||
Cables and connectors, including USB Type-C to USB legacy cables and adapters, are explicitly defined within this specification. These are the only connectors and cables that are authorized by the licensing terms of this specification. All licensed cables and connectors are required to comply with the compliance and certification requirements that are developed and maintained by the ***USB-IF***.
|
||||
|
||||
The following USB Type-C receptacles and plugs are defined.
|
||||
|
||||
- USB Full-Featured Type-C receptacle for ***USB 2.0***, ***USB 3.2***, ***USB4*** and full-featured platforms and devices.
|
||||
- ***USB 2.0*** Type-C receptacle for ***USB 2.0*** platforms and devices.
|
||||
- USB Type-C Power-Only receptacle.
|
||||
- USB Full-Featured Type-C plug.
|
||||
- ***USB 2.0*** Type-C plug.
|
||||
- USB Type-C Power-Only plug.
|
||||
|
||||
The following USB Type-C cables are defined.
|
||||
|
||||
- USB Full-Featured Type-C cable with a USB Full-Featured Type-C plug at both ends for ***USB 3.2***, ***USB4*** and full-featured applications.
|
||||
- ***USB 2.0*** Type-C cable with a ***USB 2.0*** Type-C plug at both ends for ***USB 2.0*** applications.
|
||||
- Captive cable with either a USB Full-Featured Type-C plug or ***USB 2.0*** Type-C plug at one end.
|
||||
- Active cables as defined in Chapter 6.
|
||||
|
||||
All of the defined USB Type-C receptacles, plugs and cables (except OIAC) support USB charging applications, including support for the ***optional*** USB Type-C-specific implementation of the ***USB Power Delivery*** specification (See Section 4.6.2.4).
|
||||
|
||||
All USB Full-Featured Type-C cables are electronically marked. ***USB 2.0*** Type-C cables ***may*** be electronically marked. See Section 4.9 for the requirements of Electronically Marked Cables.
|
||||
|
||||
The following USB Type-C to USB legacy cables and adapters are defined.
|
||||
|
||||
- ***USB 3.2*** Type-C to Legacy Host cable with a USB Full-Featured Type-C plug at one end and a ***USB 3.1*** Standard-A plug at the other end – this cable supports use of a USB Type-C-based device with a legacy USB host.
|
||||
|
||||
<!-- page 38 -->
|
||||
|
||||
- ***USB 2.0*** Type-C to Legacy Host cable with a ***USB 2.0*** Type-C plug at one end and a ***USB 2.0*** Standard-A plug at the other end – this cable supports use of a USB Type-C-based device with a legacy ***USB 2.0*** host (primarily for mobile charging and sync applications).
|
||||
- ***USB 3.2*** Type-C to Legacy Device cable with a USB Full-Featured Type-C plug at one end and a ***USB 3.1*** Standard-B plug at the other end – this cable supports use of legacy ***USB 3.1*** hubs and devices with a USB Type-C-based host.
|
||||
- ***USB 2.0*** Type-C to Legacy Device cable with a ***USB 2.0*** Type-C plug at one end and a ***USB 2.0*** Standard-B plug at the other end – this cable supports use of legacy ***USB 2.0*** hubs and devices with a USB Type-C-based host.
|
||||
- ***USB 2.0*** Type-C to Legacy Mini Device cable with a ***USB 2.0*** Type-C plug at one end and a ***USB 2.0*** Mini-B plug at the other end – this cable supports use of legacy devices with a ***USB 2.0*** Type-C-based host.
|
||||
- ***USB 3.2*** Type-C to Legacy Micro Device cable with a USB Full-Featured Type-C plug at one end and a ***USB 3.1*** Micro-B plug at the other end – this cable supports use of legacy ***USB 3.1*** hubs and devices with a USB Type-C-based host.
|
||||
- ***USB 2.0*** Type-C to Legacy Micro Device cable with a ***USB 2.0*** Type-C plug at one end and a ***USB 2.0*** Micro-B plug at the other end – this cable supports use of legacy ***USB 2.0*** hubs and devices with a USB Type-C-based host.
|
||||
- ***USB 3.2*** Type-C to Legacy Standard-A adapter with a USB Full-Featured Type-C plug at one end and a ***USB 3.1*** Standard-A receptacle at the other end – this adapter supports use of a legacy USB “thumb drive” style device or a legacy USB ThinCard device with a ***USB 3.2*** Type-C-based host.
|
||||
- ***USB 2.0*** Type-C to Legacy Micro-B adapter with a ***USB 2.0*** Type-C plug at one end and a ***USB 2.0*** Micro-B receptacle at the other end – this adapter supports charging a USB Type-C-based mobile device using a legacy USB Micro-B-based chargers, either captive cable-based or used in conjunction with a legacy ***USB 2.0*** Standard-A to Micro-B cable.
|
||||
|
||||
USB Type-C receptacle to USB legacy adapters are explicitly not defined or allowed. Such adapters would allow many invalid, and potentially unsafe, cable connections to be constructed by users.
|
||||
|
||||
## 2.3 Configuration Process
|
||||
|
||||
The USB Type-C receptacle, plug and cable solution incorporates a configuration process to detect a downstream facing port to upstream facing port (Source-to-Sink) connection for VBUS management and host-to-device connected relationship determination.
|
||||
|
||||
The USB Type-C port configuration process is used for the following:
|
||||
|
||||
- Source-to-Sink attach/detach detection,
|
||||
- plug orientation/cable twist detection,
|
||||
- initial power (Source-to-Sink) detection and establishing the data (Host-to-Device) relationship,
|
||||
- detect if cable requires VCONN,
|
||||
- USB Type-C VBUS current detection and usage,
|
||||
- ***USB PD*** communication, and
|
||||
- discovery and configuration of functional extensions.
|
||||
|
||||
Two pins on the USB Type-C receptacle, CC1 and CC2, are used for this purpose. Within a standard USB Type-C cable, only a single CC pin position within each plug of the cable is connected through the cable.
|
||||
|
||||
<!-- page 39 -->
|
||||
|
||||
### 2.3.1 Source-to-Sink Attach/Detach Detection
|
||||
|
||||
Initially, Source-to-Sink attach is detected by a host or hub port (Source) when one of the CC pins at its USB Type-C receptacle senses a specified resistance to GND. Subsequently, Source-to-Sink detach is detected when the CC pin that was terminated at its USB Type-C receptacle is no longer terminated to GND.
|
||||
|
||||
Power is not applied to the USB Type-C host or hub receptacle (VBUS or VCONN) until the Source detects the presence of an attached device (Sink) port. When a Source-to-Sink attach is detected, the Source is expected to enable power to the receptacle and proceed to normal USB operation with the attached device. When a Source-to-Sink detach is detected, the port sourcing VBUS removes power.
|
||||
|
||||
### 2.3.2 Plug Orientation/Cable Twist Detection
|
||||
|
||||
The USB Type-C plug can be inserted into a receptacle in either one of two orientations, therefore the CC pins enable a method for detecting plug orientation in order to determine the lane ordering of the USB TX/RX data signal pairs functionally connected through the cable and identify the Configuration Lane for dual-lane operation when supported. This allows for signal routing, if needed, within a host or device to be established for a successful connection.
|
||||
|
||||
### 2.3.3 Initial Power (Source-to-Sink) Detection and Establishing the Data (Host-to-Device) Relationship
|
||||
|
||||
Unlike existing USB Type-A and USB Type-B receptacles and plugs, the mechanical characteristics of the USB Type-C receptacle and plug do not inherently establish the relationship of USB host and device ports. The CC pins on the receptacle also serve to establish an initial power (Source-to-Sink) and data (Host-to-Device) relationships prior to the normal USB enumeration process.
|
||||
|
||||
For the purpose of defining how the CC pins are used to establish the initial power relationship, the following port power behavior modes are defined.
|
||||
|
||||
1. Source-only – for this mode, the port exclusively behaves as a Source.
|
||||
2. Sink-only – for this mode, the port exclusively behaves as a Sink.
|
||||
3. Dual-Role-Power (DRP) – for this mode, the port can behave either as a Source or Sink.
|
||||
|
||||
Additionally, when a port supports USB data operation, a port’s data behavior modes are defined.
|
||||
|
||||
1. DFP-only – for this mode, the port exclusively behaves as a DFP.
|
||||
2. UFP-only – for this mode, the port exclusively behaves as a UFP.
|
||||
3. Dual-Role-Data (DRD) – for this mode, the port can behave either as a DFP or UFP.
|
||||
|
||||
The DFP-only and UFP-only ports behaviorally map to traditional USB host ports and USB device ports, respectively but ***may not*** necessarily do USB data communication. When a host-only port is attached to a device-only port, the behavior from the user’s perspective follows the traditional USB host-to-device port model. However, the USB Type-C connector solution does not physically prevent host-to-host or device-to-device connections. In this case, the resulting host-to-host or device-to-device connection results in a safe but non-functional situation.
|
||||
|
||||
Once initially established, the Source supplies VBUS and behaves as a DFP, and the Sink consumes VBUS and behaves as a UFP. ***USB PD***, when supported by both ports, ***may*** then be used to independently swap both the power and data roles of the ports.
|
||||
|
||||
A port that supports dual-role operation by being able to shift to the appropriate connected mode when attached to either a Source-only or Sink-only port is a DRP. In the special case of a DRP being attached to another DRP, an initialization protocol across the CC pins is used to establish the initial host-to-device relationship. Given no role-swapping intervention, the determination of which is DFP or UFP is random from the user’s perspective.
|
||||
|
||||
<!-- page 40 -->
|
||||
|
||||
Two independent sets of mechanisms are defined to allow a USB Type-C DRP to functionally swap power and data roles. When ***USB PD*** is supported, power and data role swapping is performed as a subsequent step following the initial connection process. For non-PD implementations, power/data role swapping can ***optionally*** be dealt with as part of the initial connection process. To improve the user’s experience when connecting devices that are of categorically different types, products ***may*** be implemented to strongly prefer being a DFP or a UFP, such that the DFP/UFP determination becomes predictable when connecting two DRPs of differing categories. See Section 4.5.1.4 for more on available swapping mechanisms.
|
||||
|
||||
As an alternative to role swapping, a USB Type-C DRP ***may*** provide useful functionality by when operating as a host, exposing a CDC/network (preferably TCP/IP) stack or when operating as a device, exposing a CDC/network interface.
|
||||
|
||||
USB hubs have two types of ports, a UFP that is connected to a DFP (host or another hub) that initially functions as a Sink, and one or more DFPs for connecting other devices that initially function as Sources.
|
||||
|
||||
### 2.3.4 USB Type-C VBUS Current Detection and Usage
|
||||
|
||||
With the USB Type-C connector solution, a Source (host or downstream hub port) ***may*** implement higher source current over VBUS to enable faster charging of mobile devices or higher-power devices. All USB host and hub ports advertise via the CC pins the level of current that is presently available. The USB device port is required to manage its load to stay within the current level offered by the host or hub, including dynamically scaling back the load if the host or hub port changes its advertisement to a lower level as indicated over the CC pins.
|
||||
|
||||
Three current level advertisements at 5V VBUS are defined by ***USB Type-C Current***:
|
||||
|
||||
- ***USB Type-C Current*** at Default is the as-configured for high-power operation current value as defined by a USB Specification (500 mA for ***USB 2.0*** ports; 900 mA or 1,500 mA for ***USB 3.2*** ports operating in single-lane or dual-lane, respectively),
|
||||
- ***USB Type-C Current*** at 1.5 A, and
|
||||
- ***USB Type-C Current*** at 3.0 A.
|
||||
|
||||
There is a clear functional distinction between advertising ***USB Type-C Current*** at Default versus the ***USB Type-C Current*** at either 1.5 A or 3.0 A.
|
||||
|
||||
- ***USB Type-C Current*** at Default is intended for host operation in providing bus power to a connected device where the host manages the device’s current consumption for the low-power, high-power and suspend states as defined in the USB base specifications.
|
||||
- ***USB Type-C Current*** at either 1.5 A or 3.0 A is primarily intended for charging applications. The Sink can vary its current draw up to the advertised limit. Offering ***USB Type-C Current*** at either 1.5 A or 3.0 A is allowed for a host providing bus power to a device. The host needs to assume that the device will continuously draw up to the offered limit.
|
||||
|
||||
The higher ***USB Type-C Current*** levels that can be advertised allows hosts and devices that do not implement ***USB PD*** to take advantage of higher charging current.
|
||||
|
||||
### 2.3.5 ***USB PD*** Communications
|
||||
|
||||
***USB Power Delivery*** is a feature on products (hosts, hubs, and devices). ***USB PD*** communications is used to:
|
||||
|
||||
- establish power contracts that allow voltage and current beyond existing USB data bus specifications,
|
||||
- change the port sourcing VBUS,
|
||||
- change the port sourcing VCONN,
|
||||
- swap DFP and UFP roles, and
|
||||
- communicate with cables.
|
||||
|
||||
<!-- page 41 -->
|
||||
|
||||
The ***USB PD*** Bi-phase Mark Coded (BMC) communications are carried on the CC wire of the USB Type-C cable.
|
||||
|
||||
### 2.3.6 Functional Extensions
|
||||
|
||||
Functional extensions, including ***USB4*** and ***Alternate Modes*** (see Appendix E) are enabled via a communications channel across CC using methods defined by the ***USB Power Delivery*** specification.
|
||||
|
||||
## 2.4 VBUS
|
||||
|
||||
VBUS provides a path to deliver power between a host and a device, and between a USB power charger and a host/device. A simplified high-current supply capability is defined for hosts and chargers that ***optionally*** support current levels beyond the ***USB 2.0***, ***USB 3.2***, and ***USB4*** specifications. The ***USB Power Delivery*** specification is supported.
|
||||
|
||||
Table 2-1 summarizes the power supply options available from the perspective of a device with the USB Type-C connector. Not all options will be available to the device from all host or hub ports – only the first two listed options are mandated by the base USB specifications and form the basis of ***USB Type-C Current*** at the Default USB Power level.
|
||||
|
||||
**Table 2-1 Summary of power supply options**
|
||||
|
||||
| Mode of Operation | Voltage | Current | Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| ***USB 2.0*** | 5 V | See ***USB 2.0*** | |
|
||||
| ***USB 3.2*** | 5 V | See ***USB 3.2*** | |
|
||||
| ***USB4*** | 5 V | 1.5 A | See Section 5.3. |
|
||||
| ***USB BC 1.2*** | 5 V | 1.5 A<sup>1</sup> | Legacy charging |
|
||||
| ***USB Type-C Current*** @ 1.5 A | 5 V | 1.5 A | Supports higher power devices |
|
||||
| ***USB Type-C Current*** @ 3.0 A | 5 V | 3 A | Supports higher power devices |
|
||||
| ***USB PD*** | Configurable up to 48 V | Configurable up to 5 A | Directional control and power level management |
|
||||
|
||||
1. Whereas ***USB BC 1.2*** specification permits a power provider to be designed to support a level of power between 0.5 A and 1.5 A, the USB Type-C specification requires that a Source port that supports ***USB BC 1.2*** be at a minimum capable of supplying 1.5 A and advertise ***USB Type-C Current*** @ 1.5 A in addition to supporting the ***USB BC 1.2*** power provider termination.
|
||||
|
||||
The USB Type-C receptacle is specified for current capability of 5 A whereas standard USB Type-C cable assemblies are rated for 3 A. The higher rating of the receptacle enables systems to deliver more power over directly attached docking solutions or using appropriately designed chargers with captive cables when implementing ***USB PD***. Also, USB Type-C cable assemblies designed for ***USB PD*** and appropriately identified via electronic marking are allowed to support up to 5 A.
|
||||
|
||||
USB Type-C cable assemblies designed for ***USB PD*** Extended Power Range (EPR) operation are required to have an electronic marking indicating EPR compatibility. These cables are required to be electronically marked for 5 A and 50 V and include the EPR Mode Capable bit set.
|
||||
|
||||
## 2.5 VCONN
|
||||
|
||||
Once the connection between host and device is established, the CC pin (CC1 or CC2) in the receptacle that is not connected via the CC wire through the standard cable is repurposed to source VCONN to power circuits in the plug needed to implement Electronically Marked Cables (see Section 4.9), ***VCONN-Powered Accessories*** and ***VCONN-Powered USB Devices***. Initially, the source supplies VCONN and the source of VCONN ***may*** be swapped using ***USB PD VCONN_Swap***.
|
||||
|
||||
<!-- page 42 -->
|
||||
|
||||
Once VCONN is available, all electronically marked cables use it as the only power source. If VCONN is applied after VBUS, then until VCONN is available, the cable ***may*** remain unpowered or ***may*** draw power from VBUS.
|
||||
|
||||
VCONN functionally differs from VBUS in that it is isolated from the other end of the cable. VCONN is independent of VBUS and, unlike VBUS which can use ***USB PD*** to support higher voltages, VCONN voltage stays within the range of 3.0 to 5.5 V.
|
||||
|
||||
## 2.6 Hubs
|
||||
|
||||
USB hubs implemented with USB Type-C receptacles are required to clearly identify the upstream facing port. This requirement is needed because a user can no longer know which port on a hub is the upstream facing port and which ports are the downstream facing ports by the type of receptacles that are exposed, i.e., USB Type-B is the upstream facing port and USB Type-A is a downstream facing port.
|
||||
BIN
USB_TypeC_R2.5/02-overview.pdf
Normal file
BIN
USB_TypeC_R2.5/02-overview/figure-2-1.png
Normal file
|
After Width: | Height: | Size: 43 KiB |
BIN
USB_TypeC_R2.5/02-overview/figure-2-2.png
Normal file
|
After Width: | Height: | Size: 42 KiB |
2318
USB_TypeC_R2.5/03-mechanical.md
Normal file
BIN
USB_TypeC_R2.5/03-mechanical.pdf
Normal file
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-1-cont1.png
Normal file
|
After Width: | Height: | Size: 930 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-1-cont2.png
Normal file
|
After Width: | Height: | Size: 197 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-1-cont3.png
Normal file
|
After Width: | Height: | Size: 71 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-1.png
Normal file
|
After Width: | Height: | Size: 123 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-10.png
Normal file
|
After Width: | Height: | Size: 652 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-11.png
Normal file
|
After Width: | Height: | Size: 668 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-12-cont1.png
Normal file
|
After Width: | Height: | Size: 383 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-12-cont2.png
Normal file
|
After Width: | Height: | Size: 239 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-12.png
Normal file
|
After Width: | Height: | Size: 153 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-13.png
Normal file
|
After Width: | Height: | Size: 636 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-14.png
Normal file
|
After Width: | Height: | Size: 80 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-15.png
Normal file
|
After Width: | Height: | Size: 278 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-16.png
Normal file
|
After Width: | Height: | Size: 159 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-17.png
Normal file
|
After Width: | Height: | Size: 206 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-18.png
Normal file
|
After Width: | Height: | Size: 136 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-19.png
Normal file
|
After Width: | Height: | Size: 475 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-2.png
Normal file
|
After Width: | Height: | Size: 126 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-20.png
Normal file
|
After Width: | Height: | Size: 310 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-21.png
Normal file
|
After Width: | Height: | Size: 90 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-22.png
Normal file
|
After Width: | Height: | Size: 167 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-23.png
Normal file
|
After Width: | Height: | Size: 162 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-24.png
Normal file
|
After Width: | Height: | Size: 28 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-25.png
Normal file
|
After Width: | Height: | Size: 77 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-26.png
Normal file
|
After Width: | Height: | Size: 59 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-27.png
Normal file
|
After Width: | Height: | Size: 68 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-28.png
Normal file
|
After Width: | Height: | Size: 80 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-29.png
Normal file
|
After Width: | Height: | Size: 38 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-3-cont1.png
Normal file
|
After Width: | Height: | Size: 1.1 MiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-3-cont2.png
Normal file
|
After Width: | Height: | Size: 339 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-3.png
Normal file
|
After Width: | Height: | Size: 148 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-30.png
Normal file
|
After Width: | Height: | Size: 86 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-31.png
Normal file
|
After Width: | Height: | Size: 34 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-32.png
Normal file
|
After Width: | Height: | Size: 61 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-33.png
Normal file
|
After Width: | Height: | Size: 77 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-34.png
Normal file
|
After Width: | Height: | Size: 33 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-35.png
Normal file
|
After Width: | Height: | Size: 58 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-36.png
Normal file
|
After Width: | Height: | Size: 63 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-37.png
Normal file
|
After Width: | Height: | Size: 90 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-38.png
Normal file
|
After Width: | Height: | Size: 45 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-39.png
Normal file
|
After Width: | Height: | Size: 129 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-4.png
Normal file
|
After Width: | Height: | Size: 103 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-40.png
Normal file
|
After Width: | Height: | Size: 155 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-41.png
Normal file
|
After Width: | Height: | Size: 73 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-42.png
Normal file
|
After Width: | Height: | Size: 62 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-43.png
Normal file
|
After Width: | Height: | Size: 52 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-44.png
Normal file
|
After Width: | Height: | Size: 72 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-45.png
Normal file
|
After Width: | Height: | Size: 15 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-46.png
Normal file
|
After Width: | Height: | Size: 266 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-47.png
Normal file
|
After Width: | Height: | Size: 74 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-48.png
Normal file
|
After Width: | Height: | Size: 15 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-49.png
Normal file
|
After Width: | Height: | Size: 63 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-5.png
Normal file
|
After Width: | Height: | Size: 543 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-50.png
Normal file
|
After Width: | Height: | Size: 72 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-51.png
Normal file
|
After Width: | Height: | Size: 24 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-52.png
Normal file
|
After Width: | Height: | Size: 89 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-53.png
Normal file
|
After Width: | Height: | Size: 86 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-54.png
Normal file
|
After Width: | Height: | Size: 149 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-55.png
Normal file
|
After Width: | Height: | Size: 184 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-56.png
Normal file
|
After Width: | Height: | Size: 187 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-57.png
Normal file
|
After Width: | Height: | Size: 24 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-58.png
Normal file
|
After Width: | Height: | Size: 442 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-59.png
Normal file
|
After Width: | Height: | Size: 49 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-6.png
Normal file
|
After Width: | Height: | Size: 943 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-60.png
Normal file
|
After Width: | Height: | Size: 408 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-61.png
Normal file
|
After Width: | Height: | Size: 95 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-62.png
Normal file
|
After Width: | Height: | Size: 105 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-63.png
Normal file
|
After Width: | Height: | Size: 60 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-64.png
Normal file
|
After Width: | Height: | Size: 54 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-65.png
Normal file
|
After Width: | Height: | Size: 123 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-66.png
Normal file
|
After Width: | Height: | Size: 282 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-67.png
Normal file
|
After Width: | Height: | Size: 203 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-68.png
Normal file
|
After Width: | Height: | Size: 661 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-69.png
Normal file
|
After Width: | Height: | Size: 411 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-7.png
Normal file
|
After Width: | Height: | Size: 178 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-70-cont1.png
Normal file
|
After Width: | Height: | Size: 73 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-70.png
Normal file
|
After Width: | Height: | Size: 350 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-71.png
Normal file
|
After Width: | Height: | Size: 32 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-72.png
Normal file
|
After Width: | Height: | Size: 174 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-73.png
Normal file
|
After Width: | Height: | Size: 358 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-74.png
Normal file
|
After Width: | Height: | Size: 409 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-75.png
Normal file
|
After Width: | Height: | Size: 115 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-76.png
Normal file
|
After Width: | Height: | Size: 422 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-77.png
Normal file
|
After Width: | Height: | Size: 241 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-78.png
Normal file
|
After Width: | Height: | Size: 457 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-79.png
Normal file
|
After Width: | Height: | Size: 770 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-8.png
Normal file
|
After Width: | Height: | Size: 729 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-80.png
Normal file
|
After Width: | Height: | Size: 48 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-81.png
Normal file
|
After Width: | Height: | Size: 59 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-82.png
Normal file
|
After Width: | Height: | Size: 391 KiB |
BIN
USB_TypeC_R2.5/03-mechanical/figure-3-83.png
Normal file
|
After Width: | Height: | Size: 191 KiB |