Searched +full:thead +full:- +full:extension +full:- +full:spec (Results 1 – 3 of 3) sorted by relevance
1 # SPDX-License-Identifier: (GPL-2.0 OR MIT)3 ---5 $schema: http://devicetree.org/meta-schemas/core.yaml#7 title: RISC-V ISA extensions10 - Paul Walmsley <paul.walmsley@sifive.com>11 - Palmer Dabbelt <palmer@sifive.com>12 - Conor Dooley <conor@kernel.org>15 RISC-V has a large number of extensions, some of which are "standard"16 extensions, meaning they are ratified by RISC-V International, and others19 given extension.[all …]
1 // SPDX-License-Identifier: GPL-2.0-only24 #include <asm/text-patching.h>30 #include <asm/vendor_extensions/thead.h>32 #define NUM_ALPHA_EXTS ('z' - 'a' + 1)42 /* Per-cpu ISA extensions. */48 * riscv_isa_extension_base() - Get base extension word51 * Return: base extension word as unsigned long value62 * __riscv_isa_extension_available() - Check whether given extension66 * @bit: bit position of the desired extension88 return -EPROBE_DEFER; in riscv_ext_f_depends()[all …]
1 .. SPDX-License-Identifier: GPL-2.03 RISC-V Hardware Probing Interface4 ---------------------------------6 The RISC-V hardware probing interface is based around a single syscall, which18 The arguments are split into three groups: an array of key-value pairs, a CPU19 set, and some flags. The key-value pairs are supplied with a count. Userspace22 will be cleared to -1, and its value set to 0. The CPU set is defined by23 CPU_SET(3) with size ``cpusetsize`` bytes. For value-like keys (eg. vendor,25 have the same value. Otherwise -1 will be returned. For boolean-like keys, the33 by sys_riscv_hwprobe() to only those which match each of the key-value pairs.[all …]