From: Thomas Zimmermann <tzimmermann@suse.de>
To: daniel@ffwll.ch, airlied@linux.ie, mripard@kernel.org,
maarten.lankhorst@linux.intel.com,
laurent.pinchart@ideasonboard.com,
kieran.bingham+renesas@ideasonboard.com, emma@anholt.net
Cc: linux-renesas-soc@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/cma-helper: Clean up public interface
Date: Mon, 29 Nov 2021 10:51:31 +0100 [thread overview]
Message-ID: <9518975e-89c2-b863-e514-a8c68b6dbb03@suse.de> (raw)
In-Reply-To: <20211115120148.21766-1-tzimmermann@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1610 bytes --]
ping. Are there further comments on this patchset?
Am 15.11.21 um 13:01 schrieb Thomas Zimmermann:
> Convert GEM CMA functions to accept struct drm_gem_cma_object, provide
> small wrappers for GEM object callbacks and update all users. Brings
> up the interface to the pattern used in SHMEM and VRAM helpers.
>
> Converting all GEM object functions to use drm_gem_cma_object enables
> type checking by the C compiler. Previous callers could have passed any
> implementation of drm_gem_object to the GEM CMA helpers. It also
> removes upcasting in the GEM functions and simplifies the caller side.
> No functional changes.
>
> For GEM object callbacks, the CMA helper library now provides a
> number of small wrappers that do the necessary upcasting. Again no
> functional changes.
>
> Thomas Zimmermann (3):
> drm/cma-helper: Move driver and file ops to the end of header
> drm/cma-helper: Export dedicated wrappers for GEM object functions
> drm/cma-helper: Pass GEM CMA object in public interfaces
>
> drivers/gpu/drm/drm_gem_cma_helper.c | 73 +++++-----
> drivers/gpu/drm/rcar-du/rcar_du_kms.c | 10 +-
> drivers/gpu/drm/vc4/vc4_bo.c | 8 +-
> include/drm/drm_gem_cma_helper.h | 189 +++++++++++++++++++-------
> 4 files changed, 180 insertions(+), 100 deletions(-)
>
>
> base-commit: 9fccd12cfac1c863fa46d4d17c2d8ac25a44b190
> --
> 2.33.1
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2021-11-29 9:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 12:01 [PATCH 0/3] drm/cma-helper: Clean up public interface Thomas Zimmermann
2021-11-15 12:01 ` [PATCH 1/3] drm/cma-helper: Move driver and file ops to the end of header Thomas Zimmermann
2021-11-15 13:40 ` Laurent Pinchart
2021-11-16 8:59 ` Thomas Zimmermann
2021-11-29 9:58 ` Maxime Ripard
2021-11-15 12:01 ` [PATCH 2/3] drm/cma-helper: Export dedicated wrappers for GEM object functions Thomas Zimmermann
2021-11-29 9:56 ` Maxime Ripard
2021-11-15 12:01 ` [PATCH 3/3] drm/cma-helper: Pass GEM CMA object in public interfaces Thomas Zimmermann
2021-11-15 13:50 ` Laurent Pinchart
2021-11-16 9:04 ` Thomas Zimmermann
2021-11-29 9:57 ` Maxime Ripard
2021-11-29 9:51 ` Thomas Zimmermann [this message]
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=9518975e-89c2-b863-e514-a8c68b6dbb03@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@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