From: "Heiko Stübner" <heiko@sntech.de>
To: Klaus Goger <klaus.goger@theobroma-systems.com>
Cc: linux-rockchip@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: rockchip: add OPPs for rk3368-lion
Date: Sat, 17 Feb 2018 10:38:57 +0100 [thread overview]
Message-ID: <2925711.gDsaR89c37@diego> (raw)
In-Reply-To: <20180130123931.50781-5-klaus.goger@theobroma-systems.com>
Am Dienstag, 30. Januar 2018, 13:39:31 CET schrieb Klaus Goger:
> This adds CPU operation points for the RK3368. We only add them to the
> the RK3368-uQ7 SoM (Lion) because patches for the SoC where reverted
> in the past.
> commit 6354a06cbaa8 ("Revert "arm64: dts: rockchip: Add basic cpu
> frequencies for RK3368"")
>
> Signed-off-by: Klaus Goger <klaus.goger@theobroma-systems.com>
>
> ---
>
> arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi | 96
> ++++++++++++++++++++++++--- 1 file changed, 88 insertions(+), 8
> deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi
> b/arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi index
> 72be1ae0854f..881f0b44c5b5 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi
> @@ -11,6 +11,70 @@
> stdout-path = "serial0:115200n8";
> };
>
> + cluster0_opp: opp-table0 {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp00 {
> + opp-hz = /bits/ 64 <408000000>;
> + opp-microvolt = <950000 950000 1350000>;
> + clock-latency-ns = <40000>;
> + };
> + opp01 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <950000 950000 1350000>;
> + };
> + opp02 {
> + opp-hz = /bits/ 64 <816000000>;
> + opp-microvolt = <975000 975000 1350000>;
> + };
> + opp03 {
> + opp-hz = /bits/ 64 <1008000000>;
> + opp-microvolt = <1050000 1050000 1350000>;
> + };
> + opp04 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <1150000 1150000 1350000>;
> + };
> + opp05 {
> + opp-hz = /bits/ 64 <1416000000>;
> + opp-microvolt = <1300000 1300000 1350000>;
> + turbo-mode;
> + };
> + opp06 {
> + opp-hz = /bits/ 64 <1512000000>;
> + opp-microvolt = <1300000 1300000 1350000>;
> + turbo-mode;
> + };
> + };
> +
> + cluster1_opp: opp-table1 {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp00 {
> + opp-hz = /bits/ 64 <408000000>;
> + opp-microvolt = <950000 950000 1350000>;
> + clock-latency-ns = <40000>;
> + };
> + opp01 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <950000 950000 1350000>;
> + };
> + opp02 {
> + opp-hz = /bits/ 64 <816000000>;
> + opp-microvolt = <1025000 1025000 1350000>;
> + };
> + opp03 {
> + opp-hz = /bits/ 64 <1008000000>;
> + opp-microvolt = <1125000 1125000 1350000>;
> + };
> + opp04 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <1225000 1225000 1350000>;
> + };
> + };
> +
> ext_gmac: gmac-clk {
> compatible = "fixed-clock";
> clock-frequency = <125000000>;
> @@ -239,36 +303,52 @@
> status = "okay";
> };
>
> -&cpu_l0 {
> +&cpu_b0 {
> + clocks = <&cru ARMCLKB>;
> cpu-supply = <&vdd_cpu>;
> + operating-points-v2 = <&cluster0_opp>;
> };
Looks ok for the time being until we have working general OPPs
for rk3368 but can you please adapt the patch to not unecessarily
touch the &cpu_XX handles?
Thanks
Heiko
prev parent reply other threads:[~2018-02-17 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 12:39 [PATCH 0/4] add RK3368-uQ7 SoM Klaus Goger
2018-01-30 12:39 ` [PATCH 1/4] dt-bindings: add RK3368-uQ7 SoM and EVK base board Klaus Goger
2018-02-17 9:27 ` Heiko Stübner
2018-01-30 12:39 ` [PATCH 2/4] arm64: dts: rockchip: add RK3368-uQ7 (Lion) SoM Klaus Goger
2018-02-17 9:28 ` Heiko Stübner
2018-01-30 12:39 ` [PATCH 3/4] arm64: dts: rockchip: add Haikou baseboard with RK3368-uQ7 SoM Klaus Goger
2018-02-17 9:28 ` Heiko Stübner
2018-01-30 12:39 ` [PATCH 4/4] arm64: dts: rockchip: add OPPs for rk3368-lion Klaus Goger
2018-02-17 9:38 ` Heiko Stübner [this message]
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=2925711.gDsaR89c37@diego \
--to=heiko@sntech.de \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox