From: Mark yao <mark.yao@rock-chips.com>
To: John Keeping <john@metanate.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: Re: [PATCH v2 0/3] drm/rockchip: fix cursor performance with atomic
Date: Thu, 21 Jan 2016 08:51:58 +0800 [thread overview]
Message-ID: <56A02BAE.1050009@rock-chips.com> (raw)
In-Reply-To: <cover.1453200263.git.john@metanate.com>
On 2016年01月19日 18:46, John Keeping wrote:
> The first two patches are unchanged since v1 but the comment in the
> third has been expanded following Thierry's comments.
>
> 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 | 23 +++++++++++++++++++++--
> include/drm/drm_atomic_helper.h | 4 ++++
> 3 files changed, 45 insertions(+), 6 deletions(-)
>
Hi John
Thanks for your fix, applied these three patches into my drm-next, :-)
--
Ｍark Yao
_______________________________________________
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: mark.yao@rock-chips.com (Mark yao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] drm/rockchip: fix cursor performance with atomic
Date: Thu, 21 Jan 2016 08:51:58 +0800 [thread overview]
Message-ID: <56A02BAE.1050009@rock-chips.com> (raw)
In-Reply-To: <cover.1453200263.git.john@metanate.com>
On 2016?01?19? 18:46, John Keeping wrote:
> The first two patches are unchanged since v1 but the comment in the
> third has been expanded following Thierry's comments.
>
> 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 | 23 +++++++++++++++++++++--
> include/drm/drm_atomic_helper.h | 4 ++++
> 3 files changed, 45 insertions(+), 6 deletions(-)
>
Hi John
Thanks for your fix, applied these three patches into my drm-next, :-)
--
?ark Yao
WARNING: multiple messages have this Message-ID (diff)
From: Mark yao <mark.yao@rock-chips.com>
To: John Keeping <john@metanate.com>
Cc: 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>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH v2 0/3] drm/rockchip: fix cursor performance with atomic
Date: Thu, 21 Jan 2016 08:51:58 +0800 [thread overview]
Message-ID: <56A02BAE.1050009@rock-chips.com> (raw)
In-Reply-To: <cover.1453200263.git.john@metanate.com>
On 2016年01月19日 18:46, John Keeping wrote:
> The first two patches are unchanged since v1 but the comment in the
> third has been expanded following Thierry's comments.
>
> 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 | 23 +++++++++++++++++++++--
> include/drm/drm_atomic_helper.h | 4 ++++
> 3 files changed, 45 insertions(+), 6 deletions(-)
>
Hi John
Thanks for your fix, applied these three patches into my drm-next, :-)
--
Ｍark Yao
next prev parent reply other threads:[~2016-01-21 0:51 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 ` [PATCH 0/3] drm/rockchip: fix cursor performance with atomic John Keeping
2016-01-14 14:39 ` 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 ` Mark yao [this message]
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-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=56A02BAE.1050009@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=john@metanate.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 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.