From: Viresh Kumar <viresh.kumar@linaro.org>
To: Andy Tang <andy.tang@nxp.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [EXT] Re: Ask for help about cpufreq issue
Date: Tue, 11 Feb 2020 11:23:15 +0530 [thread overview]
Message-ID: <20200211055315.qlqrxiqf72u36ijl@vireshk-i7> (raw)
In-Reply-To: <VI1PR04MB4333E6B3340BADBC737E9CFFF3180@VI1PR04MB4333.eurprd04.prod.outlook.com>
On 11-02-20, 04:20, Andy Tang wrote:
> Hi Viresh,
>
> I checked the clk part, no issue was found.
> I did found a odd thing in cpufreq directory.
>
> # cat scaling_available_frequencies
> 1600000 1000000 800000 500000
> # cat scaling_max_freq
> 500000
Ahh, sorry about that as I must have noticed it earlier.
> Why there is a 1600Mhz frequency available, but the max freq is only 500M?
> How the max freq is set?
Hmm, I am not sure why this happened. Can you try to write 1600000 to
scaling_max_freq? This will fix it if the userspace is responsible for
this limitation and you need to find which part of your userspace is
causing it.
Else this is coming from within kernel and you need to track calls to
dev_pm_qos_add_request() and check all calls related to freq qos
constraints.
--
viresh
next prev parent reply other threads:[~2020-02-11 5:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 5:09 Ask for help about cpufreq issue Andy Tang
2020-02-07 5:23 ` 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 [this message]
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=20200211055315.qlqrxiqf72u36ijl@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andy.tang@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).