opensbi.git/lib/utils/fdt/fdt_fixup.c, branch v1.0

utils: fdt: Add fdt helper functions to parse PMU DT nodes

2021-07-11T04:57:57Z

The PMU DT node bindings are defined in docs/pmu_support.md Add few fdt helper functions to parse the DT node and update the event-counter mapping tables. Reviewed-by: Anup Patel Signed-off-by: Atish Patra

lib/utils: Support fixing up the official DT bindings of PLIC

2021-04-01T05:01:11Z

Current fdt_plic_fixup() only does necessary fix-up against the legacy "riscv,plic0" node. The upstream Linux kernel defines its official DT bindings which uses "sifive,plic-1.0.0" as the compatible string and we should check that first, and if not present fall back to legacy. Signed-off-by: Bin Meng Reviewed-by: Anup Patel

lib/utils: Drop the 'compat' parameter of fdt_plic_fixup()

2021-04-01T04:57:28Z

At present fdt_plic_fixup() accepts a 'compat' parameter for PLIC compatible string. In preparation to support the new DT bindings, drop this and use "riscv,plic0" directly in fdt_plic_fixup(). Signed-off-by: Bin Meng Reviewed-by: Anup Patel

lib: utils: Update fdt_cpu_fixup() to use current domain

2020-10-20T08:34:51Z

The fdt_cpu_fixup() should disable a HART in DT if the HART is not assigned to the current HART domain. This patch updates fdt_cpu_fixup() accordingly. Signed-off-by: Anup Patel Reviewed-by: Atish Patra

lib: utils: Update fdt_reserved_memory_fixup() to use current domain

2020-10-20T08:34:43Z

Now that each HART is mapped to a domain having a set of memory regions, we update fdt_reserved_memory_fixup() to use domain memory regions for adding reserved memory nodes in device tree. We also change reserved memory node name prefix from "mmode_pmp" to "mmode_resv" because domain memory regions can impact other hardware configurations (such as IOPMP, etc) along with PMP. Signed-off-by: Anup Patel Reviewed-by: Atish Patra

lib: utils: Improve fdt_cpu_fixup() implementation

2020-09-16T03:35:27Z

The fdt_cpu_fixup() should work fine even if HARTs without MMU are not marked invalid by platform support code. In future, we plan to treat HARTs without MMU as valid in the generic platform support so that we can hold these HARTs in HSM STOPPED state. Signed-off-by: Anup Patel Reviewed-by: Atish Patra

lib: sbi: Remove redundant SBI_HART_HAS_PMP feature

2020-09-01T04:58:26Z

The SBI_HART_HAS_PMP feature is redundant because we already have number of PMP regions returned by sbi_hart_pmp_count(). Checking whether PMP is supported for a HART can be simply done by checking non-zero value returned by sbi_hart_pmp_count(). Signed-off-by: Anup Patel Reviewed-by: Alistair Francis Reviewed-by: Atish Patra

lib/utils: fdt: Update FDT expand size to 1024 for reserved memory node

2020-07-06T08:35:29Z

Currently 256 bytes is used for the FDT expand size when fixing up reserved memory node. Increase it to 1024 bytes with an estimated size of 64 bytes per PMP memory region by 16 regions in total. Signed-off-by: Bin Meng Reviewed-by: Atish Patra

platform/lib: Allow the OS to map the regions that are protected by PMP

2020-06-15T03:55:44Z

This is achieved by removing the 'no-map' property from the 'reserved-memory' node when PMP is present, otherwise we keep it as it offers a small protection if the OS does not map this region at all. A new callback in platform_override is introduced and allows to fixup the device-tree. It is used here to override this new default behaviour on SiFive Fu540 platforms that has an erratum that prevents S-mode software to access a PMP protected region using 1GB page table mapping. If PMP is present, telling the OS not to map the reserved regions does not add much protection since it only avoids access to regions that are already protected by PMP. But by not allowing the OS to map those regions, it creates holes in the OS system memory map and prevents the use of hugepages which would generate, among other benefits, less TLB miss. Signed-off-by: Alexandre Ghiti Reviewed-by: Atish Patra Reviewed-by: Anup Patel

lib: sbi_hart: Detect number of supported PMP regions

2020-05-19T03:49:48Z

It is not mandatory for a RISC-V systems to implement all PMP regions so we have to check all PMPADDRx CSRs to determine excat number of supported PMP regions. Signed-off-by: Anup Patel