From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: yuq825@gmail.com, dri-devel@lists.freedesktop.org,
lima@lists.freedesktop.org, airlied@linux.ie, daniel@ffwll.ch,
linux-kernel@vger.kernel.org, tomeu.vizoso@collabora.com,
robh@kernel.org, steven.price@arm.com,
linux-amlogic@lists.infradead.org,
linux-rockchip@lists.infradead.org, wens@csie.org
Subject: Re: [RFC v1 0/1] drm: lima: devfreq and cooling device support
Date: Mon, 16 Dec 2019 10:48:03 -0500 [thread overview]
Message-ID: <20191216154803.GA3921@kevin> (raw)
In-Reply-To: <20191215211223.1451499-1-martin.blumenstingl@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
If so much code is being duplicated over, I'm wondering if it makes
sense for us to move some of the common devfreq code to core DRM
helpers?
On Sun, Dec 15, 2019 at 10:12:22PM +0100, Martin Blumenstingl wrote:
> This is my attempt at adding devfreq (and cooling device) support to
> the lima driver.
> I didn't have much time to do in-depth testing. However, I'm sending
> this out early because there are many SoCs with Mali-400/450 GPU so
> I want to avoid duplicating the work with somebody else.
>
> The code is derived from panfrost_devfreq.c which is why I kept the
> Collabora copyright in lima_devfreq.c. Please let me know if I should
> drop this or how I can make it more clear that I "borrowed" the code
> from panfrost.
>
> 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).
>
>
> 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 | 162 ++++++++++++++++++++++++++++
> drivers/gpu/drm/lima/lima_devfreq.h | 15 +++
> drivers/gpu/drm/lima/lima_device.c | 4 +
> drivers/gpu/drm/lima/lima_device.h | 11 ++
> 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, 217 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
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-16 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 21:12 [RFC v1 0/1] drm: lima: devfreq and cooling device support Martin Blumenstingl
2019-12-15 21:12 ` [RFC v1 1/1] drm/lima: Add optional devfreq support Martin Blumenstingl
2019-12-16 2:51 ` [RFC v1 0/1] drm: lima: devfreq and cooling device support Qiang Yu
2019-12-24 11:22 ` Martin Blumenstingl
2019-12-16 3:03 ` Chen-Yu Tsai
2019-12-24 11:22 ` Martin Blumenstingl
2019-12-16 15:48 ` Alyssa Rosenzweig [this message]
2019-12-24 11:28 ` Martin Blumenstingl
2019-12-24 11:35 ` [Lima] " Icenowy Zheng
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=20191216154803.GA3921@kevin \
--to=alyssa.rosenzweig@collabora.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=lima@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--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