aboutsummaryrefslogtreecommitdiff
path: root/sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml')
-rw-r--r--sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml11
1 files changed, 11 insertions, 0 deletions
diff --git a/sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml b/sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml
index 423b7c4e62f2..b2218c151939 100644
--- a/sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml
+++ b/sys/contrib/device-tree/Bindings/phy/mediatek,tphy.yaml
@@ -78,6 +78,7 @@ properties:
- items:
- enum:
- mediatek,mt2712-tphy
+ - mediatek,mt6893-tphy
- mediatek,mt7629-tphy
- mediatek,mt7986-tphy
- mediatek,mt8183-tphy
@@ -125,6 +126,16 @@ properties:
$ref: /schemas/types.yaml#/definitions/uint32
default: 28
+ power-domains:
+ description:
+ The TPHY of MediaTek should exist within a power domain. The
+ developer should be aware that the hardware design of MediaTek TPHY
+ does not require the addition of MTCMOS. If the power to the TPHY
+ is turned off, it will impact other functions. From the current
+ perspective of USB hardware design, even if MTCMOS is added to the
+ TPHY, it should remain always on.
+ maxItems: 1
+
# Required child node:
patternProperties:
"^(usb|pcie|sata)-phy@[0-9a-f]+$":