From: Derek Basehore <dbasehore@chromium.org> To: linux-kernel@vger.kernel.org Cc: linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, tony.xie@rock-chips.com, zyw@rock-chips.com, ayaka@soulik.info, nickey.yang@rock-chips.com, zhengsq@rock-chips.com, klaus.goger@theobroma-systems.com, dianders@chromium.org, briannorris@chromium.org, enric.balletbo@collabora.com, heiko@sntech.de, mark.rutland@arm.com, robh+dt@kernel.org, Derek Basehore <dbasehore@chromium.org> Subject: [PATCH] arm64: dts: rockchip: Add 32k clk on rk3399-gru Date: Tue, 27 Nov 2018 15:23:31 -0800 [thread overview] Message-ID: <20181127232331.49628-1-dbasehore@chromium.org> (raw) This adds the 32k clock to the RK3399 Gru board file. Even though it's not directly used, muxes will end up traversing the entire clk tree on calls to determine_rate if it doesn't exist. This is because the 32k clk is listed as a possible parent on some clks. Since the clk doesn't know about the 32k clk (it was never registered), it triggers a global search for it. This can happen about 40 times per second, which isn't great for power. Signed-off-by: Derek Basehore <dbasehore@chromium.org> --- arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi index ca07f6032200..a07aa4c570c0 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi @@ -14,6 +14,13 @@ stdout-path = "serial2:115200n8"; }; + ap_rtc_clk: ap-rtc-clk { + compatible = "fixed-clock"; + clock-frequency = <32768>; + clock-output-names = "xin32k"; + #clock-cells = <0>; + }; + /* * Power Tree * -- 2.20.0.rc0.387.gc7a69e6b6c-goog
WARNING: multiple messages have this Message-ID (diff)
From: dbasehore@chromium.org (Derek Basehore) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] arm64: dts: rockchip: Add 32k clk on rk3399-gru Date: Tue, 27 Nov 2018 15:23:31 -0800 [thread overview] Message-ID: <20181127232331.49628-1-dbasehore@chromium.org> (raw) This adds the 32k clock to the RK3399 Gru board file. Even though it's not directly used, muxes will end up traversing the entire clk tree on calls to determine_rate if it doesn't exist. This is because the 32k clk is listed as a possible parent on some clks. Since the clk doesn't know about the 32k clk (it was never registered), it triggers a global search for it. This can happen about 40 times per second, which isn't great for power. Signed-off-by: Derek Basehore <dbasehore@chromium.org> --- arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi index ca07f6032200..a07aa4c570c0 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi @@ -14,6 +14,13 @@ stdout-path = "serial2:115200n8"; }; + ap_rtc_clk: ap-rtc-clk { + compatible = "fixed-clock"; + clock-frequency = <32768>; + clock-output-names = "xin32k"; + #clock-cells = <0>; + }; + /* * Power Tree * -- 2.20.0.rc0.387.gc7a69e6b6c-goog
next reply other threads:[~2018-11-27 23:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-27 23:23 Derek Basehore [this message] 2018-11-27 23:23 ` [PATCH] arm64: dts: rockchip: Add 32k clk on rk3399-gru Derek Basehore 2018-11-28 0:42 ` Doug Anderson 2018-11-28 0:42 ` Doug Anderson 2018-11-28 13:45 ` Heiko Stübner 2018-11-28 13:45 ` Heiko Stübner 2018-11-28 17:04 ` Doug Anderson 2018-11-28 17:04 ` Doug Anderson 2018-11-28 17:04 ` Doug Anderson
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20181127232331.49628-1-dbasehore@chromium.org \ --to=dbasehore@chromium.org \ --cc=ayaka@soulik.info \ --cc=briannorris@chromium.org \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=enric.balletbo@collabora.com \ --cc=heiko@sntech.de \ --cc=klaus.goger@theobroma-systems.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=mark.rutland@arm.com \ --cc=nickey.yang@rock-chips.com \ --cc=robh+dt@kernel.org \ --cc=tony.xie@rock-chips.com \ --cc=zhengsq@rock-chips.com \ --cc=zyw@rock-chips.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.