From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: eddie.cai.linux@gmail.com, briannorris@chromium.org,
dianders@chromium.org, linux-arm-kernel@lists.infradead.org,
wxt@rock-chips.com
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: update common rk3399 operating points
Date: Tue, 30 May 2017 12:13:19 +0200 [thread overview]
Message-ID: <83138441.zQW9Y5vCCV@phil> (raw)
In-Reply-To: <20170523095109.7337-1-heiko@sntech.de>
Am Dienstag, 23. Mai 2017, 11:51:08 CEST schrieb Heiko Stuebner:
> The rk3399 has multiple variants with different frequency ratings.
> The operating points currently in the kernel stem from the op1 variant
> used in Gru ChromeOS devices and may not be suitable for general rk3399
> chips. Therefore bring it back to the official general operating points.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
applied both for 4.13 with the description in patch2 fixed and
having the patches in reverse order, as discussed in patch2.
Heiko
prev parent reply other threads:[~2017-05-30 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 9:51 [PATCH 1/2] arm64: dts: rockchip: update common rk3399 operating points Heiko Stuebner
[not found] ` <20170523095109.7337-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2017-05-23 9:51 ` [PATCH 2/2] arm64: dts: rockchip: introduce rk3399-op1 " Heiko Stuebner
2017-05-23 15:57 ` Doug Anderson
[not found] ` <CAD=FV=XbUjuvt+ctm8Xw6JPqe7m4PdyZ1hm3Uast2+1+nJ=nPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-23 16:10 ` Heiko Stuebner
2017-05-23 16:35 ` Doug Anderson
[not found] ` <CAD=FV=WjwDd6VmeWmMxBb0_kE78zsbqiqxg7u4zXQy6LWWPV6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-23 16:38 ` Heiko Stuebner
2017-05-30 10:13 ` Heiko Stuebner [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=83138441.zQW9Y5vCCV@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=eddie.cai.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wxt@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: 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