1. 03 1月, 2011 1 次提交
  2. 20 10月, 2010 1 次提交
  3. 16 7月, 2010 1 次提交
  4. 13 2月, 2010 1 次提交
  5. 23 11月, 2009 1 次提交
  6. 30 10月, 2009 3 次提交
    • M
      iop: enable generic time · 980f2296
      Mikael Pettersson 提交于
      This updates the IOP platform to use the kernel's generic time
      framework. With clockevent support in place, this reduces to
      selecting GENERIC_TIME and removing the platform's private timer
      ->offset() operation (iop_gettimeoffset).
      
      Tested on n2100, compile-tested for all plat-iop machines.
      Signed-off-by: NMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      980f2296
    • M
      iop: clockevent support · 469d3044
      Mikael Pettersson 提交于
      This updates the IOP platform to expose the interrupting
      timer 0 as a clockevent object. The timer interrupt handler
      is changed to call the clockevent ->event_handler() instead
      of timer_tick(), and ->set_next_event() and ->set_mode()
      operations are added to allow the mode of the timer to be
      updated (required for ONESHOT/NOHZ mode).
      
      Timer 0 must now be properly initialised, which requires
      a new write_tcr0() function from the mach-specific code.
      
      The mode of timer 0 must be read at the start of ->set_mode(),
      which requires a new read_tmr0() function from the mach-
      specific code.
      
      Initial setup of timer 0 is also rewritten to be more robust.
      
      Tested on n2100, compile-tested for all plat-iop machines.
      Signed-off-by: NMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      469d3044
    • M
      iop: clocksource support · a91549a8
      Mikael Pettersson 提交于
      This updates the IOP platform to expose the free-running
      timer 1 as a clocksource object. This timer is now also
      properly initialised, which requires a new write_tcr1()
      function from the mach-specific code. Apart from the
      explicit initialisation, there is no functional change
      in how timer 1 is programmed.
      
      Tested on n2100, compile-tested for all plat-iop machines.
      Signed-off-by: NMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      a91549a8
  7. 30 8月, 2009 2 次提交
    • D
      iop-adma: P+Q support for iop13xx adma engines · 7bf649ae
      Dan Williams 提交于
      iop33x support is not included because that engine is a bit more awkward
      to handle in that it can either be in xor mode or pq mode.  The
      dmaengine/async_tx layers currently only comprehend static capabilities.
      
      Note iop13xx does not support hardware PQ continuation so the driver
      must handle the DMA_PREP_CONTINUE flag for operations across > 16
      sources. From the comment for dma_maxpq:
      
      /* When an engine does not support native continuation we need 3 extra
       * source slots to reuse P and Q with the following coefficients:
       * 1/ {00} * P : remove P from Q', but use it as a source for P'
       * 2/ {01} * Q : use Q to continue Q' calculation
       * 3/ {00} * Q : subtract Q from P' to cancel (2)
       */
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      
      
      
      
      
      7bf649ae
    • D
      async_tx: add sum check flags · ad283ea4
      Dan Williams 提交于
      Replace the flat zero_sum_result with a collection of flags to contain
      the P (xor) zero-sum result, and the soon to be utilized Q (raid6 reed
      solomon syndrome) zero-sum result.  Use the SUM_CHECK_ namespace instead
      of DMA_ since these flags will be used on non-dma-zero-sum enabled
      platforms.
      Reviewed-by: NAndre Noll <maan@systemlinux.org>
      Acked-by: NMaciej Sosnowski <maciej.sosnowski@intel.com>
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      ad283ea4
  8. 20 3月, 2009 1 次提交
    • R
      [ARM] pass reboot command line to arch_reset() · be093beb
      Russell King 提交于
      OMAP wishes to pass state to the boot loader upon reboot in order to
      instruct it whether to wait for USB-based reflashing or not.  There is
      already a facility to do this via the reboot() syscall, except we ignore
      the string passed to machine_restart().
      
      This patch fixes things to pass this string to arch_reset().  This means
      that we keep the reboot mode limited to telling the kernel _how_ to
      perform the reboot which should be independent of what we request the
      boot loader to do.
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      be093beb
  9. 16 3月, 2009 1 次提交
    • N
      [ARM] make page_to_dma() highmem aware · 58edb515
      Nicolas Pitre 提交于
      If a machine class has a custom __virt_to_bus() implementation then it
      must provide a __arch_page_to_dma() implementation as well which is
      _not_ based on page_address() to support highmem.
      
      This patch fixes existing __arch_page_to_dma() and provide a default
      implementation otherwise.  The default implementation for highmem is
      based on __pfn_to_bus() which is defined only when no custom
      __virt_to_bus() is provided by the machine class.
      
      That leaves only ebsa110 and footbridge which cannot support highmem
      until they provide their own __arch_page_to_dma() implementation.
      But highmem support on those legacy platforms with limited memory is
      certainly not a priority.
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      58edb515
  10. 30 11月, 2008 1 次提交
    • R
      [ARM] Hide ISA DMA API when ISA_DMA_API is unset · dcea83ad
      Russell King 提交于
      When ISA_DMA_API is unset, we're not implementing the ISA DMA API,
      so there's no point in publishing the prototypes via asm/dma.h, nor
      including the machine dependent parts of that API.
      
      This allows us to remove a lot of mach/dma.h files which don't contain
      any useful code.  Unfortunately though, some platforms put their own
      private non-ISA definitions into mach/dma.h, so we leave these behind
      and fix the appropriate #include statments.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      dcea83ad
  11. 29 11月, 2008 1 次提交
  12. 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
  13. 12 11月, 2008 1 次提交
  14. 21 10月, 2008 1 次提交
  15. 18 9月, 2008 1 次提交
  16. 06 9月, 2008 1 次提交
  17. 01 9月, 2008 1 次提交
  18. 07 8月, 2008 1 次提交