dt-bindings: dp-connector: describe separate DP and AUX lines

In some cases it's reasonable to describe DP lanes and AUX signal lines
separately in the DT. One of the typical reasons is if the source of DP
signals can support either USB-C or DP connections. In such a case the
transmitter of DP signals have separate ports: one for SS lanes and
another one for SBU / AUX signals.

Instead of leaving AUX signals from the controller unconnected, add an
option to the DT schema to AUX signal lines separately from the main
link lanes.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20250907-dp-conenctor-sbu-v1-1-de79c0fcd64d@oss.qualcomm.com
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
This commit is contained in:
Dmitry Baryshkov 2025-09-07 00:48:52 +03:00 committed by Rob Herring (Arm)
parent 3ef9c995fa
commit b132e9745e

View File

@ -31,10 +31,32 @@ properties:
$ref: /schemas/graph.yaml#/properties/port
description: Connection to controller providing DP signals
ports:
$ref: /schemas/graph.yaml#/properties/ports
description: OF graph representation of signales routed to DP connector
properties:
port@0:
$ref: /schemas/graph.yaml#/properties/port
description: Connection to controller providing DP signals
port@1:
$ref: /schemas/graph.yaml#/properties/port
description: Connection to controller providing AUX signals
required:
- port@0
- port@1
required:
- compatible
- type
- port
oneOf:
- required:
- port
- required:
- ports
additionalProperties: false
@ -52,4 +74,32 @@ examples:
};
};
- |
/* DP connecttor being driven by the USB+DP combo PHY */
connector {
compatible = "dp-connector";
label = "dp0";
type = "full-size";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
endpoint {
remote-endpoint = <&phy_ss_out>;
};
};
port@1 {
reg = <1>;
endpoint {
remote-endpoint = <&phy_sbu_out>;
};
};
};
};
...