[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6b68ec7-9195-4961-86dc-802a7cc55e38@kernel.org>
Date: Tue, 14 Oct 2025 23:46:09 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kamal Dasu <kamal.dasu@...adcom.com>
Cc: peng.fan@....nxp.com, andersson@...nel.org,
baolin.wang@...ux.alibaba.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, florian.fainelli@...adcom.com,
bcm-kernel-feedback-list@...adcom.com, linux-remoteproc@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: hwlock: Adding brcmstb-hwspinlock
support
On 14/10/2025 17:40, Kamal Dasu wrote:
> On Thu, Oct 9, 2025 at 10:00 PM Krzysztof Kozlowski <krzk@...nel.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
Powered by blists - more mailing lists