Skip to content

C
clone-Linux

gsplhtlxg / clone-Linux

通知 2
Star 0
Fork 1
C
clone-Linux

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 31 7月, 2014 1 次提交
  3. 22 7月, 2014 1 次提交
  5. 10 7月, 2014 2 次提交
  7. 08 3月, 2014 1 次提交
  9. 06 1月, 2014 1 次提交
  11. 12 12月, 2013 1 次提交
  13. 26 11月, 2013 1 次提交
  15. 20 11月, 2013 1 次提交
  17. 03 10月, 2013 1 次提交
  19. 30 7月, 2013 1 次提交
    • M
      staging: nvec: re-enable the clock on resume · ca250b60
      由 Marc Dietrich 提交于 
      On resume the slave controller is reinitialized. The tegra i2c master
controller disables the clock at the end of the initialiation, propably
to save some power, and enables it again on each transfer. We don't
do this yet and also forgot to enable the clock on resume. Fix this
copy-paste error by not disabling the clock after initialization.

This didn't striked us yet because suspend/resume hasn't landed in mainline
yet, but will soon.
Signed-off-by: NMarc Dietrich <marvin24@gmx.de>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ca250b60
  21. 25 6月, 2013 2 次提交
  23. 18 5月, 2013 1 次提交
  25. 17 5月, 2013 1 次提交
  27. 14 5月, 2013 5 次提交
  29. 26 3月, 2013 1 次提交
  31. 30 1月, 2013 2 次提交
  33. 29 1月, 2013 2 次提交
  35. 23 1月, 2013 1 次提交
  37. 22 11月, 2012 4 次提交
  39. 06 11月, 2012 1 次提交
  41. 16 9月, 2012 1 次提交
    • M
      mfd: core: Push irqdomain mapping out into devices · 0848c94f
      由 Mark Brown 提交于 
      Currently the MFD core supports remapping MFD cell interrupts using an
irqdomain but only if the MFD is being instantiated using device tree
and only if the device tree bindings use the pattern of registering IPs
in the device tree with compatible properties.  This will be actively
harmful for drivers which support non-DT platforms and use this pattern
for their DT bindings as it will mean that the core will silently change
remapping behaviour and it is also limiting for drivers which don't do
DT with this particular pattern.  There is also a potential fragility if
there are interrupts not associated with MFD cells and all the cells are
omitted from the device tree for some reason.

Instead change the code to take an IRQ domain as an optional argument,
allowing drivers to take the decision about the parent domain for their
interrupts.  The one current user of this feature is ab8500-core, it has
the domain lookup pushed out into the driver.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      0848c94f
  43. 14 9月, 2012 1 次提交
    • M
      mfd: core: Push irqdomain mapping out into devices · 55692af5
      由 Mark Brown 提交于 
      Currently the MFD core supports remapping MFD cell interrupts using an
irqdomain but only if the MFD is being instantiated using device tree
and only if the device tree bindings use the pattern of registering IPs
in the device tree with compatible properties.  This will be actively
harmful for drivers which support non-DT platforms and use this pattern
for their DT bindings as it will mean that the core will silently change
remapping behaviour and it is also limiting for drivers which don't do
DT with this particular pattern.  There is also a potential fragility if
there are interrupts not associated with MFD cells and all the cells are
omitted from the device tree for some reason.

Instead change the code to take an IRQ domain as an optional argument,
allowing drivers to take the decision about the parent domain for their
interrupts.  The one current user of this feature is ab8500-core, it has
the domain lookup pushed out into the driver.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      55692af5
  45. 05 9月, 2012 3 次提交
  47. 14 8月, 2012 2 次提交
  49. 26 6月, 2012 2 次提交