linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Tang <andy.tang@nxp.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Ask for help about cpufreq issue
Date: Fri, 7 Feb 2020 05:09:19 +0000	[thread overview]
Message-ID: <VI1PR04MB4333D45D033CB8E33CB9070FF31C0@VI1PR04MB4333.eurprd04.prod.outlook.com> (raw)

Hi Viresh,

Cpufreq failed to work on our board. CPU frequency keeps at the lowest frequency whatever governor I choose.

Hardware platform: ls1043ardb board (4 cores arm64 arch)
Software: linux kernel v5.4.3 + ubuntu 1804.

Test log:
root@localhost:~# echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
root@localhost:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
500000
root@localhost:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1600000 1000000 800000 500000

All the parameters you may need:
root@localhost:~# for entry in `ls /sys/devices/system/cpu/cpufreq/policy0/` ; do echo $entry;  cat  /sys/devices/system/cpu/cpufreq/policy0/$entry; done
affected_cpus
0 1 2 3
cpuinfo_cur_freq
500000
cpuinfo_max_freq
1600000
cpuinfo_min_freq
500000
cpuinfo_transition_latency
31
related_cpus
0 1 2 3
scaling_available_frequencies
1600000 1000000 800000 500000
scaling_available_governors
userspace ondemand performance schedutil
scaling_cur_freq
500000
scaling_driver
qoriq_cpufreq
scaling_governor
performance
scaling_max_freq
500000
scaling_min_freq
500000
scaling_setspeed
<unsupported>
stats
cat: /sys/devices/system/cpu/cpufreq/policy0/stats: Is a directory


Could you please instruct me how to investigate this issue?

BR,
Andy

             reply	other threads:[~2020-02-07  5:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07  5:09 Andy Tang [this message]
2020-02-07  5:23 ` Ask for help about cpufreq issue Viresh Kumar
2020-02-07  6:03   ` [EXT] " Andy Tang
2020-02-07  7:05     ` Viresh Kumar
2020-02-11  4:20       ` Andy Tang
2020-02-11  5:53         ` Viresh Kumar
2020-02-11  6:23           ` Andy Tang
2020-02-11  6:34             ` Viresh Kumar
2020-02-11  7:20               ` Andy Tang
2020-02-12 10:11               ` Andy Tang
2020-02-12 11:50                 ` Viresh Kumar
2020-02-13  8:18                   ` Andy Tang
2020-02-13  8:48                     ` Viresh Kumar
2020-02-13  9:12                       ` Andy Tang
2020-02-13  9:15                         ` Viresh Kumar
2020-02-13  9:21                           ` Andy Tang
2020-02-14 10:00                       ` Andy Tang
2020-02-17  8:22                         ` 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=VI1PR04MB4333D45D033CB8E33CB9070FF31C0@VI1PR04MB4333.eurprd04.prod.outlook.com \
    --to=andy.tang@nxp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).