1. 14 1月, 2013 13 次提交
  2. 05 11月, 2012 1 次提交
  3. 22 9月, 2012 1 次提交
  4. 31 8月, 2012 1 次提交
  5. 11 5月, 2012 1 次提交
    • L
      dmaengine: Use dma_sg_len(sg) instead of sg->length · fdaf9c4b
      Lars-Peter Clausen 提交于
      sg->length may or may not contain the length of the dma region to transfer,
      depending on the architecture - dma_sg_len(sg) always will though. For the
      architectures which use the drivers modified by this patch it probably is the
      case that sg->length contains the dma transfer length. But to be consistent and
      future proof change them to use dma_sg_len.
      
      To quote Russel King:
      	sg->length is meaningless to something performing DMA.
      
      	In cases where sg_dma_len(sg) and sg->length are the same storage, then
      	there's no problem. But scatterlists _can_ (and one some architectures) do
      	split them - especially when you have an IOMMU which can allow you to
      	combine a scatterlist into fewer entries.
      
      	So, anything using sg->length for the size of a scatterlist's DMA transfer
      	_after_ a call to dma_map_sg() is almost certainly buggy.
      
      The patch has been generated using the following coccinelle patch:
      <smpl>
      @@
      struct scatterlist *sg;
      expression X;
      @@
      -sg[X].length
      +sg_dma_len(&sg[X])
      @@
      struct scatterlist *sg;
      @@
      -sg->length
      +sg_dma_len(sg)
      </smpl>
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NVinod Koul <vinod.koul@linux.intel.com>
      fdaf9c4b
  6. 23 4月, 2012 3 次提交
  7. 21 3月, 2012 1 次提交
  8. 13 3月, 2012 6 次提交
  9. 02 1月, 2012 1 次提交
  10. 05 12月, 2011 1 次提交
  11. 28 11月, 2011 1 次提交
  12. 22 11月, 2011 1 次提交
  13. 01 11月, 2011 1 次提交
  14. 27 10月, 2011 1 次提交
  15. 05 9月, 2011 7 次提交