linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: rjw@sisk.pl, viresh.kumar@linaro.org, toralf.foerster@gmx.de,
	robert.jarzmik@intel.com, durgadoss.r@intel.com,
	tianyu.lan@intel.com, lantianyu1986@gmail.com,
	dirk.brandewie@gmail.com
Cc: stern@rowland.harvard.edu, srivatsa.bhat@linux.vnet.ibm.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/7] Cpufreq, cpu hotplug, suspend/resume related fixes
Date: Tue, 30 Jul 2013 04:23:12 +0530	[thread overview]
Message-ID: <20130729225213.20863.56722.stgit@srivatsabhat.in.ibm.com> (raw)


Hi,

This patchset reorganizes the cpufreq code and preserves the file permissions
of cpufreq-related per-cpu sysfs files across suspend/resume cycles, by
performing a light-weight init/teardown in those paths.

Patches 1 - 4 reorganize the code and have no functional impact, and can go
in as general cleanups as well. This reorganization builds a base that the
rest of the patches will make use of.

Patch 5 and 6 add a mechanism to perform light-weight init/tear-down of CPUs
in the cpufreq subsystem and finally patch 7 uses it to preserve sysfs files
across suspend/resume.

All the patches apply on Rafael's bleeding-edge branch on linux-pm git
tree[1].


Changes in v2:
* Fixed a refcounting bug explained here:
  http://marc.info/?l=linux-kernel&m=137511192600806&w=2

* Addressed some suggestions about code reorganization received in v1.
* Rebased on top of the bleeding-edge branch.


[1]. git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge

Thank you very much!


 Srivatsa S. Bhat (7):
      cpufreq: Fix misplaced call to cpufreq_update_policy()
      cpufreq: Add helper to perform alloc/free of policy structure
      cpufreq: Extract non-interface related stuff from cpufreq_add_dev_interface
      cpufreq: Extract the handover of policy cpu to a helper function
      cpufreq: Introduce a flag ('frozen') to separate full vs temporary init/teardown
      cpufreq: Preserve policy structure across suspend/resume
      cpufreq: Perform light-weight init/teardown during suspend/resume


 drivers/cpufreq/cpufreq.c       |  303 ++++++++++++++++++++++++++-------------
 drivers/cpufreq/cpufreq_stats.c |    8 -
 2 files changed, 205 insertions(+), 106 deletions(-)


Thanks,
Srivatsa S. Bhat
IBM Linux Technology Center


             reply	other threads:[~2013-07-29 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 22:53 Srivatsa S. Bhat [this message]
2013-07-29 22:53 ` [PATCH v2 1/7] cpufreq: Fix misplaced call to cpufreq_update_policy() Srivatsa S. Bhat
2013-07-29 22:54 ` [PATCH v2 2/7] cpufreq: Add helper to perform alloc/free of policy structure Srivatsa S. Bhat
2013-07-29 22:54 ` [PATCH v2 3/7] cpufreq: Extract non-interface related stuff from cpufreq_add_dev_interface Srivatsa S. Bhat
2013-07-29 22:54 ` [PATCH v2 4/7] cpufreq: Extract the handover of policy cpu to a helper function Srivatsa S. Bhat
2013-07-29 22:54 ` [PATCH v2 5/7] cpufreq: Introduce a flag ('frozen') to separate full vs temporary init/teardown Srivatsa S. Bhat
2013-07-29 22:55 ` [PATCH v2 6/7] cpufreq: Preserve policy structure across suspend/resume Srivatsa S. Bhat
2013-07-30  9:09   ` Viresh Kumar
2013-07-29 22:55 ` [PATCH v2 7/7] cpufreq: Perform light-weight init/teardown during suspend/resume Srivatsa S. Bhat
2013-07-30  9:09   ` Viresh Kumar
2013-07-30 14:06 ` [PATCH v2 0/7] Cpufreq, cpu hotplug, suspend/resume related fixes Rafael J. Wysocki

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=20130729225213.20863.56722.stgit@srivatsabhat.in.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=dirk.brandewie@gmail.com \
    --cc=durgadoss.r@intel.com \
    --cc=lantianyu1986@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=robert.jarzmik@intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tianyu.lan@intel.com \
    --cc=toralf.foerster@gmx.de \
    --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).