From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Christian König" <christian.koenig@amd.com>,
asrivats@redhat.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, airlied@gmail.com, simona@ffwll.ch,
jean-christophe@guillain.net, superm1@kernel.org,
satadru@gmail.com, bp@alien8.de
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Bert Karwatzki <spasswolf@web.de>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3] drm/framebuffer: Acquire internal references on GEM handles
Date: Mon, 7 Jul 2025 15:33:32 +0200 [thread overview]
Message-ID: <4c1bc40d-6bd4-4102-b12f-fda320216e1d@suse.de> (raw)
In-Reply-To: <a3336964-1b72-421c-b4dc-2ac3f548430b@amd.com>
Hi
Am 07.07.25 um 15:21 schrieb Christian König:
>>
>> +#define DRM_FRAMEBUFFER_HAS_HANDLE_REF(_i) BIT(0u + (_i))
> Why the "0u + (_i)" here? An macro trick?
You mean why not just BIT(_i)? internal_flags could possibly contain
additional flags. Just using BIT(_i) would make it look as if it's only
for those handle refs.
Best regards
Thomas
>
> Regards,
> Christian.
>
>> +
>> /**
>> * struct drm_framebuffer - frame buffer object
>> *
>> @@ -188,6 +191,10 @@ struct drm_framebuffer {
>> * DRM_MODE_FB_MODIFIERS.
>> */
>> int flags;
>> + /**
>> + * @internal_flags: Framebuffer flags like DRM_FRAMEBUFFER_HAS_HANDLE_REF.
>> + */
>> + unsigned int internal_flags;
>> /**
>> * @filp_head: Placed on &drm_file.fbs, protected by &drm_file.fbs_lock.
>> */
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-07-07 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 13:11 Thomas Zimmermann
2025-07-07 13:21 ` Christian König
2025-07-07 13:33 ` Thomas Zimmermann [this message]
[not found] ` <CAFrh3J9uh0M5bWeS3cv_Cb1yFTKhE2+9mSk5hsZTzWW3uYKaWg@mail.gmail.com>
2025-07-08 7:38 ` Thomas Zimmermann
2025-07-08 14:44 ` Borislav Petkov
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=4c1bc40d-6bd4-4102-b12f-fda320216e1d@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=asrivats@redhat.com \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jean-christophe@guillain.net \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=satadru@gmail.com \
--cc=simona@ffwll.ch \
--cc=spasswolf@web.de \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=superm1@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
all inboxes | Powered by JetHome®