diff options
| author | Anup Patel <anup.patel@wdc.com> | 2019-11-06 16:24:35 +0530 |
|---|---|---|
| committer | Anup Patel <anup@brainfault.org> | 2019-11-15 17:41:18 +0530 |
| commit | 7a13beb213266cbf6f15ddbbef5bfca274086bd3 (patch) | |
| tree | 31feb9270d13674ef8134618729a06ea269d46eb /firmware/fw_jump.S | |
| parent | 18897aaf5d0382017c05a5690d0bc8e0d044270f (diff) | |
firmware: Add preferred boot HART field in struct fw_dynamic_info
It has been reported that link address range of previous booting stage
(such as U-Boot SPL) can overlap the link address rage of FW_DYNAMIC.
This means self-relocation in FW_DYNAMIC can potentially corrupt
previous booting stage if any of the secondary HART enter FW_DYNAMIC
before primary HART.
To tackle this, we add preferred boot HART field (i.e boot_hart) in
struct fw_dyanmic_info. We use this field to force secondary HARTs
into relocation wait loop till preferred/primary boot HART enters
FW_DYNAMIC completes self-relocation. If preferred boot HART is not
available then we fall back to relocation lottery approach.
Signed-off-by: Anup Patel <anup.patel@wdc.com>
Reviewed-by: Atish Patra <atish.patra@wdc.com>
Diffstat (limited to 'firmware/fw_jump.S')
| -rw-r--r-- | firmware/fw_jump.S | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/firmware/fw_jump.S b/firmware/fw_jump.S index cdf1f41..84391c9 100644 --- a/firmware/fw_jump.S +++ b/firmware/fw_jump.S @@ -11,6 +11,19 @@ .align 3 .section .entry, "ax", %progbits + .global fw_boot_hart + /* + * This function is called very early even before + * fw_save_info() is called. + * We can only use a0, a1, and a2 registers here. + * The boot HART id should be returned in 'a0'. + */ +fw_boot_hart: + li a0, -1 + ret + + .align 3 + .section .entry, "ax", %progbits .global fw_save_info /* * We can only use a0, a1, a2, a3, and a4 registers here. |