From: John Hunter <zhjwpku@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 3/7] drm/cirrus: phase 3: atomic updates of planes
Date: Thu, 30 Jul 2015 18:08:54 +0800 [thread overview]
Message-ID: <1438250938-59728-4-git-send-email-zhjwpku@gmail.com> (raw)
In-Reply-To: <1438250938-59728-1-git-send-email-zhjwpku@gmail.com>
From: Zhao Junwang <zhjwpku@gmail.com>
Now that phase 1 and 2 are complete we can switch the
update/disable_plane callbacks to their atomic version
Signed-off-by: Zhao Junwang <zhjwpku@gmail.com>
---
drivers/gpu/drm/cirrus/cirrus_main.c | 3 +++
drivers/gpu/drm/cirrus/cirrus_mode.c | 4 ++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/cirrus/cirrus_main.c b/drivers/gpu/drm/cirrus/cirrus_main.c
index d95de34..cfa92bc 100644
--- a/drivers/gpu/drm/cirrus/cirrus_main.c
+++ b/drivers/gpu/drm/cirrus/cirrus_main.c
@@ -10,6 +10,7 @@
*/
#include <drm/drmP.h>
#include <drm/drm_crtc_helper.h>
+#include <drm/drm_atomic_helper.h>
#include "cirrus_drv.h"
@@ -82,6 +83,8 @@ cirrus_user_framebuffer_create(struct drm_device *dev,
static const struct drm_mode_config_funcs cirrus_mode_funcs = {
.fb_create = cirrus_user_framebuffer_create,
+ .atomic_check = drm_atomic_helper_check,
+ .atomic_commit = drm_atomic_helper_commit,
};
/* Unmap the framebuffer from the core and release the memory */
diff --git a/drivers/gpu/drm/cirrus/cirrus_mode.c b/drivers/gpu/drm/cirrus/cirrus_mode.c
index 42a4d86..e8f038b 100644
--- a/drivers/gpu/drm/cirrus/cirrus_mode.c
+++ b/drivers/gpu/drm/cirrus/cirrus_mode.c
@@ -431,8 +431,8 @@ static void cirrus_plane_atomic_disable(struct drm_plane *plane,
}
static const struct drm_plane_funcs cirrus_plane_funcs = {
- .update_plane = drm_plane_helper_update,
- .disable_plane = drm_plane_helper_disable,
+ .update_plane = drm_atomic_helper_update_plane,
+ .disable_plane = drm_atomic_helper_disable_plane,
.reset = drm_atomic_helper_plane_reset,
.atomic_duplicate_state = drm_atomic_helper_plane_duplicate_state,
.atomic_destroy_state = drm_atomic_helper_plane_destroy_state,
--
1.7.10.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-30 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 10:08 [PATCH 0/7] drm/cirrus: convert cirrus to atomic mode-setting John Hunter
2015-07-30 10:08 ` [PATCH 1/7] drm/cirrus: phase 1 - use the transitional helpers John Hunter
2015-07-30 10:08 ` [PATCH 2/7] drm/cirrus: phase 2: wire up state reset, duplicate and destroy John Hunter
2015-07-30 10:08 ` John Hunter [this message]
2015-07-30 10:08 ` [PATCH 4/7] drm/cirrus: add return 0 to make sure if (bo->pin_count) early_exit John Hunter
2015-07-30 10:08 ` [PATCH 5/7] drm/cirrus: phase 3: use atomic .set_config helper John Hunter
2015-07-30 10:08 ` [PATCH 6/7] drm/cirrus: atomic dpms support John Hunter
2015-07-30 10:08 ` [PATCH 7/7] drm/cirrus: add DRIVER_ATOMIC to .driver_features John Hunter
2016-03-02 10:18 ` [PATCH 0/7] drm/cirrus: convert cirrus to atomic mode-setting Emil Velikov
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 7:22 John Hunter
2015-08-05 7:22 ` [PATCH 3/7] drm/cirrus: phase 3: atomic updates of planes John Hunter
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=1438250938-59728-4-git-send-email-zhjwpku@gmail.com \
--to=zhjwpku@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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