summaryrefslogtreecommitdiff
path: root/services/surfaceflinger/Layer.cpp
diff options
context:
space:
mode:
author Leon Scroggins III <scroggo@google.com> 2023-03-02 14:21:44 -0500
committer Leon Scroggins III <scroggo@google.com> 2023-03-03 10:38:06 -0500
commit1af0fb6ed00132a4f9c8f45eae420a7f552cd37a (patch)
tree57fb3288c30b7ff61166444f45e7786ba9b48e73 /services/surfaceflinger/Layer.cpp
parent5b6ca88e1444ebba97db26a226c9b3a8f169062b (diff)
Rename "leader" display to "pacesetter"
"Leader" became ambiguous once we began to consider that there are two orthogonal concepts that "leader" seems to imply: - The display with the highest refresh rate (originally called "leader") - The display that is refreshed first in a given update (assuming it's being updated) To better distinguish between the two, we've come up with new names: - pacesetter - front runner (for the second concept) Change uses of "leader" to "pacesetter" throughout SF and Scheduler. Bug: 255635821 Bug: 256196556 Test: m Change-Id: Ia02c35dd442d310695f1ce873fbaf30910c12419
Diffstat (limited to 'services/surfaceflinger/Layer.cpp')
-rw-r--r--services/surfaceflinger/Layer.cpp3
1 files changed, 2 insertions, 1 deletions
diff --git a/services/surfaceflinger/Layer.cpp b/services/surfaceflinger/Layer.cpp
index 9d5c835f80..96d8e2155d 100644
--- a/services/surfaceflinger/Layer.cpp
+++ b/services/surfaceflinger/Layer.cpp
@@ -196,7 +196,8 @@ Layer::Layer(const LayerCreationArgs& args)
mDrawingState.color.b = -1.0_hf;
}
- mFrameTracker.setDisplayRefreshPeriod(args.flinger->mScheduler->getLeaderVsyncPeriod().ns());
+ mFrameTracker.setDisplayRefreshPeriod(
+ args.flinger->mScheduler->getPacesetterVsyncPeriod().ns());
mOwnerUid = args.ownerUid;
mOwnerPid = args.ownerPid;