From: Conor Dooley <conor@kernel.org>
To: Xingyu Wu <xingyu.wu@starfivetech.com>
Cc: 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>,
Mason Huo <mason.huo@starfivetech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: hwlock: Add the support of HWspinlock for StarFive JHB100
Date: Fri, 24 Apr 2026 18:05:24 +0100 [thread overview]
Message-ID: <20260424-corsage-strict-026754e5f045@spud> (raw)
In-Reply-To: <20260424032026.62301-2-xingyu.wu@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
On Fri, Apr 24, 2026 at 11:20:25AM +0800, Xingyu Wu wrote:
> Add the new documentation of hardware spinlock for the StarFive JHB100 SoC.
>
> Signed-off-by: Xingyu Wu <xingyu.wu@starfivetech.com>
> ---
> .../hwlock/starfive,jhb100-hwspinlock.yaml | 40 +++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwlock/starfive,jhb100-hwspinlock.yaml
>
> diff --git a/Documentation/devicetree/bindings/hwlock/starfive,jhb100-hwspinlock.yaml b/Documentation/devicetree/bindings/hwlock/starfive,jhb100-hwspinlock.yaml
> new file mode 100644
> index 000000000000..b1b27fafe9bc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwlock/starfive,jhb100-hwspinlock.yaml
> @@ -0,0 +1,40 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/hwlock/starfive,jhb100-hwspinlock.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: StarFive Hardware Spinlock
> +
> +maintainers:
> + - Xingyu Wu <xingyu.wu@starfivetech.com>
> +
> +properties:
> + compatible:
> + const: starfive,jhb100-hwspinlock
> +
> + reg:
> + maxItems: 1
> +
> + resets:
> + maxItems: 1
> +
> + "#hwlock-cells":
> + const: 1
Does this peripheral not have a clock?
Seems unlikely to me that it doesnt.
> +
> +required:
> + - compatible
> + - reg
> + - resets
> + - "#hwlock-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + hwspinlock@13012000 {
> + compatible = "starfive,jhb100-hwspinlock";
> + reg = <0x13012000 0x400>;
> + resets = <&sys0crg 0>;
> + #hwlock-cells = <1>;
> + };
> --
> 2.34.1
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-04-24 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 3:20 [PATCH v1 0/2] Add hwspinlock driver for StarFive JHB100 SoC Xingyu Wu
2026-04-24 3:20 ` [PATCH v1 1/2] dt-bindings: hwlock: Add the support of HWspinlock for StarFive JHB100 Xingyu Wu
2026-04-24 17:05 ` Conor Dooley [this message]
2026-04-27 6:22 ` Xingyu Wu
2026-04-25 10:15 ` Krzysztof Kozlowski
2026-04-27 6:24 ` Xingyu Wu
2026-04-24 3:20 ` [PATCH v1 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=20260424-corsage-strict-026754e5f045@spud \
--to=conor@kernel.org \
--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=mason.huo@starfivetech.com \
--cc=robh@kernel.org \
--cc=xingyu.wu@starfivetech.com \
/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