1. 24 4月, 2013 1 次提交
  2. 23 4月, 2013 1 次提交
  3. 22 4月, 2013 4 次提交
  4. 30 3月, 2012 1 次提交
  5. 21 3月, 2012 1 次提交
  6. 18 11月, 2011 5 次提交
  7. 07 11月, 2011 2 次提交
  8. 01 11月, 2011 1 次提交
  9. 02 7月, 2011 1 次提交
    • R
      PM / Domains: Rename struct dev_power_domain to struct dev_pm_domain · 564b905a
      Rafael J. Wysocki 提交于
      The naming convention used by commit 7538e3db6e015e890825fbd9f86599b
      (PM: Add support for device power domains), which introduced the
      struct dev_power_domain type for representing device power domains,
      evidently confuses some developers who tend to think that objects
      of this type must correspond to "power domains" as defined by
      hardware, which is not the case.  Namely, at the kernel level, a
      struct dev_power_domain object can represent arbitrary set of devices
      that are mutually dependent power management-wise and need not belong
      to one hardware power domain.  To avoid that confusion, rename struct
      dev_power_domain to struct dev_pm_domain and rename the related
      pointers in struct device and struct pm_clk_notifier_block from
      pwr_domain to pm_domain.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NKevin Hilman <khilman@ti.com>
      564b905a
  10. 23 5月, 2011 1 次提交
  11. 29 4月, 2011 1 次提交
    • R
      shmobile: Use power domains for platform runtime PM · 38ade3a1
      Rafael J. Wysocki 提交于
      shmobile platforms replace the runtime PM callbacks of the platform
      bus type with their own routines, but this means that the callbacks
      are replaced system-wide.  This may not be the right approach if the
      platform devices on the system are not of the same type (e.g. some
      of them belong to an SoC and the others are located in separate
      chips), because in those cases they may require different handling.
      Thus it is better to use power domains to override the platform bus
      type's PM handling, as it generally is possible to use different
      power domains for devices with different PM requirements.
      
      Define a default power domain for shmobile in both the SH and ARM
      falvors and use it to override the platform bus type's PM callbacks.
      Since the suspend and hibernate callbacks of the new "default" power
      domains need to be the same and the platform bus type's suspend and
      hibernate callbacks for the time being, export those callbacks so
      that can be used outside of the platform bus type code.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      38ade3a1
  12. 11 3月, 2011 1 次提交
  13. 13 1月, 2011 1 次提交
  14. 16 11月, 2010 1 次提交
  15. 26 2月, 2010 1 次提交
  16. 04 12月, 2009 1 次提交
  17. 30 10月, 2009 7 次提交
  18. 23 8月, 2009 2 次提交
    • P
      sh: Fix section mismatch in platform bus notifier. · a62926fe
      Paul Mundt 提交于
      The runtime PM for SH-Mobile code had platform_bus_notify() as __devinit,
      which is rather bogus. Kill off the annotation, which subsequently
      silences the section mismatch warnings.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      a62926fe
    • M
      sh: Runtime PM for SuperH Mobile platform bus devices · 6a93dde1
      Magnus Damm 提交于
      This patch is V3 of the SuperH Mobile Runtime PM platform bus
      implentation matching Rafael's Runtime PM v16.
      
      The code gets invoked from the SuperH specific Runtime PM
      platform bus functions that override the weak symbols for:
       - platform_pm_runtime_suspend()
       - platform_pm_runtime_resume()
       - platform_pm_runtime_idle()
      
      This Runtime PM implementation performs two levels of power
      management. At the time of platform bus runtime suspend the
      clock to the device is stopped instantly. Later on if all
      devices within the power domain has their clocks stopped
      then the device driver ->runtime_suspend() callbacks are
      used to save hardware register state for each device.
      
      Device driver ->runtime_suspend() calls are scheduled from
      cpuidle context using platform_pm_runtime_suspend_idle().
      When all devices have been fully suspended the processor
      is allowed to enter deep sleep from cpuidle.
      
      The runtime resume operation turns on clocks and also
      restores registers if needed. It is worth noting that the
      devices start in a suspended state and the device driver
      is responsible for calling runtime resume before accessing
      the actual hardware.
      
      In this particular platform bus implementation runtime
      resume is not allowed from interrupt context. Runtime
      suspend is however allowed from interrupt context as
      long as the synchronous functions are avoided.
      
      [ updated for v17 -- PFM. ]
      Signed-off-by: NMagnus Damm <damm@igel.co.jp>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      6a93dde1
  19. 18 8月, 2009 2 次提交
  20. 15 8月, 2009 1 次提交
    • M
      sh: sh7724 ddr self-refresh changes · 237674e0
      Magnus Damm 提交于
      This patch updates the SuperH Mobile sleep assembly code with
      support for DBSC memory controller found in the sh7724 processor.
      
      Without this fix the memory hooked up to the sh7724 processor
      will never enter self-refresh mode before suspending to ram. The
      effect of this is that the memory contents most likeley will be
      lost upon resume which may or may not be what you want.
      Signed-off-by: NMagnus Damm <damm@igel.co.jp>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      237674e0
  21. 04 7月, 2009 1 次提交
    • M
      sh: cpuidle for SuperH Mobile using hwblk · 7426394f
      Magnus Damm 提交于
      This patch adds cpuidle support for SuperH Mobile.
      
      The sleep mode selected by cpuidle is compared with
      the mode selected by the hwblk sleep code and the
      best allowed mode is entered.
      
      At this point "Sleep mode" and "Sleep mode + SF" are
      supported. This code can easily be extended to support
      "Software suspend mode", but the assembly code must
      first be updated to avoid loosing interrupts.
      
      Also, update the code to only copy the assembly snippet
      into internal memory once at bootup.
      Signed-off-by: NMagnus Damm <damm@igel.co.jp>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      7426394f
  22. 16 3月, 2009 1 次提交