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: RE: [EXT] Re: Ask for help about cpufreq issue
Date: Tue, 11 Feb 2020 07:20:03 +0000	[thread overview]
Message-ID: <VI1PR04MB433391DABC853D5E6811B76AF3180@VI1PR04MB4333.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200211063439.aqc4h6np3wjpsg2j@vireshk-i7>

Thank you very much. I confirmed it was caused by QOS.
To be specific, it was caused by TMU.

BR,
Andy

> -----Original Message-----
> From: Viresh Kumar <viresh.kumar@linaro.org>
> Sent: 2020年2月11日 14:35
> To: Andy Tang <andy.tang@nxp.com>
> Cc: rjw@rjwysocki.net; linux-pm@vger.kernel.org
> Subject: Re: [EXT] Re: Ask for help about cpufreq issue
> 
> Caution: EXT Email
> 
> On 11-02-20, 06:23, Andy Tang wrote:
> > I am going to track to dev_pm_qos_add_request() as you suggested.
> > Before that, I am also wondering what the factor it could be to limit the cpu
> max frequency?
> 
> One of them is thermal, but there can be others as well. Just do following
> search in your kernel source code:
> 
> git grep freq_qos_add_request
> 
> This will list all the sources of this constraint.
> 
> --
> viresh

  reply	other threads:[~2020-02-11  7:20 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
2020-02-11  6:23           ` Andy Tang
2020-02-11  6:34             ` Viresh Kumar
2020-02-11  7:20               ` Andy Tang [this message]
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=VI1PR04MB433391DABC853D5E6811B76AF3180@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).