From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: "Leonidas P. Papadakos"
<papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] arm64: dts: rockchip: add more cpu operating points for RK3328
Date: Fri, 01 Mar 2019 19:24:12 +0100 [thread overview]
Message-ID: <29290155.VRdV4K0DQe@phil> (raw)
In-Reply-To: <20190301175452.6701-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi,
Am Freitag, 1. März 2019, 18:54:53 CET schrieb Leonidas P. Papadakos:
> This allows for greater max frequency on rk3328 boards,
> increasing performance.
>
> It has been included in Armbian (a linux distibution for ARM boards)
> for a while now without any reported issues
>
> https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-default/enable-1392mhz-opp.patch
> https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-default/enable-1512mhz-opp.patch
>
> Cc: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
> Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> Signed-off-by: Leonidas P. Papadakos <papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index 84f14b132..18caef3c3 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -123,6 +123,20 @@
> opp-microvolt = <1300000>;
> clock-latency-ns = <40000>;
> };
> + opp-1392000000 {
> + opp-hz = /bits/ 64 <1392000000>;
> + opp-microvolt = <1350000 1350000 1350000>;
> + opp-microvolt-L0 = <1350000 1350000 1350000>;
> + opp-microvolt-L1 = <1325000 1325000 1325000>;
I checked Rockchip's productpage and the chip really seems to be
rated up to 1.5GHz, but you should get rid of opp-microvolt-Lx
options as these are still vendor-specific regarding the leakage
handling.
While on it, when all microvolt elements are the same, using the
absolute value instead of "preferred min max" saves a bit of space
similar to the other OPPs in the file.
Thanks
Heiko
> + clock-latency-ns = <40000>;
> + };
> + opp-1512000000 {
> + opp-hz = /bits/ 64 <1512000000>;
> + opp-microvolt = <1450000 1450000 1450000>;
> + opp-microvolt-L0 = <1450000 1450000 1450000>;
> + opp-microvolt-L1 = <1425000 1425000 1425000>;
> + clock-latency-ns = <40000>;
> + };
> };
>
> amba {
>
next prev parent reply other threads:[~2019-03-01 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 17:54 [PATCH] arm64: dts: rockchip: add more cpu operating points for RK3328 Leonidas P. Papadakos
[not found] ` <20190301175452.6701-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-01 18:24 ` Heiko Stuebner [this message]
2019-03-01 19:33 ` Jonas Karlman
[not found] ` <AM3PR03MB0966D92B504944D7C6D06123AC760-XQTXrJX/giFAc9da7WRX18eAHadYHfrlvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-03-05 7:48 ` [PATCH] arm64: dts: rockchip: add more cpu operating points for RK3328【请注意,邮件由linux-rockchip-bounces+cl=rock-chips.com@lists.infradead.org代发】 陈亮
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=29290155.VRdV4K0DQe@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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