remoteproc: support non-iommu carveout assignment

Publish carveout addresses on non-iommu setups too.
Reported-and-acked-by: NSjur Brændeland <sjur.brandeland@stericsson.com>
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>

drivers/remoteproc/remoteproc_core.c

@@ -713,6 +713,7 @@ static int rproc_handle_carveout(struct rproc *rproc,
 		list_add_tail(&mapping->node, &rproc->mappings);
 
 		dev_dbg(dev, "carveout mapped 0x%x to 0x%x\n", rsc->da, dma);
+	}
 
 	/*
 	 * Some remote processors might need to know the pa
@@ -726,9 +727,12 @@ static int rproc_handle_carveout(struct rproc *rproc,
 	 * _not_ trusted), so we might want to do this only for
 	 * remote processor that _must_ have this (e.g. OMAP4's
 	 * dual M3 subsystem).
+	 *
+	 * Non-IOMMU processors might also want to have this info.
+	 * In this case, the device address and the physical address
+	 * are the same.
 	 */
 	rsc->pa = dma;
-	}
 
 	carveout->va = va;
 	carveout->len = rsc->len;