summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorTom Rini <[email protected]>2025-11-18 12:50:38 -0600
committerTom Rini <[email protected]>2025-11-18 12:50:38 -0600
commitabf15eb60c8a87f833f7e75e5e8a51a7eb115e0b (patch)
treedeed0c31b00bc75d4c516c0e250b630ad4e7f19e /arch
parent96edadab5476c37f3c0b0b99877db16e3e58d5e1 (diff)
parent0c192f52cfb8a4b1c29d61750f48e016ba6b978b (diff)
Merge patch series "remoteproc: k3-r5: Build fixes and security improvements"
Philippe Schenker <[email protected]> says: This series fixes compilation errors when building for R5 cores and addresses a security issue where authenticated images were not being used correctly. Patch 1: Cosmetic removal of duplicate code Patches 2-3: Fix build errors caused by type mismatches between function signatures and the types used in R5 builds. Patches 4-5: fix a bug where ti_secure_image_post_process() relocates images during authentication, but callers were still using the original unverified addresses. Patch 6: Implements is_running operation to allow querying R5F core status. Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/dts/k3-am642-evm-u-boot.dtsi4
-rw-r--r--arch/arm/mach-k3/security.c2
2 files changed, 2 insertions, 4 deletions
diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi b/arch/arm/dts/k3-am642-evm-u-boot.dtsi
index 705b3baa81c..6469f43fca8 100644
--- a/arch/arm/dts/k3-am642-evm-u-boot.dtsi
+++ b/arch/arm/dts/k3-am642-evm-u-boot.dtsi
@@ -19,10 +19,6 @@
dr_mode="peripheral";
};
-&main_mmc1_pins_default {
- bootph-all;
-};
-
&sdhci0 {
bootph-all;
};
diff --git a/arch/arm/mach-k3/security.c b/arch/arm/mach-k3/security.c
index 3468a370a45..c7017bba99a 100644
--- a/arch/arm/mach-k3/security.c
+++ b/arch/arm/mach-k3/security.c
@@ -119,6 +119,8 @@ void ti_secure_image_post_process(void **p_image, size_t *p_size)
*/
*p_size = image_size;
+ *p_image = (void *)(uintptr_t)image_addr;
+
/*
* Output notification of successful authentication to re-assure the
* user that the secure code is being processed as expected. However