[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250410-radical-condor-from-hell-cbb910@shite>
Date: Thu, 10 Apr 2025 08:25:00 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Alex Elder <elder@...cstar.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
mturquette@...libre.com, sboyd@...nel.org, p.zabel@...gutronix.de, dlan@...too.org,
heylenay@....org, guodong@...cstar.com, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, spacemit@...ts.linux.dev,
devicetree@...r.kernel.org, linux-clk@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/7] dt-bindings: soc: spacemit: define
spacemit,k1-ccu resets
On Wed, Apr 09, 2025 at 04:17:34PM GMT, Alex Elder wrote:
> There are additional SpacemiT syscon CCUs whose registers control both
> clocks and resets: RCPU, RCPU2, and APBC2. Unlike those defined
> previously, these will (initially) support only resets. They do not
> incorporate power domain functionality.
>
> Previously the clock properties were required for all compatible nodes.
> Make that requirement only apply to the three existing CCUs (APBC, APMU,
> and MPMU), so that the new reset-only CCUs can go without specifying them.
>
> Define the index values for resets associated with all SpacemiT K1
> syscon nodes, including those with clocks already defined, as well as
> the new ones (without clocks).
>
> Signed-off-by: Alex Elder <elder@...cstar.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists