Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp1275270ybi; Wed, 17 Jul 2019 12:22:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqymyj+cy+0CUGix9edeOkdpfFjm3FByF9z79jxQVCRGWrvpUTaT8Y7pvH4m+91WfgGV9/CG X-Received: by 2002:a63:b1d:: with SMTP id 29mr43156384pgl.103.1563391336075; Wed, 17 Jul 2019 12:22:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563391336; cv=none; d=google.com; s=arc-20160816; b=uTgD442mtxow0S2vzX7MW6evyA85t5RkBe7Kuk69kGbuW/fhjeTeeAl+B0cXAC50Eb MsOg/a9NEdH0Mnlo676U0SlMAPVAh3LL+6kpEtCpur0zHLRwkycpwYeisL7WDc5aaiND U/XMq1BjykQqYdd9qtNRbYHMtk4GtEppbdaWRYAof+/9XpPK1rzzJQUrlcvGx0aZdSzJ 9A4YpztknRjeKaDUhDAYcLhqumu0wRff8ocEbMr/Znlm0wvcdm6H0GAY3O4aHHwAUmYg FBtU7/6/pAPFR0PJLOuxAXCP4MjfoDzTfxgJlShmGN2k4GV0VMSRgpDYAOsXXaJhKAk9 I4Uw== 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 :message-id:date:subject:cc:to:from; bh=q0OWxjWRa1Tm7am9sNF7lzHxih1+eK5sKOHbnucSwRY=; b=GpW3Jj3zP8ETDT1YF/S58Se5KUTn8erdHcTM8xaC4AuUFC+rUMQlzyrHJm9ca8QFwv VJ8mvDj+VkrKxxgzvQMJm/mX6I6UCZsZBz5vpRexLrbuWW8n6DGarR4I5S0me0q0GfVX JEAB0HBeKQdHfNifaU4ClHYkaDrk9/g7LziMrosOO+csj0SFrC+iKcuj1yJ/DxFgWvp5 +T0XZDoMoNSSIOjwuLIdyUg3mA5ZIw8DIyZ1X1PrU3VfW5rmpZXe1id6BL+WvmfrbHp/ tIabZwCWI8hdzgJa0fF1cc4da6aSL06dIbeBy3NxmRoD9bsSQQcE+aETnvCWfDQYm29x P67Q== 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 o13si22961400pjr.101.2019.07.17.12.21.59; Wed, 17 Jul 2019 12:22:16 -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 S1727351AbfGQTVh (ORCPT + 99 others); Wed, 17 Jul 2019 15:21:37 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:46704 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726917AbfGQTVg (ORCPT ); Wed, 17 Jul 2019 15:21:36 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: koike) with ESMTPSA id 3F28928A884 From: Helen Koike To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org Cc: kernel@collabora.com, mcasas@google.com, zhenyu.z.wang@intel.com, airlied@linux.ie, daniel.vetter@ffwll.ch, joonas.lahtinen@linux.intel.com, linux-kernel@vger.kernel.org, jani.nikula@linux.intel.com, tfiga@chromium.org, gustavo.padovan@collabora.com, rodrigo.vivi@intel.com, enric.balletbo@collabora.com, tina.zhang@intel.com, ville.syrjala@linux.intel.com, Helen Koike Subject: [PATCH v10 1/2] drm/i915: Introduce async plane update to i915 Date: Wed, 17 Jul 2019 16:21:12 -0300 Message-Id: <20190717192114.21855-1-helen.koike@collabora.com> X-Mailer: git-send-email 2.22.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Gustavo Padovan Add implementation for async plane update callbacks Signed-off-by: Gustavo Padovan Signed-off-by: Enric Balletbo i Serra Signed-off-by: Tina Zhang Signed-off-by: Helen Koike Tested-by: Tina Zhang --- Hi, This is v10, I just fixed the order in how the commit_ready fence is initialized in the intel_atomic_commit() function and solved some conflicts during rebase. This patch depends on [1] "[PATCH] drm: don't block fb changes for async plane updates", which is already on drm-misc, otherwise there will be a regression on igt tests: cursor-vs-flip-atomic-transitions-varying-size cursor-vs-flip-toggle cursor-vs-flip-varying-size with errors of type: "CRITICAL: completed 97 cursor updated in a period of 30 flips, we expect to complete approximately 15360 updates, with the threshold set at 7680" When picking this patch, please backmerge [1] into drm-intel tree. [1] https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-fixes&id=89a4aac0ab0e6f5eea10d7bf4869dd15c3de2cd4 Thanks Helen Changes in v10: - v9: https://patchwork.kernel.org/patch/11000561/ - rebase on drm-tip - call i915_sw_fence_init() in the begining of intel_atomic_commit(), otherwise drm_atomic_helper_prepare_planes() without initializing the fence object, casing errors like: ODEBUG: assert_init not available (active state 0) object type: i915_sw_fence hint: 0x0 Changes in v9: - v8: https://patchwork.kernel.org/patch/10843395/ - Added tested-by tag - submitted to intel-gfx@lists.freedesktop.org to invoke CI - rebased and fixed conflicts on top of drm-tip Changes in v8: - v7: https://lkml.org/lkml/2018/6/8/168 - v7 was splited in two, one that adds the async callbacks and another that updates the cursor. - rebase with drm-intel - allow async update in all types of planes, not only cursor - add watermark checks in async update - remove bypass of intel_prepare_plane_fb() in case of async update - add missing drm_atomic_helper_cleanup_planes(dev, state) call in intel_atomic_commit(). - use swap() function in async update to set the old_fb in the new_state object. - use helpers intel_update_plane()/intel_disable_plane() Changes in v7: - Rebase on top of drm-intel repository. Hopefully now will play nicely with autobuilders. Changes in v6: - Rework the intel_plane_atomic_async_update due driver changed from last time. - Removed the mutex_lock/unlock as causes a deadlock. Changes in v5: - Call drm_atomic_helper_async_check() from the check hook Changes in v4: - Set correct vma to new state for cleanup - Move size checks back to drivers (Ville Syrjälä) Changes in v3: - Move fb setting to core and use new state (Eric Anholt) .../gpu/drm/i915/display/intel_atomic_plane.c | 71 +++++++++++++++++++ drivers/gpu/drm/i915/display/intel_display.c | 14 +++- 2 files changed, 83 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/display/intel_atomic_plane.c b/drivers/gpu/drm/i915/display/intel_atomic_plane.c index ab411d5e093c..2aa6e2ab4ac8 100644 --- a/drivers/gpu/drm/i915/display/intel_atomic_plane.c +++ b/drivers/gpu/drm/i915/display/intel_atomic_plane.c @@ -364,8 +364,79 @@ void i9xx_update_planes_on_crtc(struct intel_atomic_state *state, } } +static int intel_plane_atomic_async_check(struct drm_plane *plane, + struct drm_plane_state *state) +{ + struct drm_crtc_state *crtc_state; + + crtc_state = drm_atomic_get_existing_crtc_state(state->state, + state->crtc); + if (WARN_ON(!crtc_state)) + return -EINVAL; + + /* + * When crtc is inactive or there is a modeset pending, + * wait for it to complete in the slowpath + */ + if (!crtc_state->active || to_intel_crtc_state(crtc_state)->update_pipe) + return -EINVAL; + + /* + * If any parameters change that may affect watermarks, + * take the slowpath. Only changing fb or position should be + * in the fastpath. + */ + if (plane->state->crtc != state->crtc || + plane->state->src_w != state->src_w || + plane->state->src_h != state->src_h || + plane->state->crtc_w != state->crtc_w || + plane->state->crtc_h != state->crtc_h || + !plane->state->fb != !state->fb) + return -EINVAL; + + return 0; +} + +static void intel_plane_atomic_async_update(struct drm_plane *plane, + struct drm_plane_state *new_state) +{ + struct intel_atomic_state *intel_new_state = + to_intel_atomic_state(new_state->state); + struct intel_plane *intel_plane = to_intel_plane(plane); + struct drm_crtc *crtc = plane->state->crtc; + struct intel_crtc_state *new_crtc_state; + struct intel_crtc *intel_crtc; + int i; + + for_each_new_intel_crtc_in_state(intel_new_state, intel_crtc, + new_crtc_state, i) + WARN_ON(new_crtc_state->wm.need_postvbl_update || + new_crtc_state->update_wm_post); + + i915_gem_track_fb(intel_fb_obj(plane->state->fb), + intel_fb_obj(new_state->fb), + intel_plane->frontbuffer_bit); + + plane->state->src_x = new_state->src_x; + plane->state->src_y = new_state->src_y; + plane->state->crtc_x = new_state->crtc_x; + plane->state->crtc_y = new_state->crtc_y; + + swap(plane->state->fb, new_state->fb); + + if (plane->state->visible) + intel_update_plane(intel_plane, + to_intel_crtc_state(crtc->state), + to_intel_plane_state(plane->state)); + else + intel_disable_plane(intel_plane, + to_intel_crtc_state(crtc->state)); +} + const struct drm_plane_helper_funcs intel_plane_helper_funcs = { .prepare_fb = intel_prepare_plane_fb, .cleanup_fb = intel_cleanup_plane_fb, .atomic_check = intel_plane_atomic_check, + .atomic_async_check = intel_plane_atomic_async_check, + .atomic_async_update = intel_plane_atomic_async_update, }; diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c index e25b82d07d4f..acfb9b7939e2 100644 --- a/drivers/gpu/drm/i915/display/intel_display.c +++ b/drivers/gpu/drm/i915/display/intel_display.c @@ -14142,11 +14142,21 @@ static int intel_atomic_commit(struct drm_device *dev, struct drm_i915_private *dev_priv = to_i915(dev); int ret = 0; + i915_sw_fence_init(&state->commit_ready, + intel_atomic_commit_ready); + + if (_state->async_update) { + ret = drm_atomic_helper_prepare_planes(dev, _state); + if (ret) + return ret; + drm_atomic_helper_async_commit(dev, _state); + drm_atomic_helper_cleanup_planes(dev, _state); + return 0; + } + state->wakeref = intel_runtime_pm_get(&dev_priv->runtime_pm); drm_atomic_state_get(&state->base); - i915_sw_fence_init(&state->commit_ready, - intel_atomic_commit_ready); /* * The intel_legacy_cursor_update() fast path takes care -- 2.22.0