[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163214478703.1547258.2785345284675906680.b4-ty@sntech.de>
Date: Mon, 20 Sep 2021 16:28:38 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Brian Norris <briannorris@...omium.org>
Cc: Heiko Stuebner <heiko@...ech.de>,
linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
Chen-Yu Tsai <wenst@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] clk: rockchip: rk3399: make CPU clocks critical
On Wed, 8 Sep 2021 11:13:38 -0700, Brian Norris wrote:
> The CPU clocks don't currently have any owner (e.g., cpufreq-dt doesn't
> enable() them -- and even if it did, it's not early enough compared to
> other consumers -- nor does arch/arm64/kernel/smp.c), and instead are
> simply assumed to be "on" all the time.
>
> They are also parents of a few other clocks which haven't been
> previously exposed for other devices to consume. If we want to expose
> those clocks, then the common clock framework may eventually choose to
> disable their parents (including the CPU PLLs) -- which is no fun for
> anyone.
>
> [...]
Applied, thanks!
[1/3] clk: rockchip: rk3399: make CPU clocks critical
commit: ef087b7ecf8aaeb08a17ae825f10cd94e116616e
[2/3] clk: rockchip: rk3399: expose PCLK_COREDBG_{B,L}
commit: bd2c1f664ea647d8f66fbe083f9256511d4f2b9a
[3/3] arm64: dts: rockchip: add Coresight debug range for RK3399
commit: 75dccea503b8e176ad044175e891d7bb291b6ba0
Best regards,
--
Heiko Stuebner <heiko@...ech.de>
Powered by blists - more mailing lists