On Wed, 27 Mar 2024 at 04:04, Bjorn Andersson <quic_bjorande@xxxxxxxxxxx> wrote: > > The RB3Gen2 board comes with a mini DP connector, describe this, enable > MDSS, DP controller and the PHY that drives this. > > Signed-off-by: Bjorn Andersson <quic_bjorande@xxxxxxxxxxx> > --- > arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 40 ++++++++++++++++++++++++++++ > 1 file changed, 40 insertions(+) > > diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts > index 63ebe0774f1d..f90bf3518e98 100644 > --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts > +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts > @@ -39,6 +39,20 @@ chosen { > stdout-path = "serial0:115200n8"; > }; > > + dp-connector { > + compatible = "dp-connector"; > + label = "DP"; > + type = "mini"; > + > + hpd-gpios = <&tlmm 60 GPIO_ACTIVE_HIGH>; Is it the standard hpd gpio? If so, is there any reason for using it through dp-connector rather than as a native HPD signal? > + > + port { > + dp_connector_in: endpoint { > + remote-endpoint = <&mdss_edp_out>; > + }; > + }; > + }; > + > reserved-memory { > xbl_mem: xbl@80700000 { > reg = <0x0 0x80700000 0x0 0x100000>; > @@ -471,6 +485,25 @@ &gcc { > <GCC_WPSS_RSCP_CLK>; > }; > > +&mdss { > + status = "okay"; > +}; > + > +&mdss_edp { > + status = "okay"; > +}; > + > +&mdss_edp_out { > + data-lanes = <0 1 2 3>; > + link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>; > + > + remote-endpoint = <&dp_connector_in>; > +}; > + > +&mdss_edp_phy { > + status = "okay"; > +}; > + > &qupv3_id_0 { > status = "okay"; > }; > @@ -511,3 +544,10 @@ &usb_1_qmpphy { > &wifi { > memory-region = <&wlan_fw_mem>; > }; > + > +/* PINCTRL - ADDITIONS TO NODES IN PARENT DEVICE TREE FILES */ > + > +&edp_hot_plug_det { > + function = "gpio"; > + bias-disable; > +}; > > -- > 2.25.1 > -- With best wishes Dmitry