diff options
| author | Philippe Schenker <[email protected]> | 2025-11-11 08:16:29 +0100 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-11-18 12:50:05 -0600 |
| commit | 3a43fc9016c3c37eefca10ed404c95ac7cecd3dc (patch) | |
| tree | c028850e64636316da3cec8c93738e3bc5e2ebd2 | |
| parent | fe114f3662c655cae44b45370d6dc4de2055a611 (diff) | |
remoteproc: k3-r5: Use verified image address
After ti_secure_image_post_process() authenticates the image, it may
relocate it to a different memory location and update image_addr to
point to the verified image.
However, rproc_elf_load_image() and rproc_elf_get_boot_addr() were
still using the original "addr" parameter, potentially operating on
the unverified or stale image location instead of the authenticated
image.
Use image_addr (cast to ulong to match function signatures) after
authentication to ensure all operations work with the verified image.
Signed-off-by: Philippe Schenker <[email protected]>
| -rw-r--r-- | drivers/remoteproc/ti_k3_r5f_rproc.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/remoteproc/ti_k3_r5f_rproc.c b/drivers/remoteproc/ti_k3_r5f_rproc.c index 48ebdaf0693..c6356729e9d 100644 --- a/drivers/remoteproc/ti_k3_r5f_rproc.c +++ b/drivers/remoteproc/ti_k3_r5f_rproc.c @@ -346,13 +346,13 @@ static int k3_r5f_load(struct udevice *dev, ulong addr, ulong size) ti_secure_image_post_process(&image_addr, &size_img); size = size_img; - ret = rproc_elf_load_image(dev, addr, size); + ret = rproc_elf_load_image(dev, (ulong)image_addr, size); if (ret < 0) { dev_err(dev, "Loading elf failedi %d\n", ret); goto proc_release; } - boot_vector = rproc_elf_get_boot_addr(dev, addr); + boot_vector = rproc_elf_get_boot_addr(dev, (ulong)image_addr); dev_dbg(dev, "%s: Boot vector = 0x%llx\n", __func__, boot_vector); |