Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp2503694imb; Mon, 4 Mar 2019 06:52:32 -0800 (PST) X-Google-Smtp-Source: APXvYqxEs1CSh/X/1w00iyXkZVsiJcRC+NtN6kyUh+wyWEwCiDDhuJiNan4hGkqKMwnr/hhy7873 X-Received: by 2002:a17:902:8bc6:: with SMTP id r6mr21135787plo.235.1551711151967; Mon, 04 Mar 2019 06:52:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551711151; cv=none; d=google.com; s=arc-20160816; b=BsS7GvpTHx1+q4UoZKam0vQELChVS05R6D4hIW+UbMASpPrciTcgrOagLbz6C0JtB+ NhzcTfF9bR08YNI+KGqitFAXFg5df9NbpFnWWe7gvMSAfOekNWSPcCEN9SYe1n2fzChM P+zcyRlmcrZ89rYrxFnTiAT7IMoFFDnxlutimp5KNZQJu9iTIdkCaFTe+ssnOMH9nc8m QaXPp0kMngyB+bXBH/tAj+6aXpeP1KyBJnacNJGhf1jdCpNMMOAA/B2Lfnpbbp926dSU OJrKLlbD5uSsLFOUdAg1GdAjUNT6COZl3gD2bulrN55RxOLW9KBmVmzjhnIvHjwV8vhm C4QQ== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=XigGrB2NbPtFBrSZZELkZvsaAHusEGIfjD2Sku+QZ8Y=; b=V04h1YkDqOvCPhIdsP36oyVgNCuQE0hgaJ02rqwksDT9MajrPHaKgXpWe8Yw2HMRBj 9eD6e1JkkYFIrHKHZEcJh6pb1nXzo4W/9gVa54wup+8wE7qnx9FIhKZDXxc4Asc1jpRQ fwn2sMJj/kDmJnmk4O4tZsQ7bsa1YU3IJvlh6PCc5SS6P0B65Z+GlQMhlteqtSIkb0IS Agyr8eEkcpktIkazPFh/MQELBZP+cRZ0MKunAupBkH7ApK/2biPKnj4ZsoOSIYRCje37 yAdWgj+Ykwj4b9C4dmwc3O6pVlPb7Cx+CetMqGSka6QKzBzYjixfjJ1Ehh15yizoAmud PaPg== 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 g4si5417490pgi.380.2019.03.04.06.52.16; Mon, 04 Mar 2019 06:52:31 -0800 (PST) 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 S1726063AbfCDOts (ORCPT + 99 others); Mon, 4 Mar 2019 09:49:48 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:49346 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726161AbfCDOtr (ORCPT ); Mon, 4 Mar 2019 09:49:47 -0500 Received: from localhost.localdomain (unknown [IPv6:2804:431:9718:a1b1:9d17:4c45:79a4:9c61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: koike) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 585DD2807B1; Mon, 4 Mar 2019 14:49:42 +0000 (GMT) From: Helen Koike To: dri-devel@lists.freedesktop.org, nicholas.kazlauskas@amd.com Cc: andrey.grodzovsky@amd.com, daniel.vetter@ffwll.ch, linux-kernel@vger.kernel.org, Tomasz Figa , boris.brezillon@collabora.com, David Airlie , Sean Paul , kernel@collabora.com, harry.wentland@amd.com, =?UTF-8?q?St=C3=A9phane=20Marchesin?= Subject: [PATCH 5/5] drm/vc4: fix fb references in async update Date: Mon, 4 Mar 2019 11:49:09 -0300 Message-Id: <20190304144909.6267-6-helen.koike@collabora.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190304144909.6267-1-helen.koike@collabora.com> References: <20190304144909.6267-1-helen.koike@collabora.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Async update callbacks are expected to set the old_fb in the new_state so prepare/cleanup framebuffers are balanced. Calling drm_atomic_set_fb_for_plane() (which gets a reference of the new fb and put the old fb) is not required, as it's taken care by drm_mode_cursor_universal() when calling drm_atomic_helper_update_plane(). Cc: # v4.19+: 25dc194b34dd: drm: Block fb changes for async plane updates Cc: # v4.19+: 8105bbaf9afd: drm: don't block fb changes for async plane updates Fixes: 25dc194b34dd ("drm: Block fb changes for async plane updates") Suggested-by: Boris Brezillon Signed-off-by: Helen Koike --- Hello, As mentioned in the cover letter, I tested on the rockchip and on i915 using igt plane_cursor_legacy and kms_cursor_legacy and I didn't see any regressions. But I couldn't test on VC4. I have a Raspberry pi model B rev2, when FB_SIMPLE is running I can see output on the screen, but when vc4 is loaded my hdmi display is not detected anymore, I am still debugging this, probably some config in the firmware, but I would appreciate if anyone could help me testing it. Also the Cc statble commit hash dependency needs to be updated once the refered commit is merged. Thanks! Helen drivers/gpu/drm/vc4/vc4_plane.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c index 1babfeca0c92..1235e53b22a3 100644 --- a/drivers/gpu/drm/vc4/vc4_plane.c +++ b/drivers/gpu/drm/vc4/vc4_plane.c @@ -968,7 +968,7 @@ static void vc4_plane_atomic_async_update(struct drm_plane *plane, { struct vc4_plane_state *vc4_state, *new_vc4_state; - drm_atomic_set_fb_for_plane(plane->state, state->fb); + swap(plane->state->fb, state->fb); plane->state->crtc_x = state->crtc_x; plane->state->crtc_y = state->crtc_y; plane->state->crtc_w = state->crtc_w; -- 2.20.1