Firmware/opensbi
8
0
Fork 0
forked from Mirrors/opensbi
Code Pull Requests Activity

include: sbi: Use scratch pointer as parmeter in HART feature APIs

Browse Source 
It makes more sense to have scratch pointer as parameter in
HART feature APIs because:
1. We already have scratch pointer at places where these APIs
   are used.
2. This is consistent with lot of other APIs in sbi_hart.h

Signed-off-by: Anup Patel <anup.patel@wdc.com>
Reviewed-by: Atish Patra <atish.patra@wdc.com>
This commit is contained in:
Anup Patel
2020-05-11 11:30:15 +05:30
committed by Anup Patel
parent 3a8fc81357
commit 63b0f5f71a
5 changed files with 32 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
lib/utils/fdt/fdt_fixup.c
View File

@@ -183,10 +183,11 @@ int fdt_reserved_memory_fixup(void *fdt)
return err;
}
if (!sbi_hart_has_feature(current_hartid(), SBI_HART_HAS_PMP)) {
/* update the DT with firmware start & size even if PMP is not
if (!sbi_hart_has_feature(scratch, SBI_HART_HAS_PMP)) {
/*
* Update the DT with firmware start & size even if PMP is not
* supported. This makes sure that supervisor OS is always
* aware of wheren OpenSBI resident memory area.
* aware of OpenSBI resident memory area.
*/
addr = scratch->fw_start & ~(scratch->fw_size - 1UL);
size = (1UL << log2roundup(scratch->fw_size));