From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Kamal Dasu <kamal.dasu@broadcom.com>,
Bjorn Andersson <andersson@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: robh@kernel.org, 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: Thu, 13 Aug 2026 16:57:58 -0700 [thread overview]
Message-ID: <d448dccd-27be-477b-8444-2574f95f7f37@broadcom.com> (raw)
In-Reply-To: <CAKekbevRigjTVMUvbOsnU0rAvWZRZnuqhnxprujvG_k4OFC0HA@mail.gmail.com>
On 8/13/26 12:25, Kamal Dasu wrote:
> On Tue, Jun 2, 2026 at 11:39 PM Florian Fainelli
> <florian.fainelli@broadcom.com> wrote:
>>
>> 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
>>
>
> Florian,
>
> Since there hasn't been a response from the hwspinlock maintainers to
> your ping from May, and given that:
>
> Krzysztof reviewed the DT bindings (Reviewed-by),
> The series is self-contained under Broadcom STB platform code and has
> no core framework changes,
>
> Could you please take this series through your Broadcom SoC tree for
> the next merge window?
I want to give Bjorn and Baolin a chance to respond, but would otherwise
have to seek help from the ARM SoCs maintainers in order to get these
patches moving forward.
--
Florian
prev parent reply other threads:[~2026-08-13 23:58 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 ` [PATCH v7 0/3] Adding brcmstb-hwspinlock support Florian Fainelli
2026-08-13 19:25 ` Kamal Dasu
2026-08-13 23:57 ` Florian Fainelli [this message]
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=d448dccd-27be-477b-8444-2574f95f7f37@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