public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/etnaviv: add etnaviv cooling device
Date: Mon, 20 Mar 2017 09:50:08 +0000	[thread overview]
Message-ID: <20170320095007.GE21222@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1490001575.2895.8.camel@pengutronix.de>

On Mon, Mar 20, 2017 at 10:19:35AM +0100, Lucas Stach wrote:
> Yes, probably we want to have both at some point. The cooling-device
> stuff is about throttling the GPU when the SoC reaches critical
> temperatures.
> 
> The devfreq governors are about providing exactly the right performance
> point.
> Though as I have not yet seen any SoCs where the voltage would be scaled
> with GPU frequency, downclocking the GPU is of limited value. For most
> of those SoCs a race-to-idle policy is probably okay, as this allows
> other components of the system like the DRAM to go into lower power
> operating modes when the GPU is idle.

However, since we already have runtime PM support in etnaviv (where we
even power the GPU off on some SoCs) the lack of voltage scaling does
suggest that GPU frequency scaling would be of limited value in terms
of overall power usage.

It's also worth bearing in mind that Vivante GPUs internally control
clock gates to various modules when they're on.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-03-20  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 19:00 [PATCH] drm/etnaviv: add etnaviv cooling device Russell King
2017-03-15 13:03 ` Lucas Stach
2017-03-15 14:05   ` Russell King - ARM Linux
2017-03-19 20:03     ` Chris Healy
2017-03-19 20:50       ` Russell King - ARM Linux
2017-03-20  9:19       ` Lucas Stach
2017-03-20  9:50         ` Russell King - ARM Linux [this message]
2017-03-20  9:21     ` Lucas Stach

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=20170320095007.GE21222@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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