[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174176555624.249409.2523115865031259262.b4-ty@sntech.de>
Date: Wed, 12 Mar 2025 08:46:01 +0100
From: Heiko Stuebner <heiko@...ech.de>
To: Jonas Karlman <jonas@...boo.se>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Detlev Casanova <detlev.casanova@...labora.com>,
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>,
Liang Chen <cl@...k-chips.com>,
Elaine Zhang <zhangqing@...k-chips.com>,
Finley Xiao <finley.xiao@...k-chips.com>,
Yifeng Zhao <yifeng.zhao@...k-chips.com>,
Nicolas Frattaroli <nicolas.frattaroli@...labora.com>
Cc: Heiko Stuebner <heiko@...ech.de>,
kernel@...labora.com,
linux-clk@...r.kernel.org,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix CPU and GPU clocks on RK3576
On Mon, 10 Mar 2025 10:59:55 +0100, Nicolas Frattaroli wrote:
> As Jonas Karlman pointed out on the #linux-rockchip IRC channel on
> Libera yesterday, mainline has once again chosen a different set of
> clock IDs compared to downstream, with hugely detrimental effects to
> mainline's ability to use SCMI for clock operations. This is because
> TF-A will use the downstream IDs, and when we reclock things through
> SCMI, TF-A will get the wrong clock ID from us.
>
> [...]
Applied, thanks!
[1/2] dt-bindings: clock: rk3576: add SCMI clocks
commit: 33a409dd1fc8be5ef8f33ebed76856c4cbc5bc15
[2/2] arm64: dts: rockchip: fix RK3576 SCMI clock IDs
commit: 825f48a12e597e7556768088b74f3384840df5e6
Best regards,
--
Heiko Stuebner <heiko@...ech.de>
Powered by blists - more mailing lists