From: Joonas Saarinen <jza@saunalahti.fi>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Bobcat cpufreq
Date: Fri, 18 Oct 2013 16:19:49 +0300 (EEST) [thread overview]
Message-ID: <31997499.9414731382102390275.JavaMail.jza@saunalahti.fi> (raw)
Borislav Petkov [bp@alien8.de] wrote:
> Once you've done that successfully, you need to run as root:
>
> $ cd tools/power/cpupower/
> $ LD_LIBRARY_PATH=. ./cpupower frequency-info
This is what I get:
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
hardware limits: 800 MHz - 1000 MHz
available frequency steps: 1000 MHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1000 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:-nan%, 800 MHz:-nan% (646)
boost state support:
Supported: yes
Active: yes
It's promising that the boost state support is "supported and active"
but the output is still kind of sparse. There's no mention about
specific turbo states, nor do I get /proc/cpuinfo or that cpupower tool
ever to show an evidence that the CPU is going to 1333MHz. On Windows
CPU-Z showed it constantly visiting that state.
That's all for now.
Joonas
next reply other threads:[~2013-10-18 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 13:19 Joonas Saarinen [this message]
2013-10-18 13:36 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2013-10-18 15:23 Joonas Saarinen
2013-10-18 15:36 ` Borislav Petkov
2013-10-17 20:54 Joonas Saarinen
2013-10-17 22:20 ` Borislav Petkov
2013-08-20 19:58 Joonas Saarinen
2013-08-22 11:17 ` Borislav Petkov
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=31997499.9414731382102390275.JavaMail.jza@saunalahti.fi \
--to=jza@saunalahti.fi \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®