1. 29 9月, 2011 1 次提交
  2. 28 9月, 2011 6 次提交
  3. 27 9月, 2011 2 次提交
  4. 20 9月, 2011 8 次提交
  5. 06 9月, 2011 5 次提交
  6. 14 8月, 2011 3 次提交
  7. 12 8月, 2011 1 次提交
  8. 09 8月, 2011 2 次提交
  9. 08 8月, 2011 7 次提交
  10. 06 8月, 2011 2 次提交
    • K
      PM / Runtime: Allow _put_sync() from interrupts-disabled context · 02b26774
      Kevin Hilman 提交于
      Currently the use of pm_runtime_put_sync() is not safe from
      interrupts-disabled context because rpm_idle() will release the
      spinlock and enable interrupts for the idle callbacks.  This enables
      interrupts during a time where interrupts were expected to be
      disabled, and can have strange side effects on drivers that expected
      interrupts to be disabled.
      
      This is not a bug since the documentation clearly states that only
      _put_sync_suspend() is safe in IRQ-safe mode.
      
      However, pm_runtime_put_sync() could be made safe when in IRQ-safe
      mode by releasing the spinlock but not re-enabling interrupts, which
      is what this patch aims to do.
      
      Problem was found when using some buggy drivers that set
      pm_runtime_irq_safe() and used _put_sync() in interrupts-disabled
      context.
      Reported-by: NColin Cross <ccross@google.com>
      Tested-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      02b26774
    • R
      PM / Domains: Fix pm_genpd_poweron() · fe202fde
      Rafael J. Wysocki 提交于
      The local variable ret is defined twice in pm_genpd_poweron(), which
      causes this function to always return 0, even if the PM domain's
      .power_on() callback fails, in which case an error code should be
      returned.
      
      Remove the wrong second definition of ret and additionally remove an
      unnecessary definition of wait from pm_genpd_poweron().
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      fe202fde
  11. 28 7月, 2011 1 次提交
    • A
      devtmpfs: missing initialialization in never-hit case · 9d108d25
      Al Viro 提交于
      create_path() on something without a single / in it will return err
      without initializing it.  It actually can't happen (we call that thing
      only if create on the same path returns -ENOENT, which won't happen
      happen for single-component path), but in this case initializing err
      to 0 is more than making compiler to STFU - would be the right thing
      to return on such paths; the function creates a parent directory of
      given pathname and in that case it has no work to do...
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      9d108d25
  12. 27 7月, 2011 2 次提交