From: Jani Nikula <jani.nikula@linux.intel.com>
To: Icenowy Zheng <zhengxingda@iscas.ac.cn>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Sam Ravnborg <sam@ravnborg.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Icenowy Zheng <uwu@icenowy.me>,
Icenowy Zheng <zhengxingda@iscas.ac.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/client: check whether CRTC is active before waiting for vblank
Date: Tue, 19 May 2026 12:41:56 +0300 [thread overview]
Message-ID: <889a09d63c62d88a85d8a31a85feb8bbc178534c@intel.com> (raw)
In-Reply-To: <20260519092420.1124348-1-zhengxingda@iscas.ac.cn>
On Tue, 19 May 2026, Icenowy Zheng <zhengxingda@iscas.ac.cn> wrote:
> Currently the implementaion of drm_client_modeset_wait_for_vblank()
> assumes drm_vblank_get() will fail when the CRTC isn't active. However
> it seems that this is not true, and running fbcon on a device with the
> first CRTC inactive will lead to kernel warning in some cases (which
> could be reproduced with the loongson driver).
>
> Change the implementation to add a check for the active state (atomic) /
> enabled state (non-atomic) before calling drm_vblank_get(). As the
> assumption of drm_vblank_get() failing for inactive CRTC isn't met, the
> error status of drm_vblank_get() can now be exported too.
>
> Cc: stable@vger.kernel.org
> Fixes: d8c4bddcd8bc ("drm/fb-helper: Synchronize dirty worker with vblank")
> Signed-off-by: Icenowy Zheng <zhengxingda@iscas.ac.cn>
> ---
> drivers/gpu/drm/drm_client_modeset.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> index bb49b8361271a..1b03bf351256e 100644
> --- a/drivers/gpu/drm/drm_client_modeset.c
> +++ b/drivers/gpu/drm/drm_client_modeset.c
> @@ -1310,7 +1310,7 @@ int drm_client_modeset_wait_for_vblank(struct drm_client_dev *client, unsigned i
> {
> struct drm_device *dev = client->dev;
> struct drm_crtc *crtc;
> - int ret;
> + int ret = 0;
>
> /*
> * Rate-limit update frequency to vblank. If there's a DRM master
> @@ -1326,15 +1326,24 @@ int drm_client_modeset_wait_for_vblank(struct drm_client_dev *client, unsigned i
> * Only wait for a vblank event if the CRTC is enabled, otherwise
> * just don't do anything, not even report an error.
> */
I'll dodge the question whether the change below is right or not, but
for sure the comment above needs to be amended to match the change.
(Please wait for other review comments before sending another version
with the comment changed.)
BR,
Jani.
> + if (drm_drv_uses_atomic_modeset(dev)) {
> + if (!crtc->state || !crtc->state->active)
> + goto out;
> + } else {
> + if (!crtc->enabled)
> + goto out;
> + }
> +
> ret = drm_crtc_vblank_get(crtc);
> if (!ret) {
> drm_crtc_wait_one_vblank(crtc);
> drm_crtc_vblank_put(crtc);
> }
>
> +out:
> drm_master_internal_release(dev);
>
> - return 0;
> + return ret;
> }
> EXPORT_SYMBOL(drm_client_modeset_wait_for_vblank);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-05-19 9:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 9:24 [PATCH] drm/client: check whether CRTC is active before waiting for vblank Icenowy Zheng
2026-05-19 9:41 ` Jani Nikula [this message]
2026-05-19 11:29 ` Icenowy Zheng
2026-05-22 9:23 ` Maarten Lankhorst
2026-05-22 9:48 ` Icenowy Zheng
2026-05-22 11:55 ` Thomas Zimmermann
2026-05-22 13:13 ` Ville Syrjälä
2026-05-22 13:24 ` Thomas Zimmermann
2026-05-22 13:28 ` Ville Syrjälä
2026-05-22 13:43 ` Thomas Zimmermann
2026-05-22 14:01 ` Icenowy Zheng
2026-05-22 14:09 ` Thomas Zimmermann
2026-05-22 19:39 ` Ville Syrjälä
2026-05-25 8:13 ` Maarten Lankhorst
2026-05-25 12:30 ` Ville Syrjälä
2026-05-26 11:14 ` Maarten Lankhorst
2026-05-26 14:49 ` Ville Syrjälä
2026-05-26 7:59 ` Thomas Zimmermann
2026-05-26 8:18 ` Icenowy Zheng
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=889a09d63c62d88a85d8a31a85feb8bbc178534c@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=uwu@icenowy.me \
--cc=zhengxingda@iscas.ac.cn \
/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