Add graphite_renderengine_compile_only to SF flags
This will be used to guard compilation of Graphite in RenderEngine.
Enabling the flag will ONLY compile Graphite, but not enable it. The
debug.renderengine.graphite system property could then be set to true to
enable Graphite in RenderEngine.
The existing graphite_renderengine flag will both compile and enable
Graphite in RenderEngine.
Compilation is gated on a logical inclusive OR of the two flags.
Bug: b/293371537
Bug: b/331678326
Bug: b/341728634
Test: compiles
Change-Id: I4d6408b5e65b8b8862c79086dba2f4ce56a3d179
diff --git a/services/surfaceflinger/surfaceflinger_flags_new.aconfig b/services/surfaceflinger/surfaceflinger_flags_new.aconfig
index 0772891..ee12325 100644
--- a/services/surfaceflinger/surfaceflinger_flags_new.aconfig
+++ b/services/surfaceflinger/surfaceflinger_flags_new.aconfig
@@ -66,6 +66,14 @@
} # flush_buffer_slots_to_uncache
flag {
+ name: "force_compile_graphite_renderengine"
+ namespace: "core_graphics"
+ description: "Compile Skia's Graphite Vulkan backend in RenderEngine, but do NOT enable it, unless graphite_renderengine is also set. It can also be enabled with the debug.renderengine.graphite system property for testing. In contrast, the graphite_renderengine flag both compiles AND enables Graphite in RenderEngine."
+ bug: "293371537"
+ is_fixed_read_only: true
+} # force_compile_graphite_renderengine
+
+flag {
name: "frame_rate_category_mrr"
namespace: "core_graphics"
description: "Enable to use frame rate category and newer frame rate votes such as GTE in SurfaceFlinger scheduler, to guard dVRR changes from MRR devices"