diff options
author | Peiyong Lin <lpy@google.com> | 2023-01-18 23:28:46 +0000 |
---|---|---|
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2023-01-18 23:28:46 +0000 |
commit | 96d426fbfb45f7620e71a2fa97a6f17cebe1b218 (patch) | |
tree | 5774f19674c26cdb9043978797907d32e01cdbae | |
parent | c150630e839316f9bda6268c88102f7aa26165c1 (diff) | |
parent | 431cb0b74b224cfea8fc51a614fdc7894857aa34 (diff) | |
download | native-96d426fbfb45f7620e71a2fa97a6f17cebe1b218.tar.gz |
Merge "Expose FRONT_BUFFER usage flags"
-rw-r--r-- | libs/nativewindow/include/android/hardware_buffer.h | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/libs/nativewindow/include/android/hardware_buffer.h b/libs/nativewindow/include/android/hardware_buffer.h index b2e8beac43..85a524988d 100644 --- a/libs/nativewindow/include/android/hardware_buffer.h +++ b/libs/nativewindow/include/android/hardware_buffer.h @@ -311,6 +311,16 @@ enum AHardwareBuffer_UsageFlags { */ AHARDWAREBUFFER_USAGE_GPU_MIPMAP_COMPLETE = 1UL << 26, + /** + * Usage: The buffer is used for front-buffer rendering. When + * front-buffering rendering is specified, different usages may adjust their + * behavior as a result. For example, when used as GPU_COLOR_OUTPUT the buffer + * will behave similar to a single-buffered window. When used with + * COMPOSER_OVERLAY, the system will try to prioritize the buffer receiving + * an overlay plane & avoid caching it in intermediate composition buffers. + */ + AHARDWAREBUFFER_USAGE_FRONT_BUFFER = 1UL << 32, + AHARDWAREBUFFER_USAGE_VENDOR_0 = 1ULL << 28, AHARDWAREBUFFER_USAGE_VENDOR_1 = 1ULL << 29, AHARDWAREBUFFER_USAGE_VENDOR_2 = 1ULL << 30, |