From: Atish Patra <atishp@atishpatra.org>
To: linux-kernel@vger.kernel.org
Cc: Atish Patra <atishp@rivosinc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Atish Patra <atishp@atishpatra.org>,
Anup Patel <anup@brainfault.org>,
Damien Le Moal <damien.lemoal@wdc.com>,
devicetree@vger.kernel.org, Jisheng Zhang <jszhang@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Rob Herring <robh+dt@kernel.org>
Subject: [PATCH v1 0/2] Provide a fraemework for RISC-V ISA extensions
Date: Fri, 24 Dec 2021 13:16:30 -0800 [thread overview]
Message-ID: <20211224211632.1698523-1-atishp@rivosinc.com> (raw)
This series implements a generic framework to parse multi-letter ISA
extensions. It introduces a new DT node that can be under /cpus or
individual cpu depends on the platforms with homogeneous or heterogeneous
harts. This version of the series only allows adds support for homogeneous
harts as there are no platforms with heterogeneous harts yet. However,
the DT binding allows both.
The patch also indicates the user space about the available ISA extensions
via /proc/cpuinfo.
Here is the example output of /proc/cpuinfo:
(with debug patches in Qemu and Linux kernel)
/ # cat /proc/cpuinfo
processor : 0
hart : 0
isa : rv64imafdcsu
isa-ext : sstc,sscofpmf
mmu : sv48
processor : 1
hart : 1
isa : rv64imafdcsu
isa-ext : sstc,sscofpmf
mmu : sv48
processor : 2
hart : 2
isa : rv64imafdcsu
isa-ext : sstc,sscofpmf
mmu : sv48
processor : 3
hart : 3
isa : rv64imafdcsu
isa-ext : sstc,sscofpmf
mmu : sv48
Anybody adding support for any new multi-letter extensions should add an
entry to the riscv_isa_ext_id and the isa extension array.
E.g. The patch[1] adds the support for sscofpmf extension.
[1] https://github.com/atishp04/linux/commit/a23157264118d6fd905fd08d8717c7df03078bb1
Atish Patra (2):
RISC-V: Provide a framework for parsing multi-letter ISA extensions
dt-bindings: riscv: Add DT binding for RISC-V ISA extensions
.../devicetree/bindings/riscv/cpus.yaml | 9 +++
arch/riscv/include/asm/hwcap.h | 31 ++++++++++
arch/riscv/kernel/cpu.c | 16 +++++
arch/riscv/kernel/cpufeature.c | 58 ++++++++++++++++++-
4 files changed, 113 insertions(+), 1 deletion(-)
--
2.33.1
next reply other threads:[~2021-12-24 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 21:16 Atish Patra [this message]
2021-12-24 21:16 ` [PATCH v1 1/2] RISC-V: Provide a framework for parsing multi-letter " Atish Patra
2021-12-25 3:12 ` Tsukasa OI
2021-12-25 6:09 ` Atish Patra
2021-12-25 10:11 ` Krzysztof Kozlowski
2021-12-24 21:16 ` [PATCH v1 2/2] dt-bindings: riscv: Add DT binding for RISC-V " Atish Patra
2021-12-24 23:25 ` Jessica Clarke
2021-12-25 5:52 ` Atish Patra
2021-12-25 14:48 ` Rob Herring
2022-01-07 21:58 ` [PATCH v1 0/2] Provide a fraemework " Palmer Dabbelt
2022-01-08 2:24 ` Atish Patra
2022-02-03 13:56 ` Heiko Stübner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211224211632.1698523-1-atishp@rivosinc.com \
--to=atishp@atishpatra.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=damien.lemoal@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®