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 1/2] arm64: dts: qcom: qcs8300: add DisplayPort device nodes
Date: Thu, 9 Jan 2025 17:43:51 +0800	[thread overview]
Message-ID: <7585ba2b-589c-4f85-98cd-76a989b537d7@quicinc.com> (raw)
In-Reply-To: <71c6609e-e853-4680-939e-f3c9ec15233e@oss.qualcomm.com>



On 2024/12/30 21:27, Konrad Dybcio wrote:
> On 26.12.2024 8:03 AM, Yongxing Mou wrote:
>>
>>
>> On 2024/12/6 5:36, Konrad Dybcio wrote:
>>> On 27.11.2024 11:45 AM, Yongxing Mou wrote:
>>>> Add device tree nodes for the DPTX0 controller with their
>>>> corresponding PHYs found on Qualcomm QCS8300 SoC.
>>>>
>>>> Signed-off-by: Yongxing Mou <quic_yongmou@quicinc.com>
>>>> ---
> 
> [...]
> 
>>>> +            mdss_dp0_phy: phy@aec2a00 {
>>>> +                compatible = "qcom,qcs8300-edp-phy";
>>>> +
>>>> +                reg = <0x0 0x0aec2a00 0x0 0x200>,
>>>
>>> 0x19c
>>>
>> got it.thanks.
>>>> +                      <0x0 0x0aec2200 0x0 0xd0>,
>>>
>>> 0xec
>> got it.thanks.
>>>> +                      <0x0 0x0aec2600 0x0 0xd0>,
>>>
>>> 0xec
>>>
>>> For lengths
>> got it.thanks.
>>>
>>>> +                      <0x0 0x0aec2000 0x0 0x1c8>;
>>>
>>> This one's correct
>>>
>>>> +
>>>> +                clocks = <&dispcc MDSS_DISP_CC_MDSS_DPTX0_AUX_CLK>,
>>>> +                     <&dispcc MDSS_DISP_CC_MDSS_AHB_CLK>;
>>>> +                clock-names = "aux",
>>>> +                          "cfg_ahb";
>>>
>>> power-domains = <&rpmhpd RPMHPD_MX>;
>>>
>> emm,we use RPMHPD_MMCX in qcs8300 mdss and dpu..
>>> (or maybe even MXC?)
> 
> Please verify what backs the PHY and update accordingly
> 
> Konrad

Thank you for the reminder. it should use RPMHPD_MX.My previous 
understanding that using MMCX was incorrect.





  reply	other threads:[~2025-01-09  9:44 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 [this message]
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
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=7585ba2b-589c-4f85-98cd-76a989b537d7@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