From: Rob Herring <robh@kernel.org>
To: Kamal Dasu <kamal.dasu@broadcom.com>
Cc: peng.fan@oss.nxp.com, andersson@kernel.org,
baolin.wang@linux.alibaba.com, krzk+dt@kernel.org,
conor+dt@kernel.org, florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: hwlock: Adding brcmstb-hwspinlock support
Date: Wed, 8 Oct 2025 10:56:39 -0500 [thread overview]
Message-ID: <20251008155639.GA3512742-robh@kernel.org> (raw)
In-Reply-To: <20251001181641.1561472-2-kamal.dasu@broadcom.com>
On Wed, Oct 01, 2025 at 02:16:39PM -0400, Kamal Dasu wrote:
> Adding brcmstb-hwspinlock bindings.
That's obvious from the diff. Tell us something about the h/w and
convince me we don't need per SoC compatible which is standard practice.
>
> Signed-off-by: Kamal Dasu <kamal.dasu@broadcom.com>
> ---
> .../hwlock/brcm,brcmstb-hwspinlock.yaml | 36 +++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
>
> diff --git a/Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml b/Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
> new file mode 100644
> index 000000000000..f45399b4fe0b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
> @@ -0,0 +1,36 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/hwlock/brcm,brcmstb-hwspinlock.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom settop Hardware Spinlock
> +
> +maintainers:
> + - Kamal Dasu <kamal.dasu@broadcom.com>
> +
> +properties:
> + compatible:
> + const: brcm,brcmstb-hwspinlock
hwspinlock is the name of the h/w block? Use the name of the h/w, not
linux subsystem names.
> +
> + "#hwlock-cells":
> + const: 1
> +
> + reg:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - "#hwlock-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + hwlock@8404038 {
> + compatible = "brcm,brcmstb-hwspinlock";
> + reg = <0x8404038 0x40>;
h/w blocks rarely start at an offset like that. Is this part of some
other h/w block? If so, then just add '#hwlock-cells' to *that* node.
> + #hwlock-cells = <1>;
> + };
> +
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-10-08 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 18:16 [PATCH v2 0/3] Adding brcmstb-hwspinlock support Kamal Dasu
2025-10-01 18:16 ` [PATCH v2 1/3] dt-bindings: hwlock: " Kamal Dasu
2025-10-08 15:56 ` Rob Herring [this message]
2025-10-08 16:39 ` Florian Fainelli
2025-10-09 0:40 ` Krzysztof Kozlowski
2025-10-09 15:40 ` Kamal Dasu
2025-10-01 18:16 ` [PATCH v2 2/3] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2025-10-01 18:16 ` [PATCH v2 3/3] MAINTAINERS: adding entry for BRCMSTB HWSPINLOCK driver Kamal Dasu
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=20251008155639.GA3512742-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=peng.fan@oss.nxp.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;
as well as URLs for NNTP newsgroup(s).