1. 13 8月, 2013 1 次提交
    • J
      ARM: tegra: add LP1 suspend support for Tegra30 · e7a932b1
      Joseph Lo 提交于
      The LP1 suspend mode will power off the CPU, clock gated the PLLs and put
      SDRAM to self-refresh mode. Any interrupt can wake up device from LP1. The
      sequence when LP1 suspending:
      
      * tunning off L1 data cache and the MMU
      * storing some EMC registers, DPD (deep power down) status, clk source of
        mselect and SCLK burst policy
      * putting SDRAM into self-refresh
      * switching CPU to CLK_M (12MHz OSC)
      * tunning off PLLM, PLLP, PLLA, PLLC and PLLX
      * switching SCLK to CLK_S (32KHz OSC)
      * shutting off the CPU rail
      
      The sequence of LP1 resuming:
      
      * re-enabling PLLM, PLLP, PLLA, PLLC and PLLX
      * restoring the clk source of mselect and SCLK burst policy
      * setting up CCLK burst policy to PLLX
      * restoring DPD status and some EMC registers
      * resuming SDRAM to normal mode
      * jumping to the "tegra_resume" from PMC_SCRATCH41
      
      Due to the SDRAM will be put into self-refresh mode, the low level
      procedures of LP1 suspending and resuming should be copied to
      TEGRA_IRAM_CODE_AREA (TEGRA_IRAM_BASE + SZ_4K) when suspending. Before
      restoring the CPU context when resuming, the SDRAM needs to be switched
      back to normal mode. And the PLLs need to be re-enabled, SCLK burst policy
      be restored, CCLK burst policy be set in PLLX. Then jumping to
      "tegra_resume" that was expected to be stored in PMC_SCRATCH41 to restore
      CPU context and back to kernel.
      
      Based on the work by: Scott Williams <scwilliams@nvidia.com>
      Signed-off-by: NJoseph Lo <josephl@nvidia.com>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      e7a932b1
  2. 04 4月, 2013 1 次提交
  3. 29 1月, 2013 1 次提交
    • J
      ARM: tegra: add pending SGI checking API · d4b92fb2
      Joseph Lo 提交于
      The "powered-down" CPU idle mode of Tegra cut off the vdd_cpu rail, it
      include the power of GIC. That caused the SGI (Software Generated
      Interrupt) been lost. Because the SGI can't wake up the CPU that in
      the "powered-down" CPU idle mode. We need to check if there is any
      pending SGI when go into "powered-down" CPU idle mode. This is important
      especially when applying the coupled cpuidle framework into "power-down"
      cpuidle dirver. Because the coupled cpuidle framework may have the
      chance that misses IPI_SINGLE_FUNC handling sometimes.
      
      For the PPI or SPI, something like the legacy peripheral interrupt. It
      still can be maintained by Tegra legacy interrupt controller. If there
      is any pending PPI or SPI when CPU in "powered-down" CPU idle mode. The
      CPU can be woken up immediately. So we don't need to take care the same
      situation for PPI or SPI.
      Signed-off-by: NJoseph Lo <josephl@nvidia.com>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      d4b92fb2
  4. 07 2月, 2012 1 次提交
  5. 21 1月, 2012 1 次提交
  6. 05 1月, 2012 2 次提交
  7. 31 10月, 2011 1 次提交
  8. 23 12月, 2010 1 次提交
  9. 10 9月, 2009 1 次提交
  10. 02 8月, 2008 1 次提交
    • T
      [IA64] Move include/asm-ia64 to arch/ia64/include/asm · 7f30491c
      Tony Luck 提交于
      After moving the the include files there were a few clean-ups:
      
      1) Some files used #include <asm-ia64/xyz.h>, changed to <asm/xyz.h>
      
      2) Some comments alerted maintainers to look at various header files to
      make matching updates if certain code were to be changed. Updated these
      comments to use the new include paths.
      
      3) Some header files mentioned their own names in initial comments. Just
      deleted these self references.
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      7f30491c
  11. 27 4月, 2008 1 次提交