1. 26 1月, 2012 2 次提交
  2. 21 1月, 2012 1 次提交
  3. 14 1月, 2012 1 次提交
  4. 12 1月, 2012 2 次提交
  5. 10 1月, 2012 3 次提交
  6. 09 1月, 2012 9 次提交
  7. 06 1月, 2012 1 次提交
  8. 03 1月, 2012 1 次提交
  9. 26 12月, 2011 4 次提交
    • R
      PM / shmobile: Allow the A4R domain to be turned off at run time · a8cf27be
      Rafael J. Wysocki 提交于
      After adding PM QoS constraints for the I2C controller in the A4R
      domain, that domain can be allowed to be turned off and on by runtime
      PM, so remove the "always on" governor from it.
      
      However, the A4R domain has to be "on" when suspend_device_irqs() and
      resume_device_irqs() are executed during system suspend and resume,
      respectively, so that those functions don't crash while accessing the
      INTCS.  For this reason, add a PM notifier to the SH7372 PM code and
      make it restore power to A4R before system suspend and remove power
      from all unused PM domains after system resume.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NMagnus Damm <damm@opensource.se>
      a8cf27be
    • R
      PM / shmobile: Remove the stay_on flag from SH7372's PM domains · 767c0f3a
      Rafael J. Wysocki 提交于
      SH7372 uses two independent mechanisms for ensuring that power
      domains will never be turned off: the stay_on flag and the "always
      on" domain governor.  Moreover, the "always on" governor is only taken
      into accout by runtime PM code paths, while the stay_on flag affects
      all attempts to turn the given domain off.  Thus setting the stay_on
      flag causes the "always on" governor to be unnecessary, which is
      quite confusing.
      
      However, the stay_on flag is currently only set for two domains: A3SP
      and A4S.  Moreover, it only is set for the A3SP domain if
      console_suspend_enabled is set, so stay_on won't be necessary for
      that domain any more if console_suspend_enabled is checked directly
      in its .suspend() routine.  [This requires domain .suspend() to
      return a result, but that is a minor modification.]  Analogously,
      stay_on won't be necessary for the A4S domain if it's .suspend()
      routine always returns an error code.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NMagnus Damm <damm@opensource.se>
      767c0f3a
    • R
      PM / shmobile: Don't include SH7372's INTCS in syscore suspend/resume · 0f966d74
      Rafael J. Wysocki 提交于
      Since the SH7372's INTCS in included into syscore suspend/resume,
      which causes the chip to be accessed when PM domains have been
      turned off during system suspend, the A4R domain containing the
      INTCS has to stay on during system sleep, which is suboptimal
      from the power consumption point of view.
      
      For this reason, add a new INTC flag, skip_syscore_suspend, to mark
      the INTCS for intc_suspend() and intc_resume(), so that they don't
      touch it.  This allows the A4R domain to be turned off during
      system suspend and the INTCS state is resrored during system
      resume by the A4R's "power on" code.
      Suggested-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NMagnus Damm <damm@opensource.se>
      0f966d74
    • M
      PM / shmobile: Add support for the sh7372 A4S power domain / sleep mode · f7dadb37
      Magnus Damm 提交于
      The sh7372 contains a power domain named A4S which in turn
      contains power domains for both I/O Devices and CPU cores.
      
      At this point only System wide Suspend-to-RAM is supported,
      but the the hardware can also support CPUIdle. With more
      efforts in the future CPUIdle can work with bot A4S and A3SM.
      
      Tested on the sh7372 Mackerel board.
      
      [rjw: Rebased on top of the current linux-pm tree.]
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      f7dadb37
  10. 24 12月, 2011 1 次提交
  11. 20 12月, 2011 1 次提交
  12. 10 12月, 2011 1 次提交
  13. 07 12月, 2011 1 次提交
  14. 06 12月, 2011 1 次提交
  15. 02 12月, 2011 2 次提交
    • R
      PM / Domains: Add device stop governor function (v4) · b02c999a
      Rafael J. Wysocki 提交于
      Add a function deciding whether or not devices should be stopped in
      pm_genpd_runtime_suspend() depending on their PM QoS constraints
      and stop/start timing values.  Make it possible to add information
      used by this function to device objects.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NMagnus Damm <damm@opensource.se>
      b02c999a
    • R
      PM / Domains: Make it possible to use per-device domain callbacks · d5e4cbfe
      Rafael J. Wysocki 提交于
      The current generic PM domains code requires that the same .stop(),
      .start() and .active_wakeup() device callback routines be used for
      all devices in the given domain, which is inflexible and may not
      cover some specific use cases.  For this reason, make it possible to
      use device specific .start()/.stop() and .active_wakeup() callback
      routines by adding corresponding callback pointers to struct
      generic_pm_domain_data.  Add a new helper routine,
      pm_genpd_register_callbacks(), that can be used to populate
      the new per-device callback pointers.
      
      Modify the shmobile's power domains code to allow drivers to add
      their own code to be run during the device stop and start operations
      with the help of the new callback pointers.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NMagnus Damm <damm@opensource.se>
      d5e4cbfe
  16. 27 11月, 2011 1 次提交
  17. 24 11月, 2011 7 次提交
    • K
      ASoC: fsi-ak4642: modify specification method of FSI / ak464x · 45f31216
      Kuninori Morimoto 提交于
      Current fsi-ak4642 was using id_entry name in order to specify
      FSI port and ak464x codec.
      But it was no sense, no flexibility.
      Platform can specify FSI/ak464x pair by this patch.
      Acked-by: NPaul Mundt <lethal@linux-sh.org>
      Signed-off-by: NKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      45f31216
    • M
      ARM: mach-shmobile: SH73A0 external Ethernet fix · 9bcc0a5d
      Magnus Damm 提交于
      Keep the ZB clock enabled on sh73a0 to allow the BSC
      to access external peripherals hooked up to CS signals.
      
      This is needed to unbreak Ethernet support on sh73a0 boards
      such as AG5EVM and Kota2 together with the following patch:
      
       794d78fe drivers: sh: late disabling of clocks V2
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      9bcc0a5d
    • M
      ARM: mach-shmobile: AG5EVM GIC Sparse IRQ fix · eded9143
      Magnus Damm 提交于
      Fix IRQ support on the AG5EVM board. The sh73a0 and the AG5EVM
      board make use of the ARM GIC hardware block as main interrupt
      controller. The following commit changed the default behaviour
      for non-device tree platforms and broke AG5EVM irq support:
      
      f37a53cc ARM: gic: fix irq_alloc_descs handling for sparse irq
      
      Without this fix the following warning triggers at boot:
      
      NR_IRQS:1024 nr_irqs:1024 1024
      ------------[ cut here ]------------
      WARNING: at arch/arm/common/gic.c:607 gic_init+0x90/0x2e4()
      Cannot allocate irq_descs @ IRQ16, assuming pre-allocated
      [<c000c868>] (unwind_backtrace+0x0/0xe0) from [<c001857c>] (warn_slowpath_commo)
      [<c001857c>] (warn_slowpath_common+0x48/0x60) from [<c00185d8>] (warn_slowpath_)
      [<c00185d8>] (warn_slowpath_fmt+0x2c/0x3c) from [<c029ee08>] (gic_init+0x90/0x2)
      [<c029ee08>] (gic_init+0x90/0x2e4) from [<c029f278>] (sh73a0_init_irq+0x30/0x18)
      [<c029f278>] (sh73a0_init_irq+0x30/0x184) from [<c029c0b4>] (init_IRQ+0x14/0x1c)
      [<c029c0b4>] (init_IRQ+0x14/0x1c) from [<c029a5cc>] (start_kernel+0x15c/0x2b8)
      [<c029a5cc>] (start_kernel+0x15c/0x2b8) from [<4000803c>] (0x4000803c)
      ---[ end trace 1b75b31a2719ed1c ]---
      
      With this fix applied interrupts work as expected.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      eded9143
    • M
      ARM: mach-shmobile: Kota2 TPU LED platform data · 33661c9e
      Magnus Damm 提交于
      This patch updates the Kota2 board support code to
      use the recently merged TPU LED driver whenever
      possible.
      
      The sh73a0 SoC has 5 TPU hardware blocks each with
      4 timer channels which in theory allows a total of
      20 LEDs to be controlled by "leds-renesas-tpu"
      driver instances. The Kota2 board has 4 LEDs connected
      to GPIO pins that also come with TPU pin functions, so
      this patch ties up these 4 LEDS and leaves the remaining
      3 LEDS for the GPIO based LED driver.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      33661c9e
    • M
      ARM: mach-shmobile: Kota2 GIC Sparse IRQ fix · dcb4ea86
      Magnus Damm 提交于
      Fix IRQ support on the Kota2 board. The sh73a0 and the Kota2
      board make use of the ARM GIC hardware block as main interrupt
      controller. The following commit changed the default behaviour
      for non-device tree platforms and broke Kota2 irq support:
      
      f37a53cc ARM: gic: fix irq_alloc_descs handling for sparse irq
      
      Without this fix the following warning triggers at boot:
      
      NR_IRQS:1024 nr_irqs:1024 1024
      ------------[ cut here ]------------
      WARNING: at arch/arm/common/gic.c:607 gic_init+0x90/0x2e4()
      Cannot allocate irq_descs @ IRQ16, assuming pre-allocated
      [<c000c868>] (unwind_backtrace+0x0/0xe0) from [<c001857c>] (warn_slowpath_commo)
      [<c001857c>] (warn_slowpath_common+0x48/0x60) from [<c00185d8>] (warn_slowpath_)
      [<c00185d8>] (warn_slowpath_fmt+0x2c/0x3c) from [<c029ee08>] (gic_init+0x90/0x2)
      [<c029ee08>] (gic_init+0x90/0x2e4) from [<c029f278>] (sh73a0_init_irq+0x30/0x18)
      [<c029f278>] (sh73a0_init_irq+0x30/0x184) from [<c029c0b4>] (init_IRQ+0x14/0x1c)
      [<c029c0b4>] (init_IRQ+0x14/0x1c) from [<c029a5cc>] (start_kernel+0x15c/0x2b8)
      [<c029a5cc>] (start_kernel+0x15c/0x2b8) from [<4000803c>] (0x4000803c)
      ---[ end trace 1b75b31a2719ed1c ]---
      
      With this fix applied interrupts work as expected.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      dcb4ea86
    • M
      ARM: mach-shmobile: Kota2 PINT fix · 1b6cec8a
      Magnus Damm 提交于
      Support PINT on sh73a0 and Kota2 using INTC PINT macros.
      
      With this patch applied the Kota2 ethernet is handled
      through one of the chained sh73a0 PINT interrupt controllers.
      
      sh73a0 PINT support is included in 3.2-rc but the Kota2 board
      code does not make use of this shared code base without this
      patch. Without this patch kota2 on-board ethernet is broken.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      1b6cec8a
    • K
      sh: clkfwk: setup clock parent from current register value · 56242a1f
      Kuninori Morimoto 提交于
      Some clocks can select its parent clock by CPG register.
      But it might have been modified by boot-loader or something.
      This patch removed fixed initial parent clock,
      and setup it from their current register settings.
      It works on div6 reparent clocks for now.
      Signed-off-by: NKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      56242a1f
  18. 22 11月, 2011 1 次提交