Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f5fe85cb authored by Alec Mouri's avatar Alec Mouri
Browse files

Report DispSync model updates in the correct place. 

Otherwise, metrics sometimes aren't updated in the right spot.

Also, add the reference time to detailed trace info, as it's important
for event calculation.

Bug: 124383894
Test: systrace
Change-Id: I4ad834fc2076600116831e0f6c38c6ee8f178c11
parent 77b510f1

services/surfaceflinger/Scheduler/DispSync.cpp

+5 −5
Original line number Diff line number Diff line
@@ -78,6 +78,11 @@ public: 
        mPeriod = period;

        mPhase = phase;

        mReferenceTime = referenceTime;

        if (mTraceDetailedInfo) {

            ATRACE_INT64("DispSync:Period", mPeriod);

            ATRACE_INT64("DispSync:Phase", mPhase + mPeriod / 2);

            ATRACE_INT64("DispSync:Reference Time", mReferenceTime);

        }

        ALOGV("[%s] updateModel: mPeriod = %" PRId64 ", mPhase = %" PRId64

              " mReferenceTime = %" PRId64,

              mName, ns2us(mPeriod), ns2us(mPhase), ns2us(mReferenceTime));
@@ -580,11 +585,6 @@ void DispSync::updateModelLocked() { 
            ALOGV("[%s] Adjusting mPhase -> %" PRId64, mName, ns2us(mPhase));

        }



        if (mTraceDetailedInfo) {

            ATRACE_INT64("DispSync:Period", mPeriod);

            ATRACE_INT64("DispSync:Phase", mPhase + mPeriod / 2);

        }



        // Artificially inflate the period if requested.

        mPeriod += mPeriod * mRefreshSkipCount;