1. 04 7月, 2014 1 次提交
  2. 02 7月, 2014 2 次提交
  3. 23 5月, 2014 1 次提交
  4. 19 5月, 2014 1 次提交
  5. 16 4月, 2014 15 次提交
  6. 11 12月, 2013 2 次提交
  7. 21 11月, 2013 2 次提交
  8. 13 3月, 2013 1 次提交
    • S
      clocksource: sh_tmu: Set initcall level to subsys · b9773c3f
      Simon Horman 提交于
      The reason for this is to ensure that TMU is probed earlier
      than with its previous initcall level, module init.
      
      This came up as a problem with using CMT as a clock source kzm9g-reference
      which does not make use of early timers or devices. In that scenario
      initialisation of SDHI and MMCIF both stall on msleep() calls due to the
      absence of a initialised clock source.
      
      The purpose of this change is to keep the TMU code in sync with the CMT code
      which has been modified in a similar manner..
      
      Boot tested on: mackerel.
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      b9773c3f
  9. 04 1月, 2013 1 次提交
    • G
      Drivers: clocksource: remove __dev* attributes. · 1850514b
      Greg Kroah-Hartman 提交于
      CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
      markings need to be removed.
      
      This change removes the use of __devinit, __devexit_p, __devinitdata,
      __devinitconst, and __devexit from these drivers.
      
      Based on patches originally written by Bill Pemberton, but redone by me
      in order to handle some of the coding style issues better, by hand.
      
      Cc: Bill Pemberton <wfp5p@virginia.edu>
      Cc: John Stultz <johnstul@us.ibm.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      1850514b
  10. 04 9月, 2012 4 次提交
  11. 11 6月, 2012 2 次提交
  12. 17 3月, 2012 1 次提交
  13. 01 11月, 2011 1 次提交
  14. 31 5月, 2011 1 次提交
    • P
      Revert "clocksource: sh_tmu: Runtime PM support" · d4905ce3
      Paul Mundt 提交于
      This reverts commit 1b842e91.
      
      There is a fundamental ordering race between the early and late probe
      paths and the runtime PM tie-in that results in __pm_runtime_resume()
      attempting to take a lock that hasn't been initialized yet (which by
      proxy also suggests that pm_runtime_init() hasn't yet been run on the
      device either, making the entire thing unsafe) -- resulting in instant
      death on SMP or on UP with spinlock debugging enabled:
      
      	 sh_tmu.0: used for clock events
      	 sh_tmu.0: used for periodic clock events
      	BUG: spinlock trylock failure on UP on CPU#0, swapper/0
      	 lock: 804db198, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
      	...
      
      Revert it for now until the ordering issues can be resolved, or we can get
      some more help from the runtime PM framework to make this possible.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      d4905ce3
  15. 23 5月, 2011 2 次提交
  16. 31 10月, 2010 1 次提交
  17. 02 6月, 2010 1 次提交
  18. 15 4月, 2010 1 次提交
新手
引导
客服 返回
顶部