# USB Type-C power delivery
Source: [https://docs.qualcomm.com/doc/80-88500-4/topic/114_USB_Type_C.html](https://docs.qualcomm.com/doc/80-88500-4/topic/114_USB_Type_C.html)
The USB Type-C can transmit both data and power using a single cable. PM8150B handles
the USB Type-C power delivery (PD) detection.
## Hardware features
PM8150B manages the following:
- Channel configuration (CC) detection
- Charger type detection (automatic power save delivery)
- PD negotiation
The PMI software driver interacts with the USB software driver to notify the current USB
state:
- UFP/DFP
- Source/Sink
- Cable direction
Figure : USB Type-C
The following are the methods to determine the orientation of the cable:
- Value on GPIO\_38:
- Output of PM8150B
- Currently used in PBL
- SPMI read on the SCHG\_P\_TYPEC\_TYPE\_C\_MISC\_STATUS
Table : USB Type-C cable orientation (1)
| CC1 | CC2 | CC\_DIR/GPIO\_38 state | SS PHY active (PHY0 or PHY1) |
| --- | --- | --- | --- |
| Open | Open | Hi-Z | Not connected/PHY0 |
| Rd | Open | 0 | PHY0 |
| Open | Rd | 1 | PHY1 |
| Rd | Rd | Hi-Z | Not connected/PHY0 |
| Ra | Open | Hi-Z | Not connected/PHY0 |
| Open | Ra | Hi-Z | Not connected/PHY0 |
| Ra | Rd | 1 | PHY1 |
| Rd | Ra | 0 | PHY0 |
| Ra | Ra | Hi-Z | Not connected/PHY0 |
Note: The following table shows the different USB lanes based on the value of
GPIO\_38.
Table : USB Type-C cable orientation (2)
| SCHG\_P\_TYPEC\_TYPE\_C\_MISC\_STATUS | Offset: 0x0000150B | SCHG\_P\_TYPEC\_TYPE\_C\_MISC\_STATUS | Offset: 0x0000150B | SCHG\_P\_TYPEC\_TYPE\_C\_MISC\_STATUS | Offset: 0x0000150B |
| --- | --- | --- |
| Bits | Field name | Description |
| 7 | TYPEC\_WATER\_DETECTION\_STATUS | Indicates SRC crude sensor tripped but SRC accurate sensor is not tripped, which
means pulldown between 5.1k and 300k is detected |
| 6 | SNK\_SRC\_MODE | Indicates SNK/SRC mode (0=SNK, 1=SRC) |
| 5 | TYPEC\_VBUS\_STATUS | USBIN > 1 V |
| 4 | TYPEC\_VBUS\_ERROR\_STATUS | Status bit goes high when CC pin is debounced by `Tccdebounce`
during SNK mode but VBUS does not go high within 275 ms |
| 3 | TYPEC\_TCCDEBOUNCE\_DONE\_STATUS | CC1/CC2 TCC (120 ms/140 ms/160 ms/180 ms) debounce done |
| 2 | TYPEC\_VCONN\_OVERCURR\_STATUS | VCONN overcurrent detected |
| 1 | CCOUT\_VALUE | Indicates value driven on CCOUT pin when CCOUT\_ BUFFER\_ON is high |
| 0 | CCOUT\_BUFFER\_ON | Indicates when orientation of CC pin is defined and CCOUT is driven 0/1 based on
CCOUT\_VALUE |
Note: SCHG\_P\_TYPEC\_TYPE\_C\_MISC\_STATUS register bits [1:0] is used to determine
cable orientation.
## Software features
The following are the USB Type-C features:
- Display port
- Digital/analog audio
- power delivery (PD)
- Plugin reversibility
- Configuration channel (CC) charging
Figure : Potential USB Type-C use cases
Table : USB Type-C and USB PD software drivers
| Main drivers | Location | Description |
| --- | --- | --- |
| qpnp-smb5.c | <apps root>/kernel/MSM-5.4/drivers/
power/supply/qcom/qpnp-smb5.c |
- PMIC driver handles the CC detection, charger type detection, and OTG VBUS
regulator enablement
- PMIC driver handles the power supplies through the power supply framework
(that is, battery, USB, DC, and so on)
- Contains the set_property() and
get_property() callbacks for each supply
- Interacts heavily with the smb-lib.c driver
|
| policy\_engine.c | <apps root>/kernel/MSM-5.4/drivers/
drivers/usb/pd/policy\_engine.c |
- USB driver handles the power supply-changed events on the USB supply
- Contains the PD state machine to handle the different PD messages and states,
as well as a USB state machine to handle the type of notification to be sent to
the DWC3 driver
|
| qpnp-pdphy.c | <apps root>/kernel/MSM-5.4/drivers/
drivers/usb/pd/qpnp-pdphy.c | PMIC driver handles the interaction between the policy\_engine and PMIC
registers/hardware |
**Parent Topic:** USB
Last Published: Aug 18, 2023
Previous Topic
MTP function over FFS Next Topic
USB analog audio