| author | Angela Stegmaier <angelabaker@ti.com> | |
| Fri, 13 Sep 2019 19:47:09 +0000 (14:47 -0500) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Mon, 23 Sep 2019 01:46:54 +0000 (20:46 -0500) | ||
| commit | ad2d6e0114687f7a94af4f25b6657b09c5475528 | |
| tree | 94e09ecdcc3aa4e6205de3e8f9c07b19ccfcf4ca | tree | snapshot (tar.xz tar.gz zip) |
| parent | 15dfdff5383cc23ee39eb41479b72975de9c47c2 | commit | diff |
TEMP: remoteproc: call the non-zeroing allocation function
For DMA pool scenario the plugged in allocation ops are not
used for carveout allocation. It is necessary to call a differnt
function that does not zero the DMA pool memory gotten from
the call to dma_alloc_coherent.
Call the dma_malloc_coherent (non-zeroing) api in the case
of late attach to guarantee that the memory is not zero-ed for
either a CMA or DMA pool. The memory for virtio rings is not
used in U-Boot, so need not use the non-zeroing function.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Shravan Karthik <shravan.karthik@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
For DMA pool scenario the plugged in allocation ops are not
used for carveout allocation. It is necessary to call a differnt
function that does not zero the DMA pool memory gotten from
the call to dma_alloc_coherent.
Call the dma_malloc_coherent (non-zeroing) api in the case
of late attach to guarantee that the memory is not zero-ed for
either a CMA or DMA pool. The memory for virtio rings is not
used in U-Boot, so need not use the non-zeroing function.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Shravan Karthik <shravan.karthik@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
| drivers/remoteproc/remoteproc_core.c | diff | blob | history |