From: "Andy Yan" <andyshrk@163.com>
To: "Dmitry Baryshkov" <lumag@kernel.org>
Cc: heiko@sntech.de, hjc@rock-chips.com, mripard@kernel.org,
cristian.ciocaltea@collabora.com, neil.armstrong@linaro.org,
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, sebastian.reichel@collabora.com,
"Andy Yan" <andy.yan@rock-chips.com>,
"stephen@radxa.com" <stephen@radxa.com>
Subject: Re:Re: [PATCH v2 7/7] arm64: dts: rockchip: Enable DP2HDMI for ROCK 5 ITX
Date: Thu, 13 Mar 2025 08:32:55 +0800 (CST) [thread overview]
Message-ID: <5858d492.44b.1958ceb23dd.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <q3y36jgswj4xa2g3hnptc6kgzphbqfg675r5paa2lwvdseytio@jysj4f2i6osu>
Hi Dmitry,
At 2025-03-12 20:39:17, "Dmitry Baryshkov" <lumag@kernel.org> wrote:
>On Wed, Mar 12, 2025 at 06:42:08PM +0800, Andy Yan wrote:
>> From: Andy Yan <andy.yan@rock-chips.com>
>>
>> The HDMI Port next to Headphone Jack is drived by
>> DP1 on rk3588 via a dp2hdmi converter.
>>
>> Add related dt nodes to enable it.
>>
>> Note: ROCKCHIP_VOP2_EP_DP1 is defined as 11 in dt-binding header,
>> but it will trigger a dtc warning like "graph node unit address
>> error, expected "b"" if we use it directly after endpoint, so we
>> use "b" instead here.
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>> ---
>>
>> (no changes since v1)
>>
>> .../boot/dts/rockchip/rk3588-rock-5-itx.dts | 37 +++++++++++++++++++
>> 1 file changed, 37 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts b/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts
>> index 67b886329248..29f10ec9f0c1 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3588-rock-5-itx.dts
>> @@ -57,6 +57,18 @@ analog-sound {
>> "Headphone", "Headphones";
>> };
>>
>> + dp-con {
>> + compatible = "dp-connector";
>
>You've written that it is an HDMI connector. Could you possibly clarify,
>why is it being registered as a DP connector? Is there any kind of
>a bridge between the DP controller and the HDMI connector?
When I was preparing this patch at that time, I also had some doubts.
Whether it should be registered as a DP connector or an HDMI connector.
There is a DP2HDMI conversion chip between the DP of RK3588 and this hdmi
interface, but this conversion chip does not require a software driver.
If the current writing is incorrect, I will change it to hdmi-connector in the next version.
Thanks
>
>> + label = "DP OUT";
>> + type = "full-size";
>> +
>> + port {
>> + dp_con_in: endpoint {
>> + remote-endpoint = <&dp1_out_con>;
>> + };
>> + };
>> + };
>> +
>> gpio-leds {
>> compatible = "gpio-leds";
>> pinctrl-names = "default";
>> @@ -268,6 +280,24 @@ &cpu_l3 {
>> cpu-supply = <&vdd_cpu_lit_s0>;
>> };
>>
>> +&dp1 {
>> + status = "okay";
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&dp1m0_pins>;
>> +};
>> +
>> +&dp1_in {
>> + dp1_in_vp2: endpoint {
>> + remote-endpoint = <&vp2_out_dp1>;
>> + };
>> +};
>> +
>> +&dp1_out {
>> + dp1_out_con: endpoint {
>> + remote-endpoint = <&dp_con_in>;
>> + };
>> +};
>> +
>> &gpu {
>> mali-supply = <&vdd_gpu_s0>;
>> status = "okay";
>> @@ -1262,3 +1292,10 @@ vp1_out_hdmi1: endpoint@ROCKCHIP_VOP2_EP_HDMI1 {
>> remote-endpoint = <&hdmi1_in_vp1>;
>> };
>> };
>> +
>> +&vp2 {
>> + vp2_out_dp1: endpoint@b {
>> + reg = <ROCKCHIP_VOP2_EP_DP1>;
>> + remote-endpoint = <&dp1_in_vp2>;
>> + };
>> +};
>> --
>> 2.34.1
>>
>
>--
>With best wishes
>Dmitry
next prev parent reply other threads:[~2025-03-13 0:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 10:42 [PATCH v2 0/7] Add support for RK3588 DisplayPort Controller Andy Yan
2025-03-12 10:42 ` [PATCH v2 1/7] dt-bindings: display: rockchip: Add schema for RK3588 DPTX Controller Andy Yan
2025-03-12 10:42 ` [PATCH v2 2/7] drm/bridge: synopsys: Add DW DPTX Controller support library Andy Yan
2025-03-12 14:23 ` Piotr Oniszczuk
2025-03-13 0:23 ` Andy Yan
2025-03-13 10:42 ` Piotr Oniszczuk
2025-03-12 10:42 ` [PATCH v2 3/7] drm/rockchip: Add RK3588 DPTX output support Andy Yan
2025-03-12 12:37 ` Dmitry Baryshkov
2025-03-12 10:42 ` [PATCH v2 4/7] arm64: dts: rockchip: Add DP0 for rk3588 Andy Yan
2025-03-12 10:42 ` [PATCH v2 5/7] arm64: dts: rockchip: Add DP1 " Andy Yan
2025-03-12 10:42 ` [PATCH v2 6/7] arm64: dts: rockchip: Enable DisplayPort for rk3588s Cool Pi 4B Andy Yan
2025-03-12 10:42 ` [PATCH v2 7/7] arm64: dts: rockchip: Enable DP2HDMI for ROCK 5 ITX Andy Yan
2025-03-12 12:39 ` Dmitry Baryshkov
2025-03-13 0:32 ` Andy Yan [this message]
2025-03-13 8:10 ` Dmitry Baryshkov
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=5858d492.44b.1958ceb23dd.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=andy.yan@rock-chips.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--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=lumag@kernel.org \
--cc=mripard@kernel.org \
--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
all inboxes | Powered by JetHome®