From: "Andy Yan" <andyshrk@163.com>
To: "Piotr Oniszczuk" <piotr.oniszczuk@gmail.com>
Cc: heiko@sntech.de, neil.armstrong@linaro.org,
sebastian.reichel@collabora.com, devicetree@vger.kernel.org,
hjc@rock-chips.com, mripard@kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
yubing.zhang@rock-chips.com, dri-devel@lists.freedesktop.org,
"Andy Yan" <andy.yan@rock-chips.com>,
krzk+dt@kernel.org, robh@kernel.org,
linux-arm-kernel@lists.infradead.org, lumag@kernel.org,
stephen@radxa.com
Subject: Re:Re: [PATCH 0/6] Add support for RK3588 DisplayPort Controller
Date: Wed, 12 Mar 2025 11:51:58 +0800 (CST) [thread overview]
Message-ID: <4003289a.41da.195887b0462.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <AD2A56F9-B4FB-406B-BE7C-49BB5DFD3BAD@gmail.com>
Hi Piotr,
在 2025-03-10 04:53:50,"Piotr Oniszczuk" <piotr.oniszczuk@gmail.com> 写道:
>
>
>> Wiadomość napisana przez Andy Yan <andyshrk@163.com> w dniu 7 mar 2025, o godz. 01:48:
>>
>>
>> Hi Piotr,
>> 在 2025-03-06 22:28:08,"Piotr Oniszczuk" <piotr.oniszczuk@gmail.com> 写道:
>>>
>>>
>>
>> All dump information currently appears to be correct, so I'm temporarily unsure why
>> there is no display on the monitor.
>> Maybe try some plug and unplug for the DP cable, or try another cable or monitor?
>>
>> It seems that this board uses a DP to HDMI converter? Does this transmitter need a driver?
>>
>> I won't be at my computer over the next two or three days, so any further replies to your email
>> might have to wait until next week.
>>
>>
>
>Andy,
>FYI:
>
>I done test on mine rock5a with applied Naoki dp0 enablement in dts (and only in dts).
>No any changes in dw dp driver (so i’m on vanilla https://patchwork.kernel.org/project/linux-rockchip/cover/20250223113036.74252-1-andyshrk@163.com/ )
>
>on mine rock5a ra620 hdmi port works ok.
>(I contacted also Radxa about ra620 and they confirmed: ra620 is just DP->HDMI converter. No any driver nor special programming/enablement is needed)
>
>This tells me that dp0 (rock5a) works ok while dp1 (rock5itx) not.
>i suspect issue is probably in https://patchwork.kernel.org/project/linux-rockchip/cover/20250223113036.74252-1-andyshrk@163.com/ and is related to dp1 handling?
With help from Stephen, we do some online debug, the DP1 display is ok on his rock5itx board now。
Try the patch as bellow:
diff --git a/drivers/gpu/drm/bridge/synopsys/dw-dp.c b/drivers/gpu/drm/bridge/synopsys/dw-dp.c
index 75a03e6a875c..d9434310a141 100644
--- a/drivers/gpu/drm/bridge/synopsys/dw-dp.c
+++ b/drivers/gpu/drm/bridge/synopsys/dw-dp.c
@@ -329,7 +329,7 @@ struct dw_dp {
struct dw_dp_link link;
struct dw_dp_video video;
- const struct dw_dp_plat_data *plat_data;
+ struct dw_dp_plat_data plat_data;
@@ -1998,7 +2012,7 @@ struct dw_dp *dw_dp_bind(struct device *dev, struct drm_encoder *encoder,
dp->dev = dev;
dp->video.pixel_mode = DW_DP_MP_QUAD_PIXEL;
- dp->plat_data = plat_data;
+ dp->plat_data.max_link_rate = plat_data->max_link_rate;
bridge = &dp->bridge;
mutex_init(&dp->irq_lock);
INIT_WORK(&dp->hpd_work, dw_dp_hpd_work);
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
index 17a98845fd31..2cf79a1409af 100644
--- a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
+++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
@@ -2089,9 +2089,9 @@ static unsigned long rk3588_set_intf_mux(struct vop2_video_port *vp, int id, u32
dip |= FIELD_PREP(RK3588_DSP_IF_POL__DP0_PIN_POL, polflags);
break;
case ROCKCHIP_VOP2_EP_DP1:
- die &= ~RK3588_SYS_DSP_INFACE_EN_MIPI1_MUX;
- die |= RK3588_SYS_DSP_INFACE_EN_MIPI1 |
- FIELD_PREP(RK3588_SYS_DSP_INFACE_EN_MIPI1_MUX, vp->id);
+ die &= ~RK3588_SYS_DSP_INFACE_EN_DP1_MUX;
+ die |= RK3588_SYS_DSP_INFACE_EN_DP1 |
+ FIELD_PREP(RK3588_SYS_DSP_INFACE_EN_DP1_MUX, vp->id);
dip &= ~RK3588_DSP_IF_POL__DP1_PIN_POL;
dip |= FIELD_PREP(RK3588_DSP_IF_POL__DP1_PIN_POL, polflags);
break;
>
>BTW: there seems to be issue with video modes handling on dp0 port:
>-playing video 1920@1080@50 - ok
>-playing then video1920@1080@59,64 hangs board….
>
>hdmi0 works ok. video modes issue is only on dp0
The dclk for vp2 is default from GPLL, it can't divde pixel clock for such a refresh rates,
But it should not hang the board, Sebastian, it seems the frequence of GPLL be changed?
Plesase try it like this: bond the dclk source for VP2 from V0PLL.
+&vop {
+ assigned-clocks = <&cru DCLK_VOP2_SRC>;
+ assigned-clock-parents = <&cru PLL_V0PLL>;
+ status = "okay";
+};
+
>
>
next prev parent reply other threads:[~2025-03-12 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 2:30 Andy Yan
2025-03-05 13:56 ` Piotr Oniszczuk
2025-03-06 0:59 ` Andy Yan
2025-03-06 8:42 ` Piotr Oniszczuk
2025-03-06 8:53 ` Andy Yan
2025-03-06 11:47 ` Piotr Oniszczuk
2025-03-06 12:15 ` Andy Yan
2025-03-06 14:08 ` Piotr Oniszczuk
2025-03-06 14:28 ` Piotr Oniszczuk
2025-03-07 0:48 ` Andy Yan
2025-03-09 20:53 ` Piotr Oniszczuk
2025-03-12 3:51 ` Andy Yan [this message]
2025-03-06 16:39 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2025-02-23 11:30 Andy Yan
2025-02-28 20:30 ` Piotr Oniszczuk
2025-03-01 12:24 ` 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=4003289a.41da.195887b0462.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=andy.yan@rock-chips.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=piotr.oniszczuk@gmail.com \
--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®