From: Joonyoung Shim <jy0922.shim@samsung.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [PATCH v2 0/3] drm/cma: use prime helpers instead GEM CMA specific dma_buf functionality
Date: Fri, 28 Jun 2013 14:24:43 +0900 [thread overview]
Message-ID: <51CD1E1B.2020403@samsung.com> (raw)
Hello,
This is the second version patchset.
GEM CMA supports dma_buf but it needs GEM CMA specific functionality for
dma_buf. We can use prime helpers for dma_buf by commit
89177644a7b6306e6084a89eab7e290f4bfef397 "drm: add prime helpers", so
this patchset is to replace from using GEM CMA specific functions to
using prime helpers.
To Laurent,
It is merged a patch to cache mapping from DRM Prime, can this patchset
get your ack?
Changes from v1:
- rebased from drm-next branch of
git://people.freedesktop.org/~airlied/linux
- fix to check whether gem_prime_mmap field is NULL
from "drm: add mmap function to prime helpers" commit
Joonyoung Shim (3):
drm: add mmap function to prime helpers
drm/cma: add low-level hook functions to use prime helpers
drm/cma: remove GEM CMA specific dma_buf functionality
drivers/gpu/drm/drm_gem_cma_helper.c | 293
+++++------------------------------
drivers/gpu/drm/drm_prime.c | 8 +-
include/drm/drmP.h | 2 +
include/drm/drm_gem_cma_helper.h | 13 +-
4 files changed, 60 insertions(+), 256 deletions(-)
next reply other threads:[~2013-06-28 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 5:24 Joonyoung Shim [this message]
2013-07-03 22:11 ` [PATCH v2 0/3] drm/cma: use prime helpers instead GEM CMA specific dma_buf functionality Laurent Pinchart
2013-07-04 7:14 ` Joonyoung Shim
2013-07-05 5:38 ` Dave Airlie
2013-07-05 6:30 ` Joonyoung Shim
2013-07-05 13:03 ` Laurent Pinchart
2013-07-08 9:14 ` Joonyoung Shim
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=51CD1E1B.2020403@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox