blob: d25ad26b341f3da1c9cc85015cbd35ded5e62e64 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
# Zephyr EC TCPC Configuration
[TOC]
## Overview
Enable support for a [USB-C] [TCPC].
## Kconfig Options
See the file [Kconfig.tcpm] for all Kconfig options related to [TCPC].
You must enable the specific Kconfig option matching the TCPC chips
used on your design.
## Devicetree Nodes
The `TCPC` device tree nodes are defined in the [`DTS Bindings TCPC`] directory.
The `TCPC` device is added to the corresponding I2C bus node and the
"named-usbc-port" contains a phandle to the `TCPC` device
## Board Specific Code
None required.
## Threads
TCPC support does not enable any threads.
## Testing and Debugging
The [`I2C bus scan`] can be used to verify the TCPC device can be accessed and
the `tcpc_dump` console command can be used to dump the TCPC register.
```
Usage: tcpc_dump <USB-C port>
```
## Example
The Herobrine system uses the Parade PS8805 TCPC on USBC port 0.
```
CONFIG_PLATFORM_EC_USB_PD_TCPM_PS8805=y
```
```
port0@0 {
compatible = "named-usbc-port";
reg = <0>;
tcpc = <&tcpc_port0>;
};
&i2c1_0 {
tcpc_port0: ps8xxx@b {
compatible = "parade,ps8xxx";
reg = <0xb>;
};
};
```
[USB-C]: ../usb-c.md
[TCPC]: ../ec_terms.md#tcpc
[`I2C bus scan`]: ./zephyr_i2c.md#Shell-Command_i2c
[Kconfig.tcpm]: https://source.chromium.org/chromiumos/chromiumos/codesearch/+/main:src/platform/ec/zephyr/Kconfig.tcpm
[`DTS Bindings TCPC`]: https://source.chromium.org/chromiumos/chromiumos/codesearch/+/main:src/platform/ec/zephyr/dts/bindings/usbc/tcpc
|
