1. 22 8月, 2011 1 次提交
  2. 19 7月, 2011 1 次提交
  3. 12 5月, 2011 2 次提交
  4. 18 2月, 2011 1 次提交
  5. 16 7月, 2010 1 次提交
  6. 05 2月, 2010 2 次提交
    • S
      davinci: add power management support · efc1bb8a
      Sekhar Nori 提交于
      This patch adds core power management (suspend-to-RAM)
      support for DaVinci SoCs.
      
      The code depends on the the "deepsleep" feature to suspend
      the SoC and saves power by gating the input clock.
      
      The wakeup can be based on an external event as supported
      by the SoC.
      
      Assembly code (in sleep.S) is added to aid gating DDR2
      clocks. Code doing this work should not be accessing DDR2.
      The assembly code is relocated to SRAM by the code in pm.c
      
      The support has been validated on DA850/OMAP-L138 only
      though the code is (hopefully) generic enough that other
      SoCs supporting deepsleep feature simply requires SoC
      specific code to start using this driver.
      
      Note that all the device drivers don't support suspend/resume
      still and are being worked on.
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      efc1bb8a
    • S
      davinci: move DDR2 controller defines to memory.h · 7ec4b243
      Sekhar Nori 提交于
      Move defintions of DDR2 controller registers to memory.h
      from cpuidle.c. The motivation behind the change is to be
      able to use these defintions in assembly code that puts
      DDR2 in self-refresh and enables the SoC to enter suspend
      state.
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      7ec4b243
  7. 26 8月, 2009 1 次提交
    • M
      davinci: da8xx: Add base DA830/OMAP-L137 SoC support · 55c79a40
      Mark A. Greer 提交于
      The da830/omap l137 is a new SoC from TI that is similar
      to the davinci line.  Since its so similar to davinci,
      put the support for the da830 in the same directory as
      the davinci code.
      
      There are differences, however.  Some of those differences
      prevent support for davinci and da830 platforms to work
      in the same kernel binary.  Those differences are:
      
      1) Different physical address for RAM.  This is relevant
         to Makefile.boot addresses and PHYS_OFFSET.  The
         Makefile.boot issue isn't truly a kernel issue but
         it means u-boot won't work with a uImage including
         both architectures.  The PHYS_OFFSET issue is
         addressed by the "Allow for runtime-determined
         PHYS_OFFSET" patch by Lennert Buytenhek but it
         hasn't been accepted yet.
      
      2) Different uart addresses.  This is only an issue
         for the 'addruart' assembly macro when CONFIG_DEBUG_LL
         is enabled.  Since the code in that macro is called
         so early (e.g., by _error_p in kernel/head.S when
         the processor lookup fails), we can't determine what
         platform the kernel is running on at runtime to use
         the correct uart address.
      
      These areas have compile errors intentionally inserted
      to indicate to the builder they're doing something wrong.
      
      A new config variable, CONFIG_ARCH_DAVINCI_DMx, is added
      to distinguish between a true davinci architecture and
      the da830 architecture.
      
      Note that the da830 currently has an issue with writeback
      data cache so CONFIG_CPU_DCACHE_WRITETHROUGH should be
      enabled when building a da830 kernel.
      
      Additional generalizations for future SoCs in the da8xx family done by
      Sudhakar Rajashekhara and Sekhar Nori.
      Signed-off-by: NSteve Chen <schen@mvista.com>
      Signed-off-by: NMikhail Cherkashin <mcherkashin@ru.mvista.com>
      Signed-off-by: NMark A. Greer <mgreer@mvista.com>
      Cc: Sudhakar Rajashekhara <sudhakar.raj@ti.com>
      Cc: Sekhar Nori <nsekhar@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      55c79a40
  8. 29 5月, 2009 1 次提交
  9. 30 11月, 2008 1 次提交
  10. 28 11月, 2008 1 次提交
    • N
      [ARM] remove a common set of __virt_to_bus definitions · b5ee9002
      Nicolas Pitre 提交于
      Let's provide an overridable default instead of having every machine
      class define __virt_to_bus and __bus_to_virt to the same thing.  What
      most platforms are using is bus_addr == phys_addr so such is the default.
      
      One exception is ebsa110 which has no DMA what so ever, so the actual
      definition is not important except only for proper compilation.  Also
      added a comment about the special footbridge bus translation.
      
      Let's also remove comments alluding to set_dma_addr which is not
      (and should not) be commonly used.
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      b5ee9002
  11. 07 8月, 2008 1 次提交
  12. 12 5月, 2007 1 次提交