linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: srivatsa.bhat@linux.vnet.ibm.com,
	"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
Subject: [PATCH v2 5/6] powernv:cpufreq: Export nominal frequency via sysfs.
Date: Mon, 10 Mar 2014 16:41:00 +0530	[thread overview]
Message-ID: <1394449861-8688-6-git-send-email-ego@linux.vnet.ibm.com> (raw)
In-Reply-To: <1394449861-8688-1-git-send-email-ego@linux.vnet.ibm.com>

From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>

Create a driver attribute named cpuinfo_nominal_freq which
creates a sysfs read-only file named cpuinfo_nominal_freq. Export
the frequency corresponding to the nominal_pstate through this
interface.

Nominal frequency is the highest non-turbo frequency for the
platform.  This is generally used for setting governor policies from
user space for optimal energy efficiency.

Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
---
 drivers/cpufreq/powernv-cpufreq.c | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
index 0ecd163..183bbc4 100644
--- a/drivers/cpufreq/powernv-cpufreq.c
+++ b/drivers/cpufreq/powernv-cpufreq.c
@@ -142,8 +142,30 @@ static unsigned int pstate_id_to_freq(int pstate_id)
 	return powernv_freqs[i].frequency;
 }
 
+/**
+ * show_cpuinfo_nominal_freq - Show the nominal CPU frequency as indicated by
+ * the firmware
+ */
+static ssize_t show_cpuinfo_nominal_freq(struct cpufreq_policy *policy,
+					char *buf)
+{
+	int nominal_freq;
+	nominal_freq = pstate_id_to_freq(powernv_pstate_info.pstate_nominal_id);
+	return sprintf(buf, "%u\n", nominal_freq);
+}
+
+
+struct freq_attr cpufreq_freq_attr_cpuinfo_nominal_freq = {
+	.attr = { .name = "cpuinfo_nominal_freq",
+		  .mode = 0444,
+		},
+	.show = show_cpuinfo_nominal_freq,
+};
+
+
 static struct freq_attr *powernv_cpu_freq_attr[] = {
 	&cpufreq_freq_attr_scaling_available_freqs,
+	&cpufreq_freq_attr_cpuinfo_nominal_freq,
 	NULL,
 };
 
-- 
1.8.3.1

  parent reply	other threads:[~2014-03-10 11:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 11:10 [PATCH v2 0/6] powernv:cpufreq: Dynamic cpu-frequency scaling Gautham R. Shenoy
2014-03-10 11:10 ` [PATCH v2 1/6] powernv: cpufreq driver for powernv platform Gautham R. Shenoy
2014-03-10 11:10 ` [PATCH v2 2/6] powernv:cpufreq: Create a powernv_cpu_to_core_mask() helper Gautham R. Shenoy
2014-03-18 23:37   ` Benjamin Herrenschmidt
2014-03-19  6:35     ` Srivatsa S. Bhat
2014-03-19 11:02       ` Gautham R Shenoy
2014-03-10 11:10 ` [PATCH v2 3/6] powernv, cpufreq:Add per-core locking to serialize frequency transitions Gautham R. Shenoy
2014-03-17  9:04   ` Preeti U Murthy
2014-03-10 11:10 ` [PATCH v2 4/6] powernv:cpufreq: Create pstate_id_to_freq() helper Gautham R. Shenoy
2014-03-17  9:06   ` Preeti U Murthy
2014-03-10 11:11 ` Gautham R. Shenoy [this message]
2014-03-10 11:11 ` [PATCH v2 6/6] powernv:cpufreq: Implement the driver->get() method Gautham R. Shenoy
2014-03-17  9:11   ` Preeti U Murthy

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=1394449861-8688-6-git-send-email-ego@linux.vnet.ibm.com \
    --to=ego@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).