Lines Matching full:autosuspend

156 also respecting devices configured for autosuspend.  In essence this means a
212     - timer used for scheduling (delayed) suspend and autosuspend requests
284     - indicates that the device's driver supports delayed autosuspend (see
289     - indicates that the PM core should attempt to carry out an autosuspend
293     - the delay time (in milliseconds) to be used for autosuspend
298       periods for autosuspend
329     - same as pm_runtime_suspend() except that the autosuspend delay is taken
331       not yet expired then an autosuspend is scheduled for the appropriate time
349       device when the autosuspend delay has expired; if the delay has already
492     - set the power.use_autosuspend flag, enabling autosuspend delays; call
497     - clear the power.use_autosuspend flag, disabling autosuspend delays;
511     - calculate the time when the current autosuspend delay period will expire,
590 time.  A driver that makes use of the runtime autosuspend feature, may want to
826 9. Autosuspend, or automatically-delayed suspends
838 The term "autosuspend" is an historical remnant.  It doesn't mean that the
851 In order to use autosuspend, subsystems or drivers must call
854 instead of the non-autosuspend counterparts::
861 Drivers may also continue to use the non-autosuspend helper functions; they
862 will behave normally, which means sometimes taking the autosuspend delay into
867 autosuspend delay time has expired.  If the ->runtime_suspend() callback
868 returns -EAGAIN or -EBUSY, and if the next autosuspend delay expiration time is
871 autosuspend.  The ->runtime_suspend() callback can't do this rescheduling
935 The important point is that after foo_io_completion() asks for an autosuspend,