From: "Andy Yan" <andyshrk@163.com>
To: "Sebastian Reichel" <sebastian.reichel@collabora.com>
Cc: dmitry.baryshkov@oss.qualcomm.com, heiko@sntech.de,
hjc@rock-chips.com, mripard@kernel.org, naoki@radxa.com,
stephen@radxa.com, cristian.ciocaltea@collabora.com,
neil.armstrong@linaro.org, Laurent.pinchart@ideasonboard.com,
yubing.zhang@rock-chips.com, krzk+dt@kernel.org,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh@kernel.org, "Andy Yan" <andy.yan@rock-chips.com>
Subject: Re:Re: [PATCH v6 09/10] arm64: dts: rockchip: Enable DisplayPort for rk3588s Cool Pi 4B
Date: Wed, 30 Jul 2025 20:15:44 +0800 (CST) [thread overview]
Message-ID: <5deac95c.8ec2.1985b428b0b.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <hbvwlucm5mnjpve6hb6h7dusgrokvdxzbpq5zrwib4yesrdakp@v77ofq7u2vv2>
Hello Sebastian,
At 2025-07-30 01:09:41, "Sebastian Reichel" <sebastian.reichel@collabora.com> wrote:
>Hi,
>
>On Mon, Jul 28, 2025 at 04:28:34PM +0800, Andy Yan wrote:
>> From: Andy Yan <andy.yan@rock-chips.com>
>>
>> Enable the Mini DisplayPort on this board.
>> Note that ROCKCHIP_VOP2_EP_DP0 is defined as 10 in dt-binding header,
>> but it will trigger a dtc warning like "graph node unit address error,
>> expected "a"" if we use it directly after endpoint, so we use "a"
>> instead here.
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> ---
>
>The graph currently looks like this:
>
>VOP <-> DP controller <-> DP Connector
>
>IIUIC this does not work for USB-C and needs to look like this,
>because the USBDP PHY handles the lane muxing and thus must be
>the thing connected to the USB-C controller/connector:
I previously tests USB-C Altmode on Linux 5.15 using Rock 5b, this function works well.
However, when the same dts configuration is used on Linux 6.16 and tested with Rock 5b in USB-C Altmode,
the HPD interrupt of DP cannot be triggered. I'm not sure yet what changes have occurred between them.
Moreover, I noticed that on your test branch[1], the DTS configuration has also changed compared to before.
I would greatly appreciate it if you could share some details.
[0]https://github.com/andyshrk/linux/commit/b9f87a562d431fb59b664b7aed41869a8f184de3
[1]https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/commit/0e7e90494482cf77d5bb058a47583b6747b140f4
>
>VOP <-> DP controller <-> USBDP PHY <-> USB-C Connector
>
>I wonder if the simple case not involving USB-C should also have
>the USBDP PHY described in the graph as a transparent bridge?
>Note, that the USBDP PHY DT binding is currently not ready for
>this (this also affects the next patch, but should be enough to
>discuss this once :)).
>
>Greetings,
>
>-- Sebastian
>
>>
>> (no changes since v2)
>>
>> Changes in v2:
>> - Sort in alphabetical order
>>
>> .../boot/dts/rockchip/rk3588s-coolpi-4b.dts | 37 +++++++++++++++++++
>> 1 file changed, 37 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-coolpi-4b.dts b/arch/arm64/boot/dts/rockchip/rk3588s-coolpi-4b.dts
>> index 8b717c4017a46..5393c6cc493c3 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3588s-coolpi-4b.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-coolpi-4b.dts
>> @@ -39,6 +39,18 @@ chosen {
>> stdout-path = "serial2:1500000n8";
>> };
>>
>> + dp-con {
>> + compatible = "dp-connector";
>> + label = "DP OUT";
>> + type = "mini";
>> +
>> + port {
>> + dp_con_in: endpoint {
>> + remote-endpoint = <&dp0_out_con>;
>> + };
>> + };
>> + };
>> +
>> hdmi-con {
>> compatible = "hdmi-connector";
>> type = "d";
>> @@ -215,6 +227,24 @@ &cpu_b2 {
>> cpu-supply = <&vdd_cpu_big1_s0>;
>> };
>>
>> +&dp0 {
>> + status = "okay";
>> + pinctrl-0 = <&dp0m0_pins>;
>> + pinctrl-names = "default";
>> +};
>> +
>> +&dp0_in {
>> + dp0_in_vp2: endpoint {
>> + remote-endpoint = <&vp2_out_dp0>;
>> + };
>> +};
>> +
>> +&dp0_out {
>> + dp0_out_con: endpoint {
>> + remote-endpoint = <&dp_con_in>;
>> + };
>> +};
>> +
>> &gpu {
>> mali-supply = <&vdd_gpu_s0>;
>> status = "okay";
>> @@ -889,3 +919,10 @@ vp0_out_hdmi0: endpoint@ROCKCHIP_VOP2_EP_HDMI0 {
>> remote-endpoint = <&hdmi0_in_vp0>;
>> };
>> };
>> +
>> +&vp2 {
>> + vp2_out_dp0: endpoint@a {
>> + reg = <ROCKCHIP_VOP2_EP_DP0>;
>> + remote-endpoint = <&dp0_in_vp2>;
>> + };
>> +};
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2025-07-30 12:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 8:28 [PATCH v6 00/10] Add support for RK3588 DisplayPort Controller Andy Yan
2025-07-28 8:28 ` [PATCH v6 01/10] dt-bindings: display: rockchip: Add schema for RK3588 DPTX Controller Andy Yan
2025-07-28 8:28 ` [PATCH v6 02/10] drm/bridge: synopsys: Add DW DPTX Controller support library Andy Yan
2025-07-28 12:05 ` Dmitry Baryshkov
2025-08-15 17:44 ` Sebastian Reichel
2025-07-28 8:28 ` [PATCH v6 03/10] drm/rockchip: Add RK3588 DPTX output support Andy Yan
2025-07-28 8:28 ` [PATCH v6 04/10] MAINTAINERS: Add entry for DW DPTX Controller bridge Andy Yan
2025-08-21 11:31 ` Dmitry Baryshkov
2025-07-28 8:28 ` [PATCH v6 05/10] dt-bindings: display: simple-bridge: Add ra620 compatible Andy Yan
2025-07-28 8:28 ` [PATCH v6 06/10] drm/birdge: simple-bridge: Add support for radxa ra620 Andy Yan
2025-08-21 11:36 ` Dmitry Baryshkov
2025-07-28 8:28 ` [PATCH v6 07/10] arm64: dts: rockchip: Add DP0 for rk3588 Andy Yan
2025-07-29 15:10 ` Sebastian Reichel
2025-07-28 8:28 ` [PATCH v6 08/10] arm64: dts: rockchip: Add DP1 " Andy Yan
2025-07-29 15:10 ` Sebastian Reichel
2025-07-28 8:28 ` [PATCH v6 09/10] arm64: dts: rockchip: Enable DisplayPort for rk3588s Cool Pi 4B Andy Yan
2025-07-29 17:09 ` Sebastian Reichel
2025-07-30 12:15 ` Andy Yan [this message]
2025-07-31 2:52 ` Andy Yan
2025-08-15 18:00 ` Sebastian Reichel
2025-07-28 8:28 ` [PATCH v6 10/10] arm64: dts: rockchip: Enable DP2HDMI for ROCK 5 ITX Andy Yan
2025-08-21 10:44 ` Re:[PATCH v6 00/10] Add support for RK3588 DisplayPort Controller Andy Yan
2025-08-21 11:36 ` [PATCH " Dmitry Baryshkov
2025-08-22 9:34 ` Andy Yan
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=5deac95c.8ec2.1985b428b0b.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andy.yan@rock-chips.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=naoki@radxa.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stephen@radxa.com \
--cc=yubing.zhang@rock-chips.com \
/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;
as well as URLs for NNTP newsgroup(s).