Lines Matching refs:counter
136 indicated to the PM core by two counters, the device's usage counter and the
137 counter of 'active' children of the device.
140 the PM core and it turns out to be equal to zero, the other counter is
141 checked. If that counter also is equal to zero, the PM core executes the
174 the usage counter of which is equal to zero _and_ either the counter of
223 - the usage counter of the device
364 - increment the device's usage counter
367 - increment the device's usage counter, run pm_request_resume(dev) and
371 - increment the device's usage counter, run pm_runtime_resume(dev) and
375 - decrement the device's usage counter
378 - decrement the device's usage counter; if the result is 0 then run
382 - decrement the device's usage counter; if the result is 0 then run
386 - decrement the device's usage counter; if the result is 0 then run
390 - decrement the device's usage counter; if the result is 0 then run
394 - decrement the device's usage counter; if the result is 0 then run
424 PM status to 'active' and update its parent's counter of 'active'
432 PM status to 'suspended' and update its parent's counter of 'active'
454 counter (used by the /sys/devices/.../power/control interface to
459 counter (used by the /sys/devices/.../power/control interface to
625 * Even though the device was suspended, if its usage counter was > 0 then most
637 The PM core always increments the runtime usage counter before calling the
832 from autosuspending immediately, even though the usage counter is zero and the