1. 02 5月, 2010 2 次提交
  2. 30 4月, 2010 1 次提交
  3. 02 3月, 2010 3 次提交
  4. 01 3月, 2010 1 次提交
  5. 02 12月, 2009 1 次提交
  6. 28 11月, 2009 1 次提交
  7. 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
  8. 09 9月, 2009 1 次提交
  9. 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
  10. 19 8月, 2009 1 次提交
    • A
      iop3xx: ATU and PCI memory configuration corrected · 5b9eda33
      Aaro Koskinen 提交于
      There are two 64 MB outbound memory windows at bus addresses
      0x80000000..0x83ffffff and 0x84000000..0x87ffffff for PCI
      memory. Currently, on iop32x, only the lower window is available for
      allocations, limiting the available space to 64 MB. On iop33x the full
      128 MB can be allocated, but the translation value is wrong for the
      upper window.
      
      The patch enables the full 128 MB space on iop32x and corrects the
      initialization of OMWTVR1. Redundant definitions are deleted. Tested
      using a Thecus N2100 board with a graphics adapter in the expansion
      slot. Both windows are in use:
      
        00:05.0 VGA compatible controller: XGI Technology Inc. (eXtreme Graphics
        Innovation) Volari Z7 (prog-if 00 [VGA controller])
        [...]
      	Region 0: Memory at 80000000 (32-bit, prefetchable) [size=64M]
      	Region 1: Memory at 84080000 (32-bit, non-prefetchable) [size=256K]
      Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
      Cc: Lennert Buytenhek <kernel@wantstofly.org>
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      5b9eda33
  11. 11 6月, 2009 1 次提交
  12. 30 5月, 2009 1 次提交
  13. 18 5月, 2009 2 次提交
  14. 17 5月, 2009 1 次提交
  15. 07 5月, 2009 1 次提交
    • B
      [ARM] VIC: Add power management device · c07f87f2
      Ben Dooks 提交于
      Add power management support to the VIC by registering
      each VIC as a system device to get suspend/resume
      events going.
      
      Since the VIC registeration is done early, we need to
      record the VICs in a static array which is used to add
      the system devices later once the initcalls are run. This
      means there is now a configuration value for the number
      of VICs in the system.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      c07f87f2
  16. 25 3月, 2009 1 次提交
  17. 16 12月, 2008 1 次提交
  18. 27 11月, 2008 1 次提交
  19. 12 11月, 2008 1 次提交
  20. 07 8月, 2008 2 次提交
  21. 03 8月, 2008 1 次提交