1. 08 7月, 2016 2 次提交
  2. 21 6月, 2016 2 次提交
    • K
      dmaengine: vdma: Add 64 bit addressing support for the axi cdma · 9791e71a
      Kedareswara rao Appana 提交于
      The AXI CDMA is a soft ip, which can be programmed to support
      32 bit addressing or greater than 32 bit addressing.
      
      When the AXI CDMA ip is configured for 32 bit address space
      in simple dma mode the source/destination buffer address is
      specified by a single register(18h for Source buffer address and
      20h for Destination buffer address). When configured in SG mode
      the current descriptor and tail descriptor are specified by a
      Single register(08h for curdesc 10h for tail desc).
      
      When the  AXI CDMA core is configured for an address space greater
      than 32 then each buffer address or descriptor address is specified by
      a combination of two registers.
      
      The first register specifies the LSB 32 bits of address,
      while the next register specifies the MSB 32 bits of address.
      
      For example, 08h will specify the LSB 32 bits while 0Ch will
      specify the MSB 32 bits of the first start address.
      So we need to program two registers at a time.
      
      This patch adds the 64 bit addressing support to the axicdma
      IP in the driver.
      Signed-off-by: NKedareswara rao Appana <appanad@xilinx.com>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      9791e71a
    • K
      dmaengine: vdma: Add 64 bit addressing support for the axi dma · f0cba685
      Kedareswara rao Appana 提交于
      The AXI DMA is a soft ip, which can be programmed to support
      32 bit addressing or greater than 32 bit addressing.
      
      When the AXI DMA ip is configured for 32 bit address space
      in simple dma mode the buffer address is specified by a single register
      (18h for MM2S channel and 48h for S2MM channel). When configured in SG mode
      The current descriptor and tail descriptor are specified by a single
      Register(08h for curdesc 10h for tail desc for MM2S channel and 38h for
      Curdesc and 40h for tail desc for S2MM).
      
      When the  AXI DMA core is configured for an address space greater
      than 32 then each buffer address or descriptor address is specified by
      a combination of two registers.
      
      The first register specifies the LSB 32 bits of address,
      while the next register specifies the MSB 32 bits of address.
      
      For example, 48h will specify the LSB 32 bits while 4Ch will
      specify the MSB 32 bits of the first start address.
      So we need to program two registers at a time.
      
      This patch adds the 64 bit addressing support for the axidma
      IP in the driver.
      Signed-off-by: NKedareswara rao Appana <appanad@xilinx.com>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      f0cba685
  3. 14 6月, 2016 1 次提交
    • A
      dmaengine: xilinx-vdma: add some sanity checks · f67c3bda
      Arnd Bergmann 提交于
      The newly added xilinx_dma_prep_dma_cyclic function sometimes causes
      a gcc warning about the use of the segment function in case
      we never run into the inner loop of the function:
      
      dma/xilinx/xilinx_vdma.c: In function 'xilinx_dma_prep_dma_cyclic':
      dma/xilinx/xilinx_vdma.c:1808:23: error: 'segment' may be used uninitialized in this function [-Werror=maybe-uninitialized]
         segment->hw.control |= XILINX_DMA_BD_SOP;
      
      This can only happen if the period len is zero (which would cause other
      problems earlier), or if the buffer is shorter than a period. Neither
      of them should ever happen, but by adding an explicit check for these two
      cases, we can abort in a more controlled way, and the compiler is
      able to see that we never use uninitialized data.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      f67c3bda
  4. 13 6月, 2016 1 次提交
  5. 07 6月, 2016 2 次提交
  6. 13 5月, 2016 2 次提交
  7. 12 5月, 2016 3 次提交
  8. 03 5月, 2016 1 次提交
  9. 06 4月, 2016 4 次提交
  10. 04 3月, 2016 1 次提交
  11. 03 3月, 2016 4 次提交
  12. 01 10月, 2015 1 次提交
  13. 17 3月, 2015 1 次提交
  14. 22 12月, 2014 1 次提交
  15. 06 11月, 2014 3 次提交
  16. 20 8月, 2014 1 次提交
  17. 30 4月, 2014 1 次提交