Home
last modified time | relevance | path

Searched full:harts (Results 1 – 9 of 9) sorted by relevance

/Documentation/arch/riscv/
Duabi.rst49 RISC-V ISA extensions recognized by the kernel and implemented on all harts. The
52 be present on all harts in the system.
Dboot.rst68 - ``RISCV_BOOT_SPINWAIT``: the firmware releases all harts in the kernel, one hart
69 wins a lottery and executes the early boot code while the other harts are
73 initialization phase and then will start all other harts using the SBI HSM
/Documentation/devicetree/bindings/interrupt-controller/
Driscv,imsics.yaml22 which is same for given privilege level across CPUs (or HARTs).
26 IMSIC interrupt files at that privilege level across CPUs (or HARTs).
73 This property represents the set of CPUs (or HARTs) for which given
Driscv,aplic.yaml46 RISC-V HARTS (or CPUs). Each node pointed to should be a riscv,cpu-intc
114 // Example 1 (APLIC domains directly injecting interrupt to HARTs):
Driscv,cpu-intc.yaml31 present HARTs in the system.
Dsifive,plic-1.0.0.yaml18 in an 4 core system with 2-way SMT, you have 8 harts and probably at least two
/Documentation/devicetree/bindings/timer/
Dsifive,clint.yaml17 lines of various HARTs (or CPUs) so RISC-V per-HART (or per-CPU) local
/Documentation/devicetree/bindings/riscv/
Dcpus.yaml24 having four harts.
/Documentation/devicetree/bindings/cpu/
Didle-states.yaml55 On RISC-V systems, the HARTs (or CPUs) [6] can be put in platform specific