66619a991e66d65cd96e41a9b48c25ae0ced6c0c

To provide more peak memory space for camera usecase, utilize system-movable heap. This will first check in standard system heap for allocation, if memory is not available, allocation will happen from system-movable heap. As we can not keep memory from system-movable heap to stay forever (which will regress memory power features), need to be careful when allocating from this heap. All camera userspace allocations' lifetime is at the usecase boundary, so allocate userspace allocations from system-movable heap if available, fallback to standard system heap if not available. kmd internal allocations will most likely stay forever, so allocate them only from standard system heap. CRs-Fixed: 3450854 Change-Id: Ic6644dea04cb44bf963b6277205de8502bc34bd9 Signed-off-by: Pavan Kumar Chilamkurthi <quic_pchilamk@quicinc.com>
Description
No description provided
Languages
C
98.7%
C++
0.9%
Makefile
0.3%
Starlark
0.1%