From 0c1a059f01307e9ca6fff963dd4c0d28627d35cf Mon Sep 17 00:00:00 2001 From: John Reck Date: Tue, 10 Jan 2023 11:25:56 -0500 Subject: [PATCH] Clarify format BLOB locking Bug: 162571907 Test: n/a doc only change Change-Id: I3ab26cee8a790067447781e13062c62fc3b7c01c --- .../include/android/hardware/graphics/mapper/IMapper.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/graphics/mapper/stable-c/include/android/hardware/graphics/mapper/IMapper.h b/graphics/mapper/stable-c/include/android/hardware/graphics/mapper/IMapper.h index 0f6d146fb8..0de88cd4c6 100644 --- a/graphics/mapper/stable-c/include/android/hardware/graphics/mapper/IMapper.h +++ b/graphics/mapper/stable-c/include/android/hardware/graphics/mapper/IMapper.h @@ -241,7 +241,9 @@ typedef struct AIMapperV5 { * acceptable. * * 1D buffers (width = size in bytes, height = 1, pixel_format = BLOB) must - * "lock in place". The buffers must be directly accessible via mapping. + * "lock in place" and behave similar to shared memory. That is, multiple threads or processes + * may lock the buffer for reading & writing and the results must follow the device's memory + * model. * * The client must not modify the content of the buffer outside of * @p accessRegion, and the device need not guarantee that content outside