Jesse Hall fcd15b478c surfaceflinger: use Mutex timedLock instead of tryLock loop ... Rather than trying to acquire the state lock without waiting three times at 1 second intervals in SurfaceFlinger::dump(), just try to acquire the lock once with a 1 second timeout. Avoids spurious mutex acquire failures that lead to flaky com.android.cts.jank.opengl.CtsHostJankOpenGl results. Bug: 18842510 Change-Id: I00ce6109647de2aef8831dd2f8fa98652ba7f4e0		2015-01-10 15:41:01 -08:00
..
DisplayHardware
Effects
EventLog
RenderEngine
tests
Android.mk
Barrier.h
Client.cpp
Client.h
clz.h
Colorizer.h
DdmConnection.cpp
DdmConnection.h
DisplayDevice.cpp
DisplayDevice.h
DispSync.cpp
DispSync.h
EventControlThread.cpp
EventControlThread.h
EventThread.cpp
EventThread.h
FrameTracker.cpp
FrameTracker.h
Layer.cpp
Layer.h
LayerDim.cpp
LayerDim.h
main_surfaceflinger.cpp
MessageQueue.cpp
MessageQueue.h
MODULE_LICENSE_APACHE2
MonitoredProducer.cpp
MonitoredProducer.h
SurfaceFlinger.cpp
SurfaceFlinger.h
SurfaceFlingerConsumer.cpp
SurfaceFlingerConsumer.h
Transform.cpp
Transform.h