aboutsummaryrefslogtreecommitdiff
path: root/drivers/base/power/runtime.c
diff options
context:
space:
mode:
authorRavi Chandra Sadineni <ravisadineni@chromium.org>2018-06-01 19:32:15 -0700
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-06-06 09:23:36 +0200
commit2d5ed61ce9820a1fe7b076cc45c169524d767746 (patch)
treeaa9a3d4d0e75d2cb0a3a5afb2373592540a9ae32 /drivers/base/power/runtime.c
parent3c89adb0d11117f64d5b501730be7fb2bf53a479 (diff)
downloadlinux-stericsson-2d5ed61ce9820a1fe7b076cc45c169524d767746.tar.gz
PM / wakeup: Export wakeup_count instead of event_count via sysfs
Currently we export event_count instead of wakeup_count via the per-device wakeup_count sysfs attribute. Change it to wakeup_count to make it more meaningful. wakeup_count increments only when events_check_enabled is set, that is whenever writes the current wakeup count to /sys/power/wakeup_count. Also events_check_enabled is cleared on every resume. User space is expected to write to this just before suspend. This way pm_wakeup_event(), when called from IRQs handles, will increment wakeup_count only if we are in system-wide suspend-resume cycle and should give a fair approximation of how many times a device may have triggered a wakeup from system suspend. event_count on the other hand will increment every time pm_wakeup_event() is called irrespective of whether we are in a suspend-resume cycle and some drivers call it on every interrupt which makes it less useful for system wakeup tracking. Signed-off-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Acked-by: Pavel Machek <pavel@ucw.cz> [ rjw: Subject & changelog ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/base/power/runtime.c')
0 files changed, 0 insertions, 0 deletions