Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Yongxing Mou <quic_yongmou@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Ritesh Kumar <quic_riteshk@quicinc.com>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: qcs8300-ride: Enable Display Port
Date: Thu, 26 Dec 2024 15:06:29 +0800	[thread overview]
Message-ID: <9a42ba40-9984-4c19-8de4-f814d27cb20d@quicinc.com> (raw)
In-Reply-To: <466ea213-5f20-4a9f-a9dc-751756792845@oss.qualcomm.com>



On 2024/12/6 5:46, Konrad Dybcio wrote:
> On 27.11.2024 11:45 AM, Yongxing Mou wrote:
>> Enable DPTX0 along with their corresponding PHYs for
>> qcs8300-ride platform.
>>
>> Signed-off-by: Yongxing Mou <quic_yongmou@quicinc.com>
>> ---
> 
> [...]
> 
>> +
>> +	dp0-connector {
>> +		compatible = "dp-connector";
>> +		label = "DP0";
>> +		type = "full-size";
> 
> I was surprised to see it but yeah this is real
> 
>> +
>> +		port {
>> +			dp0_connector_in: endpoint {
>> +				remote-endpoint = <&mdss_dp0_out>;
>> +			};
>> +		};
>> +	};
>>   };
>>   
>>   &apps_rsc {
>> @@ -223,6 +235,30 @@ &gcc {
>>   		 <0>;
>>   };
>>   
>> +&mdss {
>> +	status = "okay";
>> +};
>> +
>> +&mdss_dp0 {
>> +	status = "okay";
> status should be the last property
> 
got it. thanks for ponit it.
>> +
>> +	pinctrl-0 = <&dp_hot_plug_det>;
>> +	pinctrl-names = "default";
>> +};
>> +
>> +&mdss_dp0_out {
>> +	data-lanes = <0 1 2 3>;
>> +	link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>;
>> +	remote-endpoint = <&dp0_connector_in>;
>> +};
>> +
>> +&mdss_dp0_phy {
>> +	status = "okay";
>> +
>> +	vdda-phy-supply = <&vreg_l5a>;
>> +	vdda-pll-supply = <&vreg_l4a>;
> I couldn't find the reference for these, so I have to trust you
> 
yes, this two power can work for qcs8300.and we verify it.status also 
should be last property?
> Konrad
> 


  reply	other threads:[~2024-12-26  7:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 10:45 [PATCH 0/2] Enable Display Port for Qualcomm QCS8300-ride platform Yongxing Mou
2024-11-27 10:45 ` [PATCH 1/2] arm64: dts: qcom: qcs8300: add DisplayPort device nodes Yongxing Mou
2024-12-05 21:36   ` Konrad Dybcio
2024-12-26  7:03     ` Yongxing Mou
2024-12-26 19:57       ` Dmitry Baryshkov
2025-01-09  9:41         ` Yongxing Mou
2024-12-30 13:27       ` Konrad Dybcio
2025-01-09  9:43         ` Yongxing Mou
2025-01-08 23:06   ` Bjorn Andersson
2025-01-09  9:47     ` Yongxing Mou
2024-11-27 10:45 ` [PATCH 2/2] arm64: dts: qcom: qcs8300-ride: Enable Display Port Yongxing Mou
2024-12-05 21:46   ` Konrad Dybcio
2024-12-26  7:06     ` Yongxing Mou [this message]
2024-12-30 13:27       ` Konrad Dybcio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a42ba40-9984-4c19-8de4-f814d27cb20d@quicinc.com \
    --to=quic_yongmou@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_riteshk@quicinc.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox