From: Lukasz Luba <lukasz.luba@arm.com>
To: linux-kernel@vger.kernel.org, airlied@linux.ie, daniel@ffwll.ch,
lima@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: yuq825@gmail.com, christianshewitt@gmail.com, lukasz.luba@arm.com
Subject: [PATCH] drm/lima: Use delayed timer as default in devfreq profile
Date: Wed, 27 Jan 2021 10:51:21 +0000 [thread overview]
Message-ID: <20210127105121.20345-1-lukasz.luba@arm.com> (raw)
Devfreq framework supports 2 modes for monitoring devices.
Use delayed timer as default instead of deferrable timer
in order to monitor the GPU status regardless of CPU idle.
Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
---
Hi all,
I've missed the Lima driver while working on Panfrost patch for fixing
the issue with default devfreq framework polling mode. More about this
and the patch, can be found here [1].
Regards,
Lukasz Luba
[1] https://lore.kernel.org/lkml/20210105164111.30122-1-lukasz.luba@arm.com/
drivers/gpu/drm/lima/lima_devfreq.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/lima/lima_devfreq.c b/drivers/gpu/drm/lima/lima_devfreq.c
index 5686ad4aaf7c..f1c9eb3e71bd 100644
--- a/drivers/gpu/drm/lima/lima_devfreq.c
+++ b/drivers/gpu/drm/lima/lima_devfreq.c
@@ -81,6 +81,7 @@ static int lima_devfreq_get_dev_status(struct device *dev,
}
static struct devfreq_dev_profile lima_devfreq_profile = {
+ .timer = DEVFREQ_TIMER_DELAYED,
.polling_ms = 50, /* ~3 frames */
.target = lima_devfreq_target,
.get_dev_status = lima_devfreq_get_dev_status,
--
2.17.1
next reply other threads:[~2021-01-27 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 10:51 Lukasz Luba [this message]
2021-01-30 13:51 ` [PATCH] drm/lima: Use delayed timer as default in devfreq profile Qiang Yu
2021-02-01 9:53 ` Lukasz Luba
2021-02-02 1:01 ` Qiang Yu
2021-02-02 14:02 ` Lukasz Luba
2021-02-03 2:01 ` Qiang Yu
2021-02-04 13:39 ` Robin Murphy
2021-02-04 14:23 ` Lukasz Luba
2021-02-07 13:11 ` Qiang Yu
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=20210127105121.20345-1-lukasz.luba@arm.com \
--to=lukasz.luba@arm.com \
--cc=airlied@linux.ie \
--cc=christianshewitt@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=lima@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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).