From: Xingyu Wu <xingyu.wu@starfivetech.com>
To: Bjorn Andersson <andersson@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Xingyu Wu <xingyu.wu@starfivetech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: [PATCH v2 0/2] Add hwspinlock driver for StarFive JHB100 SoC
Date: Fri, 15 May 2026 17:53:55 +0800 [thread overview]
Message-ID: <20260515095357.75998-1-xingyu.wu@starfivetech.com> (raw)
This patch serises are to add hardware spinlock driver for the StarFive
JHB100 SoC. The first patch adds documentation for StarFive Hardware
Spinlock. The subsequent patch adds hwspinlock driver and support JHB100
SoC.
The StarFive hwspinlock supports 16 channels for using by secur core and
AP core to restrict access and protect the memory area.
Changes since v1:
- Simplified the subject.
- Added 'StarFive JHB100' in documentation title.
- Modified the name of example.
- Added the property of 'clocks'.
v1: https://lore.kernel.org/all/20260424032026.62301-1-xingyu.wu@starfivetech.com/
Xingyu Wu (2):
dt-bindings: hwlock: Add StarFive JHB100 HW lock
hwspinlock: Add StarFive hwspinlock device
.../hwlock/starfive,jhb100-hwspinlock.yaml | 43 ++++++
MAINTAINERS | 6 +
drivers/hwspinlock/Kconfig | 8 ++
drivers/hwspinlock/Makefile | 1 +
drivers/hwspinlock/starfive_hwspinlock.c | 130 ++++++++++++++++++
5 files changed, 188 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwlock/starfive,jhb100-hwspinlock.yaml
create mode 100644 drivers/hwspinlock/starfive_hwspinlock.c
--
2.34.1
next reply other threads:[~2026-05-15 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:53 Xingyu Wu [this message]
2026-05-15 9:53 ` [PATCH v2 1/2] dt-bindings: hwlock: Add StarFive JHB100 HW lock Xingyu Wu
2026-05-15 9:53 ` [PATCH v2 2/2] hwspinlock: Add StarFive hwspinlock device Xingyu Wu
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=20260515095357.75998-1-xingyu.wu@starfivetech.com \
--to=xingyu.wu@starfivetech.com \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=robh@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