From: Conor Dooley <conor@kernel.org>
To: Kamal Dasu <kamal.dasu@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com, andersson@kernel.org,
baolin.wang@linux.alibaba.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
florian.fainelli@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 1/3] dt-bindings: hwlock: Adding brcmstb-hwspinlock support
Date: Tue, 30 Sep 2025 20:03:38 +0100 [thread overview]
Message-ID: <20250930-slapstick-volatile-60ad540f4b66@spud> (raw)
In-Reply-To: <20250929200628.3699525-2-kamal.dasu@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]
On Mon, Sep 29, 2025 at 04:06:24PM -0400, Kamal Dasu wrote:
> Adding brcmstb-hwspinlock bindings.
>
> 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
Is "brcmstb" actually the name of a single platform?
Looking at the "brcmstb" pci binding, it looks like there's a whole load
of different devices there and none use "brcmstb":
- brcm,bcm2711-pcie # The Raspberry Pi 4
- brcm,bcm2712-pcie # Raspberry Pi 5
- brcm,bcm4908-pcie
- brcm,bcm7211-pcie # Broadcom STB version of RPi4
- brcm,bcm7216-pcie # Broadcom 7216 Arm
- brcm,bcm7278-pcie # Broadcom 7278 Arm
- brcm,bcm7425-pcie # Broadcom 7425 MIPs
- brcm,bcm7435-pcie # Broadcom 7435 MIPs
- brcm,bcm7445-pcie # Broadcom 7445 Arm
- brcm,bcm7712-pcie # Broadcom STB sibling of Rpi 5
If "stb" means "set top box", it sounds like a catchall for disparate
devices, which isn't permitted.
> +
> + "#hwlock-cells":
> + const: 1
> +
> + reg:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - "#hwlock-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + hwlock@8404038 {
> + compatible = "brcm,brcmstb-hwspinlock";
> + reg = <0x8404038 0x40>;
> + #hwlock-cells = <1>;
> + };
> +
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-30 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 20:06 [PATCH 0/3] Adding brcmstb-hwspinlock support Kamal Dasu
2025-09-29 20:06 ` [PATCH 1/3] dt-bindings: hwlock: " Kamal Dasu
2025-09-30 19:03 ` Conor Dooley [this message]
2025-09-30 19:09 ` Florian Fainelli
2025-09-30 19:34 ` Conor Dooley
2025-10-01 2:58 ` Peng Fan
2025-10-01 15:17 ` Kamal Dasu
2025-10-01 15:28 ` Florian Fainelli
2025-10-10 10:11 ` Peng Fan
2025-09-29 20:06 ` [PATCH 1/3] dt-bindings: hwlock: support for brcmstb-hwspinlock Kamal Dasu
2025-09-30 19:04 ` Conor Dooley
2025-09-30 20:25 ` Kamal Dasu
2025-09-29 20:06 ` [PATCH 2/3] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2025-10-01 2:53 ` Peng Fan
2025-09-29 20:06 ` [PATCH 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=20250930-slapstick-volatile-60ad540f4b66@spud \
--to=conor@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=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