public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Eduardo Valentin <edubezval@gmail.com>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Lukasz Majewski <l.majewski@majess.pl>,
	Abhilash Kesavan <kesavan.abhilash@gmail.com>,
	Abhilash Kesavan <a.kesavan@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Thomas Abraham <thomas.ab@samsung.com>,
	Kevin Hilman <khilman@linaro.org>,
	Kevin Hilman <khilman@kernel.org>,
	a.nitecki@samsung.com, Lukasz Majewski <l.majewski@samsung.com>
Subject: [PATCH 3/3] doc: cpufreq: tests: Provide cpufreq tests README
Date: Mon, 26 Jan 2015 11:41:24 +0100	[thread overview]
Message-ID: <1422268884-26173-3-git-send-email-l.majewski@samsung.com> (raw)
In-Reply-To: <1422268884-26173-1-git-send-email-l.majewski@samsung.com>

This commit adds README to ./tools/testing/cpufreq directory.

Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
---
 tools/testing/cpufreq/README | 53 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 53 insertions(+)
 create mode 100644 tools/testing/cpufreq/README

diff --git a/tools/testing/cpufreq/README b/tools/testing/cpufreq/README
new file mode 100644
index 0000000..c934016
--- /dev/null
+++ b/tools/testing/cpufreq/README
@@ -0,0 +1,53 @@
+This file contains list of cpufreq's available regression tests with a short
+usage description.
+
+1. cpufreq_freq_test.sh
+
+Description:
+------------
+This script is supposed to test if cpufreq attributes exported by sysfs are
+exposing correct values.
+
+To achieve this goal it saves the current governor and changes it to
+"performance". Afterwards, it reads the "scaling_available_frequencies"
+property. With the list of supported frequencies it is able to enforce each of
+them by writing to "scaling_max_freq" attribute. To make the test more reliable
+a superfluous load with gzip is created to be sure that we are running with
+highest possible frequency. This high load is regulated with the 'sleep'
+duration. After this time the "cpufreq_cur_freq" is read and compared with the
+original value. As the last step the original governor is restored.
+
+This script can work with or without BOOST enabled and helps in spotting errors
+related to cpufreq and common clock framework.
+
+Used attributes:
+----------------
+- "scaling_available_frequencies"
+- "cpuinfo_cur_freq"
+- "scaling_governor"
+- "scaling_max_freq"
+
+Target devices:
+---------------
+
+All devices which exports mentioned above sysfs attributes.
+
+2. governors_switch.sh
+
+Description:
+------------
+This script is supposed to test if all governors are available and possible to
+set.
+
+Moreover, it allows to test if cpufreq is able to withstand multiple accesses to
+the same sysfs attribute without crash.
+
+Used attributes:
+----------------
+- "scaling_available_governors"
+- "scaling_governor"
+
+Target devices:
+---------------
+
+All devices which exports mentioned above sysfs attributes.
-- 
2.0.0.rc2


  parent reply	other threads:[~2015-01-26 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 10:41 [PATCH 1/3] cpufreq: tests: Cpufreq test to check if all declared freqs can be set Lukasz Majewski
2015-01-26 10:41 ` [PATCH 2/3] cpufreq: tests: Provide test to check if all supported governors are working Lukasz Majewski
2015-01-26 10:41 ` Lukasz Majewski [this message]
2015-01-27  3:56   ` [PATCH 3/3] doc: cpufreq: tests: Provide cpufreq tests README Viresh Kumar
2015-01-27  8:35     ` Lukasz Majewski
2015-01-27  8:40       ` Viresh Kumar
2015-01-27  8:57         ` Lukasz Majewski

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=1422268884-26173-3-git-send-email-l.majewski@samsung.com \
    --to=l.majewski@samsung.com \
    --cc=a.kesavan@samsung.com \
    --cc=a.nitecki@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=edubezval@gmail.com \
    --cc=kesavan.abhilash@gmail.com \
    --cc=khilman@kernel.org \
    --cc=khilman@linaro.org \
    --cc=l.majewski@majess.pl \
    --cc=linux-pm@vger.kernel.org \
    --cc=thomas.ab@samsung.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