From: Markus Mayer <code@mmayer.net>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: Power Management List <linux-pm@vger.kernel.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Markus Mayer <mmayer@broadcom.com>
Subject: [PATCH v2 0/2] cpufreq: stats: clear statistics
Date: Fri, 4 Nov 2016 09:55:34 -0700 [thread overview]
Message-ID: <20161104165536.20088-1-code@mmayer.net> (raw)
From: Markus Mayer <mmayer@broadcom.com>
This series lets the user clear the CPUfreq stats by writing to a new
sysfs attribute.
Changes since v1:
- add new cpufreq_freq_attr_wr_perm() macro for write-only
attributes (because this is a separate commit, this patch has
turned into a series)
- remove the Kconfig option, compiling the code unconditionally
- remove show_reset()
- cpufreq_stats_clear_table() takes a struct cpufreq_stats * as
argument rather than a struct cpufreq_policy *
For v1, see https://lkml.org/lkml/2016/11/3/581.
Markus Mayer (2):
cpufreq: add new attribute type cpufreq_freq_attr_wr_perm()
cpufreq: stats: clear statistics
Documentation/cpu-freq/cpufreq-stats.txt | 6 ++++++
drivers/cpufreq/cpufreq_stats.c | 22 ++++++++++++++++++++++
include/linux/cpufreq.h | 4 ++++
3 files changed, 32 insertions(+)
--
2.7.4
next reply other threads:[~2016-11-04 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 16:55 Markus Mayer [this message]
2016-11-04 16:55 ` [PATCH v2 1/2] cpufreq: add new attribute type cpufreq_freq_attr_wr_perm() Markus Mayer
2016-11-07 4:33 ` Viresh Kumar
2016-11-07 4:35 ` Viresh Kumar
2016-11-04 16:55 ` [PATCH v2 2/2] cpufreq: stats: clear statistics Markus Mayer
2016-11-07 4:38 ` 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=20161104165536.20088-1-code@mmayer.net \
--to=code@mmayer.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=rjw@rjwysocki.net \
--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).