mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yongxing Mou <quic_yongmou@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: hamoa-iot-evk: Enable display support
Date: Thu, 24 Jul 2025 15:40:52 +0800	[thread overview]
Message-ID: <c7041754-7be9-44f5-89a4-03bb21e2d342@quicinc.com> (raw)
In-Reply-To: <6wwcxwgcf4wm4ekb3d4ukkyyqsseaawo6l66umzxim4kcilynm@fc6mwj6ymnes>



On 2025/7/23 19:21, Dmitry Baryshkov wrote:
> On Wed, Jul 23, 2025 at 02:14:55PM +0800, Yongxing Mou wrote:
>> Enable DisplayPort support on all three USB-C ports of the
>> hamoa-iot-evk platform.
>>
>> Unlike most X1E-based boards, this platform uses FSUSB42 USB
>> switches for the USB0 Type-C port, while USB1 and USB2 rely on
>> Parade PS8830 retimers for Alt Mode switching.
>>
>> Support for the PS8830 retimers was already included in the
>> initial DTS, so this change adds support for the FSUSB42 switches.
>>
>> Due to limitations in the USB/DP combo PHY driver, DisplayPort
>> functionality is limited to 2 lanes instead of the maximum 4,
>> consistent with other X1E-based platforms.
>>
>> The platform also supports embedded DisplayPort (eDP) by default.
>>
>> Signed-off-by: Yongxing Mou <quic_yongmou@quicinc.com>
>> ---
>> This change made top of initial DTS:
>> https://lore.kernel.org/all/20250716-hamoa_initial-v1-0-f6f5d0f9a163@oss.qualcomm.com/
>> ---
>>   arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts | 156 +++++++++++++++++++++++++++++
>>   1 file changed, 156 insertions(+)
>> +
>> +	ports {
>> +		port@1 {
>> +			reg = <1>;
>> +			mdss_dp3_out: endpoint {
> 
> Add empty endpoint to x1e80100.dtsi, then patch it here like you do for
> all other DP endpoints.
> 
Hi So i need to add mdss_dp3_out: endpoint {} in x1e80100.dtsi and 
+&mdss_dp3_out {
+       data-lanes = <0 1 2 3>;
...
in board dts..  is this understanding correct?

i just wondering that here can we just follow other x1e80100-based dts?
others 8 x1e80100-based board dts all introduce edp-panel in this way..
>> +				data-lanes = <0 1 2 3>;
>> +				link-frequencies = /bits/ 64 <1620000000 2700000000
>> +							      5400000000 8100000000>;
>> +
>> +				remote-endpoint = <&edp_panel_in>;
>> +			};
>> +		};
>> +	};
>> +};
>> +
> 


  reply	other threads:[~2025-07-24  7:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  6:14 Yongxing Mou
2025-07-23  6:26 ` Krzysztof Kozlowski
2025-07-23  8:08   ` Yongxing Mou
2025-07-23  9:08     ` Krzysztof Kozlowski
2025-07-23  9:24       ` Yongxing Mou
2025-07-23 11:21 ` Dmitry Baryshkov
2025-07-24  7:40   ` Yongxing Mou [this message]
2025-07-25 11:15     ` Dmitry Baryshkov
2025-07-23 11:38 ` Konrad Dybcio
2025-07-24  6:13   ` Yongxing Mou

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=c7041754-7be9-44f5-89a4-03bb21e2d342@quicinc.com \
    --to=quic_yongmou@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@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=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

all inboxes | Powered by JetHome®