[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1936032.MyG8hOvIyE@diego>
Date: Tue, 06 Aug 2024 17:13:30 +0200
From: Heiko Stübner <heiko@...ech.de>
To: linux-kernel@...r.kernel.org, zhangqing <zhangqing@...k-chips.com>,
Detlev Casanova <detlev.casanova@...labora.com>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, kernel@...labora.com,
Finley Xiao <finley.xiao@...k-chips.com>, YouMin Chen <cym@...k-chips.com>,
Liang Chen <cl@...k-chips.com>, Sugar Zhang <sugar.zhang@...k-chips.com>
Subject: Re: [PATCH v2 3/3] clk: rockchip: Add clock controller for the RK3576
Hi Detlev,
Am Dienstag, 6. August 2024, 16:15:41 CEST schrieb Detlev Casanova:
> The suggestion from Heiko was that those reset should be managed by the
> subsystems that use them, because they are on a different offset and therefore
> seem to be on a different core.
>
> But I think I will include them here like you suggested because:
> - That's actually how it is done for rk3588 (which is quite close th rk3576),
> - According to you and the TRM, those resets are on the same core, just with
> big offsets.
>
> Having the same structure for both SoC makes sense for maintening them.
Just without the big offsets between areas please.
Similar to how rk3588 does it already.
And yep most likely they are in the same block. Just that huge block of
space for the cru somehow suggested some algamation of multiple ones,
but looking up the rk3588, you're right that it really seems to be one block.
I did request the rk3576 TRM from Rockchip - hopefully they'll follow up
with that at some point ;-) .
Heiko
Powered by blists - more mailing lists