MA-9931 [#imx-667] use kzalloc instead of kmalloc during fence_init.

Fix cts android.app.uiautomation.cts.UiAutomationTest#testWindowContentFrameStats fail.
This case check fence getSignalTime, which is get from fence->timestamp.
If use kmalloc, timestamp value is not guaranteed and can't be updated during fence_signal.

Date: Jul 17, 2017
Signed-off-by: juan.hao <juan.hao@nxp.com>

diff --git a/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_sync.c b/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_sync.c
index 9750219..66da1dc 100644 (file)
--- a/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_sync.c
+++ b/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_sync.c
@@ -313,7 +313,7 @@ struct fence * viv_fence_create(struct viv_sync_timeline *timeline,
     struct fence *old_fence = NULL;
     unsigned seqno;
 
-    fence = kmalloc(sizeof(struct viv_fence), gcdNOWARN | GFP_KERNEL);
+    fence = kzalloc(sizeof(struct viv_fence), gcdNOWARN | GFP_KERNEL);
 
     if (!fence)
         return NULL;