OSDN Git Service

drm_hwcomposer: Initialize timeline_next to 1
authorSean Paul <seanpaul@chromium.org>
Sun, 22 Feb 2015 22:55:43 +0000 (17:55 -0500)
committerSean Paul <seanpaul@google.com>
Mon, 23 Feb 2015 17:57:17 +0000 (17:57 +0000)
commite147a2a71f7c7f0b3cc925199fe68951cb311379
treef7ec237b7efe5811e75ba1d050bedc8332da4b4d
parenta99534ab0ddf258a46b7a680a6bc56b128c6ae48
drm_hwcomposer: Initialize timeline_next to 1

Initialize timeline_next to 1, because point 0 will be the very first
set operation. Since we increment every time set() is called,
initializing to 0 would cause an off-by-one error where
surfaceflinger would always composite on the front buffer.

Change-Id: I1e67c36864716595eb489286a7db3f1dcb04f67e
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://chrome-internal-review.googlesource.com/200735
Tested-by: Alexandre Courbot <acourbot@nvidia.com>
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Reviewed-by: Allen Martin <amartin@nvidia.com>
Reviewed-by: Sean Paul <seanpaul@google.com>
hwcomposer.cpp