From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: yuq825@gmail.com, dri-devel@lists.freedesktop.org
Cc: robh@kernel.org, tomeu.vizoso@collabora.com, airlied@linux.ie,
linux-kernel@vger.kernel.org, steven.price@arm.com,
linux-rockchip@lists.infradead.org, wens@csie.org,
alyssa.rosenzweig@collabora.com, daniel@ffwll.ch,
linux-amlogic@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [RFC v2 0/1] drm: lima: devfreq and cooling device support
Date: Fri, 27 Dec 2019 18:37:06 +0100 [thread overview]
Message-ID: <20191227173707.20413-1-martin.blumenstingl@googlemail.com> (raw)
This is my attempt at adding devfreq (and cooling device) support to
the lima driver.
I am seeking comments in two general areas:
- regarding the integration into the existing lima code
- for the actual devfreq code (I had to adapt the panfrost code
slightly, because lima uses a bus and a GPU/core clock)
My own TODO list includes "more" testing on various Amlogic SoCs.
So far I have tested this on Meson8b and Meson8m2 (which both have a
GPU OPP table defined). However, I still need to test this on a GXL
board (which is currently missing the GPU OPP table).
Test results from a Meson8m2 board:
TEST #1: glmark2-es2-drm --off-screen in an infinite loop while cycling
through all available frequencies using the userspace governor
From : To
: 182142857 318750000 425000000 510000000 637500000 time(ms)
182142857: 0 1274 1274 1273 1279 5399468
318750000: 1274 0 1274 1273 1272 5114700
425000000: 1276 1274 0 1272 1271 5122008
510000000: 1909 1273 1273 0 636 5274292
* 637500000: 640 1272 1272 1273 0 5186796
Total transition : 24834
TEST #2: glmark2-es2-drm --off-screen in an infinite loop with the
simple_ondemand governor
From : To
: 182142857 318750000 425000000 510000000 637500000 time(ms)
182142857: 0 0 0 0 203 318328
318750000: 53 0 0 0 21 56044
425000000: 27 18 0 0 2 34172
510000000: 27 6 14 0 1 41348
* 637500000: 95 50 33 48 0 2085312
Changes since RFC v1 at [0]:
- added lock to protect the statistics as these can be written
concurrently for example when the GP and PP IRQ are firing at the
same time. Thanks to Qiang Yu for the suggestion!
- updated the copyright notice of lima_devfreq.c to indicate that the
code is derived from panfrost_devfreq.c. Thanks to Chen-Yu Tsai for
the suggestion!
- I did not unify the code with panfrost yet because I don't know where
to put the result. any suggestion is welcome though!
[0] https://patchwork.freedesktop.org/series/70967/
Martin Blumenstingl (1):
drm/lima: Add optional devfreq support
drivers/gpu/drm/lima/Kconfig | 1 +
drivers/gpu/drm/lima/Makefile | 3 +-
drivers/gpu/drm/lima/lima_devfreq.c | 183 ++++++++++++++++++++++++++++
drivers/gpu/drm/lima/lima_devfreq.h | 15 +++
drivers/gpu/drm/lima/lima_device.c | 4 +
drivers/gpu/drm/lima/lima_device.h | 17 +++
drivers/gpu/drm/lima/lima_drv.c | 14 ++-
drivers/gpu/drm/lima/lima_sched.c | 7 ++
drivers/gpu/drm/lima/lima_sched.h | 3 +
9 files changed, 244 insertions(+), 3 deletions(-)
create mode 100644 drivers/gpu/drm/lima/lima_devfreq.c
create mode 100644 drivers/gpu/drm/lima/lima_devfreq.h
--
2.24.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-12-27 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 17:37 Martin Blumenstingl [this message]
2019-12-27 17:37 ` [RFC v2 1/1] drm/lima: Add optional devfreq support Martin Blumenstingl
2019-12-29 22:58 ` Robin Murphy
2019-12-29 23:19 ` Martin Blumenstingl
2019-12-30 0:47 ` Robin Murphy
2019-12-31 14:17 ` Martin Blumenstingl
2019-12-31 16:39 ` Robin Murphy
2019-12-31 16:47 ` Martin Blumenstingl
2020-01-01 12:55 ` Robin Murphy
2020-01-02 21:56 ` Martin Blumenstingl
2019-12-31 2:54 ` Qiang Yu
2019-12-31 14:19 ` Martin Blumenstingl
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=20191227173707.20413-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.com \
--cc=wens@csie.org \
--cc=yuq825@gmail.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).