mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>
Subject: [PATCH v2 0/5] vc4 V3D fencing and msm/etnaviv cleanups
Date: Wed, 12 Apr 2017 12:11:57 -0700	[thread overview]
Message-ID: <20170412191202.22740-1-eric@anholt.net> (raw)

Since I got feedback that the dma_fence .release pattern I followed
was unnecessary, here's a resubmit with that changed and the two
drivers I was looking at cleaned up as well.  As before, they're only
compile-tested.

I'd prefer that if msm/etnaviv developers like them, they pull those
two patches themselves.

Eric Anholt (5):
  drm/msm: Expose our reservation object when exporting a dmabuf.
  drm/etnaviv: Expose our reservation object when exporting a dmabuf.
  drm/msm: Reuse dma_fence_release.
  drm/etnaviv: Reuse dma_fence_release.
  drm/vc4: Expose dma-buf fences for V3D rendering.

 drivers/gpu/drm/etnaviv/etnaviv_drv.c       |   1 +
 drivers/gpu/drm/etnaviv/etnaviv_drv.h       |   1 +
 drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c |   7 ++
 drivers/gpu/drm/etnaviv/etnaviv_gpu.c       |  11 +--
 drivers/gpu/drm/msm/msm_drv.c               |   1 +
 drivers/gpu/drm/msm/msm_drv.h               |   1 +
 drivers/gpu/drm/msm/msm_fence.c             |  10 +-
 drivers/gpu/drm/msm/msm_gem_prime.c         |   7 ++
 drivers/gpu/drm/vc4/Makefile                |   1 +
 drivers/gpu/drm/vc4/vc4_bo.c                |  37 +++++++-
 drivers/gpu/drm/vc4/vc4_drv.c               |   3 +-
 drivers/gpu/drm/vc4/vc4_drv.h               |  30 ++++++
 drivers/gpu/drm/vc4/vc4_fence.c             |  56 ++++++++++++
 drivers/gpu/drm/vc4/vc4_gem.c               | 136 +++++++++++++++++++++++++++-
 drivers/gpu/drm/vc4/vc4_irq.c               |   4 +
 15 files changed, 284 insertions(+), 22 deletions(-)
 create mode 100644 drivers/gpu/drm/vc4/vc4_fence.c

-- 
2.11.0

             reply	other threads:[~2017-04-12 19:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 19:11 Eric Anholt [this message]
2017-04-12 19:11 ` [PATCH v2 1/5] drm/msm: Expose our reservation object when exporting a dmabuf Eric Anholt
2017-05-02 10:20   ` Rob Clark
2017-04-12 19:11 ` [PATCH v2 2/5] drm/etnaviv: " Eric Anholt
2017-04-12 19:12 ` [PATCH v2 3/5] drm/msm: Reuse dma_fence_release Eric Anholt
2017-05-02 10:20   ` Rob Clark
2017-04-12 19:12 ` [PATCH v2 4/5] drm/etnaviv: " Eric Anholt
2017-04-13  7:00   ` Daniel Vetter
2017-05-03 10:19   ` Lucas Stach
2017-05-03 16:03     ` Eric Anholt
2017-04-12 19:12 ` [PATCH v2 5/5] drm/vc4: Expose dma-buf fences for V3D rendering Eric Anholt
2017-04-13  7:13   ` Daniel Vetter
2017-04-13 17:16     ` Eric Anholt
2017-04-13 18:01     ` Eric Anholt

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=20170412191202.22740-1-eric@anholt.net \
    --to=eric@anholt.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®