From: Thomas Zimmermann <tzimmermann@suse.de>
To: daniel@ffwll.ch, kraxel@redhat.com, sam@ravnborg.org,
airlied@redhat.com, yc_chen@aspeedtech.com,
Christian.Koenig@amd.com
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/3] Provide vmap/vunmap for VRAM helpers
Date: Wed, 24 Jul 2019 13:30:17 +0200 [thread overview]
Message-ID: <20190724113020.3752-1-tzimmermann@suse.de> (raw)
The vmap operation is pin+kmap, as already implemented for PRIME
support. The vunmap operation is the inverse. This patch set makes
both available for drivers that use VRAM helpers, and replaces the
respective code in ast and mgag200.
Thomas Zimmermann (3):
drm/vram: Provide vmap and vunmap operations for GEM VRAM objects
drm/ast: Use drm_gem_vram_{vmap,vunmap}() to map cursor source BO
drm/mgag200: Use drm_gem_vram_{vmap,vunmap}() to map cursor source BO
drivers/gpu/drm/ast/ast_mode.c | 21 +++------
drivers/gpu/drm/drm_gem_vram_helper.c | 55 +++++++++++++++++++-----
drivers/gpu/drm/mgag200/mgag200_cursor.c | 22 +++-------
include/drm/drm_gem_vram_helper.h | 12 ++++++
4 files changed, 71 insertions(+), 39 deletions(-)
--
2.22.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-07-24 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 11:30 Thomas Zimmermann [this message]
2019-07-24 11:30 ` [PATCH 1/3] drm/vram: Provide vmap and vunmap operations for GEM VRAM objects Thomas Zimmermann
2019-07-24 12:00 ` Daniel Vetter
2019-07-24 16:55 ` Thomas Zimmermann
2019-07-24 11:30 ` [PATCH 2/3] drm/ast: Use drm_gem_vram_{vmap, vunmap}() to map cursor source BO Thomas Zimmermann
2019-07-24 11:30 ` [PATCH 3/3] drm/mgag200: " Thomas Zimmermann
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=20190724113020.3752-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=Christian.Koenig@amd.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=sam@ravnborg.org \
--cc=yc_chen@aspeedtech.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