From: robert.foss@collabora.com
To: daniel.vetter@ffwll.ch, airlied@linux.ie, eric@anholt.net,
aniel.vetter@ffwll.ch, fengguang.wu@intel.com,
maarten.lankhorst@linux.intel.com, julia.lawall@lip6.fr,
alexander.deucher@amd.com, daniels@collabora.com,
derekf@osg.samsung.com, varadgautam@gmail.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Robert Foss <robert.foss@collabora.com>
Subject: [PATCH v2] drm/vc4: Return -EBUSY if there's already a pending flip event.
Date: Tue, 3 May 2016 13:48:20 -0400 [thread overview]
Message-ID: <1462297700-17491-1-git-send-email-robert.foss@collabora.com> (raw)
From: Robert Foss <robert.foss@collabora.com>
As per the documentation in drm_crtc.h, atomic_commit should return
-EBUSY if an asycnhronous update is requested and there is an earlier
update pending.
Note: docs cited here are drm_crtc.h, and the whole quote is:
* - -EBUSY, if an asynchronous updated is requested and there is
* an earlier updated pending. Drivers are allowed to support a queue
* of outstanding updates, but currently no driver supports that.
* Note that drivers must wait for preceding updates to complete if a
* synchronous update is requested, they are not allowed to fail the
* commit in that case.
Signed-off-by: Robert Foss <robert.foss@collabora.com>
---
Changes since v1:
- Corrected and simplified patch to piggyback on a previously existing check.
drivers/gpu/drm/vc4/vc4_kms.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4_kms.c b/drivers/gpu/drm/vc4/vc4_kms.c
index 4718ae5..7c7188d 100644
--- a/drivers/gpu/drm/vc4/vc4_kms.c
+++ b/drivers/gpu/drm/vc4/vc4_kms.c
@@ -117,10 +117,18 @@ static int vc4_atomic_commit(struct drm_device *dev,
return -ENOMEM;
/* Make sure that any outstanding modesets have finished. */
- ret = down_interruptible(&vc4->async_modeset);
- if (ret) {
- kfree(c);
- return ret;
+ if (async) {
+ ret = down_trylock(&vc4->async_modeset);
+ if (ret) {
+ kfree(c);
+ return -EBUSY;
+ }
+ } else {
+ ret = down_interruptible(&vc4->async_modeset);
+ if (ret) {
+ kfree(c);
+ return ret;
+ }
}
ret = drm_atomic_helper_prepare_planes(dev, state);
--
2.5.0
next reply other threads:[~2016-05-03 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 17:48 robert.foss [this message]
2016-05-03 19:22 ` [PATCH v2] drm/vc4: Return -EBUSY if there's already a pending flip event Eric Anholt
2016-05-10 15:35 ` Robert Foss
2016-05-10 17:06 ` Eric Anholt
2016-05-10 17:19 ` Robert Foss
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=1462297700-17491-1-git-send-email-robert.foss@collabora.com \
--to=robert.foss@collabora.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=aniel.vetter@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=derekf@osg.samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=fengguang.wu@intel.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=varadgautam@gmail.com \
/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