From: Antti P Miettinen <amiettinen@nvidia.com>
To: davej@redhat.com, pavel@ucw.cz, rjw@sisk.pl, len.brown@intel.com,
khilman@ti.com, j-pihet@ti.com, markgross@thegnar.org,
cpufreq@vger.kernel.org, linux-pm@lists.linux-foundation.org
Subject: [PATCH] cpufreq: Export user_policy min/max
Date: Thu, 19 Jan 2012 14:51:01 +0200 [thread overview]
Message-ID: <1326977461-4348-1-git-send-email-amiettinen@nvidia.com> (raw)
Add read-only sysfs nodes for user_policy min and max settings.
This helps diagnosis in the presence of other constraints that
affect the currently enforced policy minimum and maximum that
can be viewed with scaling_{min,max}_freq.
Signed-off-by: Antti P Miettinen <amiettinen@nvidia.com>
---
Related to "RFC: CPU frequency min as PM QoS param" patchset.
drivers/cpufreq/cpufreq.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index f2c7fc2..c2c1c62 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -364,6 +364,8 @@ show_one(cpuinfo_transition_latency, cpuinfo.transition_latency);
show_one(scaling_min_freq, min);
show_one(scaling_max_freq, max);
show_one(scaling_cur_freq, cur);
+show_one(policy_min_freq, user_policy.min);
+show_one(policy_max_freq, user_policy.max);
static int __cpufreq_set_policy(struct cpufreq_policy *data,
struct cpufreq_policy *policy);
@@ -582,6 +584,8 @@ cpufreq_freq_attr_rw(scaling_min_freq);
cpufreq_freq_attr_rw(scaling_max_freq);
cpufreq_freq_attr_rw(scaling_governor);
cpufreq_freq_attr_rw(scaling_setspeed);
+cpufreq_freq_attr_ro(policy_min_freq);
+cpufreq_freq_attr_ro(policy_max_freq);
static struct attribute *default_attrs[] = {
&cpuinfo_min_freq.attr,
@@ -595,6 +599,8 @@ static struct attribute *default_attrs[] = {
&scaling_driver.attr,
&scaling_available_governors.attr,
&scaling_setspeed.attr,
+ &policy_min_freq.attr,
+ &policy_max_freq.attr,
NULL
};
--
1.7.4.1
reply other threads:[~2012-01-19 12:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1326977461-4348-1-git-send-email-amiettinen@nvidia.com \
--to=amiettinen@nvidia.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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