From: <lv.yating@zte.com.cn>
To: <pjw@kernel.org>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<alex@ghiti.fr>, <corbet@lwn.net>, <skhan@linuxfoundation.org>,
<rdunlap@infradead.org>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<liu.qingtao2@zte.com.cn>, <he.yilin@zte.com.cn>,
<ye.zhihao1@zte.com.cn>, <zhang.cheng35@zte.com.cn>,
<hu.shengming@zte.com.cn>, <lv.yating@zte.com.cn>,
<linux-doc@vger.kernel.org>
Subject: [PATCH v2 0/2] riscv: Add Beijing LeapRise Technology vendor ID and vendor extension framework
Date: Fri, 20 Nov 2026 14:51:17 +0800 (CST) [thread overview]
Message-ID: <20261120145117988UPrFJYA461pgTds3xOCwH@zte.com.cn> (raw)
From: Lv Yating <lv.yating@zte.com.cn>
Hi,
Beijing LeapRise Technology has been assigned a JEDEC manufacturer
identity, encoded as 0x966 in the mvendorid CSR per the JEP106
scheme (bank 0x12, final byte 0x66).
This series lays the kernel groundwork for LeapRise RISC-V cores:
Patch 1 adds the vendor ID constant (LEAPRISE_VENDOR_ID) to the
RISC-V vendor list.
Patch 2 adds the vendor extension framework support: hwprobe key
recognition (RISCV_HWPROBE_KEY_VENDOR_EXT_LEAPRISE_0) and an empty
extension probe list hooked into the common probing path. The key
reports an empty bitmask for now, allowing userspace to distinguish
it from unknown keys (reported as -1), so LeapRise userspace
libraries can be prepared ahead of the first hardware shipping
vendor extensions. The key is documented in
Documentation/arch/riscv/hwprobe.rst.
Follow-up patches will register extensions as their specifications
are finalized.
---
Changelog:
v2:
- Bumped RISCV_HWPROBE_MAX_KEY to 17 so the new key is valid for
userspace and in the vDSO data.
- Registered LeapRise in the vendor extension framework: added the entry
to riscv_isa_vendor_ext_list[], the LEAPRISE_VENDOR_ID switch case,
riscv_isa_vendor_ext_list_leaprise in leaprise.c, and
RISCV_ISA_VENDOR_EXT_MAX_LEAPRISE.
- Fixed the build failure in vendor_extensions.c and the wrong
MIPS_VENDOR_ID case label.
- Fixed the Kconfig.vendor syntax error.
- Unified SPDX on GPL-2.0-only and cleaned up the new files.
v1:
-https://lore.kernel.org/all/202611160811.6AG8B8QM046993@mse-db.zte.com.cn/
-https://lore.kernel.org/all/202611160824.6AG8OXL4051238@mse-db.zte.com.cn/
best regards,
Lv Yating
Lv Yating (2):
riscv: Add LeapRise Technology to the vendor list
riscv: hwprobe: Add LeapRise vendor extension framework support
Documentation/arch/riscv/hwprobe.rst | 4 ++++
arch/riscv/Kconfig.vendor | 14 +++++++++++++
arch/riscv/include/asm/hwprobe.h | 3 ++-
.../include/asm/vendor_extensions/leaprise.h | 17 ++++++++++++++++
.../asm/vendor_extensions/leaprise_hwprobe.h | 20 +++++++++++++++++++
arch/riscv/include/asm/vendorid_list.h | 1 +
arch/riscv/include/uapi/asm/hwprobe.h | 1 +
arch/riscv/include/uapi/asm/vendor/leaprise.h | 3 +++
arch/riscv/kernel/sys_hwprobe.c | 4 ++++
arch/riscv/kernel/vendor_extensions.c | 10 ++++++++++
arch/riscv/kernel/vendor_extensions/Makefile | 2 ++
.../riscv/kernel/vendor_extensions/leaprise.c | 12 +++++++++++
.../vendor_extensions/leaprise_hwprobe.c | 19 ++++++++++++++++++
13 files changed, 109 insertions(+), 1 deletion(-)
create mode 100644 arch/riscv/include/asm/vendor_extensions/leaprise.h
create mode 100644 arch/riscv/include/asm/vendor_extensions/leaprise_hwprobe.h
create mode 100644 arch/riscv/include/uapi/asm/vendor/leaprise.h
create mode 100644 arch/riscv/kernel/vendor_extensions/leaprise.c
create mode 100644 arch/riscv/kernel/vendor_extensions/leaprise_hwprobe.c
--
2.27.0
next reply other threads:[~2026-11-20 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 6:51 lv.yating [this message]
2026-11-20 7:02 ` [PATCH v2 1/2] riscv: Add LeapRise Technology to the vendor list lv.yating
2026-11-20 7:04 ` [PATCH v2 2/2] riscv: hwprobe: Add LeapRise vendor extension framework support lv.yating
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=20261120145117988UPrFJYA461pgTds3xOCwH@zte.com.cn \
--to=lv.yating@zte.com.cn \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=he.yilin@zte.com.cn \
--cc=hu.shengming@zte.com.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liu.qingtao2@zte.com.cn \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=ye.zhihao1@zte.com.cn \
--cc=zhang.cheng35@zte.com.cn \
/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®