From: Thomas Zimmermann <tzimmermann@suse.de>
To: daniel@ffwll.ch, airlied@linux.ie,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
inki.dae@samsung.com, jy0922.shim@samsung.com,
sw0312.kim@samsung.com, kyungmin.park@samsung.com,
krzysztof.kozlowski@canonical.com,
oleksandr_andrushchenko@epam.com
Cc: dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
xen-devel@lists.xenproject.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [RESEND PATCH 0/3] drm/{exynos,xen}: Implement gem_prime_mmap with drm_gem_prime_mmap()
Date: Mon, 8 Nov 2021 11:28:43 +0100 [thread overview]
Message-ID: <20211108102846.309-1-tzimmermann@suse.de> (raw)
(Resending the patchset from [1]. Most drivers have already been updated and
only two drivers are left.)
Replace all remaining implementations of struct drm_driver.gem_prime_mmap
with use drm_gem_prime_mmap(). For each affected driver, put the mmap code
into struct drm_gem_object_funcs.mmap. With the latter change in place,
create struct file_operations via DEFINE_DRM_GEM_FOPS().
As next steps, drivers can be converted to use drm_gem_prime_mmap() and
drm_gem_mmap() (e.g., Tegra). The default mmap code in drm_gem_prime_mmap()
can be pushed into affected drivers or a helper function. The gem_prime_mmap
hook can probably be removed at some point.
[1] https://lore.kernel.org/dri-devel/20210609112012.10019-1-tzimmermann@suse.de/
Thomas Zimmermann (3):
drm/exynox: Implement mmap as GEM object function
drm/xen: Implement mmap as GEM object function
drm: Update documentation and TODO of gem_prime_mmap hook
Documentation/gpu/todo.rst | 11 ---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 13 +--
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 20 +---
drivers/gpu/drm/exynos/exynos_drm_gem.c | 43 ++-------
drivers/gpu/drm/exynos/exynos_drm_gem.h | 5 -
drivers/gpu/drm/xen/xen_drm_front.c | 16 +---
drivers/gpu/drm/xen/xen_drm_front_gem.c | 108 +++++++++-------------
drivers/gpu/drm/xen/xen_drm_front_gem.h | 7 --
include/drm/drm_drv.h | 11 ++-
9 files changed, 64 insertions(+), 170 deletions(-)
base-commit: 215295e7b0a3deb2015c6d6b343b319e4f6d9a1d
prerequisite-patch-id: c2b2f08f0eccc9f5df0c0da49fa1d36267deb11d
prerequisite-patch-id: c67e5d886a47b7d0266d81100837557fda34cb24
--
2.33.1
next reply other threads:[~2021-11-08 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 10:28 Thomas Zimmermann [this message]
2021-11-08 10:28 ` [PATCH 1/3] drm/exynox: Implement mmap as GEM object function Thomas Zimmermann
2021-11-08 15:29 ` Daniel Vetter
2021-11-09 9:34 ` Inki Dae
2021-11-09 9:44 ` Thomas Zimmermann
2021-11-09 5:08 ` Inki Dae
2021-11-08 10:28 ` [PATCH 2/3] drm/xen: " Thomas Zimmermann
2021-11-08 10:46 ` Oleksandr Andrushchenko
2021-11-08 11:32 ` Thomas Zimmermann
2021-11-08 10:28 ` [PATCH 3/3] drm: Update documentation and TODO of gem_prime_mmap hook Thomas Zimmermann
2021-11-10 10:46 ` Daniel Vetter
2021-11-10 12:56 ` 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=20211108102846.309-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=sw0312.kim@samsung.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).