Change buffer invalidataion FMQ to unsync
Buffer Invalidation FMQ is designed as a shared FMQ between clients in
order to minimize memory consumption. In that case, regarding FMQ is
unsync FMQ in order to not to block writer in any situation.
Bug: 112203066
Change-Id: I58989ccd332ba790193007f43dd66ecbd617f484
diff --git a/media/bufferpool/2.0/IAccessor.hal b/media/bufferpool/2.0/IAccessor.hal
index bd70945..ab7c02d 100644
--- a/media/bufferpool/2.0/IAccessor.hal
+++ b/media/bufferpool/2.0/IAccessor.hal
@@ -68,5 +68,5 @@
generates (ResultStatus status, IConnection connection,
int64_t connectionId,
fmq_sync<BufferStatusMessage> toFmqDesc,
- fmq_sync<BufferInvalidationMessage> fromFmqDesc);
+ fmq_unsync<BufferInvalidationMessage> fromFmqDesc);
};
diff --git a/media/bufferpool/2.0/types.hal b/media/bufferpool/2.0/types.hal
index 7ce53b1..456e4aa 100644
--- a/media/bufferpool/2.0/types.hal
+++ b/media/bufferpool/2.0/types.hal
@@ -100,7 +100,7 @@
struct BufferInvalidationMessage {
/**
* Buffers from fromBufferId to toBufferId must be invalidated.
- * Both of fromBufferId and toBufferId are inclusive.
+ * fromBufferId is inclusive, but toBufferId is not inclusive.
* If fromBufferId > toBufferID, wrap happens. In that case
* the wrap is based on UINT32_MAX.
*/