clk: rockchip: rk3399: make CPU clocks critical
authorBrian Norris <briannorris@chromium.org>
Wed, 8 Sep 2021 18:13:38 +0000 (11:13 -0700)
committerHeiko Stuebner <heiko@sntech.de>
Mon, 20 Sep 2021 13:12:23 +0000 (15:12 +0200)
commitef087b7ecf8aaeb08a17ae825f10cd94e116616e
tree0a09f47ee687f14bbc497f8c694c40459a84a23a
parent6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f
clk: rockchip: rk3399: make CPU clocks critical

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.

Thus, mark the CPU clocks as critical, to prevent them from being
disabled implicitly.

Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Link: https://lore.kernel.org/r/20210908111337.v2.1.I006bb36063555079b1a88f01d20e38d7e4705ae0@changeid
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
drivers/clk/rockchip/clk-rk3399.c