From: Daniel Vetter <daniel@ffwll.ch>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/9] implicit fencing clarification
Date: Mon, 9 Apr 2018 10:44:05 +0200 [thread overview]
Message-ID: <20180409084405.GR31310@phenom.ffwll.local> (raw)
In-Reply-To: <4dd81c67-b2b9-8c18-5e32-b52101450f26@gmail.com>
On Fri, Apr 06, 2018 at 10:38:38AM +0300, Oleksandr Andrushchenko wrote:
> Hi, Daniel!
>
> It seems that this series misses xen-front's
> "Use simple_display_pipe prepare_fb helper" change?
Hm indeed, I guess I was on an older tree. Will follow up. Care to review
the other patches meanwhile?
-Daniel
>
> Thank you,
> Oleksandr
>
> On 04/05/2018 06:44 PM, Daniel Vetter wrote:
> > Hi all,
> >
> > Somewhat motivated (but only really tangentially) by the dirtyfb
> > discussion with Rob and Thomas I started digging around in the various
> > driver implementations for implicit vs. explicit fencing.
> >
> > There's definitely a huge pile of drivers which don't do any implicit
> > fencing at all - not sure that's good or not. And for some of the drivers
> > with more history I think they don't correctly overwrite implicit fencing
> > when explicit fencing is present. At least I've gotten lost in the mazes
> > before I found positive proof.
> >
> > So this is just the lower hanging stuff, plus a doc patch to hopefully
> > clarify this all better.
> >
> > Comments and review and especially in the case of the msm/vc4 patches,
> > also testing, very much welcome.
> >
> > Thanks, Daniel
> >
> > Daniel Vetter (9):
> > drm/vmwgfx: Remove no-op prepare/cleanup_fb callbacks
> > drm: Move simple_display_pipe prepare_fb helper into gem fb helpers
> > drm/tve200: Use simple_display_pipe prepare_fb helper
> > drm/pl111: Use simple_display_pipe prepare_fb helper
> > drm/mxsfb: Use simple_display_pipe prepare_fb helper
> > drm/atomic: better doc for implicit vs explicit fencing
> > drm/gem-fb-helper: Always do implicit sync
> > drm/vc4: Always obey implicit sync
> > drm/msm: Always obey implicit fencing
> >
> > drivers/gpu/drm/drm_atomic.c | 8 +++++++
> > drivers/gpu/drm/drm_gem_framebuffer_helper.c | 21 ++++++++++++++++-
> > drivers/gpu/drm/msm/msm_atomic.c | 2 +-
> > drivers/gpu/drm/mxsfb/mxsfb_drv.c | 8 +------
> > drivers/gpu/drm/pl111/pl111_display.c | 8 +------
> > drivers/gpu/drm/tinydrm/core/tinydrm-pipe.c | 17 --------------
> > drivers/gpu/drm/tinydrm/ili9225.c | 2 +-
> > drivers/gpu/drm/tinydrm/mi0283qt.c | 3 ++-
> > drivers/gpu/drm/tinydrm/repaper.c | 2 +-
> > drivers/gpu/drm/tinydrm/st7586.c | 2 +-
> > drivers/gpu/drm/tinydrm/st7735r.c | 2 +-
> > drivers/gpu/drm/tve200/tve200_display.c | 8 +------
> > drivers/gpu/drm/vc4/vc4_plane.c | 11 +++++----
> > drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 35 ----------------------------
> > include/drm/drm_gem_framebuffer_helper.h | 3 +++
> > include/drm/drm_modeset_helper_vtables.h | 5 +++-
> > include/drm/drm_plane.h | 7 +++++-
> > include/drm/drm_simple_kms_helper.h | 3 +++
> > include/drm/tinydrm/tinydrm.h | 2 --
> > 19 files changed, 61 insertions(+), 88 deletions(-)
> >
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-09 8:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 15:44 [PATCH 0/9] implicit fencing clarification Daniel Vetter
2018-04-05 15:44 ` [PATCH 1/9] drm/vmwgfx: Remove no-op prepare/cleanup_fb callbacks Daniel Vetter
2018-04-05 17:06 ` Thomas Hellstrom
2018-04-05 19:59 ` Daniel Vetter
2018-04-05 15:44 ` [PATCH 2/9] drm: Move simple_display_pipe prepare_fb helper into gem fb helpers Daniel Vetter
2018-04-06 9:42 ` Noralf Trønnes
2018-04-09 8:42 ` Daniel Vetter
2018-04-09 15:23 ` David Lechner
2018-04-10 5:55 ` Oleksandr Andrushchenko
2018-04-05 15:44 ` [PATCH 3/9] drm/tve200: Use simple_display_pipe prepare_fb helper Daniel Vetter
2018-04-06 9:40 ` Linus Walleij
2018-04-05 15:44 ` [PATCH 4/9] drm/pl111: " Daniel Vetter
2018-04-05 15:44 ` [PATCH 5/9] drm/mxsfb: " Daniel Vetter
2018-04-20 21:54 ` Eric Anholt
2018-04-05 15:44 ` [PATCH 6/9] drm/atomic: better doc for implicit vs explicit fencing Daniel Vetter
2018-04-20 22:04 ` Eric Anholt
2018-04-24 12:01 ` Daniel Vetter
2018-04-05 15:44 ` [PATCH 7/9] drm/gem-fb-helper: Always do implicit sync Daniel Vetter
2018-04-20 22:11 ` Eric Anholt
2018-04-24 12:04 ` Daniel Vetter
2018-06-20 12:46 ` Daniel Vetter
2018-04-05 15:44 ` [PATCH 8/9] drm/vc4: Always obey " Daniel Vetter
2018-04-20 22:12 ` Eric Anholt
[not found] ` <20180405154449.23038-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2018-04-05 15:44 ` [PATCH 9/9] drm/msm: Always obey implicit fencing Daniel Vetter
[not found] ` <20180405154449.23038-10-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2018-06-20 9:12 ` Daniel Vetter
2018-04-06 7:38 ` [PATCH 0/9] implicit fencing clarification Oleksandr Andrushchenko
2018-04-09 8:44 ` Daniel Vetter [this message]
2018-04-09 8:51 ` [PATCH] drm/xen-front: use simple display pipe prepare_fb helper Daniel Vetter
2018-04-10 5:56 ` Oleksandr Andrushchenko
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=20180409084405.GR31310@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=andr2000@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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