1. 13 Jul, 2020 3 commits
    • Marek Szyprowski's avatar
      drm: radeon: fix common struct sg_table related issues · 7b814900
      Marek Szyprowski authored
      The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function
      returns the number of the created entries in the DMA address space.
      However the subsequent calls to the dma_sync_sg_for_{device,cpu}() and
      dma_unmap_sg must be called with the original number of the entries
      passed to the dma_map_sg().
      
      struct sg_table is a common structure used for describing a non-contiguous
      memory buffer, used commonly in the DRM and graphics subsystems. It
      consists of a scatterlist with memory pages and DMA addresses (sgl entry),
      as well as the number of scatterlist entries: CPU pages (orig_nents entry)
      and DMA mapped pages (nents entry).
      
      It turned out that it was a common mistake to misuse nents and orig_nents
      entries, calling DMA-mapping functions with a wrong number of entries or
      ignoring the number of mapped entries returned by the dma_map_sg()
      function.
      
      To avoid such issues, lets use a common dma-mapping wrappers operating
      directly on the struct sg_table objects and use scatterlist page
      iterators where possible. This, almost always, hides references to the
      nents and orig_nents entries, making the code robust, easier to follow
      and copy/paste safe.
      Signed-off-by: default avatarMarek Szyprowski <m.szyprowski@samsung.com>
      Reviewed-by: default avatarChristian König <christian.koenig@amd.com>
      Link: https://patchwork.freedesktop.org/patch/371172/Signed-off-by: default avatarChristian König <christian.koenig@amd.com>
      7b814900
    • Marek Szyprowski's avatar
      drm: amdgpu: fix common struct sg_table related issues · 39913934
      Marek Szyprowski authored
      The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function
      returns the number of the created entries in the DMA address space.
      However the subsequent calls to the dma_sync_sg_for_{device,cpu}() and
      dma_unmap_sg must be called with the original number of the entries
      passed to the dma_map_sg().
      
      struct sg_table is a common structure used for describing a non-contiguous
      memory buffer, used commonly in the DRM and graphics subsystems. It
      consists of a scatterlist with memory pages and DMA addresses (sgl entry),
      as well as the number of scatterlist entries: CPU pages (orig_nents entry)
      and DMA mapped pages (nents entry).
      
      It turned out that it was a common mistake to misuse nents and orig_nents
      entries, calling DMA-mapping functions with a wrong number of entries or
      ignoring the number of mapped entries returned by the dma_map_sg()
      function.
      
      To avoid such issues, lets use a common dma-mapping wrappers operating
      directly on the struct sg_table objects and use scatterlist page
      iterators where possible. This, almost always, hides references to the
      nents and orig_nents entries, making the code robust, easier to follow
      and copy/paste safe.
      Signed-off-by: default avatarMarek Szyprowski <m.szyprowski@samsung.com>
      Reviewed-by: default avatarChristian König <christian.koenig@amd.com>
      Link: https://patchwork.freedesktop.org/patch/371142/Signed-off-by: default avatarChristian König <christian.koenig@amd.com>
      39913934
    • Andrey Lebedev's avatar
      drm/lima: Expose job_hang_limit module parameter · de489844
      Andrey Lebedev authored
      Some pp or gp jobs can be successfully repeated even after they time outs.
      Introduce lima module parameter to specify number of times a job can hang
      before being dropped.
      Signed-off-by: default avatarAndrey Lebedev <andrey@lebedev.lt>
      Signed-off-by: default avatarQiang Yu <yuq825@gmail.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20200619075900.3030696-1-andrey.lebedev@gmail.com
      de489844
  2. 12 Jul, 2020 2 commits
  3. 11 Jul, 2020 1 commit
  4. 10 Jul, 2020 21 commits
  5. 09 Jul, 2020 4 commits
  6. 08 Jul, 2020 3 commits
  7. 07 Jul, 2020 6 commits