Bug 101241 - cpufreq ondemand does not work on AMD GX-416RA SOC
Summary: cpufreq ondemand does not work on AMD GX-416RA SOC
Status: CLOSED INVALID
Alias: None
Product: Power Management
Classification: Unclassified
Component: cpufreq (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: cpufreq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-09 03:26 UTC by Homeros
Modified: 2016-08-23 09:34 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.32
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Homeros 2015-07-09 03:26:14 UTC
I want to use cpufreq "ondemand" policy to change the CPU frequency dynamiclly.

But when I insmod the powernow-k8 driver, it detected below data

Jul  9 11:11:43 localhost kernel: powernow-k8: Found 1 AMD GX-416RA SOC                                (4 cpu cores) (version 2.20.00)
Jul  9 11:11:43 localhost kernel: powernow-k8:    0 : pstate 0 (1600 MHz)
Jul  9 11:11:43 localhost kernel: powernow-k8:    1 : pstate 1 (1600 MHz)
Jul  9 11:11:43 localhost kernel: powernow-k8:    2 : pstate 2 (1600 MHz)
Jul  9 11:11:43 localhost kernel: powernow-k8:    3 : pstate 3 (1600 MHz)
Jul  9 11:11:43 localhost kernel: powernow-k8:    4 : pstate 4 (1600 MHz)
Jul  9 11:11:43 localhost kernel: powernow-k8:    5 : pstate 5 (1600 MHz)

Why the CPU frequency is fixed? is it caused by BIOS setting?
Is there some methods to modify the limit in software not BIOS?

Thanks
Comment 1 Chen Yu 2015-11-18 12:33:10 UTC
are you using acpi-cpufreq driver?

plz provide following log with latest  4.4-rc1 if possible

skywalker@sky-lake:/$ grep . /sys/devices/system/cpu/cpu0/cpufreq/*

thank you

Yu
Comment 2 Chen Yu 2015-11-23 10:30:23 UTC
sorry I misread your log, it is related to powernow-k8 driver.. I'm not familiar with it..
How about the result after you
stress -c 4 ?
Comment 3 Chen Yu 2016-08-23 09:34:15 UTC
As we did not get response for quite sometime I'm closing this ticket, please feel free to reopen if you want to continue to debug on this.

Note You need to log in before you can comment on or make changes to this bug.