From 9580ff12b560e37b17be4fd9a3f1084415f8debc Mon Sep 17 00:00:00 2001 From: Rachel Lee Date: Tue, 26 Dec 2023 17:33:41 -0800 Subject: Support HIGH_INTERACTIVE category in native This is mainly to be used by toolkit to send the touch interaction to SF (in effort to handle touch signal in toolkit instead of SF). The HighInteractive category is similar to Heuristic layer type but will be considered in touch boost logic. Bug: 315071842 Test: atest libsurfaceflinger_unittest Test: atest CtsSurfaceControlTestsStaging Change-Id: I97a94fa970e165424757e4537468fbeda4226a72 --- libs/nativewindow/include/system/window.h | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'libs') diff --git a/libs/nativewindow/include/system/window.h b/libs/nativewindow/include/system/window.h index a98ea86073..969a5cff05 100644 --- a/libs/nativewindow/include/system/window.h +++ b/libs/nativewindow/include/system/window.h @@ -1094,11 +1094,20 @@ enum { */ ANATIVEWINDOW_FRAME_RATE_CATEGORY_NORMAL = 3, + /** + * Indicates that, as a result of a user interaction, an animation is likely to start. + * This category is a signal that a user interaction heuristic determined the need of a + * high refresh rate, and is not an explicit request from the app. + * As opposed to FRAME_RATE_CATEGORY_HIGH, this vote may be ignored in favor of + * more explicit votes. + */ + ANATIVEWINDOW_FRAME_RATE_CATEGORY_HIGH_HINT = 4, + /** * Indicates a frame rate suitable for animations that require a high frame rate, which may * increase smoothness but may also increase power usage. */ - ANATIVEWINDOW_FRAME_RATE_CATEGORY_HIGH = 4 + ANATIVEWINDOW_FRAME_RATE_CATEGORY_HIGH = 5 }; /* -- cgit v1.2.3-59-g8ed1b