From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kamal Dasu <kamal.dasu@broadcom.com>
Cc: 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,
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 v3 1/3] dt-bindings: hwlock: Adding brcmstb-hwspinlock support
Date: Tue, 14 Oct 2025 23:46:09 +0200 [thread overview]
Message-ID: <c6b68ec7-9195-4961-86dc-802a7cc55e38@kernel.org> (raw)
In-Reply-To: <CAKekbeuDux1oOOOKK8Pq-jYRzScCDOEXw1w=JBodaUQ4PU2=cA@mail.gmail.com>
On 14/10/2025 17:40, Kamal Dasu wrote:
> On Thu, Oct 9, 2025 at 10:00 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 09/10/2025 23:20, Kamal Dasu wrote:
>>> The broadcom settop SoCs have hardware semaphores as part of "sundry"
>>> IP block which has other controls that do not belong anywhere else.
>>> e.g. pin/mux controls, SoC identification, drive strength, reset controls,
>>> and other misc bits are part of this block.
>>
>> This does not explain why this has to be a separate block. Rob comment
>> stays valid - this belongs to parent node.
>>
>
> We do not have a separate parent node where this will fit in. We have
So what is the parent? simple bus?
> the DWORD aligned register defined here as organized in the SUNDRY
> block.
I don't know what SUNDRY is.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-14 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:20 [PATCH v3 0/3] " Kamal Dasu
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 [this message]
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=c6b68ec7-9195-4961-86dc-802a7cc55e38@kernel.org \
--to=krzk@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=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®