public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: rockchip: introduce rk3399-op1 operating points
Date: Tue, 23 May 2017 18:10:01 +0200	[thread overview]
Message-ID: <1597629.2TFUO1J4Mt@phil> (raw)
In-Reply-To: <CAD=FV=XbUjuvt+ctm8Xw6JPqe7m4PdyZ1hm3Uast2+1+nJ=nPw@mail.gmail.com>

Am Dienstag, 23. Mai 2017, 08:57:01 CEST schrieb Doug Anderson:
> Hi,
> 
> On Tue, May 23, 2017 at 2:51 AM, Heiko Stuebner <heiko@sntech.de> wrote:
> > The OP1 is a rk3399 variant used in ChromeOS devices with a slightly
> > higher frequency rating. Therefore introduce separate operting points,
> > from the ChromeOS tree, for it and use it in Gru devices.
> >
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> >  arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi     |   2 +-
> >  arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi | 145 +++++++++++++++++++++++
> >  2 files changed, 146 insertions(+), 1 deletion(-)
> >  create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
> 
> The numbers here match what's in the Chrome OS tree and those were all
> approved by Rockchip.
> 
> One slight nit is that the descriptions these two patches together
> make it look like this will be a no-op change for OP1 devices.  This
> is not true.  After things were posted upstream there have been
> several adjustments to the opp points in the Chrome OS tree.  Since
> what you have currently matches the ToT Chrome OS tree, that should
> mean that there's a net difference.  It would be nice to mention that
> in the commit message.

In the mainline kernel it is a no-op change, as we're still running with
the cpu-regulators disabled on gru ;-)

But to address your very valid point, I guess you mean something like

----
The OP1 is a rk3399 variant used in ChromeOS devices with a slightly
higher frequency rating compared to the regular rk3399, but right now
the only available operating points are somewhere in between both
variants with both needing adjustments to actually fit their specs.

Therefore introduce separate operting points, from the ChromeOS kernel,
for the OP1 and use it on Gru devices.
----

And I guess we should also swap patch ordering, first move Gru away from
the general opps and then adust them for the regular rk3399.


> Other than that small nit:
> 
> Reviewed-by: Douglas Anderson <dianders@chromium.org>


Heiko

  reply	other threads:[~2017-05-23 16:10 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
2017-05-23  9:51 ` [PATCH 2/2] arm64: dts: rockchip: introduce rk3399-op1 " Heiko Stuebner
2017-05-23 15:57   ` Doug Anderson
2017-05-23 16:10     ` Heiko Stuebner [this message]
2017-05-23 16:35       ` Doug Anderson
2017-05-23 16:38         ` Heiko Stuebner
2017-05-30 10:13 ` [PATCH 1/2] arm64: dts: rockchip: update common rk3399 " Heiko Stuebner

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=1597629.2TFUO1J4Mt@phil \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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