Searched refs:wakeup_count (Results 1 – 7 of 7) sorted by relevance
132 deleted_ws.wakeup_count += ws->wakeup_count; in wakeup_source_record() 587 ws->wakeup_count++; in wakeup_source_report_event() 1083 ws->wakeup_count, ws->expire_count, in print_wakeup_source_stats()
91 * wakeup_count - Report the number of wakeup events related to the device356 count = dev->power.wakeup->wakeup_count; in wakeup_count_show() 366 static DEVICE_ATTR_RO(wakeup_count);398 count = dev->power.wakeup->wakeup_count; in wakeup_abort_count_show()
35 wakeup_attr(wakeup_count);
28 What: /sys/class/wakeup/.../wakeup_count
170 What: /sys/power/wakeup_count174 The /sys/power/wakeup_count file allows user space to put the223 /sys/power/wakeup_count file block or return false). When a
80 What: /sys/devices/.../power/wakeup_count84 The /sys/devices/.../wakeup_count attribute contains the number
766 * The 'wakeup_count' attribute, along with the functions defined in783 * This difficulty may be overcome if user space uses 'wakeup_count' before784 * writing to 'state'. It first should read from 'wakeup_count' and store787 * 'wakeup_count'. If that fails, at least one wakeup event has occurred since788 * 'wakeup_count' was read and 'state' should not be written to. Otherwise, it790 * are any wakeup events detected after 'wakeup_count' was written to.832 power_attr(wakeup_count);