From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl1-f225.google.com (mail-pl1-f225.google.com [209.85.214.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C1EB333BBB1 for ; Tue, 24 Feb 2026 22:04:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.225 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771970657; cv=none; b=u+2zA4Q3zunjwfEveALEqhBOy54Fj07QjIIzzCjo8y3XWs6NtzpbqgAhyRp/MbxsHluyw6Fr3j5hyq9Ck9mG7PXzHPanS9zs0Gvjbiu8497ge4EbVjG/ud77tnzhmjg8xv8s+Nyeb+v6RYgZHCbDqrIGcUiKbZL223gdbbcDGB4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771970657; c=relaxed/simple; bh=mbwRB4ZGvL4g1BgK0BDf89bAQ8LmFkBZL5/b0mRW7iA=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=l/FsXNJnJSyOy3Ul8t9WgFaS0nEPBVUY9o9pWeinL5D36dAT3+mY67EAEQW7SRjBeeJbTP7vmeXaiAB0m73AeayU4lA0gEouvQba0KS41EMu5bfDUdKyzoQ3zBGJy5wxi9KiS2S8k7yDXdAZvM1zLlSnW5rKUqujJSlkfAkv/ks= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=broadcom.com; spf=fail smtp.mailfrom=broadcom.com; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b=VsUznEyF; arc=none smtp.client-ip=209.85.214.225 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=broadcom.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=broadcom.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="VsUznEyF" Received: by mail-pl1-f225.google.com with SMTP id d9443c01a7336-2ad617d5b80so37988375ad.1 for ; Tue, 24 Feb 2026 14:04:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771970656; x=1772575456; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:dkim-signature:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=/7wTU2wqO3eKHYFN8DRzgtidY91chf6u6I995CUEKtM=; b=JxcNwJUPwGc/3cexEgVWxUWlNPllrvCdjJDniEOMgy1cDP0vE+CbFk9Spmbwzs5cPZ PpbPy/aASWpSGihWaumy+0NY37hXKkzr8KTSPKSoCn1lxBzZwpkgZMix3hetq//NVLz3 4+R8rZ8zvWqH9G6j+wA66kitTk62BbzeM99e6pLJ8pbhCyCAfJadTPauvYKfjLjE6suI aUl2zinBTBsbkXKkQSAnfnzOnqeQvlGoc52W02Ghx/C7gt1b0GMIGXLLnXcqYX4OwqLF FVTtDrwaf45htTCZf4RSbqXBjHCuF3Kq3P/Vh7xGqOrfiiiCfBNe+vTfJ868C1tTtsMO zUaw== X-Forwarded-Encrypted: i=1; AJvYcCUc4VWErbkO3AMjhsCKT5pp61qFuZqvnNfsXXYtw0pzjFZ1Gh0y2tF6Xw1EgcZfYvvLX6txLmFcDT4ZxDk=@vger.kernel.org X-Gm-Message-State: AOJu0Yxp94a9U2SV0509+wjlYZ8CL/AjTpBdvwxowvvCsYUQT5Afz7uD Vu1OkI7W7ZtTuWAm8fuwT8jnWjhwnccxHWKY0RT0cWRdfrs7QAQMsBA1TkW6rFR76lFl0jUrrvp qcX/vSAGz6lXkK4KqstQmj0QLGYhHyQ/OtSY6VHtwOfiihBDq921d7qimnnXIH4QeSmgxoGPKWo G0n/RVSCHSijPGjf0k3wfvDssbPma/sGb2+ttr9yLHxYRRuEKw/Xv/QecyNATB19irSE3StUrz8 bSQNYfUNR/INXJK X-Gm-Gg: ATEYQzwgJSHpS/WaT2gxcyv153m0v+jmVFNSYg/FZGV9Q+xcQ6mHPHmjuTvSfkhcBi6 +OQs69bqNh2DPgjWyXcYTUUvBEvkA8go3Qz9GsWV1mBbqF2Nl0KFejwUsKv91YAAjsrfK0ed2+x xgtN57Rld4C0XXSmfXm9EMcBqnHfJVbw9uaao3Qb1MqV2OzD6riG4m7xw/+4bffYRWN5KEFSCr0 W6hQvdMeAMD5fHB7HhWNAnY6pAGu/TkMZ452TbPi+usNTmk4FRvb9XKFIInhBE2JiiJnwXeh5ZR EaekK01YThIbXH+hE876fi2+d2nxLWPv40dGj4+wn8IVficEMmmt0YsJ5H/C9XcdgtssMrHIEXe NmkaaL5eRfHECYR9jRB1KCYWeQevtIJBLZGUmdODIAsQUn3FaZSyDYwSZqvWMjBGnLx3IgcUfSm +VA9Au8RpReQOcAkrXz7VR3fLt3BsnpFjG6B5wP1QnuDacR8QjAIYCLs39 X-Received: by 2002:a17:902:e94e:b0:2ad:9326:3c3d with SMTP id d9443c01a7336-2ad93263e35mr41666595ad.54.1771970656160; Tue, 24 Feb 2026 14:04:16 -0800 (PST) Received: from smtp-us-east1-p01-i01-si01.dlp.protect.broadcom.com (address-144-49-247-103.dlp.protect.broadcom.com. [144.49.247.103]) by smtp-relay.gmail.com with ESMTPS id d9443c01a7336-2add580dfcasm5985ad.46.2026.02.24.14.04.15 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2026 14:04:16 -0800 (PST) X-Relaying-Domain: broadcom.com X-CFilter-Loop: Reflected Received: by mail-dy1-f197.google.com with SMTP id 5a478bee46e88-2bdb0c8c5bcso622526eec.1 for ; Tue, 24 Feb 2026 14:04:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1771970654; x=1772575454; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=/7wTU2wqO3eKHYFN8DRzgtidY91chf6u6I995CUEKtM=; b=VsUznEyFEW3/uiZMAGgCnLmPQNcFcIPyXBBvOhT3eBn2xKK2JBIeMTSydkX2ZpxGaU 5i+WGFa2p2DPdFhrAtNaMuCSMRwr582aNKLbd5tPWCfPDJH+WeIvT8wcfr9N20q5doLK wNJ26mS4iENkPOdZTDf9ZMRGEOyUklod04sKw= X-Forwarded-Encrypted: i=1; AJvYcCWnNudcIc4j09cLiDm4QoYmwZ0Q1I4/Z+98tNepuqifmsvpXGAobuJEfGSSncrOGowzEBWuhASl6RLisA0=@vger.kernel.org X-Received: by 2002:a05:7300:bc0e:b0:2ba:8f47:fe4f with SMTP id 5a478bee46e88-2bd7bd24d3dmr6232099eec.18.1771970654375; Tue, 24 Feb 2026 14:04:14 -0800 (PST) X-Received: by 2002:a05:7300:bc0e:b0:2ba:8f47:fe4f with SMTP id 5a478bee46e88-2bd7bd24d3dmr6232074eec.18.1771970653607; Tue, 24 Feb 2026 14:04:13 -0800 (PST) Received: from mail.broadcom.net ([192.19.144.250]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-2bdb055507bsm2374822eec.0.2026.02.24.14.04.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Feb 2026 14:04:13 -0800 (PST) From: Kamal Dasu To: andersson@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org Cc: baolin.wang@linux.alibaba.com, 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, Kamal Dasu Subject: [PATCH v6 0/3] Adding brcmstb-hwspinlock support Date: Tue, 24 Feb 2026 17:04:04 -0500 Message-Id: <20260224220407.2351692-1-kamal.dasu@broadcom.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-DetectorID-Processed: b00c1d49-9d2e-4205-b15f-d015386d3d5e This is a standalone patch for the hardware semaphore feature for all brcmstb SoCs that have the same hardware semaphore registers. The semaphore registers belong to the sundry hardware block. The node describes only the semaphore register range carved out of the larger sundry block address space. The compatible string uses "brcm,bcm7038-sun-top-ctrl-semaphore" based on the BCM7038 SoC where the semaphore registers were first introduced in settop chips. The patch has been tested to work as builtin as well as a module. v6 changes: Addressed review comments from Krzysztof Kozlowski: - Renamed DT binding YAML file from "brcm,brcmstb-hwspinlock.yaml" to "brcm,bcm7038-sun-top-ctrl-semaphore.yaml" to match the compatible string - Updated $id in the YAML to match the new filename - Updated MAINTAINERS F: entry to match the new filename v5 changes: Addressed review comments from Krzysztof Kozlowski: - Changed compatible to "brcm,bcm7038-sun-top-ctrl-semaphore" using the SoC where the semaphore hardware was first introduced, following the brcm,bcm7038-l1-intc convention v4 changes: Addressed review comments from Krzysztof Kozlowski and Rob Herring: - Renamed compatible from "brcm,brcmstb-hwspinlock" to "brcm,brcmstb-sun-top-ctrl-semaphore" to use the hardware name - Added description block to the DT binding YAML explaining what the semaphore registers are and their relationship to the sundry block - Fixed typo in Kconfig "Setttop" -> "Settop" - Fixed email typo in MODULE_AUTHOR v3 changes: Added detailed explanation 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 common compatible string v2 changes: Addressed 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 platform_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: Link: https://github.com/intel-lab-lkp/linux/commits/ Kamal-Dasu/dt-bindings-brcmstb-hwspinlock-support- for-hwspinlock/20250712-034624 Link: https://lore.kernel.org/r/20250711154221.928164- 4-kamal.dasu%40broadcom.com [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 .../brcm,bcm7038-sun-top-ctrl-semaphore.yaml | 45 +++++++++ MAINTAINERS | 8 ++ drivers/hwspinlock/Kconfig | 11 ++- drivers/hwspinlock/Makefile | 1 + drivers/hwspinlock/brcmstb_hwspinlock.c | 96 +++++++++++++++++++ 5 files changed, 160 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,bcm7038-sun-top-ctrl-semaphore.yaml create mode 100644 drivers/hwspinlock/brcmstb_hwspinlock.c -- 2.34.1