From: Alex Chiang <achiang@hp.com>
To: randy.dunlap@oracle.com, greg@kroah.com
Cc: Dave Jones <davej@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
rientjes@google.com
Subject: [PATCH 7/7] Documentation: ABI: /sys/devices/system/cpu/cpu#/cpufreq/
Date: Wed, 21 Oct 2009 21:45:46 -0600 [thread overview]
Message-ID: <20091022034546.13399.21222.stgit@bob.kio> (raw)
In-Reply-To: <20091022033506.13399.90799.stgit@bob.kio>
This is a complex interface and is already described in
Documentation/cpu-freq/, especially in the user-guide.txt file.
No need to copy/paste all that information. Let's just alert the reader
to the presence of the user-guide.
Cc: Dave Jones <davej@redhat.com>
Signed-off-by: Alex Chiang <achiang@hp.com>
---
Documentation/ABI/testing/sysfs-devices-system-cpu | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 968d8ba..81e61f5 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -121,6 +121,24 @@ Description: Discover cpuidle policy and mechanism
See files in Documentation/cpuidle/ for more information.
+What: /sys/devices/system/cpu/cpu#/cpufreq/*
+Date: pre-git history
+Contact: cpufreq@vger.kernel.org
+Description: Discover and change clock speed of CPUs
+
+ Clock scaling allows you to change the clock speed of the
+ CPUs on the fly. This is a nice method to save battery
+ power, because the lower the clock speed, the less power
+ the CPU consumes.
+
+ There are many knobs to tweak in this directory.
+
+ See files in Documentation/cpu-freq/ for more information.
+
+ In particular, read Documentation/cpu-freq/user-guide.txt
+ to learn how to control the knobs.
+
+
What: /sys/devices/system/cpu/cpu*/cache/index*/cache_disable_X
Date: August 2008
KernelVersion: 2.6.27
next prev parent reply other threads:[~2009-10-22 3:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 3:45 [PATCH 0/7] Documentation: document /sys/devices/system/cpu/ Alex Chiang
2009-10-22 3:45 ` [PATCH 1/7] Documentation: ABI: rename sysfs-devices-cache_disable properly Alex Chiang
2009-10-22 8:45 ` David Rientjes
2009-10-22 3:45 ` [PATCH 2/7] Documentation: ABI: document /sys/devices/system/cpu/ Alex Chiang
2009-10-22 3:45 ` [PATCH 3/7] Documentation: ABI: /sys/devices/system/cpu/ topology files Alex Chiang
2009-10-28 21:15 ` David Rientjes
2009-10-28 21:23 ` Alex Chiang
2009-10-29 8:44 ` David Rientjes
2009-10-22 3:45 ` [PATCH 4/7] Documentation: ABI: /sys/devices/system/cpu/cpu#/ " Alex Chiang
2009-10-22 3:45 ` [PATCH 5/7] Documentation: ABI: /sys/devices/system/cpu/sched_[mc|smt]_power_savings Alex Chiang
2009-10-22 3:45 ` [PATCH 6/7] Documentation: ABI: /sys/devices/system/cpu/cpuidle/ Alex Chiang
2009-10-22 3:45 ` Alex Chiang [this message]
2009-10-22 8:42 ` [PATCH 0/7] Documentation: document /sys/devices/system/cpu/ David Rientjes
2009-10-22 17:15 ` Alex Chiang
2009-10-22 19:15 ` David Rientjes
2009-10-23 4:29 ` Greg KH
2009-10-23 9:28 ` David Rientjes
2009-10-22 21:45 ` Randy Dunlap
2009-10-23 4:29 ` Greg KH
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=20091022034546.13399.21222.stgit@bob.kio \
--to=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rientjes@google.com \
/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