From: "Andy Yan" <andyshrk@163.com>
To: "Sebastian Reichel" <sebastian.reichel@collabora.com>
Cc: heiko@sntech.de, hjc@rock-chips.com, mripard@kernel.org,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
"Andy Yan" <andy.yan@rock-chips.com>
Subject: Re:Re: [PATCH v2] drm/rockchip: vop2: Add mode valid callback for crtc
Date: Mon, 19 Jan 2026 10:42:41 +0800 (CST) [thread overview]
Message-ID: <5cc9f5c4.27fa.19bd4221378.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <aW1uWZD6u4e2o6jF@venus>
Hello Sebastian,
At 2026-01-19 07:43:35, "Sebastian Reichel" <sebastian.reichel@collabora.com> wrote:
>Hi,
>
>On Sat, Jan 17, 2026 at 10:07:30AM +0800, Andy Yan wrote:
>> From: Andy Yan <andy.yan@rock-chips.com>
>>
>> The different Video Ports support different maximum resolutions.
>> Reject resolutions that are not supported by a specific VP.
>>
>> Only the output width is checked because the hardware itself does
>> not have a hard output height limit.
>>
>> Filter the mode that can't output by the VP/crtc.
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>>
>> ---
>
>A common RK3576 setup is VP0 mapped to HDMI and VP1 mapped to USB-C
>DP AltMode. Since RK3576 VP1 only supports 2.5K, this can easily
>become relevant when connecting a 4K screen via USB-C DP AltMode.
>I've tested that this patch properly drops all unsupported modes
>based on the resolution.
>
>Further checks will be needed to ensure the bandwidth requirements
>are also met (e.g. RK3576 VP1 only supports 2.5K@60Hz, so 2.5K@120Hz
>should be marked as BAD). I think the bandwidth check should be a
>separate patch, but thought it might be worth mentioning here in
>case somebody stumbles over it.
Yes, I also think it's better to do by a separate patch, because we should add
more detail dclk description for every VP. I will do it after this patch get merged.
>
>Anyways:
>
>Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
>Tested-by: Sebastian Reichel <sebastian.reichel@collabora.com> # Sige5
>
>Greetings,
>
>-- Sebastian
>
>>
>> Changes in v2:
>> - Add more detailed commit message
>>
>> drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
>> index 498df0ce4680..74fba29bfff3 100644
>> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
>> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
>> @@ -1439,6 +1439,17 @@ static void vop2_crtc_disable_vblank(struct drm_crtc *crtc)
>> vop2_crtc_disable_irq(vp, VP_INT_FS_FIELD);
>> }
>>
>> +static enum drm_mode_status vop2_crtc_mode_valid(struct drm_crtc *crtc,
>> + const struct drm_display_mode *mode)
>> +{
>> + struct vop2_video_port *vp = to_vop2_video_port(crtc);
>> +
>> + if (mode->hdisplay > vp->data->max_output.width)
>> + return MODE_BAD_HVALUE;
>> +
>> + return MODE_OK;
>> +}
>> +
>> static bool vop2_crtc_mode_fixup(struct drm_crtc *crtc,
>> const struct drm_display_mode *mode,
>> struct drm_display_mode *adj_mode)
>> @@ -1884,6 +1895,7 @@ static void vop2_crtc_atomic_flush(struct drm_crtc *crtc,
>>
>> static const struct drm_crtc_helper_funcs vop2_crtc_helper_funcs = {
>> .mode_fixup = vop2_crtc_mode_fixup,
>> + .mode_valid = vop2_crtc_mode_valid,
>> .atomic_check = vop2_crtc_atomic_check,
>> .atomic_begin = vop2_crtc_atomic_begin,
>> .atomic_flush = vop2_crtc_atomic_flush,
>> --
>> 2.43.0
>>
>> base-commit: 1613a67b5360d6ff78f62143a1cf123414a1b4d9
>> branch: rk3576-dp-upstream
>>
next prev parent reply other threads:[~2026-01-19 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 2:07 Andy Yan
2026-01-18 23:43 ` Sebastian Reichel
2026-01-19 2:42 ` Andy Yan [this message]
2026-01-20 10:18 ` Heiko Stuebner
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=5cc9f5c4.27fa.19bd4221378.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®