ozone: Disable primary plane when HDC gets disabled
When HardwareDisplayController get disabled we should disable all planes, including the primary, by setting the fb to 0. Not doing so can have privacy implications, where we might end up reading back the last fb when modesetting again and show to the user contents that should not be seen. In the past, when legacy modesetting was used, the fb associated with the crtc was set to 0 when calling drmModeSetCrtc. After that we'd disable the other planes but the primary. Since we moved to the atomic API for modesetting, we now need to explicitly set to 0 the fb of the primary plane along the other planes. Bug: 1102859 Test: Close/open the lid on krane, no old contents are visible. Change-Id: Ib93347b59cc847898c0713f81ad0903773699b07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412974 Commit-Queue: Daniele Castagna <dcastagna@chromium.org> Reviewed-by:Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Gil Dekel <gildekel@chromium.org> Cr-Commit-Position: refs/heads/master@{#807476}
Showing
Please register or sign in to comment