template <>class WireWeakOnewayClientImpl
Defined at line 1109 of file fidling/gen/sdk/fidl/fuchsia.images/fuchsia.images/cpp/fidl/fuchsia.images/cpp/wire_messaging.h
Public Methods
::fidl::OneWayStatus AddBufferCollection2 (uint32_t buffer_collection_id, ::fidl::ClientEnd< ::fuchsia_sysmem2::BufferCollectionToken> && buffer_collection_token)Adds a BufferCollection resource to the image pipe.
The producer is expected to set constraints on this resource for images added
via `AddImage()`. The consumer can set its constraints on
`buffer_collection_token` before or after. Note that the buffers won't be
allocated until all BufferCollectionToken instances are used to set
constraints, on both the producer and consumer side. See collection.fidl for
details.
The following errors will cause the connection to be closed:
- `buffer_collection_id` is already registered
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::OneWayStatus AddBufferCollection (uint32_t buffer_collection_id, ::fidl::ClientEnd< ::fuchsia_sysmem::BufferCollectionToken> && buffer_collection_token)Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::OneWayStatus AddImage (uint32_t image_id, uint32_t buffer_collection_id, uint32_t buffer_collection_index, const ::fuchsia_sysmem::wire::ImageFormat2 & image_format)Adds an image resource to image pipe.
`buffer_collection_id` refers to the BufferCollectionToken instance that is
registered via `AddBufferCollection()`. The underlying memory objects allocated
are used to address to the image data. `buffer_collection_index` refers to the
index of the memory object allocated in BufferCollection.
`image_format` specifiies image properties. `coded_width` and `coded_height` are
used to set image dimensions.
It is valid to create multiple images backed by the same memory object; they
may even overlap. Consumers must detect this and handle it accordingly.
The following errors will cause the connection to be closed:
- `image_id` is already registered
- `buffer_collection_id` refers to an unregistered BufferCollection.
- `buffer_collection_index` points to a resource index out of the initialized
BufferCollection bounds
- No resource is allocated in the registered BufferCollection.
Allocates 104 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::OneWayStatus RemoveBufferCollection (uint32_t buffer_collection_id)Removes a BufferCollection resource from the pipe.
The `buffer_collection_id` resource is detached as well as all Images that are
associated with that BufferCollection. Leads to the same results as calling
`RemoveImage()` on all Images for `buffer_collection_id`.
The producer must wait for all release fences associated with the Images to
be signaled before freeing or modifying the underlying memory object since
the image may still be in use in the presentation queue.
The following errors will cause the connection to be closed:
- `buffer_collection_id` does not reference a currently registered BufferCollection
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::OneWayStatus RemoveImage (uint32_t image_id)Removes an image resource from the pipe.
The `image_id` is detached from the image resource and is free to be
reused to add a new image resource.
Removing an image from the image pipe does not affect the presentation
queue or the currently presented image.
The producer must wait for all release fences associated with the image to
be signaled before freeing or modifying the underlying memory object since
the image may still be in use in the presentation queue.
The following errors will cause the connection to be closed:
- `image_id` does not reference a currently registered image resource
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.