Mathias Agopian 0dfb7b73a4 mDirtyRegion is single threaded, but could be accessed from a hwc thread ... We now have mInvalidateRegion which holds the region to invalidate, it can be set from any thread as long as mInvalidateLock is held. We use fine-grained locking here because mInvalidateRegion can be set from anywhere, in particular frmo HWC callbacks. Bug: 5466774 Change-Id: Iafca20aa3f5b25a87755e65bde7b769aa8f997bc		2011-10-21 15:41:01 -07:00
..
DisplayHardware
tests
Android.mk	Add a LayerScreenshot	2011-10-18 20:21:47 -07:00
Barrier.h
clz.cpp
clz.h
DdmConnection.cpp
DdmConnection.h
GLExtensions.cpp
GLExtensions.h
Layer.cpp	Add a LayerScreenshot	2011-10-18 20:21:47 -07:00
Layer.h
LayerBase.cpp
LayerBase.h
LayerDim.cpp
LayerDim.h
LayerScreenshot.cpp	Add a LayerScreenshot	2011-10-18 20:21:47 -07:00
LayerScreenshot.h	Add a LayerScreenshot	2011-10-18 20:21:47 -07:00
MessageQueue.cpp
MessageQueue.h
MODULE_LICENSE_APACHE2
SurfaceFlinger.cpp	mDirtyRegion is single threaded, but could be accessed from a hwc thread	2011-10-21 15:41:01 -07:00
SurfaceFlinger.h	mDirtyRegion is single threaded, but could be accessed from a hwc thread	2011-10-21 15:41:01 -07:00
SurfaceTextureLayer.cpp
SurfaceTextureLayer.h
Transform.cpp
Transform.h