linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	rjw@rjwysocki.net,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
	Linux PM list <linux-pm@vger.kernel.org>,
	linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
	linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>,
	srivatsa.bhat@linux.vnet.ibm.com
Subject: [PATCH v5 0/3] powernv,cpufreq: Dynamic Frequency Scaling support
Date: Sat, 29 Mar 2014 01:41:21 +0530	[thread overview]
Message-ID: <1396037484-23907-1-git-send-email-ego@linux.vnet.ibm.com> (raw)

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

Hi,

This is v5 of the patchset to enable dynamic frequency scaling on IBM
PowerNV platforms. This patchset does address all the review comments
obtained for v4 (which can be found at [1]).

Changes from v4:

    * Created a separate patch to select the CPUFreq related Config
      options for PowerNV

    * Dropped the per-core locking hunks in
      drivers/cpufreq/powernv-cpufreq.c since the CPUFreq core takes
      care of the for us after the following commit which is present in
      linux-next:

	commit 12478cf0c55e5969f740bb38a24b1a0104ae18d8	  
      	Author: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
        Date:   Mon Mar 24 13:35:44 2014 +0530

       	cpufreq: Make sure frequency transitions are serialized

    * [PATCH v5 3/3] gets rid of the powernv_pstate_ids[] array that
      was being used to record the pstate ids. After the following
      patch it is safe to use cpufreq_frequency_table.driver_data
      since it is opaque to the cpufreq core: 

      	From: Viresh Kumar <viresh.kumar@linaro.org>
	Date: 2014-03-28 13:53:47
	url: http://marc.info/?l=linux-pm&m=139601416804702&w=2
	    
	cpufreq: create another field .flags in cpufreq_frequency_table

The patchset is based on the commit
201544be8c37dffbf069bb5fc9edb5674f8c1754 of the linux-next tree.

While all the patches in the patchset apply cleanly on linux-next,
[PATCH v5 3/3] requires the Viresh's patch that was mentioned
above. Otherwise, the frequency corresponding to pstate id -3 will be
omited while reporting the "scaling_available_frequencies" in sysfs.

[1]: http://marc.info/?l=linux-pm&m=139585297620612&w=2

Gautham R. Shenoy (2):
  powernv, cpufreq: Select CPUFreq related Kconfig options for powernv
  powernv,cpufreq: Use cpufreq_frequency_table.driver_data to store
    pstate ids

Vaidyanathan Srinivasan (1):
  powernv, cpufreq: cpufreq driver for powernv platform

 arch/powerpc/configs/pseries_defconfig    |   1 +
 arch/powerpc/configs/pseries_le_defconfig |   1 +
 arch/powerpc/include/asm/reg.h            |   4 +
 arch/powerpc/platforms/powernv/Kconfig    |   6 +
 drivers/cpufreq/Kconfig.powerpc           |   8 +
 drivers/cpufreq/Makefile                  |   1 +
 drivers/cpufreq/powernv-cpufreq.c         | 341 ++++++++++++++++++++++++++++++
 7 files changed, 362 insertions(+)
 create mode 100644 drivers/cpufreq/powernv-cpufreq.c

-- 
1.8.3.1

             reply	other threads:[~2014-03-28 20:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 20:11 Gautham R. Shenoy [this message]
2014-03-28 20:11 ` [PATCH v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv Gautham R. Shenoy
2014-03-31  4:21   ` Viresh Kumar
2014-03-28 20:11 ` [PATCH v5 2/3] powernv, cpufreq: cpufreq driver for powernv platform Gautham R. Shenoy
2014-03-28 20:11 ` [PATCH v5 3/3] powernv, cpufreq: Use cpufreq_frequency_table.driver_data to store pstate ids Gautham R. Shenoy
2014-03-31  4:25 ` [PATCH v5 0/3] powernv, cpufreq: Dynamic Frequency Scaling support Viresh Kumar
2014-04-01  7:13   ` [PATCH REPOST v5 2/3] powernv, cpufreq: cpufreq driver for powernv platform Gautham R. Shenoy
2014-04-01  7:13     ` [PATCH REPOST v5 3/3] powernv, cpufreq: Use cpufreq_frequency_table.driver_data to store pstate ids Gautham R. Shenoy
2014-04-01  7:13     ` [PATCH REPOST v5 1/3] powernv, cpufreq: Select CPUFreq related Kconfig options for powernv Gautham R. Shenoy
2014-04-01  9:46       ` Benjamin Herrenschmidt
2014-04-01 22:03         ` Rafael J. Wysocki
2014-04-02  4:23           ` Benjamin Herrenschmidt
2014-04-02 11:03             ` Rafael J. Wysocki
2014-04-02 11:29               ` Benjamin Herrenschmidt

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=1396037484-23907-1-git-send-email-ego@linux.vnet.ibm.com \
    --to=ego@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rjw@rjwysocki.net \
    --cc=srivatsa.bhat@linux.vnet.ibm.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).