Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Kamal Dasu <kamal.dasu@broadcom.com>,
	andersson@kernel.org, robh@kernel.org,
	baolin.wang@linux.alibaba.com
Cc: krzysztof.kozlowski@linaro.org, conor+dt@kernel.org,
	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 v7 0/3] Adding brcmstb-hwspinlock support
Date: Tue, 2 Jun 2026 20:39:56 -0700	[thread overview]
Message-ID: <22348975-bfb1-42c9-9593-06215f961845@broadcom.com> (raw)
In-Reply-To: <20260427201233.380314-1-kamal.dasu@broadcom.com>

Hi Bjorn, Baolin,

On 4/27/2026 1:12 PM, Kamal Dasu wrote:
> This series adds hardware semaphore support for Broadcom set-top SoCs
> via the generic hwspinlock framework.
> 
> The semaphore registers live in the sundry block; the DT binding
> describes only the semaphore register range. The compatible is
> brcm,bcm7038-sun-top-ctrl-semaphore (BCM7038 is where this block first
> appeared on set-top chips).
> 
> The driver has been tested built-in and as a module.

Is there anything else you would want to see being done differently here 
or is this ready for being merged into your tree?

Thanks!
-- 
Florian



  parent reply	other threads:[~2026-06-03  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 20:12 [PATCH v7 0/3] Adding brcmstb-hwspinlock support Kamal Dasu
2026-04-27 20:12 ` [PATCH v7 1/3] dt-bindings: hwlock: " Kamal Dasu
2026-04-27 20:12 ` [PATCH v7 2/3] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2026-04-27 20:12 ` [PATCH v7 3/3] MAINTAINERS: adding entry for BRCMSTB HWSPINLOCK driver Kamal Dasu
2026-06-03  3:39 ` Florian Fainelli [this message]
2026-08-13 19:25   ` [PATCH v7 0/3] Adding brcmstb-hwspinlock support Kamal Dasu
2026-08-13 23:57     ` Florian Fainelli

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=22348975-bfb1-42c9-9593-06215f961845@broadcom.com \
    --to=florian.fainelli@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=kamal.dasu@broadcom.com \
    --cc=krzysztof.kozlowski@linaro.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