replicant-frameworks_native/services/surfaceflinger
Manoj Kumar AVM e04e4edcd1 sf: Fix incorrect state reporting in dumpsys
Dumpsys utility accesses layer compositionType variable
with out proper protection. These variables are modified
during hwc_prepare call. Existing HAL lock protection is not
sufficient to address this issue. Failure to do this will
result in incorrect state reporting in dumpsys.

A new displayLock mutex in HWComposer will be used in both
dumpsys and draw calls to ensure correct state is accessed.

Change-Id: I8a57de59525adc0e089b3bed95c067c01e42b666
(cherry picked from commit e54506b81a)
2015-06-12 09:48:07 -07:00
..
DisplayHardware sf: Fix incorrect state reporting in dumpsys 2015-06-12 09:48:07 -07:00
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