From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Peng Fan <peng.fan@oss.nxp.com>, Kamal Dasu <kamal.dasu@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com, andersson@kernel.org,
baolin.wang@linux.alibaba.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: hwlock: Adding brcmstb-hwspinlock support
Date: Wed, 1 Oct 2025 08:28:33 -0700 [thread overview]
Message-ID: <68e10834-0c1a-4cbe-be0b-76e17f8341e0@broadcom.com> (raw)
In-Reply-To: <20251001025817.GB23170@nxa18884-linux.ap.freescale.net>
On 9/30/2025 7:58 PM, Peng Fan wrote:
> On Mon, Sep 29, 2025 at 04:06:24PM -0400, Kamal Dasu wrote:
>> Adding brcmstb-hwspinlock bindings.
>>
>> Signed-off-by: Kamal Dasu <kamal.dasu@broadcom.com>
>> ---
>> .../hwlock/brcm,brcmstb-hwspinlock.yaml | 36 +++++++++++++++++++
>> 1 file changed, 36 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
>>
>> + - |
>> + hwlock@8404038 {
>> + compatible = "brcm,brcmstb-hwspinlock";
>> + reg = <0x8404038 0x40>;
>
> Just have a question:
> the base is not 64KB aligned, so just want to know is this module part of
> the other ip block?
The alignment is relevant to determine whether this is part of a larger
IP block or not, though I am not sure why you use 64KB as a criteria.
Our HW rules are to match the highest OS available page size for the
systems, for us it used to be 4KB and is now 16KB alignment.
The block is part of a "sundry" IP which has lots of controls that did
not belong anywhere else, for better or for worse (pin/mux controls, SoC
identification, drive strength, reset controls, and other misc bits).
--
Florian
next prev parent reply other threads:[~2025-10-01 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 20:06 [PATCH 0/3] Adding brcmstb-hwspinlock support Kamal Dasu
2025-09-29 20:06 ` [PATCH 1/3] dt-bindings: hwlock: " Kamal Dasu
2025-09-30 19:03 ` Conor Dooley
2025-09-30 19:09 ` Florian Fainelli
2025-09-30 19:34 ` Conor Dooley
2025-10-01 2:58 ` Peng Fan
2025-10-01 15:17 ` Kamal Dasu
2025-10-01 15:28 ` Florian Fainelli [this message]
2025-10-10 10:11 ` Peng Fan
2025-09-29 20:06 ` [PATCH 1/3] dt-bindings: hwlock: support for brcmstb-hwspinlock Kamal Dasu
2025-09-30 19:04 ` Conor Dooley
2025-09-30 20:25 ` Kamal Dasu
2025-09-29 20:06 ` [PATCH 2/3] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2025-10-01 2:53 ` Peng Fan
2025-09-29 20:06 ` [PATCH 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=68e10834-0c1a-4cbe-be0b-76e17f8341e0@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=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