From 207867716a0f1e6415627f115cb3aea150d4c862 Mon Sep 17 00:00:00 2001 From: Shuzhen Wang Date: Thu, 25 May 2017 10:34:13 -0700 Subject: [PATCH] Camera: Silence log spam HAL is allowed to return captureResult from different thread contexts. Do not do ALOGW if this is the case. Test: Run camera and check logspam is gone Bug: 62068207 Change-Id: I86e77fc578953cefecf10ebc4d395edf33627e8c --- camera/device/3.2/default/CameraDeviceSession.cpp | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/camera/device/3.2/default/CameraDeviceSession.cpp b/camera/device/3.2/default/CameraDeviceSession.cpp index bad406f8cc..06a6bd01d6 100644 --- a/camera/device/3.2/default/CameraDeviceSession.cpp +++ b/camera/device/3.2/default/CameraDeviceSession.cpp @@ -588,8 +588,7 @@ void CameraDeviceSession::ResultBatcher::notify(NotifyMsg& msg) { void CameraDeviceSession::ResultBatcher::invokeProcessCaptureResultCallback( hidl_vec &results, bool tryWriteFmq) { if (mProcessCaptureResultLock.tryLock() != OK) { - ALOGW("%s: previous call is not finished! waiting 1s...", - __FUNCTION__); + ALOGV("%s: previous call is not finished! waiting 1s...", __FUNCTION__); if (mProcessCaptureResultLock.timedLock(1000000000 /* 1s */) != OK) { ALOGE("%s: cannot acquire lock in 1s, cannot proceed", __FUNCTION__);