fix(tc): do not use r0 for HW_CONFIG
populate_next_bl_params_config already configures the register values
to be passed to BL33 and puts the HW_CONFIG address in r1. Therefore,
we do not need to override r0 here and should instead use r1 in BL33.
Change-Id: I00b425301957b5b0510416e1fa1f3599c0359bfc
Signed-off-by: Jackson Cooper-Driver <jackson.cooper-driver@arm.com>
diff --git a/plat/arm/board/tc/tc_bl31_setup.c b/plat/arm/board/tc/tc_bl31_setup.c
index 6789c2e..5742d07 100644
--- a/plat/arm/board/tc/tc_bl31_setup.c
+++ b/plat/arm/board/tc/tc_bl31_setup.c
@@ -75,25 +75,6 @@
void bl31_early_platform_setup2(u_register_t arg0, u_register_t arg1,
u_register_t arg2, u_register_t arg3)
{
- /*
- * Pass the hw_config to BL33 in R0. You'll notice that
- * arm_bl31_early_platform_setup does something similar but only behind
- * ARM_LINUX_KERNEL_AS_BL33 and we want to pass the DTB even to a
- * bootloader. Lucky for us, it copies the ep_info BL2 gave us to BL33
- * unconditionally in the generic case so hijack that.
- * TODO: this goes away with firmware handoff when it will be proper
- */
-
- bl_params_node_t *bl_params = ((bl_params_t *)arg0)->head;
-
- while (bl_params != NULL) {
- if (bl_params->image_id == BL33_IMAGE_ID) {
- bl_params->ep_info->args.arg0 = arg2;
- break;
- }
- bl_params = bl_params->next_params_info;
- }
-
arm_bl31_early_platform_setup((void *)arg0, arg1, arg2, (void *)arg3);
/* Fill the properties struct with the info from the config dtb */