From: Thomas Zimmermann <tzimmermann@suse.de>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: Rob Clark <robdclark@chromium.org>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
freedreno@lists.freedesktop.org, Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH v3 1/2] drm: Add DRM_GEM_FOPS
Date: Wed, 15 Jun 2022 15:46:33 +0200 [thread overview]
Message-ID: <d2a0c8e3-4987-44e9-4abe-99c571738836@suse.de> (raw)
In-Reply-To: <5066e977-52b5-ce18-98e9-44dcfe018127@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 2872 bytes --]
Am 15.06.22 um 14:45 schrieb Dmitry Baryshkov:
> On 09/06/2022 20:42, Rob Clark wrote:
>> From: Rob Clark <robdclark@chromium.org>
>>
>> The DEFINE_DRM_GEM_FOPS() helper is a bit limiting if a driver wants to
>> provide additional file ops, like show_fdinfo().
>>
>> v2: Split out DRM_GEM_FOPS instead of making DEFINE_DRM_GEM_FOPS
>> varardic
>> v3: nits
>>
>> Signed-off-by: Rob Clark <robdclark@chromium.org>
>> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
>
> I suspect that with Tomas's ack we can pick this through the drm/msm. Is
> this correct? (I'll then pick it for the msm-lumag).
Sure, go ahead.
>
>> ---
>> include/drm/drm_gem.h | 26 ++++++++++++++++++--------
>> 1 file changed, 18 insertions(+), 8 deletions(-)
>>
>> diff --git a/include/drm/drm_gem.h b/include/drm/drm_gem.h
>> index 9d7c61a122dc..87cffc9efa85 100644
>> --- a/include/drm/drm_gem.h
>> +++ b/include/drm/drm_gem.h
>> @@ -314,6 +314,23 @@ struct drm_gem_object {
>> const struct drm_gem_object_funcs *funcs;
>> };
>> +/**
>> + * DRM_GEM_FOPS - Default drm GEM file operations
>> + *
>> + * This macro provides a shorthand for setting the GEM file ops in the
>> + * &file_operations structure. If all you need are the default ops, use
>> + * DEFINE_DRM_GEM_FOPS instead.
>> + */
>> +#define DRM_GEM_FOPS \
>> + .open = drm_open,\
>> + .release = drm_release,\
>> + .unlocked_ioctl = drm_ioctl,\
>> + .compat_ioctl = drm_compat_ioctl,\
>> + .poll = drm_poll,\
>> + .read = drm_read,\
>> + .llseek = noop_llseek,\
>> + .mmap = drm_gem_mmap
>> +
>> /**
>> * DEFINE_DRM_GEM_FOPS() - macro to generate file operations for GEM
>> drivers
>> * @name: name for the generated structure
>> @@ -330,14 +347,7 @@ struct drm_gem_object {
>> #define DEFINE_DRM_GEM_FOPS(name) \
>> static const struct file_operations name = {\
>> .owner = THIS_MODULE,\
>> - .open = drm_open,\
>> - .release = drm_release,\
>> - .unlocked_ioctl = drm_ioctl,\
>> - .compat_ioctl = drm_compat_ioctl,\
>> - .poll = drm_poll,\
>> - .read = drm_read,\
>> - .llseek = noop_llseek,\
>> - .mmap = drm_gem_mmap,\
>> + DRM_GEM_FOPS,\
>> }
>> void drm_gem_object_release(struct drm_gem_object *obj);
>
>
--
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 --]
next prev parent reply other threads:[~2022-06-15 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 17:42 [PATCH v3 1/2] drm: Add DRM_GEM_FOPS Rob Clark
2022-06-09 17:42 ` [PATCH v3 2/2] drm/msm: Expose client engine utilization via fdinfo Rob Clark
2022-06-15 12:44 ` Dmitry Baryshkov
2022-06-15 12:52 ` Tvrtko Ursulin
2022-06-15 12:45 ` [PATCH v3 1/2] drm: Add DRM_GEM_FOPS Dmitry Baryshkov
2022-06-15 13:46 ` Thomas Zimmermann [this message]
2022-06-24 20:48 ` Daniel Vetter
2022-06-25 3:32 ` Rob Clark
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=d2a0c8e3-4987-44e9-4abe-99c571738836@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=cphealy@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=tvrtko.ursulin@linux.intel.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