From: Simon Ser <contact@emersion.fr>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: mripard@kernel.org, linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm: Enable PRIME import/export for all drivers
Date: Thu, 15 Jun 2023 14:47:33 +0000 [thread overview]
Message-ID: <-Zu2xcAP6KgnhQVsOLkYcnIH7KhL5Tancp7W66ZA-tToQbsE_4bbcB8oIGO1RIHhIDcGTXyAHX-aPuANlbN1FH50uAxXL1VlNFHwSXO2s_M=@emersion.fr> (raw)
In-Reply-To: <20230615094206.4424-2-tzimmermann@suse.de>
On Thursday, June 15th, 2023 at 11:31, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
> index 89e2706cac561..10af1899236a0 100644
> --- a/include/drm/drm_drv.h
> +++ b/include/drm/drm_drv.h
> @@ -309,6 +309,9 @@ struct drm_driver {
> *
> * For an in-depth discussion see :ref:`PRIME buffer sharing
> * documentation <prime_buffer_sharing>`.
> + *
> + * TODO: Convert remaining drivers to drm_gem_prime_handle_to_fd()
> + * and remove this callback.
> */
The docs right above still state: "Should be implemented with
drm_gem_prime_handle_to_fd() for GEM based drivers". Maybe we can replace that
and state that leaving this NULL will use a default implementation?
> int (*prime_handle_to_fd)(struct drm_device *dev, struct drm_file *file_priv,
> uint32_t handle, uint32_t flags, int *prime_fd);
> @@ -320,6 +323,9 @@ struct drm_driver {
> *
> * For an in-depth discussion see :ref:`PRIME buffer sharing
> * documentation <prime_buffer_sharing>`.
> + *
> + * TODO: Convert remaining drivers to drm_gem_prime_fd_to_handle()
> + * and remove this callback.
> */
Ditto.
> int (*prime_fd_to_handle)(struct drm_device *dev, struct drm_file *file_priv,
> int prime_fd, uint32_t *handle);
> --
> 2.41.0
next prev parent reply other threads:[~2023-06-15 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 9:31 [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers Thomas Zimmermann
2023-06-15 9:31 ` [PATCH 1/3] drm: Enable PRIME import/export " Thomas Zimmermann
2023-06-15 14:47 ` Simon Ser [this message]
2023-06-15 9:31 ` [PATCH 2/3] drm: Clear fd/handle callbacks in struct drm_driver Thomas Zimmermann
2023-06-15 9:31 ` [PATCH 3/3] drm/prime: Unexport helpers for fd/handle conversion Thomas Zimmermann
2023-06-15 14:50 ` [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers Simon Ser
2023-06-15 14:56 ` Thomas Zimmermann
2023-06-16 3:59 ` Zack Rusin
2023-06-16 7:11 ` Thomas Zimmermann
2023-06-16 17:00 ` Jeffrey Hugo
2023-06-19 8:52 ` Thomas Zimmermann
2023-06-16 17:22 ` Alex Deucher
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='-Zu2xcAP6KgnhQVsOLkYcnIH7KhL5Tancp7W66ZA-tToQbsE_4bbcB8oIGO1RIHhIDcGTXyAHX-aPuANlbN1FH50uAxXL1VlNFHwSXO2s_M=@emersion.fr' \
--to=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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).