From: Heiko Stuebner <heiko@sntech.de>
To: Brian Norris <briannorris@chromium.org>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Caesar Wang <wxt@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: set rk3399 dynamic CPU power coefficients
Date: Wed, 28 Jun 2017 17:45:03 +0200 [thread overview]
Message-ID: <3456973.xqkASENUTq@phil> (raw)
In-Reply-To: <20170623170737.46265-3-briannorris@chromium.org>
Am Freitag, 23. Juni 2017, 10:07:37 CEST schrieb Brian Norris:
> Provide the dynamic power coefficient of the big and little CPU
> clusters. These numbers are currently in use on the Samsung Chromebook
> Plus ("Kevin").
>
> The power allocator thermal governor doesn't know how to do anything if
> it doesn't get power parameters from its cooling devices (in this case,
> CPUfreq). So this effectively enables the power-allocator governor.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
applied for 4.14 after extending the property to all cpu cores.
Thanks
Heiko
next prev parent reply other threads:[~2017-06-28 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 17:07 [PATCH 1/3] arm64: dts: rockchip: Update CPU regulator voltage ranges for Gru Brian Norris
2017-06-23 17:07 ` [PATCH 2/3] arm64: dts: rockchip: Use vctrl regulators for dynamic CPU voltages on Gru/Kevin Brian Norris
2017-06-28 15:44 ` Heiko Stuebner
2017-06-29 20:53 ` Brian Norris
2017-06-23 17:07 ` [PATCH 3/3] arm64: dts: rockchip: set rk3399 dynamic CPU power coefficients Brian Norris
2017-06-23 18:39 ` Heiko Stuebner
2017-06-23 18:49 ` Brian Norris
2017-06-23 18:59 ` Heiko Stuebner
2017-06-28 15:45 ` Heiko Stuebner [this message]
2017-06-28 15:41 ` [PATCH 1/3] arm64: dts: rockchip: Update CPU regulator voltage ranges for Gru 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=3456973.xqkASENUTq@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mka@chromium.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;
as well as URLs for NNTP newsgroup(s).