summaryrefslogtreecommitdiff
path: root/Documentation/target
diff options
context:
space:
mode:
authorSrivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>2013-05-15 21:47:17 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-05-15 21:47:17 +0200
commita66b2e503fc79fff6632d02ef5a0ee47c1d2553d (patch)
treebd4ffaa7b2b1f93007ae73eaa090c54b50c1f161 /Documentation/target
parentb57ffac5e57bff33dde3cff35dff5c41876a6d12 (diff)
cpufreq: Preserve sysfs files across suspend/resume
The file permissions of cpufreq per-cpu sysfs files are not preserved across suspend/resume because we internally go through the CPU Hotplug path which reinitializes the file permissions on CPU online. But the user is not supposed to know that we are using CPU hotplug internally within suspend/resume (IOW, the kernel should not silently wreck the user-set file permissions across a suspend cycle). Therefore, we need to preserve the file permissions as they are across suspend/resume. The simplest way to achieve that is to just not touch the sysfs files at all - ie., just ignore the CPU hotplug notifications in the suspend/resume path (_FROZEN) in the cpufreq hotplug callback. Reported-by: Robert Jarzmik <robert.jarzmik@intel.com> Reported-by: Durgadoss R <durgadoss.r@intel.com> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'Documentation/target')
0 files changed, 0 insertions, 0 deletions