From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rafael.j.wysocki@intel.com, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [RFC PATCH 2/3] cpufreq: user_guide: update for base_frequency
Date: Fri, 4 Sep 2015 10:19:18 -0700 [thread overview]
Message-ID: <1441387159-19860-2-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
In-Reply-To: <1441387159-19860-1-git-send-email-srinivas.pandruvada@linux.intel.com>
Updated documentation for cpufreq attributes.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
Documentation/cpu-freq/user-guide.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/cpu-freq/user-guide.txt b/Documentation/cpu-freq/user-guide.txt
index 109e97b..0326a8c 100644
--- a/Documentation/cpu-freq/user-guide.txt
+++ b/Documentation/cpu-freq/user-guide.txt
@@ -212,6 +212,10 @@ bios_limit : If the BIOS tells the OS to limit a CPU to
which can be detected through the generic
thermal driver.
+base_frequency : This shows base frequency of the cpu. Any
+ request above this is purely opportunistic, if
+ boost mode is enabled.
+
If you have selected the "userspace" governor which allows you to
set the CPU operating frequency to a specific value, you can read out
the current frequency in
--
2.4.3
next prev parent reply other threads:[~2015-09-04 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 17:19 [RFC PATCH 1/3] cpufreq: Add new attribute "base_frequency" Srinivas Pandruvada
2015-09-04 17:19 ` Srinivas Pandruvada [this message]
2015-09-04 17:19 ` [RFC PATCH 3/3] cpufreq: acpi_cpufreq: Support base_frequency Srinivas Pandruvada
2015-09-07 6:06 ` [RFC PATCH 1/3] cpufreq: Add new attribute "base_frequency" Viresh Kumar
2015-09-07 15:17 ` Srinivas pandruvada
2015-09-07 15:31 ` 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=1441387159-19860-2-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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).