Commit f3f0e410 authored by Simon Ser's avatar Simon Ser

drm: document that blobs are ref'counted

User-space doesn't need to keep track of blobs that might be in use by
the kernel. User-space can just destroy blobs as soon as they don't need
them anymore.
Signed-off-by: default avatarSimon Ser <contact@emersion.fr>
Signed-off-by: default avatarDaniel Stone <daniel@fooishbar.org>
Reviewed-by: default avatarJonas Ådahl <jadahl@gmail.com>
Reviewed-by: default avatarPekka Paalanen <pekka.paalanen@collabora.com>
Reviewed-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/wgav99DTGfubfVPiurrydQEiyufYpxlJQZ0wJMWYBQ@cp7-web-042.plabs.ch
parent 24e146cd
...@@ -924,6 +924,12 @@ struct drm_mode_create_blob { ...@@ -924,6 +924,12 @@ struct drm_mode_create_blob {
* struct drm_mode_destroy_blob - Destroy user blob * struct drm_mode_destroy_blob - Destroy user blob
* @blob_id: blob_id to destroy * @blob_id: blob_id to destroy
* Destroy a user-created blob property. * Destroy a user-created blob property.
*
* User-space can release blobs as soon as they do not need to refer to them by
* their blob object ID. For instance, if you are using a MODE_ID blob in an
* atomic commit and you will not make another commit re-using the same ID, you
* can destroy the blob as soon as the commit has been issued, without waiting
* for it to complete.
*/ */
struct drm_mode_destroy_blob { struct drm_mode_destroy_blob {
__u32 blob_id; __u32 blob_id;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment