From: Joe Jin <joe.jin@oracle.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Neil Gu <qing.gu@oracle.com>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: update user_policy.max when _PPC updated
Date: Fri, 07 Jun 2013 09:48:36 +0800 [thread overview]
Message-ID: <51B13BF4.7090706@oracle.com> (raw)
In-Reply-To: <2674436.upogMLa2Oh@vostro.rjw.lan>
On 06/07/13 03:54, Rafael J. Wysocki wrote:
> Do you mean you set a limit in the BIOS setup and the kernel changed that limit
> on boot?
Sorry for the confusing.
The issue is when we disable hardcap before kernel boot up, after kernel bring
up, any changes of _PPC will update scaling_max_freq properly.
If we enable hardcap before kernel boot up, after kernel bring up, even we
disable it, scaling_max_freq does not be updated to max frequency, the max
frequency just up to the value when bring up.
Review related codes I found the limit came from user_policy.max, means when
we set user_policy.max to 1000MHZ when boot up, then any changes of _PPC could
not enlarge the scaling_max_freq, I think this is not as expected? please advise.
Thanks,
Joe
prev parent reply other threads:[~2013-06-07 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 0:52 [PATCH] ACPI: update user_policy.max when _PPC updated Joe Jin
2013-06-05 20:40 ` Rafael J. Wysocki
2013-06-06 0:27 ` Joe Jin
2013-06-06 11:06 ` Rafael J. Wysocki
2013-06-06 13:29 ` Joe Jin
2013-06-06 19:54 ` Rafael J. Wysocki
2013-06-07 1:48 ` Joe Jin [this message]
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=51B13BF4.7090706@oracle.com \
--to=joe.jin@oracle.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=qing.gu@oracle.com \
--cc=rjw@sisk.pl \
--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).