From: Kamal Dasu <kamal.dasu@broadcom.com>
To: peng.fan@oss.nxp.com, andersson@kernel.org,
baolin.wang@linux.alibaba.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
florian.fainelli@broadcom.com
Cc: 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,
Kamal Dasu <kamal.dasu@broadcom.com>
Subject: [PATCH v3 0/3] Adding brcmstb-hwspinlock support
Date: Thu, 9 Oct 2025 17:20:00 -0400 [thread overview]
Message-ID: <20251009212003.2714447-1-kamal.dasu@broadcom.com> (raw)
This is a standalone patch for the hardware semaphore feature for
all brcmstb SoCs that have the same hardware semaphore registers
hence platform driver compatible uses:
'.compatible = "brcm,brcmstb-hwspinlock"'
The patch has been tested to work as builtin as well as a module.
v3 changes:
Added detailed explantion in the all commit messages as per review
comments
- Added description of 'sundry' ip block that the hardware semaphore
belongs to
- Added reasoning for using '.compatible = "brcm,brcmstb-hwspinlock"
v2 changes:
Adressed following review comments:
- fixed ordering of obj brcmstb_hwspinlock.o in Makefile
- fixed ordering of 'config HWSPINLOCK_BRCMSTB' block in Kconfig
- Renamed BRCMSTB_MAX_SEMAPHORES to BRCMSTB_NUM_SEMAPHORES
- Removed unnecessary platfrom_set_drvdata(pdev, bank);
Also addressing duplicate PATCH 1/3 sent in error as part of v1 change.
v1 changes:
based on fixes made to Initial patch :
url: https://github.com/intel-lab-lkp/linux/commits/Kamal-Dasu/dt-bindings-brcmstb-hwspinlock-support-for-hwspinlock/20250712-034624
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20250711154221.928164-4-kamal.dasu%40broadcom.com
patch subject: [PATCH 2/4] hwspinlock: brcmstb hardware semaphore support
All the review comments and build warning have been fixed.
Kamal Dasu (3):
dt-bindings: hwlock: Adding brcmstb-hwspinlock support
hwspinlock: brcmstb hardware semaphore support
MAINTAINERS: adding entry for BRCMSTB HWSPINLOCK driver
.../hwlock/brcm,brcmstb-hwspinlock.yaml | 36 +++++++
MAINTAINERS | 8 ++
drivers/hwspinlock/Kconfig | 11 ++-
drivers/hwspinlock/Makefile | 1 +
drivers/hwspinlock/brcmstb_hwspinlock.c | 96 +++++++++++++++++++
5 files changed, 151 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
create mode 100644 drivers/hwspinlock/brcmstb_hwspinlock.c
--
2.34.1
next reply other threads:[~2025-10-09 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:20 Kamal Dasu [this message]
2025-10-09 21:20 ` [PATCH v3 1/3] dt-bindings: hwlock: " Kamal Dasu
2025-10-10 2:00 ` Krzysztof Kozlowski
2025-10-14 15:40 ` Kamal Dasu
2025-10-14 21:46 ` Krzysztof Kozlowski
2025-10-14 22:01 ` Florian Fainelli
2025-10-09 21:20 ` [PATCH v3 2/3] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2025-10-09 21:20 ` [PATCH v3 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=20251009212003.2714447-1-kamal.dasu@broadcom.com \
--to=kamal.dasu@broadcom.com \
--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=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 \
--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
all inboxes | Powered by JetHome®