summaryrefslogtreecommitdiffstats
path: root/skia
diff options
context:
space:
mode:
authorkalyan.kondapally <kalyan.kondapally@intel.com>2015-08-19 10:28:56 -0700
committerCommit bot <commit-bot@chromium.org>2015-08-19 17:29:24 +0000
commit8e36b241b80f875cf72b90798b65a106a76ace75 (patch)
treec5d0cedea25fee400f31d40b5f3f44226721d5d8 /skia
parentf5c7b1a39088d8b2f78132b5488319d986abd16a (diff)
downloadchromium_src-8e36b241b80f875cf72b90798b65a106a76ace75.zip
chromium_src-8e36b241b80f875cf72b90798b65a106a76ace75.tar.gz
chromium_src-8e36b241b80f875cf72b90798b65a106a76ace75.tar.bz2
Ozone: HDC should only keep track of planes owned by it’s crtc controllers
Hardware Display Controller keeps track of planes owned by crtc controller, even after it’s removed. This can result in unbinding the frame buffer of primary plane for that controller in subsequent page flip call. After this any page flip requests for that crtc controller will fail with error EBUSY(Tested 3.18 + kernel), assuming that user space is still handling some hot plug events. I encountered this when connected to an external display and changing between extended/mirrored mode. Frame buffer associated with primary plane of the extended display was Zero and Kernel started reporting EBUSY. Now we make sure that Hardware Display Controller only keeps track of the planes owned by its controllers. Review URL: https://codereview.chromium.org/1279703004 Cr-Commit-Position: refs/heads/master@{#344261}
Diffstat (limited to 'skia')
0 files changed, 0 insertions, 0 deletions