[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251001025817.GB23170@nxa18884-linux.ap.freescale.net>
Date: Wed, 1 Oct 2025 10:58:17 +0800
From: Peng Fan <peng.fan@....nxp.com>
To: Kamal Dasu <kamal.dasu@...adcom.com>
Cc: bcm-kernel-feedback-list@...adcom.com, andersson@...nel.org,
baolin.wang@...ux.alibaba.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, florian.fainelli@...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 1/3] dt-bindings: hwlock: Adding brcmstb-hwspinlock
support
On Mon, Sep 29, 2025 at 04:06:24PM -0400, Kamal Dasu wrote:
>Adding brcmstb-hwspinlock bindings.
>
>Signed-off-by: Kamal Dasu <kamal.dasu@...adcom.com>
>---
> .../hwlock/brcm,brcmstb-hwspinlock.yaml | 36 +++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
>
>+ - |
>+ hwlock@...4038 {
>+ 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?
Thanks,
Peng
>+ #hwlock-cells = <1>;
>+ };
>+
>--
>2.34.1
>
Powered by blists - more mailing lists