1. 20 8月, 2011 1 次提交
  2. 14 8月, 2011 2 次提交
    • C
      PM / Runtime: Add might_sleep() to runtime PM functions · 311aab73
      Colin Cross 提交于
      Some of the entry points to pm runtime are not safe to
      call in atomic context unless pm_runtime_irq_safe() has
      been called.  Inspecting the code, it is not immediately
      obvious that the functions sleep at all, as they run
      inside a spin_lock_irqsave, but under some conditions
      they can drop the lock and turn on irqs.
      
      If a driver incorrectly calls the pm_runtime apis, it can
      cause sleeping and irq processing when it expects to stay
      in atomic context.
      
      Add might_sleep_if to the majority of the __pm_runtime_* entry points
      to enforce correct usage.
      
      Add pm_runtime_put_sync_autosuspend to the list of
      functions that can be called in atomic context.
      Signed-off-by: NColin Cross <ccross@android.com>
      Reviewed-by: NKevin Hilman <khilman@ti.com>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      311aab73
    • R
      PM / Domains: Fix build for CONFIG_PM_RUNTIME unset · 17f2ae7f
      Rafael J. Wysocki 提交于
      Function genpd_queue_power_off_work() is not defined for
      CONFIG_PM_RUNTIME, so pm_genpd_poweroff_unused() causes a build
      error to happen in that case.  Fix the problem by making
      pm_genpd_poweroff_unused() depend on CONFIG_PM_RUNTIME too.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      17f2ae7f
  3. 12 8月, 2011 7 次提交
  4. 11 8月, 2011 15 次提交
  5. 10 8月, 2011 8 次提交
  6. 09 8月, 2011 7 次提交