From: Caesar Wang <wxt@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Elaine Zhang <zhangqing@rock-chips.com>,
Will Deacon <will.deacon@arm.com>,
Kever Yang <kever.yang@rock-chips.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Matthias Kaehlcke <mka@chromium.org>,
Klaus Goger <klaus.goger@theobroma-systems.com>,
Mark Rutland <mark.rutland@arm.com>,
Roger Chen <roger.chen@rock-chips.com>,
William wu <wulf@rock-chips.com>,
rocky.hao@rock-chips.com, linux-arm-kernel@lists.infradead.org,
Caesar Wang <wxt@rock-chips.com>
Subject: [PATCH 0/4] arm64: dts: rockchip: support mail and IPA thermal for rk3399
Date: Wed, 12 Jul 2017 14:29:26 +0800 [thread overview]
Message-ID: <1499840971-20392-1-git-send-email-wxt@rock-chips.com> (raw)
This series patches supported the mail in devicetree and used the
thermal IPA by default.
Verified with rk3399 kevin board on my github
https://github.com/Caesar-github/rockchip/commits/gru/next-stable-chromeos
The kernel is based on Linus's master branch and Heiko's
v4.14-armsoc-tmp/dts64 branch. ( The Linux version 4.12.0 for now).
---
Tested on Kevin board with bringing up ChromeOS.
OS VERSION:
CHROMEOS_RELEASE_DESCRIPTION=9693.1.0 (Official Build) dev-channel kevin test
BIOS VERSION:
Google_Kevin.8785.211.2017_06_20_1043
EC VERSION:
Build info: kevin_v1.10.217-24514961d 2017-07-03 07:46:36 wxt@nb
With the ARM's lastest mali driver TX011-SW-99002-r18p0-01rel0 on
https://developer.arm.com/products/software/mali-drivers/midgard-kernel
From the bootup log:
localhost devfreq0 # dmesg |grep mali
[ 0.933334] mali ff9a0000.gpu: GPU identified as 0x0860 r2p0 status 0
[ 0.940830] mali ff9a0000.gpu: Protected mode not available
[ 0.947334] mali ff9a0000.gpu: Using configured power model mali-simple-power-model, and fallback mali-simple-power-model
[ 0.960083] mali ff9a0000.gpu: Probed as mali0
localhost devfreq0 # pwd
/sys/devices/platform/ff9a0000.gpu/devfreq/devfreq0
localhost devfreq0 # ls
available_frequencies device min_freq subsystem uevent
available_governors governor polling_interval target_freq userspace
cur_freq max_freq power trans_stat
localhost ff9a0000.gpu # ls
core_availability_policy gpuinfo modalias soft_job_timeout
core_mask js_scheduling_period of_node subsystem
devfreq js_timeouts pm_poweroff uevent
driver mem_pool_max_size power
driver_override mem_pool_size power_policy
dvfs_period misc reset_timeout
---
And for thermal with IPA.
Try to run 'md5sum /dev/zero &' and octane/benchmark scripts to go up the temperature.
From the scripts to have a look at the actual control.
"
while true; do grep "" /sys/class/thermal/thermal_zone[0-1]/temp /sys/devices/system/cpu/cpu[0-5]/cpufreq/scaling_cur_freq /sys/devices/platform/ff9a0000.gpu/devfreq/ff9a0000.gpu/cur_freq;date;sleep .5; done &
"
-Caesar
Caesar Wang (4):
dt-bindings: gpu: add the RK3399 mali for rockchip specifics
arm64: dts: rockchip: add ARM Mali GPU node for RK3399 SoCs
arm64: dts: rockchip: enable the GPU for RK3399-GRU
arm64: dts: rockchip: update the thermal zones for RK3399 SoCs
.../devicetree/bindings/gpu/arm,mali-midgard.txt | 1 +
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 5 ++
arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi | 33 +++++++++
arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi | 33 +++++++++
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 78 +++++++++++++---------
5 files changed, 117 insertions(+), 33 deletions(-)
--
2.7.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-07-12 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 6:29 Caesar Wang [this message]
2017-07-12 6:29 ` [PATCH 1/4] dt-bindings: gpu: add the RK3399 mali for rockchip specifics Caesar Wang
[not found] ` <1499840971-20392-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-12 6:29 ` [PATCH 2/4] arm64: dts: rockchip: add ARM Mali GPU node for RK3399 SoCs Caesar Wang
[not found] ` <1499840971-20392-3-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-12 7:19 ` Heiko Stuebner
2017-07-12 9:16 ` Caesar Wang
2017-07-12 6:29 ` [PATCH 3/4] arm64: dts: rockchip: enable the GPU for RK3399-GRU Caesar Wang
2017-07-12 6:29 ` [PATCH 4/4] arm64: dts: rockchip: update the thermal zones for RK3399 SoCs Caesar Wang
2017-07-12 17:32 ` Brian Norris
2017-07-13 1:01 ` Caesar Wang
[not found] ` <1499840971-20392-5-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-12 18:44 ` Heiko Stuebner
2017-07-13 2:06 ` Caesar Wang
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=1499840971-20392-1-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=rocky.hao@rock-chips.com \
--cc=roger.chen@rock-chips.com \
--cc=shawn.lin@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=wulf@rock-chips.com \
--cc=zhangqing@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).