All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Plain DFS (no voltage scaling)
Date: Wed, 3 Feb 2016 16:07:53 +0100	[thread overview]
Message-ID: <56B217C9.1050405@free.fr> (raw)
In-Reply-To: <56B11B67.3090600@free.fr>

On 02/02/2016 22:11, Mason wrote:

> I plan to enable the on-demand governor on the tango platform:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tango4-smp8758.dtsi
> 
> I found the cpufreq-dt binding doc:
> 
> https://www.kernel.org/doc/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
> https://www.kernel.org/doc/Documentation/devicetree/bindings/opp/opp.txt
> 
> Something is not clear to me:
> 
> If my platform cannot scale the voltage, what information
> should I put in the voltage part of the DT?

Someone pointed out that tweaking the frequency without tweaking
the voltage might be counter-productive.

I measured the power consumption of the entire board (at the power outlet)
for 3 CPU frequencies (all other things being equal, I hope).

idle @ 111 MHz = 4.6 W
idle @ 333 MHz = 4.6 W
idle @ 999 MHz = 4.6 W

load @ 111 MHz = 5.0 W
load @ 333 MHz = 5.7 W
load @ 999 MHz = 7.7 W

When idle, the kernel calls WFI, which "turns off" most of the CPU
(clock gating?) such that the actual frequency does not matter.

At full load (I use cpuburn to jog as many FUs simultaneously as
possible) it looks like each additional MHz requires ~3 mW.

So it would appear that an on-demand governor might not help to
save power.

But I have another use-case in mind: CPU throttling on over-heating.
There's a temperature sensor in the CPU, and I'd like to say:
"if temperature exceeds a user-set threshold, don't run at the max
frequency until the temperature becomes reasonable".

And I think that requires cpufreq?

Regards.


WARNING: multiple messages have this Message-ID (diff)
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Plain DFS (no voltage scaling)
Date: Wed, 3 Feb 2016 16:07:53 +0100	[thread overview]
Message-ID: <56B217C9.1050405@free.fr> (raw)
In-Reply-To: <56B11B67.3090600@free.fr>

On 02/02/2016 22:11, Mason wrote:

> I plan to enable the on-demand governor on the tango platform:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tango4-smp8758.dtsi
> 
> I found the cpufreq-dt binding doc:
> 
> https://www.kernel.org/doc/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
> https://www.kernel.org/doc/Documentation/devicetree/bindings/opp/opp.txt
> 
> Something is not clear to me:
> 
> If my platform cannot scale the voltage, what information
> should I put in the voltage part of the DT?

Someone pointed out that tweaking the frequency without tweaking
the voltage might be counter-productive.

I measured the power consumption of the entire board (at the power outlet)
for 3 CPU frequencies (all other things being equal, I hope).

idle @ 111 MHz = 4.6 W
idle @ 333 MHz = 4.6 W
idle @ 999 MHz = 4.6 W

load @ 111 MHz = 5.0 W
load @ 333 MHz = 5.7 W
load @ 999 MHz = 7.7 W

When idle, the kernel calls WFI, which "turns off" most of the CPU
(clock gating?) such that the actual frequency does not matter.

At full load (I use cpuburn to jog as many FUs simultaneously as
possible) it looks like each additional MHz requires ~3 mW.

So it would appear that an on-demand governor might not help to
save power.

But I have another use-case in mind: CPU throttling on over-heating.
There's a temperature sensor in the CPU, and I'd like to say:
"if temperature exceeds a user-set threshold, don't run at the max
frequency until the temperature becomes reasonable".

And I think that requires cpufreq?

Regards.

  parent reply	other threads:[~2016-02-03 15:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 21:11 Plain DFS (no voltage scaling) Mason
2016-02-02 21:11 ` Mason
2016-02-03  2:10 ` Viresh Kumar
2016-02-03  2:10   ` Viresh Kumar
2016-02-03 15:35   ` Mason
2016-02-03 15:35     ` Mason
2016-02-03 16:14     ` Viresh Kumar
2016-02-03 16:14       ` Viresh Kumar
2016-02-03 18:25       ` Mason
2016-02-03 18:25         ` Mason
2016-02-04  3:23         ` Viresh Kumar
2016-02-04  3:23           ` Viresh Kumar
2016-02-03 15:07 ` Mason [this message]
2016-02-03 15:07   ` Mason
2016-02-03 16:13   ` Viresh Kumar
2016-02-03 16:13     ` Viresh Kumar
2016-02-03 18:19     ` Mason
2016-02-03 18:19       ` Mason
2016-02-04  3:23       ` Viresh Kumar
2016-02-04  3:23         ` Viresh Kumar

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=56B217C9.1050405@free.fr \
    --to=slash.tmp@free.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.