Searched refs:wakeup_count (Results 1 - 7 of 7) sorted by relevance

/linux-master/drivers/base/power/
H A Dwakeup.c133 deleted_ws.wakeup_count += ws->wakeup_count;
588 ws->wakeup_count++;
1084 ws->wakeup_count, ws->expire_count,
H A Dsysfs.c92 * wakeup_count - Report the number of wakeup events related to the device
357 count = dev->power.wakeup->wakeup_count;
367 static DEVICE_ATTR_RO(wakeup_count);
399 count = dev->power.wakeup->wakeup_count;
H A Dwakeup_stats.c35 wakeup_attr(wakeup_count); variable
/linux-master/include/linux/
H A Dpm_wakeup.h38 * @wakeup_count: Number of times the wakeup source might abort suspend.
60 unsigned long wakeup_count; member in struct:wakeup_source
/linux-master/drivers/staging/ks7010/
H A Dks_wlan.h515 unsigned int wakeup_count; /* for detect wakeup loop */ member in struct:ks_wlan_private
H A Dks7010_sdio.c197 ++priv->wakeup_count;
214 ++priv->wakeup_count;
575 priv->wakeup_count = 0;
/linux-master/kernel/power/
H A Dmain.c751 * The 'wakeup_count' attribute, along with the functions defined in
768 * This difficulty may be overcome if user space uses 'wakeup_count' before
769 * writing to 'state'. It first should read from 'wakeup_count' and store
772 * 'wakeup_count'. If that fails, at least one wakeup event has occurred since
773 * 'wakeup_count' was read and 'state' should not be written to. Otherwise, it
775 * are any wakeup events detected after 'wakeup_count' was written to.
817 power_attr(wakeup_count); variable

Completed in 293 milliseconds