Quoting Rob Herring (2020-06-17 08:38:20)
On Tue, Jun 16, 2020 at 5:15 AM Stephen Boyd swboyd@chromium.org wrote:
Quoting Tanmay Shah (2020-06-11 18:50:26)
diff --git a/Documentation/devicetree/bindings/display/msm/dp-sc7180.yaml b/Documentation/devicetree/bindings/display/msm/dp-sc7180.yaml new file mode 100644 index 000000000000..5fdb9153df00 --- /dev/null +++ b/Documentation/devicetree/bindings/display/msm/dp-sc7180.yaml @@ -0,0 +1,142 @@
data-lanes = <0 1>;ports {#address-cells = <1>;#size-cells = <0>;port@0 {reg = <0>;dp_in: endpoint {remote-endpoint = <&dpu_intf0_out>;};};port@1 {reg = <1>;dp_out: endpoint {Just curious what is eventually connected here? This is possibly a question for Rob Herring, but I can't figure out how we're supposed to connect this to the USB type-c connector that is receiving the DP signal. Does the type-c connector binding support connecting to this end of the graph? Or should this connect to the DP phy and then the phy connects to the USB type-c connector node? Right now it is empty which seems wrong.
It should connect to the Type-C connector perhaps thru some sort of switching/muxing node, but that's not really flushed out though. See 'dt-bindings: chrome: Add cros-ec-typec mux props' discussion with your CrOS colleagues.
Ok. I see that we have an sbu endpoint for an aux channel but not a DP endpoint in the type-c connector. I guess it's an alternate mode of the connector too so maybe that complicates things. I'll talk to pmalani. Thanks.