From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Yongxing Mou <quic_yongmou@quicinc.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
Subject: Re: [PATCH v4 1/2] arm64: dts: qcom: qcs8300: add display dt nodes for MDSS, DPU, DisplayPort and eDP PHY
Date: Wed, 30 Jul 2025 12:25:31 +0200 [thread overview]
Message-ID: <f3aeacf5-f178-4e61-b34a-60353f89daae@oss.qualcomm.com> (raw)
In-Reply-To: <20250730-dts_qcs8300-v4-1-5e2dd12ddf6d@quicinc.com>
On 7/30/25 11:49 AM, Yongxing Mou wrote:
> Add devicetree changes to enable MDSS display-subsystem,
> display-controller(DPU), DisplayPort controller and eDP PHY for
> Qualcomm QCS8300 platform.
>
> Signed-off-by: Yongxing Mou <quic_yongmou@quicinc.com>
> ---
[...]
> +
> + assigned-clocks = <&dispcc MDSS_DISP_CC_MDSS_VSYNC_CLK>;
> + assigned-clock-rates = <19200000>;
is this necessary?
> +
> + operating-points-v2 = <&mdp_opp_table>;
> + power-domains = <&rpmhpd RPMHPD_MMCX>;
> +
> + interrupt-parent = <&mdss>;
> + interrupts = <0>;
interrupts-extended, file-wide
Konrad
next prev parent reply other threads:[~2025-07-30 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 9:49 [PATCH v4 0/2] Enable DPU and Display Port for Qualcomm QCS8300-ride platform Yongxing Mou
2025-07-30 9:49 ` [PATCH v4 1/2] arm64: dts: qcom: qcs8300: add display dt nodes for MDSS, DPU, DisplayPort and eDP PHY Yongxing Mou
2025-07-30 10:25 ` Konrad Dybcio [this message]
2025-08-04 4:39 ` Yongxing Mou
2025-08-04 12:34 ` Konrad Dybcio
2025-08-05 5:15 ` Dmitry Baryshkov
2025-08-05 12:30 ` Konrad Dybcio
2025-07-30 9:49 ` [PATCH v4 2/2] arm64: dts: qcom: qcs8300-ride: Enable Display Port Yongxing Mou
2025-07-30 12:55 ` Konrad Dybcio
2025-08-04 4:40 ` 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=f3aeacf5-f178-4e61-b34a-60353f89daae@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_yongmou@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
all inboxes | Powered by JetHome®