summaryrefslogtreecommitdiffstats
path: root/arch/sh/lib
diff options
context:
space:
mode:
authorLokesh Vutla <lokeshvutla@ti.com>2020-03-16 16:44:53 +0530
committerDaniel Lezcano <daniel.lezcano@linaro.org>2020-03-16 12:40:29 +0100
commitb34677b0999a7c0de45e57b780508c14cb438ed8 (patch)
treed2738b1ba9e62adb1f07a58f9b264e9f8b0fa11a /arch/sh/lib
parent5e20931c6a750b4b1ea9a2f7b863cc2dd9222ead (diff)
downloadlinux-stable-b34677b0999a7c0de45e57b780508c14cb438ed8.tar.gz
linux-stable-b34677b0999a7c0de45e57b780508c14cb438ed8.tar.bz2
linux-stable-b34677b0999a7c0de45e57b780508c14cb438ed8.zip
clocksource/drivers/timer-ti-dm: Implement cpu_pm notifier for context save and restore
omap_dm_timer_enable() restores the entire context(including counter) based on 2 conditions: - If get_context_loss_count is populated and context is lost. - If get_context_loss_count is not populated update unconditionally. Case2 has a side effect of updating the counter register even though context is not lost. When timer is configured in pwm mode, this is causing undesired behaviour in the pwm period. Instead of using get_context_loss_count call back, implement cpu_pm notifier with context save and restore support. And delete the get_context_loss_count callback all together. Suggested-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> [tony@atomide.com: removed pm_runtime calls from cpuidle calls] Signed-off-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> Link: https://lore.kernel.org/r/20200316111453.15441-1-lokeshvutla@ti.com
Diffstat (limited to 'arch/sh/lib')
0 files changed, 0 insertions, 0 deletions