dma_resv_describe() appends a line per each fence described. It looks like it is supposed to be adding a new line per fence to the output and that is how MSM and Etnaviv drivers use it. Update AMDGPU to match.
--- v2: moved the EOL before the dma_resv_describe() Signed-off-by: Michał Mirosław <[email protected]> --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c index 4dd7c712b8c3..258da62992b7 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c @@ -1692,12 +1692,13 @@ u64 amdgpu_bo_print_info(int id, struct amdgpu_bo *bo, struct seq_file *m) amdgpu_bo_print_flag(m, bo, VRAM_CONTIGUOUS); amdgpu_bo_print_flag(m, bo, VM_ALWAYS_VALID); amdgpu_bo_print_flag(m, bo, EXPLICIT_SYNC); + seq_puts(m, "\n"); + /* Add the gem obj resv fence dump*/ if (dma_resv_trylock(bo->tbo.base.resv)) { dma_resv_describe(bo->tbo.base.resv, m); dma_resv_unlock(bo->tbo.base.resv); } - seq_puts(m, "\n"); return size; } -- 2.47.3
