From 2821a826dbd3097b27801e02a2d7bc412a02e76c Mon Sep 17 00:00:00 2001 From: DongJin Park Date: Tue, 16 Oct 2012 12:59:55 +0900 Subject: [PATCH] mobicore: update daemon to handle MobiCore halt status Daemon asks correct status from MobiCore: FC_INFO state_id = 1 (Update from MobiCore1.2_V005_Path3) Bug: 7179227, 7336639 Change-Id: I87dc8acc3fd7e56a6a0dd2c9be0c8a5b995e6c87 Signed-off-by: DongJin Park --- .../Daemon/Device/Platforms/Generic/TrustZoneDevice.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/mobicore/daemon/Daemon/Device/Platforms/Generic/TrustZoneDevice.cpp b/mobicore/daemon/Daemon/Device/Platforms/Generic/TrustZoneDevice.cpp index 962d2cc..5855bed 100644 --- a/mobicore/daemon/Daemon/Device/Platforms/Generic/TrustZoneDevice.cpp +++ b/mobicore/daemon/Daemon/Device/Platforms/Generic/TrustZoneDevice.cpp @@ -273,9 +273,8 @@ notification_t notification = { sessionId : uint32_t TrustZoneDevice::getMobicoreStatus(void) { uint32_t status; - //IMPROVEMENT-2012-03-07-maneaval Can fcInfo ever fail? Before it threw an - //exception but the handler depended on the context. - pMcKMod->fcInfo(0, &status, NULL); + + pMcKMod->fcInfo(1, &status, NULL); return status; } -- 2.20.1