095da6fb73efa1cebf8f04466cd6e4b40210db0b |
|
25-Jul-2016 |
Greg Hackmann <ghackmann@google.com> |
libadf: support ADF_{POST,SIMPLE_POST}_CONFIG_V2 ioctls adf_{device,interface_simple}_post_v2 let the client choose what kind of fence is returned from the kernel: * ADF_COMPLETE_FENCE_NONE: no fence is returned * ADF_COMPLETE_FENCE_PRESENT: the returned fence fires when the specified configuration appears on the screen * ADF_COMPLETE_FENCE_RELEASE: the returned fence fires when the specified configuration is removed from the screen The "V2" calls with fence type ADF_COMPLETE_FENCE_RELEASE are functionally equivalent to "V1" calls. Test: included gtest (on Nexus 9) Change-Id: I36190d1b6cea0fbaed2af3ad64fa4729200c5520 Signed-off-by: Greg Hackmann <ghackmann@google.com>
/system/core/adf/libadf/include/video/adf.h
|
fe79bcbef818924bc296da98224ac3df4ef45adc |
|
27-Jan-2017 |
Greg Hackmann <ghackmann@google.com> |
libadf: move ADF uapi header out of bionic ADF isn't a candidate for upstreaming and isn't (directly) usable from unprivileged NDK code, so it makes more sense to keep video/adf.h as a private header inside libadf, where it'll still be usable by HWC implementations without shipping in the NDK. libadf exports its entire include/ directory, so this shouldn't have any impact on HWC implementations that already link against libadf. Test: mmm system/core/adf/libadf Test: /data/nativetest64/adf-unit-tests/adf-unit-tests (on Nexus 9) Change-Id: I14532d59005196e002f7465474ac3c7cc9e59bd3 Signed-off-by: Greg Hackmann <ghackmann@google.com>
/system/core/adf/libadf/include/video/adf.h
|