Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp1767992imc; Mon, 11 Mar 2019 23:36:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqzu9oRwdgUkgRwl9b0F1J/a8WklGs2hHfQLopCqxGCfovPiTOITL0eliPYSBIXx6x4GE0oh X-Received: by 2002:a17:902:8c84:: with SMTP id t4mr11724941plo.298.1552372599012; Mon, 11 Mar 2019 23:36:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552372599; cv=none; d=google.com; s=arc-20160816; b=EnMXWiJ19tzXDXS5YL3MVQCoWjh3aXF7GdS2U5mVUQRU3td+P6AL1hqkzI7/3hcQyO BcykVZcWzJBHeEp1+QBV0JiJ8a6QEZCXGP3IiAbqBAhuLqm0yqGMqzwb5aSPxt3qIO1s dwvq9Ez0vTGea82Dlloopm9YyfU3eZCwXTCYCVHIXZk1NAyJtH7w9J4cBKL3ZkXYztY6 XV6Duxad0YabwN82FCWFEVxtEjMbc6KGuScZFIa8Ye05aZ9AGQV8Svv+6eukVVsk4MbK srGGwWIp5t3AuWajnwQ77oUIehpAivSMq8aFu91AFU/zEbCCTEICjvNp3VEwyLsuVTFq gjqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=mx9xhX8kt4/OxcjBoUTGvLnZdpBqhISLMqrm1L0aEX0=; b=doP9uPzIP03kgikxCnUuHx+XtqlJk1phNMSRew8czmHIxy9rLpXDRkHSWQe23fLeDI TWsbYP00iS2fgL+TreLzGznEV4IfYNwFaNP1mE4XBRCTL8pK035HUTCWozOkhCeCYhlD rlfRGSw8BMgaBUKtzEVUDXWCMXO+IFNYEye2is1068ICUi7t9fRF5zl2UegPbEDRJdIm Gve30qwBRZbj4ljNlO2G0V7YkwHbYpaOfN/7WSEDjxCDVcvoryefQxTgSIhD6sZQDZHW Edaf3iPuNUmU6jIpDOfGTR8OkFwJFkeJY71SI/+bmNrxRXneHyCQj/z/FyIKjVQlbiN+ pbAQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d17si2438598pgg.391.2019.03.11.23.36.22; Mon, 11 Mar 2019 23:36:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727100AbfCLGeo (ORCPT + 99 others); Tue, 12 Mar 2019 02:34:44 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:57476 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726263AbfCLGeo (ORCPT ); Tue, 12 Mar 2019 02:34:44 -0400 Received: from localhost (unknown [IPv6:2a01:e0a:2c:6930:b93f:9fae:b276:a89a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bbrezillon) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id B4AE627B896; Tue, 12 Mar 2019 06:34:41 +0000 (GMT) Date: Tue, 12 Mar 2019 07:34:38 +0100 From: Boris Brezillon To: Helen Koike Cc: dri-devel@lists.freedesktop.org, nicholas.kazlauskas@amd.com, andrey.grodzovsky@amd.com, daniel.vetter@ffwll.ch, linux-kernel@vger.kernel.org, Tomasz Figa , David Airlie , Sean Paul , kernel@collabora.com, harry.wentland@amd.com, =?UTF-8?B?U3TDqXBoYW5l?= Marchesin , Sandy Huang , linux-rockchip@lists.infradead.org, Heiko =?UTF-8?B?U3TDvGJuZXI=?= , linux-arm-kernel@lists.infradead.org, Daniel Vetter Subject: Re: [PATCH v2 1/5] drm/rockchip: fix fb references in async update Message-ID: <20190312073438.05ad8173@collabora.com> In-Reply-To: <20190312022204.2775-2-helen.koike@collabora.com> References: <20190312022204.2775-1-helen.koike@collabora.com> <20190312022204.2775-2-helen.koike@collabora.com> Organization: Collabora X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 11 Mar 2019 23:21:59 -0300 Helen Koike wrote: > In the case of async update, modifications are done in place, i.e. in the > current plane state, so the new_state is prepared and the new_state is > cleanup up (instead of the old_state, diferrently on what happen in a ^ cleaned up ^ differently (but maybe "unlike what happens" is more appropriate here). > normal sync update). > To cleanup the old_fb properly, it needs to be placed in the new_state > in the end of async_update, so cleanup call will unreference the old_fb > correctly. > > Also, the previous code had a: > > plane_state = plane->funcs->atomic_duplicate_state(plane); > ... > swap(plane_state, plane->state); > > if (plane->state->fb && plane->state->fb != new_state->fb) { > ... > } > > Which was wrong, as the fb were just assigned to be equal, so this if > statement nevers evaluates to true. > > Another details is that the function drm_crtc_vblank_get() can only be > called when vop->is_enabled is true, otherwise it has no effect and > trows a WARN_ON(). > > Calling drm_atomic_set_fb_for_plane() (which get a referent of the new > fb and pus the old fb) is not required, as it is taken care by > drm_mode_cursor_universal() when calling > drm_atomic_helper_update_plane(). > > Signed-off-by: Helen Koike > > --- > Hello, > > I tested on the rockchip ficus v1.1 using igt plane_cursor_legacy and > kms_cursor_legacy and I didn't see any regressions. > > Changes in v2: None > > drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 42 ++++++++++++--------- > 1 file changed, 24 insertions(+), 18 deletions(-) > > diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c > index c7d4c6073ea5..a1ee8c156a7b 100644 > --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c > +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c > @@ -912,30 +912,31 @@ static void vop_plane_atomic_async_update(struct drm_plane *plane, > struct drm_plane_state *new_state) > { > struct vop *vop = to_vop(plane->state->crtc); > - struct drm_plane_state *plane_state; > + struct drm_framebuffer *old_fb = plane->state->fb; > > - plane_state = plane->funcs->atomic_duplicate_state(plane); > - plane_state->crtc_x = new_state->crtc_x; > - plane_state->crtc_y = new_state->crtc_y; > - plane_state->crtc_h = new_state->crtc_h; > - plane_state->crtc_w = new_state->crtc_w; > - plane_state->src_x = new_state->src_x; > - plane_state->src_y = new_state->src_y; > - plane_state->src_h = new_state->src_h; > - plane_state->src_w = new_state->src_w; > - > - if (plane_state->fb != new_state->fb) > - drm_atomic_set_fb_for_plane(plane_state, new_state->fb); > - > - swap(plane_state, plane->state); > - > - if (plane->state->fb && plane->state->fb != new_state->fb) { > + /* > + * A scanout can still be occurring, so we can't drop the reference to > + * the old framebuffer. To solve this we get a reference to old_fb and > + * set a worker to release it later. Hm, doesn't look like an async update to me if we have to wait for the next VBLANK to happen to get the new content on the screen. Maybe we should reject async updates when old_fb != new_fb in the rk ->async_check() hook. > + */ > + if (vop->is_enabled && > + plane->state->fb && plane->state->fb != new_state->fb) { > drm_framebuffer_get(plane->state->fb); > WARN_ON(drm_crtc_vblank_get(plane->state->crtc) != 0); > drm_flip_work_queue(&vop->fb_unref_work, plane->state->fb); > set_bit(VOP_PENDING_FB_UNREF, &vop->pending); > } In any case, I think this should be called after vop_plane_atomic_update() to prevent the situation where the VBLANK event happens between this point and the following vop_plane_atomic_update() call. > > + plane->state->crtc_x = new_state->crtc_x; > + plane->state->crtc_y = new_state->crtc_y; > + plane->state->crtc_h = new_state->crtc_h; > + plane->state->crtc_w = new_state->crtc_w; > + plane->state->src_x = new_state->src_x; > + plane->state->src_y = new_state->src_y; > + plane->state->src_h = new_state->src_h; > + plane->state->src_w = new_state->src_w; > + plane->state->fb = new_state->fb; Any reason not to use swap() here and reference plane->state->fb instead of new_state->fb after this point? > + > if (vop->is_enabled) { > rockchip_drm_psr_inhibit_get_state(new_state->state); > vop_plane_atomic_update(plane, plane->state); > @@ -945,7 +946,12 @@ static void vop_plane_atomic_async_update(struct drm_plane *plane, > rockchip_drm_psr_inhibit_put_state(new_state->state); > } > > - plane->funcs->atomic_destroy_state(plane, plane_state); > + /* > + * In async update we perform inplace modifications and release the > + * new_state. The following is required so we release the reference of > + * the old framebuffer. > + */ > + new_state->fb = old_fb; > } > > static const struct drm_plane_helper_funcs plane_helper_funcs = {