summaryrefslogtreecommitdiffstats
path: root/scripts/genksyms
diff options
context:
space:
mode:
authorColin Cross <ccross@android.com>2012-08-07 20:05:10 +0200
committerRussell King <rmk+kernel@arm.linux.org.uk>2012-08-11 10:15:58 +0200
commit237ec6f2e51d2fc2ff37c7c5f1ccc9264d09c85b (patch)
tree17a21e6c00129a703d906166f0e640089e3af6b7 /scripts/genksyms
parentARM: 7484/1: Don't enable GENERIC_LOCKBREAK with ticket spinlocks (diff)
downloadlinux-237ec6f2e51d2fc2ff37c7c5f1ccc9264d09c85b.tar.xz
linux-237ec6f2e51d2fc2ff37c7c5f1ccc9264d09c85b.zip
ARM: 7486/1: sched_clock: update epoch_cyc on resume
Many clocks that are used to provide sched_clock will reset during suspend. If read_sched_clock returns 0 after suspend, sched_clock will appear to jump forward. This patch resets cd.epoch_cyc to the current value of read_sched_clock during resume, which causes sched_clock() just after suspend to return the same value as sched_clock() just before suspend. In addition, during the window where epoch_ns has been updated before suspend, but epoch_cyc has not been updated after suspend, it is unknown whether the clock has reset or not, and sched_clock() could return a bogus value. Add a suspended flag, and return the pre-suspend epoch_ns value during this period. The new behavior is triggered by calling setup_sched_clock_needs_suspend instead of setup_sched_clock. Signed-off-by: Colin Cross <ccross@android.com> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'scripts/genksyms')
0 files changed, 0 insertions, 0 deletions