From: John Keeping <john@metanate.com>
To: Mark yao <mark.yao@rock-chips.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/3] drm/rockchip: fix cursor performance with atomic
Date: Thu, 14 Jan 2016 14:39:39 +0000 [thread overview]
Message-ID: <cover.1452782114.git.john@metanate.com> (raw)
In-Reply-To: <20160114142047.GD19130@phenom.ffwll.local>
On Thu, 14 Jan 2016 15:20:47 +0100, Daniel Vetter wrote:
> Ugh. Oh well, there's not really anything we can do in core nore helpers
> to make this easier for drivers. This really only can be fixed sensibly at
> the hardware level.
>
> So yeah I think exposing framebuffer_changed as a helper is the way to go
> here.
OK, here's a series to do that. I also added a comment to
rockchip_atomic_wait_for_complete() explaining why we can't use
drm_atomic_helper_wait_for_vblanks().
John Keeping (3):
drm/atomic-helper: Export framebuffer_changed()
drm/rockchip: don't wait for vblank if fb hasn't changed
drm/rockchip: explain why we can't wait_for_vblanks
drivers/gpu/drm/drm_atomic_helper.c | 24 ++++++++++++++++++++----
drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 14 ++++++++++++--
include/drm/drm_atomic_helper.h | 4 ++++
3 files changed, 36 insertions(+), 6 deletions(-)
--
2.7.0.226.gfe986fe
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: john@metanate.com (John Keeping)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] drm/rockchip: fix cursor performance with atomic
Date: Thu, 14 Jan 2016 14:39:39 +0000 [thread overview]
Message-ID: <cover.1452782114.git.john@metanate.com> (raw)
In-Reply-To: <20160114142047.GD19130@phenom.ffwll.local>
On Thu, 14 Jan 2016 15:20:47 +0100, Daniel Vetter wrote:
> Ugh. Oh well, there's not really anything we can do in core nore helpers
> to make this easier for drivers. This really only can be fixed sensibly at
> the hardware level.
>
> So yeah I think exposing framebuffer_changed as a helper is the way to go
> here.
OK, here's a series to do that. I also added a comment to
rockchip_atomic_wait_for_complete() explaining why we can't use
drm_atomic_helper_wait_for_vblanks().
John Keeping (3):
drm/atomic-helper: Export framebuffer_changed()
drm/rockchip: don't wait for vblank if fb hasn't changed
drm/rockchip: explain why we can't wait_for_vblanks
drivers/gpu/drm/drm_atomic_helper.c | 24 ++++++++++++++++++++----
drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 14 ++++++++++++--
include/drm/drm_atomic_helper.h | 4 ++++
3 files changed, 36 insertions(+), 6 deletions(-)
--
2.7.0.226.gfe986fe
WARNING: multiple messages have this Message-ID (diff)
From: John Keeping <john@metanate.com>
To: Mark yao <mark.yao@rock-chips.com>
Cc: John Keeping <john@metanate.com>, Daniel Vetter <daniel@ffwll.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/3] drm/rockchip: fix cursor performance with atomic
Date: Thu, 14 Jan 2016 14:39:39 +0000 [thread overview]
Message-ID: <cover.1452782114.git.john@metanate.com> (raw)
In-Reply-To: <20160114142047.GD19130@phenom.ffwll.local>
On Thu, 14 Jan 2016 15:20:47 +0100, Daniel Vetter wrote:
> Ugh. Oh well, there's not really anything we can do in core nore helpers
> to make this easier for drivers. This really only can be fixed sensibly at
> the hardware level.
>
> So yeah I think exposing framebuffer_changed as a helper is the way to go
> here.
OK, here's a series to do that. I also added a comment to
rockchip_atomic_wait_for_complete() explaining why we can't use
drm_atomic_helper_wait_for_vblanks().
John Keeping (3):
drm/atomic-helper: Export framebuffer_changed()
drm/rockchip: don't wait for vblank if fb hasn't changed
drm/rockchip: explain why we can't wait_for_vblanks
drivers/gpu/drm/drm_atomic_helper.c | 24 ++++++++++++++++++++----
drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 14 ++++++++++++--
include/drm/drm_atomic_helper.h | 4 ++++
3 files changed, 36 insertions(+), 6 deletions(-)
--
2.7.0.226.gfe986fe
next prev parent reply other threads:[~2016-01-14 14:39 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 12:53 [RFC/PATCH] drm/rockchip: don't wait for vblank if fb hasn't changed John Keeping
2016-01-13 12:53 ` John Keeping
2016-01-13 12:53 ` John Keeping
2016-01-13 14:23 ` Daniel Vetter
2016-01-13 14:23 ` Daniel Vetter
2016-01-13 14:23 ` Daniel Vetter
2016-01-13 14:34 ` John Keeping
2016-01-13 14:34 ` John Keeping
2016-01-13 14:34 ` John Keeping
2016-01-13 15:40 ` Daniel Vetter
2016-01-13 15:40 ` Daniel Vetter
2016-01-13 15:40 ` Daniel Vetter
2016-01-13 15:55 ` John Keeping
2016-01-13 15:55 ` John Keeping
2016-01-13 15:55 ` John Keeping
2016-01-13 16:21 ` Daniel Vetter
2016-01-13 16:21 ` Daniel Vetter
2016-01-13 16:21 ` Daniel Vetter
2016-01-13 16:40 ` John Keeping
2016-01-13 16:40 ` John Keeping
2016-01-13 16:40 ` John Keeping
2016-01-13 17:19 ` Daniel Vetter
2016-01-13 17:19 ` Daniel Vetter
2016-01-13 17:19 ` Daniel Vetter
2016-01-13 17:39 ` John Keeping
2016-01-13 17:39 ` John Keeping
2016-01-13 17:39 ` John Keeping
2016-01-14 1:16 ` Mark yao
2016-01-14 1:16 ` Mark yao
2016-01-14 1:16 ` Mark yao
2016-01-14 8:32 ` Daniel Vetter
2016-01-14 8:32 ` Daniel Vetter
2016-01-14 8:32 ` Daniel Vetter
2016-01-14 8:46 ` Mark yao
2016-01-14 8:46 ` Mark yao
2016-01-14 8:46 ` Mark yao
2016-01-14 14:20 ` Daniel Vetter
2016-01-14 14:20 ` Daniel Vetter
2016-01-14 14:20 ` Daniel Vetter
2016-01-14 14:39 ` John Keeping [this message]
2016-01-14 14:39 ` [PATCH 0/3] drm/rockchip: fix cursor performance with atomic John Keeping
2016-01-14 14:39 ` John Keeping
2016-01-14 14:39 ` [PATCH 1/3] drm/atomic-helper: Export framebuffer_changed() John Keeping
2016-01-14 14:39 ` John Keeping
2016-01-14 14:39 ` John Keeping
2016-01-14 14:56 ` Daniel Vetter
2016-01-14 14:56 ` Daniel Vetter
2016-01-14 14:56 ` Daniel Vetter
2016-01-14 14:39 ` [PATCH 2/3] drm/rockchip: don't wait for vblank if fb hasn't changed John Keeping
2016-01-14 14:39 ` John Keeping
2016-01-14 14:39 ` [PATCH 3/3] drm/rockchip: explain why we can't wait_for_vblanks John Keeping
2016-01-14 14:39 ` John Keeping
2016-01-14 14:39 ` John Keeping
2016-01-14 14:57 ` Thierry Reding
2016-01-14 14:57 ` Thierry Reding
2016-01-14 14:57 ` Thierry Reding
2016-01-14 16:26 ` John Keeping
2016-01-14 16:26 ` John Keeping
2016-01-14 16:26 ` John Keeping
2016-01-18 1:40 ` Mark yao
2016-01-18 1:40 ` Mark yao
2016-01-18 1:40 ` Mark yao
2016-01-19 10:46 ` [PATCH v2 0/3] drm/rockchip: fix cursor performance with atomic John Keeping
2016-01-19 10:46 ` John Keeping
2016-01-19 10:46 ` John Keeping
2016-01-19 10:46 ` [PATCH v2 1/3] drm/atomic-helper: Export framebuffer_changed() John Keeping
2016-01-19 10:46 ` John Keeping
2016-01-19 10:46 ` John Keeping
2016-01-19 11:03 ` Daniel Vetter
2016-01-19 11:03 ` Daniel Vetter
2016-01-19 11:03 ` Daniel Vetter
2016-01-19 10:46 ` [PATCH v2 2/3] drm/rockchip: don't wait for vblank if fb hasn't changed John Keeping
2016-01-19 10:46 ` John Keeping
2016-01-19 10:46 ` John Keeping
2016-01-19 10:47 ` [PATCH v2 3/3] drm/rockchip: explain why we can't wait_for_vblanks John Keeping
2016-01-19 10:47 ` John Keeping
2016-01-19 10:47 ` John Keeping
2016-01-21 0:51 ` [PATCH v2 0/3] drm/rockchip: fix cursor performance with atomic Mark yao
2016-01-21 0:51 ` Mark yao
2016-01-21 0:51 ` Mark yao
2016-01-17 15:21 ` [RFC/PATCH] drm/rockchip: don't wait for vblank if fb hasn't changed Heiko Stuebner
2016-01-17 15:21 ` Heiko Stuebner
2016-01-17 15:21 ` Heiko Stuebner
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=cover.1452782114.git.john@metanate.com \
--to=john@metanate.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.