1. 25 Apr, 2018 1 commit
  2. 23 Apr, 2018 1 commit
  3. 22 Apr, 2018 1 commit
  4. 26 Mar, 2018 4 commits
  5. 23 Mar, 2018 7 commits
  6. 22 Mar, 2018 3 commits
  7. 20 Mar, 2018 2 commits
  8. 06 Mar, 2018 1 commit
  9. 19 Feb, 2018 1 commit
  10. 16 Feb, 2018 1 commit
  11. 02 Feb, 2018 2 commits
  12. 25 Jan, 2018 1 commit
  13. 10 Jan, 2018 5 commits
  14. 09 Jan, 2018 1 commit
  15. 08 Jan, 2018 2 commits
  16. 02 Jan, 2018 2 commits
    • Rafael J. Wysocki's avatar
      PM / core: Direct DPM_FLAG_LEAVE_SUSPENDED handling · 32bfa56a
      Rafael J. Wysocki authored
      Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for
      devices whose "noirq", "late" and "early" driver callbacks are
      invoked directly by it.
      Namely, make it skip all of the system-wide resume callbacks for
      such devices with DPM_FLAG_LEAVE_SUSPENDED set if they are in
      runtime suspend during the "noirq" phase of system-wide suspend
      (or analogous) transitions or the system transition under way is
      a proper suspend (rather than anything related to hibernation) and
      the device's wakeup settings are compatible with runtime PM (that
      is, the device cannot generate wakeup signals at all or it is
      allowed to wake up the system from sleep).
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
    • Rafael J. Wysocki's avatar
      PM / core: Direct DPM_FLAG_SMART_SUSPEND optimization · 75e94645
      Rafael J. Wysocki authored
      Make the PM core avoid invoking the "late" and "noirq" system-wide
      suspend (or analogous) callbacks provided by device drivers directly
      for devices with DPM_FLAG_SMART_SUSPEND set that are in runtime
      suspend during the "late" and "noirq" phases of system-wide suspend
      (or analogous) transitions.  That is only done for devices without
      any middle-layer "late" and "noirq" suspend callbacks (to avoid
      confusing the middle layer if there is one).
      The underlying observation is that runtime PM is disabled for devices
      during the "late" and "noirq" system-wide suspend phases, so if they
      remain in runtime suspend from the "late" phase forward, it doesn't
      make sense to invoke the "late" and "noirq" callbacks provided by
      the drivers for them (arguably, the device is already suspended and
      in the right state).  Thus, if the remaining driver suspend callbacks
      are to be invoked directly by the core, they can be skipped.
      This change really makes it possible for, say, platform device
      drivers to re-use runtime PM suspend and resume callbacks by
      pointing ->suspend_late and ->resume_early, respectively (and
      possibly the analogous hibernation-related callback pointers too),
      to them without adding any extra "is the device already suspended?"
      type of checks to the callback routines, as long as they will be
      invoked directly by the core.
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
  17. 21 Dec, 2017 1 commit
  18. 19 Dec, 2017 2 commits
  19. 12 Dec, 2017 1 commit
  20. 11 Dec, 2017 1 commit