Linux Power Management development
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Zengtao (B)" <prime.zeng@hisilicon.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: cpufreq_resume warning issue
Date: Mon, 21 Mar 2016 15:14:41 +0530	[thread overview]
Message-ID: <20160321094441.GC27778@vireshk-i7> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED0A6D9756@SZXEMA509-MBX.china.huawei.com>

On 21-03-16, 09:26, Zengtao (B) wrote:
> Actually the freq is tunable, but voltage is fixed, So we fix it to a high freq because little benefit by freq tuning.

Okay, then just enable cpufreq and select performace governor for it, which will
select the highest frequency for the CPU.

> Since the DVFS has percpu dvfs policy, so I think it is reasonable to allow cpu to disable dvfs, what do you think about that?

Its not that we can't update core code for some specific use cases, but here you
should be using cpufreq core for the CPU0 as well, with a proper governor which
would not have any overheads during operations.

-- 
viresh

  reply	other threads:[~2016-03-21  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  3:43 cpufreq_resume warning issue Zengtao (B)
2016-03-21  7:32 ` Viresh Kumar
2016-03-21  8:05   ` Zengtao (B)
2016-03-21  8:34     ` Viresh Kumar
2016-03-21  9:07       ` Zengtao (B)
2016-03-21  9:09         ` Viresh Kumar
2016-03-21  9:26           ` Zengtao (B)
2016-03-21  9:44             ` Viresh Kumar [this message]
2016-03-22  9:58               ` Zengtao (B)
2016-03-22 10:32                 ` 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=20160321094441.GC27778@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=prime.zeng@hisilicon.com \
    --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