• Suman Anna's avatar
    remoteproc: free carveout memories only after unmapping them · b6356a01
    Suman Anna authored
    It is not preferable to have the allocated pages for carveout
    memories freed before they are unmapped. The code that deals
    with the cleanup of carveout memories is therefore moved after
    the corresponding mapping entries were cleaned up.
    
    This is mostly a no-op since the remote processors are already
    stopped when the cleanup function is called, but this will make
    the cleanup code follow the exact reverse path of allocation.
    Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
    Signed-off-by: default avatarOhad Ben-Cohen <ohad@wizery.com>
    b6356a01
Name
Last commit
Last update
..
Kconfig Loading commit data...
Makefile Loading commit data...
da8xx_remoteproc.c Loading commit data...
omap_remoteproc.c Loading commit data...
omap_remoteproc.h Loading commit data...
remoteproc_core.c Loading commit data...
remoteproc_debugfs.c Loading commit data...
remoteproc_elf_loader.c Loading commit data...
remoteproc_internal.h Loading commit data...
remoteproc_virtio.c Loading commit data...
ste_modem_rproc.c Loading commit data...