From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Abel Vesa <abel.vesa@linaro.org>
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>,
Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: glymur: Describe display related nodes
Date: Sat, 27 Sep 2025 14:25:09 +0200 [thread overview]
Message-ID: <13eeb653-390e-4f71-aa6c-d048bbf988ab@oss.qualcomm.com> (raw)
In-Reply-To: <mztchl7blmp5cdjiyg2btl65o2jrydpn4m3fc2liyxjci5vish@k33bvcyvz25j>
On 9/27/25 12:33 AM, Dmitry Baryshkov wrote:
> On Fri, Sep 26, 2025 at 09:50:22AM +0300, Abel Vesa wrote:
>> On 25-09-25 20:11:11, Dmitry Baryshkov wrote:
>>> On Thu, Sep 25, 2025 at 06:02:48PM +0300, Abel Vesa wrote:
>>>> The MDSS (Mobile Display SubSystem) on Glymur comes with 4 DisplayPort
>>>> controllers. Describe them along with display controller and the eDP
>>>> PHY. Then, attach the combo PHYs link and vco_div clocks to the Display
>>>> clock controller and link up the PHYs and DP endpoints in the graph.
>>>>
>>>> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
>>>> ---
>>>> arch/arm64/boot/dts/qcom/glymur.dtsi | 492 ++++++++++++++++++++++++++++++++++-
>>>> 1 file changed, 484 insertions(+), 8 deletions(-)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/qcom/glymur.dtsi b/arch/arm64/boot/dts/qcom/glymur.dtsi
>>>> index a131cd6c3d9e7f14ed1c4aef4b68e1860cc3bca5..41d89998b1fe14a24cd528e73afc37cf2a840bab 100644
>>>> --- a/arch/arm64/boot/dts/qcom/glymur.dtsi
>>>> +++ b/arch/arm64/boot/dts/qcom/glymur.dtsi
>>
>> [...]
>>
>>>> + mdss_dp0: displayport-controller@af54000 {
>>>> + compatible = "qcom,glymur-dp";
>>>> + reg = <0x0 0xaf54000 0x0 0x104>,
>>>> + <0x0 0xaf54200 0x0 0xc0>,
>>>> + <0x0 0xaf55000 0x0 0x770>,
>>>> + <0x0 0xaf56000 0x0 0x9c>,
>>>> + <0x0 0xaf57000 0x0 0x9c>;
>>>> +
>>>> + interrupts-extended = <&mdss 12>;
>>>> +
>>>> + clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
>>>> + <&dispcc DISP_CC_MDSS_DPTX0_AUX_CLK>,
>>>> + <&dispcc DISP_CC_MDSS_DPTX0_LINK_CLK>,
>>>> + <&dispcc DISP_CC_MDSS_DPTX0_LINK_INTF_CLK>,
>>>> + <&dispcc DISP_CC_MDSS_DPTX0_PIXEL0_CLK>;
>>>
>>> No pixel1 clock?
>>
>> Will add it in next version. Everywhere.
>
> Except DP3, if I'm not mistaken.
$ rg PIXEL1 drivers/clk/qcom/dispcc-glymur.c
1841: [DISP_CC_MDSS_DPTX0_PIXEL1_CLK] = &disp_cc_mdss_dptx0_pixel1_clk.clkr,
1842: [DISP_CC_MDSS_DPTX0_PIXEL1_CLK_SRC] = &disp_cc_mdss_dptx0_pixel1_clk_src.clkr,
1855: [DISP_CC_MDSS_DPTX1_PIXEL1_CLK] = &disp_cc_mdss_dptx1_pixel1_clk.clkr,
1856: [DISP_CC_MDSS_DPTX1_PIXEL1_CLK_SRC] = &disp_cc_mdss_dptx1_pixel1_clk_src.clkr,
1869: [DISP_CC_MDSS_DPTX2_PIXEL1_CLK] = &disp_cc_mdss_dptx2_pixel1_clk.clkr,
1870: [DISP_CC_MDSS_DPTX2_PIXEL1_CLK_SRC] = &disp_cc_mdss_dptx2_pixel1_clk_src.clkr,
looks like it
Konrad
next prev parent reply other threads:[~2025-09-27 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:02 [PATCH 0/2] arm64: dts: qcom: glymur: Enable SoC-wise display and eDP panel on CRD Abel Vesa
2025-09-25 15:02 ` [PATCH 1/2] arm64: dts: qcom: glymur: Describe display related nodes Abel Vesa
2025-09-25 17:11 ` Dmitry Baryshkov
2025-09-26 6:50 ` Abel Vesa
2025-09-26 22:33 ` Dmitry Baryshkov
2025-09-27 12:25 ` Konrad Dybcio [this message]
2025-09-25 15:02 ` [PATCH 2/2] arm64: dts: qcom: glymur-crd: Enable eDP display support Abel Vesa
2025-09-25 16:46 ` Dmitry Baryshkov
2025-09-26 6:52 ` Abel Vesa
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=13eeb653-390e-4f71-aa6c-d048bbf988ab@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@linaro.org \
--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=pankaj.patil@oss.qualcomm.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