aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Ser <[email protected]>2020-11-04 17:01:40 +0000
committerSimon Ser <[email protected]>2020-11-05 11:55:42 +0100
commitf3f0e410c6a848c8f5b2715167eaa31c407cfb70 (patch)
tree284ca1725c7c5e682e011bf9c8aa96af6f1f256b
parent24e146cdf9f5a8fb464dd98ba8357d662d37d22f (diff)
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: Simon Ser <[email protected]> Signed-off-by: Daniel Stone <[email protected]> Reviewed-by: Jonas Ã…dahl <[email protected]> Reviewed-by: Pekka Paalanen <[email protected]> Reviewed-by: Daniel Vetter <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
-rw-r--r--include/uapi/drm/drm_mode.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h
index 863eda048265..5ad10ab2a577 100644
--- a/include/uapi/drm/drm_mode.h
+++ b/include/uapi/drm/drm_mode.h
@@ -924,6 +924,12 @@ struct drm_mode_create_blob {
* struct drm_mode_destroy_blob - Destroy user blob
* @blob_id: blob_id to destroy
* 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 {
__u32 blob_id;