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: Wed, 15 Mar 2017 14:05:41 +0000 [thread overview]
Message-ID: <20170315140541.GT21222@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1489582989.16018.4.camel@pengutronix.de>
On Wed, Mar 15, 2017 at 02:03:09PM +0100, Lucas Stach wrote:
> Am Sonntag, den 12.03.2017, 19:00 +0000 schrieb Russell King:
> > Each Vivante GPU contains a clock divider which can divide the GPU clock
> > by 2^n, which can lower the power dissipation from the GPU. It has been
> > suggested that the GC600 on Dove is responsible for 20-30% of the power
> > dissipation from the SoC, so lowering the GPU clock rate provides a way
> > to throttle the power dissiptation, and reduce the temperature when the
> > SoC gets hot.
> >
> > This patch hooks the Etnaviv driver into the kernel's thermal management
> > to allow the GPUs to be throttled when necessary, allowing a reduction in
> > GPU clock rate from /1 to /64 in power of 2 steps.
>
> Are those power of 2 steps a hardware limitation, or is it something you
> implemented this way to get a smaller number of steps, with a more
> meaningful difference in clock speed?
> My understanding was that the FSCALE value is just a regular divider
> with all steps values in the range of 1-64 being usable.
I don't share your understanding. The Vivante GAL kernel driver only
ever sets power-of-two values. I have no evidence to support your
suggestion.
There's evidence that says your understanding is incorrect however.
It isn't a divider. A value of 0x40 gives the fastest clock rate,
a value of 0x01 gives the slowest. If it were a binary divider,
a value of 0x7f would give the slowest rate - so why doesn't Vivante
use that in galcore when putting the GPU into idle/lower power - why
do they just 0x01.
This all leads me to believe that it's not a binary divider, but a
set of bits that select the clock from a set of divide-by-two stages,
and having more than one bit set is invalid.
However, without definitive information from Vivante, we'll never
really know. We're unlikely to get that.
--
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.
next prev parent reply other threads:[~2017-03-15 14:05 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 [this message]
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
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=20170315140541.GT21222@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