From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Rob Clark <robdclark@chromium.org>,
Abhinav Kumar <abhinavk@codeaurora.org>,
Alexios Zavras <alexios.zavras@intel.com>,
Allison Randal <allison@lohutok.net>,
Boris Brezillon <bbrezillon@kernel.org>,
Bruce Wang <bzwang@chromium.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Enrico Weigelt <info@metux.net>,
freedreno@lists.freedesktop.org (open list:DRM DRIVER FOR MSM
ADRENO GPU), Fritz Koenig <frkoenig@google.com>,
Georgi Djakov <georgi.djakov@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jeykumar Sankaran <jsanka@codeaurora.org>,
Jonathan Marek <jonathan@marek.ca>,
Jordan Crouse <jcrouse@codeaurora.org>,
linux-arm-msm@vger.kernel.org (open list:DRM DRIVER FOR MSM
ADRENO GPU), linux-kernel@vger.kernel.org (open list),
Mamta Shukla <mamtashukla555@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
Sravanthi Kollukuduru <skolluku@codeaurora.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 0/9] drm/msm: async commit support
Date: Tue, 27 Aug 2019 14:33:30 -0700 [thread overview]
Message-ID: <20190827213421.21917-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
Currently the dpu backend attempts to handle async commits. But it
is racey and could result in flushing multiple times in a frame, or
modifying hw state (such as scanout address or cursor position) after
the previous flush, but before vblank, causing underflows (which
manifest as brief black flashes).
This patchset removes the previous dpu async commit handling, and
reworks the internal kms backend API to decouple flushing. And in
the end introduces an hrtimer to flush async updates. The overall
approach is:
1) Move flushing various hw state out of encoder/crtc atomic commit
(which is anyways an improvement over the current state, where
we either flush from crtc or encoder, depending on whether it is
a full modeset)
2) Switch to crtc_mask for anything that completes after atomic
_commit_tail(), so we do not need to keep the atomic state
around. Ie. from drm core's perspective, an async commit
completes immediately.
This avoids fighting with drm core about the lifecycle of an
atomic state object.
3) Track a bitmask of crtcs w/ pending async flush, and setup
an hrtimer with expiration 1ms before vblank, to trigger
the flush. For async commits, we push the state down to
the double buffered hw registers immediately, and only
defer writing the flush registers.
Current patchset only includes the dpu backend support for async
commits.. mdp4 and mdp5 should be relatively trivial (less layers
of indirection involved). But I won't have access to any mdp4 hw
for a few more weeks, so at least that part I might punt on for
now.
Rob Clark (9):
drm/msm/dpu: unwind async commit handling
drm/msm/dpu: add real wait_for_commit_done()
drm/msm/dpu: handle_frame_done() from vblank irq
drm/msm: add kms->wait_flush()
drm/msm: convert kms->complete_commit() to crtc_mask
drm/msm: add kms->flush_commit()
drm/msm: split power control from prepare/complete_commit
drm/msm: async commit support
drm/msm/dpu: async commit support
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 48 +---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h | 7 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 46 ++--
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 8 +-
.../drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 39 ++--
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 99 +++++----
drivers/gpu/drm/msm/disp/mdp4/mdp4_kms.c | 48 ++--
drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c | 47 ++--
drivers/gpu/drm/msm/msm_atomic.c | 210 +++++++++++++++---
drivers/gpu/drm/msm/msm_drv.c | 1 +
drivers/gpu/drm/msm/msm_drv.h | 4 +
drivers/gpu/drm/msm/msm_kms.h | 108 ++++++++-
12 files changed, 466 insertions(+), 199 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-27 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 21:33 Rob Clark [this message]
2019-08-27 21:33 ` [PATCH 1/9] drm/msm/dpu: unwind async commit handling Rob Clark
2019-08-29 13:04 ` Sean Paul
2019-08-27 21:33 ` [PATCH 2/9] drm/msm/dpu: add real wait_for_commit_done() Rob Clark
2019-08-29 13:04 ` Sean Paul
2019-08-27 21:33 ` [PATCH 3/9] drm/msm/dpu: handle_frame_done() from vblank irq Rob Clark
2019-08-29 13:05 ` Sean Paul
2019-08-27 21:33 ` [PATCH 4/9] drm/msm: add kms->wait_flush() Rob Clark
2019-08-29 13:04 ` Sean Paul
2019-08-27 21:33 ` [PATCH 5/9] drm/msm: convert kms->complete_commit() to crtc_mask Rob Clark
2019-08-27 21:33 ` [PATCH 6/9] drm/msm: add kms->flush_commit() Rob Clark
2019-08-27 21:33 ` [PATCH 7/9] drm/msm: split power control from prepare/complete_commit Rob Clark
2019-08-27 21:33 ` [PATCH 8/9] drm/msm: async commit support Rob Clark
2019-08-27 21:33 ` [PATCH 9/9] drm/msm/dpu: " Rob Clark
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=20190827213421.21917-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=abhinavk@codeaurora.org \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=bbrezillon@kernel.org \
--cc=bzwang@chromium.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=frkoenig@google.com \
--cc=georgi.djakov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=jcrouse@codeaurora.org \
--cc=jonathan@marek.ca \
--cc=jsanka@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamtashukla555@gmail.com \
--cc=robdclark@chromium.org \
--cc=seanpaul@chromium.org \
--cc=skolluku@codeaurora.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).