cma: Delay non-placed memblocks until after all allocations
CMA is now responsible for almost all memory reservation/removal.
Some regions are at fixed locations, some are placed dynamically.
We need to place all fixed regions first before trying to place
dynamic regions to avoid overlap. Additionally, allow an
architectural callback after all removals/fixed location has
happened to potentially update any relevant limits.
Change-Id: Iaaffe60445ef44d432f0d87875ce2b292b717cc7
Signed-off-by:
Laura Abbott <lauraa@codeaurora.org>
Loading
Please register or sign in to comment